HP-UX HB v13.00 Ch-15 - Serviceguard

HP-UX Handbook – Rev 13.00 Page 38 (of 108)
Chapter 15 Serviceguard
October 29, 2013
Successfully halted all nodes specified.
Halt operation complete.
If the user only wants to shutdown a subset of daemons, the cmhaltnode command should be
used instead.
Joining a node to a running cluster
If a node is not running Serviceguard, and it’s sister nodes are, it can be joined to the cluster
using cmrunnode.
Example:
root@Node1:/# cmrunnode Node2
cmrunnode: Validating network configuration...
cmrunnode: Network validation complete
Waiting for nodes to join ..... done
Cluster successfully formed.
Check the syslog files on all nodes in the cluster to verify that no warnings
occurred during startup.
Starting a node will not cause any active packages to move to the node unless
FAILBACK_POLICY is configured to AUTOMATIC in the package. However, if a package is
down, has its AUTO_RUN and Node_switching enabled for that node, that package will
automatically start on the joining node.
Cmrunnode causes a node to join a running cluster. The command will time out after the
AUTO_START_TIMEOUT (configured in the cluster ASCII file - default 10 minutes) window
expires. If AUTOSTART_CMCLD=1 in /etc/rc.config.d/cmcluster, the node will perform a
cmrunnode when it enters run level 3. If all nodes are executing cmrunnode within the
AUTO_START_TIMEOUT window, a cluster will form.
Halting Serviceguard on a node
cmhaltnode causes a node to halt its packages and cluster daemons and remove itself from the
cluster. Cmhaltnode can force packages to adoptive nodes.
root@Node1:/# cmhaltnode -v Node2 # halting the other node
Disabling all packages from starting on nodes to be halted.
Disabling all packages from running on Node2.
Warning: Do not modify or enable packages until the halt operation is
completed.
Waiting for nodes to halt .... done
Successfully halted all nodes specified.
Halt operation complete.
If no node name is specified, the cluster daemon running on the local node will be halted and