HP Serviceguard for Linux Version A.11.19 Release Notes, April 2009

failure - set if the package halts because of the failure of a resource or service
it depends on
user_halt - set if the package is halted by a cmhaltpkg or cmhaltnode
command, or by corresponding actions in Serviceguard Manager
automatic_halt - set if the package is failed over automatically because of
the failure of a package it depends on, or is failed back to its primary node
automatically (failback_policy = automatic)
You can add custom code to the package to interrogate this variable, determine
why the package halted, and take appropriate action. For legacy packages, put
the code in the customer_defined_halt_cmds() function in the CUSTOMER
DEFINED FUNCTIONS area of the package control script; for modular packages,
put the code in the package’s external script (see About External Scripts” in
chapter 4 of Managing Serviceguard for Linux).
For example, if a database package is being halted by an administrator
(SG_HALT_REASON set to user_halt) you would probably want the custom
code to perform an orderly shutdown of the database; on the other hand, a
forced shutdown might be needed if SG_HALT_REASON is set to failure,
indicating thatthe package is halting abnormally (for example because
of the failure of a service it depends on).
cmviewcl -v -f line has a new field, last_halt_failed, that shows
whether the last invocation of the halt script of a package on a node succeeded or
failed. The value is no if the halt script ran successfully, or was not run since the
node joined the cluster, or was not run since the package was configured to run
on the node; otherwise it is yes.
You can use cmmakepkg -l (letter “l”) to see a list of all available modules,
including non-Serviceguard modules such as those supplied in the HP Toolkits.
You can use cmgetconf -P to write out the configuration information for all
packages in the cluster to a specified location; for example:
mkdir /tmp/pkgconfig
cmgetconf -c clusterA -P /tmp/pkgconfig
Alternate Quorum Server Subnet
Serviceguard 11.19 allows you to configure an alternate subnet for communication
between the cluster nodes and the Quorum Server. You can do this from the command
line or in Serviceguard Manager. For details and instructions, see the HP Serviceguard
Quorum Server Version A.04.00 Release Notes at http://docs.hp.com -> High
Availability -> Quorum Server.
What’s in this Release 25