Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Cluster and Package Maintenance
Reconfiguring a Cluster
Chapter 7 267
NOTE Before you start, make sure you have configured access to ftsys10 as
described under “Configuring Root-Level Access” on page 144.
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.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 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 you so decide, set the
AUTOSTART_CMCLD parameter to 1 in the $SGAUTOSTART file (see
“Understanding the Location of Serviceguard Files” on page 142) 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” on page 258.
• 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” on page 259.