Managing HP Serviceguard A.11.20.00 for Linux, June 2012

IMPORTANT: For detailed information and examples, see the cmeval (1m) manpage.
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 Table 11, 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”
(page 121). You can use cmgetconf 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 cmruncl to start the cluster on all nodes, or on a subset of nodes.
Reconfiguring a Running Cluster
You can add new nodes to the cluster configuration or delete nodes from the cluster configuration
while the cluster is up and running. Note the following, however:
• You cannot remove an active node from the cluster. You must halt the node first.
• The only configuration change allowed while a node is unreachable (for example, completely
disconnected from the network) is to delete the unreachable node from the cluster configuration.
If there are also packages that depend upon that node, the package configuration must also
be modified to delete the node. This all must be done in one configuration request
(cmapplyconf command).
• The access control list for the cluster can be changed while the cluster is running.
Changes to the package configuration are described in a later section.
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.
NOTE: Before you start, make sure you have configured access to ftsys10 as described under
“Configuring Root-Level Access” (page 122).
1. Use the following command to store a current copy of the existing cluster configuration in a
temporary file in case you need to revert to it:
cmgetconf -C temp.conf
2. Specify a new set of nodes to be configured and generate a template of the new configuration
(all on one line):
cmquerycl -C clconfig.conf -c cluster1 -n ftsys8 -n ftsys9 -n ftsys10
3. Edit clconfig.conf to check the information about the new node.
4. Verify the new configuration:
cmcheckconf -C clconfig.conf
5. Apply the changes to the configuration and send the new binary configuration file to all cluster
nodes:
cmapplyconf -C clconfig.conf
Reconfiguring a Cluster 205