Managing Serviceguard Sixteenth Edition, March 2009

NOTE: Special considerations apply in the case of the root volume group:
• If the root volume group is mirrored using MirrorDisk/UX, include it in the
custom_vg_activation function so that any stale extents in the mirror will be
re-synchronized.
• Otherwise, the root volume group does not need to be included in the
custom_vg_activation function, because it is automatically activated before
the/etc/lvmrc file is used at boot time.
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. 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 the other two cases becomes true
in that time, startup will fail.
To enable automatic cluster start, set the flag AUTOSTART_CMCLD to 1 in the
/etc/rc.conf.d/cmcluster file on each node in the cluster; the nodes will then
join the cluster at boot time.
Here is an example of the /etc/rc.conf.d/cmcluster file:
#************************ CMCLUSTER ************************
# Highly Available Cluster configuration
#
# @(#) $Revision: 72.2 $
#
# AUTOSTART_CMCLD: If set to 1, the node will attempt to
# join it's CM cluster automatically when
# the system boots.
# If set to 0, the node will not attempt
# to join it's CM cluster.
#
AUTOSTART_CMCLD=1
248 Building an HA Cluster Configuration