Managing HP Serviceguard A.11.20.00 for Linux, June 2012

CAUTION: Serviceguard does not check LVM volume groups, mount points, and relocatable
IP addresses when re-attaching packages.
• cmviewcl (1m) reports the status and state of detached packages as detached.
This is true even if a problem has occurred since the package was detached and some or all
of the package components are not healthy or not running.
• Because Serviceguard assumes that a detached package has remained healthy, the package
is considered to be UP for dependency purposes.
This means, for example, that if you halt node1, detaching pkgA, and pkgB depends on
pkgA to be UP on ANY_NODE, pkgB on node2 will continue to run (or can start) while pkgA
is detached. See “About Package Dependencies” (page 100) for more information about
dependencies.
• As always, packages cannot start on a halted node or in a halted cluster.
• When a node having detached packages is back up after a reboot they can:
Rejoin the cluster and the detached packages can move to "running" or "failed" state. If
the detached packages are moved to running state, then they must be halted and rerun
as they may have several inconsistencies post reboot.
◦
◦ Not rejoin the cluster and the detached packages remain detached. Such packages must
be halted and rerun to avoid any inconsistencies that can be caused due to the reboot.
• If you halt a package and disable it before running cmhaltcl -d to detach other packages
running in the cluster, auto_run will be automatically re-enabled for this package when the
cluster is started again, forcing the package to start.
To prevent this behavior and keep the package halted and disabled after the cluster restarts,
change auto_run to no in the package configuration file (page 160), and re-apply the
package, before running cmhaltcl -d.
Halting a Node and Detaching its Packages
To halt a node and detach its packages, proceed as follows:
1. Make sure that the conditions spelled out under “Rules and Restrictions” (page 192) are met.
2. Halt any packages that do not qualify for Live Application Detach, such as legacy and system
multi-node packages.
For example:
cmhaltpkg -n node1 legpak1 legpak2
NOTE: If you do not do this, the cmhaltnode in the next step will fail.
3. Halt the node with the -d (detach) option:
cmhaltnode -d node1
NOTE: -d and -f are mutually exclusive. See cmhaltnode (1m) for more information.
To re-attach the packages, restart the node:
cmrunnode -n node1
Halting a Detached Package
To halt a package that is detached on node1, proceed as follows:
1. Log in as superuser on another node that is still running in the cluster.
194 Cluster and Package Maintenance