Managing HP Serviceguard for Linux Ninth Edition, April 2009

NOTE: Before you start, make sure you have configured access to ftsys10 as
described under “Configuring Root-Level Access” (page 149).
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
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 147)) 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 233).
• 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 234).
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.
246 Cluster and Package Maintenance