Managing HP Serviceguard A.12.00.00 for Linux, June 2014

By default, cmruncl will check the networks. Serviceguard will probe the actual network
configuration with the network information in the cluster configuration. If you do not need this
validation, use cmruncl -v -w none instead, to turn off validation and save time
2. When the cluster has started, make sure that cluster components are operating correctly:
cmviewcl -v
Make sure that all nodes and networks are functioning as expected. For more information,
refer to the chapter on “Cluster and Package Maintenance.”
3. Verify that nodes leave and enter the cluster as expected using the following steps:
• Halt the cluster. You can use Serviceguard Manager or the cmhaltnode command.
• Check the cluster membership to verify that the node has left the cluster. You can use the
Serviceguard Manager main page or the cmviewcl command.
• Start the node. You can use Serviceguard Manager or the cmrunnode command.
• Verify that the node has returned to operation. You can use Serviceguard Manager or
the cmviewcl command again.
4. Bring down the cluster. You can use Serviceguard Manager or the cmhaltcl -v -f
command.
See the manpages for more information about these commands. See Chapter 10: “Troubleshooting
Your Cluster” (page 269) for more information about cluster testing.
5.3.2 Setting up Autostart Features
Automatic startup is the process in which each node individually joins a cluster; Serviceguard
provides a startup script to control the startup process. If a cluster already exists, the node attempts
to join it; if no cluster is running, the node attempts to form a cluster consisting of all configured
nodes. Automatic cluster start is the preferred way to start a cluster. No action is required by the
system administrator.
There are three cases:
• The cluster is not running on any node, all cluster nodes must be reachable, and all must be
attempting to start up. In this case, the node attempts to form a cluster consisting of all
configured nodes.
• The cluster is already running on at least one node. In this case, the node attempts to join that
cluster.
• Neither is true: the cluster is not running on any node, and not all the nodes are reachable
and trying to start. In this case, the node will attempt to start for the AUTO_START_TIMEOUT
period. If neither of these things becomes true in that time, startup will fail.
To enable automatic cluster start, set the flag AUTOSTART_CMCLD to 1 in the $SGAUTOSTARTfile
($SGCONF/cmcluster.rc) on each node in the cluster; the nodes will then join the cluster at
boot time.
Here is an example of the $SGAUTOSTART file:
SGAUTOSTART=/usr/local/cmcluster/conf/cmcluster.rc
#*************************** CMCLUSTER *************************
# Highly Available Cluster configuration
#
# @(#) $Revision: 82.2 $
#
#
# AUTOSTART_CMCLD
#
# Automatic startup is the process in which each node individually
# joins a cluster. If a cluster already exists, the node attempts
176 Building an HA Cluster Configuration