Managing HP Serviceguard for Linux, Tenth Edition, September 2012

What You Can Do
You can do the following.
• Halt a node (cmhaltnode (1m) with the -d option) without causing its running
packages to halt or fail over.
Until you restart the node (cmrunnode (1m)) these packages are detached — not
being monitored by Serviceguard.
• Halt the cluster (cmhaltcl (1m) with the -d option) without causing its running
packages to halt.
Until you restart the cluster (cmruncl (1m)) these packages are detached — not
being monitored by Serviceguard.
• Halt a detached package, including instances of detached multi-node packages.
• Restart normal package monitoring by restarting the node (cmrunnode) or the
cluster (cmruncl).
Rules and Restrictions
The following rules and restrictions apply.
• All the nodes in the cluster must be running A.11.20.
• All the configured cluster nodes must be reachable by an available network (not
necessarily a network that is configured into the cluster).
• You must be root user (superuser) to halt or start a node or cluster with Live
Application Detach, and to halt a detached package.
• Live Application Detach is not supported for SGeRAC clusters configured with SLVM
or ASM.
• Live Application Detach is not supported for clusters using the Veritas Cluster Volume
Manager (CVM) or Cluster File System (CFS).
• Live Application Detach is supported only for modular failover packages and modular
multi-node packages.
◦ You cannot detach legacy packages, but you can halt them and then detach the
modular packages.
◦ You cannot use Live Application Detach if system multi-node packages (such as
SG-CFS-pkg) are configured in the cluster.
See Chapter 6 (page 199) for more information about package types.
Halting a Node or the Cluster while Keeping Packages Running 247