Managing HP Serviceguard for Linux, Sixth Edition, August 2006

Cluster and Package Maintenance
Managing the Cluster and Nodes
Chapter 7 247
Reconfiguring a Halted Cluster
You can also make a permanent change in cluster configuration when the
cluster is halted. This procedure must be used for changes to the quorum
server configuration, changes in timing parameters, and changes to the
Maximum Number of Packages parameter, but it can be used for any
other cluster configuration changes as well.
Use the following steps:
1. Halt the cluster on all nodes.
2. On one node, reconfigure the cluster as described in the chapter
“Building an HA Cluster Configuration.” You can use the cmgetconf
command to generate an ASCII file, which you then edit.
3. Make sure that all nodes listed in the cluster configuration file are
powered up and accessible. Use cmapplyconf to copy the binary
cluster configuration file to all nodes. This file overwrites any
previous version of the binary cluster configuration file.
4. Use the cmruncl command to start the cluster on all nodes or on a
subset of nodes, as desired.
Changing MAX_CONFIGURED_PACKAGES
Use the cmgetconf command to obtain a current copy of the cluster's
existing configuration. Example:
# cmgetconf -C clconfig.ascii
Edit the clconfig.ascii file to include the desired value for
MAX_CONFIGURED_PACKAGES. Then use the cmcheckconf command to
verify the new configuration. Use the cmapplyconf command to apply
the changes to the configuration and send the new configuration file to
all cluster nodes.
Automatically Restarting the Cluster
You can configure your cluster to automatically restart after an event,
such as a long-term power failure, which brought down all nodes in the
cluster. This is done by setting AUTOSTART_CMCLD to 1 in the
$SGAUTOSTART file.