Managing HP Serviceguard A.11.20.00 for Linux, June 2012

Use cmrunnode to start the new node, and, if you so decide, set the AUTOSTART_CMCLD
parameter to 1 in the $SGAUTOSTART file (see “Understanding the Location of Serviceguard Files”
(page 121)) to enable the new node to join the cluster automatically each time it reboots.
Removing Nodes from the Cluster while the Cluster Is Running
You can use Serviceguard Manager to delete nodes, or Serviceguard commands as shown below.
The following restrictions apply:
• The node must be halted. See “Removing Nodes from Participation in a Running Cluster”
(page 191).
• If the node you want to delete is unreachable (disconnected from the LAN, for example), you
can delete the node only if there are no packages which specify the unreachable node. If
there are packages that depend on the unreachable node, halt the cluster; see “Halting the
Entire Cluster ” (page 191).
Use the following procedure to delete a node with Serviceguard commands. In this example, nodes
ftsys8, ftsys9 and ftsys10 are already configured in a running cluster named cluster1,
and you are deleting node ftsys10.
NOTE: If you want to remove a node from the cluster, run the cmapplyconf command from
another node in the same cluster. If you try to issue the command on the node you want removed,
you will get an error message.
1. Use the following command to store a current copy of the existing cluster configuration in a
temporary file:
cmgetconf -c cluster1 temp.conf
2. Specify the new set of nodes to be configured (omitting ftsys10) and generate a template
of the new configuration:
cmquerycl -C clconfig.conf -c cluster1 -n ftsys8 -n ftsys9
3. Edit the file clconfig.conf to check the information about the nodes that remain in the
cluster.
4. Halt the node you are going to remove (ftsys10in this example):
cmhaltnode -f -v ftsys10
5. Verify the new configuration:
cmcheckconf -C clconfig.conf
6. From ftsys8 or ftsys9, apply the changes to the configuration and distribute the new
binary configuration file to all cluster nodes.:
cmapplyconf -C clconfig.conf
NOTE: If you are trying to remove an unreachable node on which many packages are configured
to run, you may see the following message:
The configuration change is too large to process while the cluster is running.
Split the configuration change into multiple requests or halt the cluster.
In this situation, you must halt the cluster to remove the node.
206 Cluster and Package Maintenance