Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Cluster and Package Maintenance
Reconfiguring a Cluster
Chapter 7 265
Reconfiguring a Halted Cluster
You can make a permanent change in cluster configuration when the
cluster is halted. This procedure must be used for changes marked
“Cluster must not be running” in the table on page 264, 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 “Building an HA
Cluster Configuration” on page 141. You can use the cmgetconf
command to generate a template 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.
Reconfigure IP addresses for a
NIC used by the cluster
Must delete the interface from the
cluster configuration, reconfigure it,
then add it back into the cluster
configuration. See “What You Must
Keep in Mind” on page 269. Cluster
can be running throughout
Change
NETWORK_POLLING_INTERVAL
Cluster can be running.
Change HEARTBEAT_INTERVAL,
NODE_TIMEOUT,
AUTO_START_TIMEOUT
Cluster can be running.
Change Access Control Policy Cluster and package can be
running.
Table 7-1 Types of Changes to the Cluster Configuration (Continued)
Change to the Cluster
Configuration Required Cluster State