Managing HP Serviceguard for Linux, Sixth Edition, August 2006

Cluster and Package Maintenance
Reconfiguring a Running Cluster
Chapter 7 249
The following sections describe how to perform dynamic reconfiguration
tasks.
Adding Nodes to the Configuration While the Cluster
is Running
Use the following procedure to add a node. For this example, nodes ftsys8
and ftsys9 are already configured in a running cluster named cluster1,
and you are adding node ftsys10.
1. Use the following command to store a current copy of the existing
cluster configuration in a temporary file:
# cmgetconf -C temp.ascii
2. Specify a new set of nodes to be configured and generate a template
of the new configuration:
# cmquerycl -C clconfig.ascii -c cluster1 \
-n ftsys8 -n ftsys9 -n ftsys10
3. Edit the file clconfig.ascii to check the information about the new
node.
4. Verify the new configuration:
# cmcheckconf -C clconfig.ascii
5. Apply the changes to the configuration and send the new binary
configuration file to all cluster nodes:
# cmapplyconf -C clconfig.ascii
Use cmrunnode to start the new node, and, if desired, set the
AUTOSTART_CMCLD parameter to 1 in the $SGAUTOSTART file to enable the
new node to join the cluster automatically each time it reboots.
Change IP addresses for
heartbeats or monitored
subnets
Cluster must not be running.
Table 7-2 Types of Changes to Permanent Cluster Configuration
Change to the Cluster
Configuration Required Cluster State