Managing Serviceguard 14th Edition, June 2007

Cluster and Package Maintenance
Reconfiguring a Cluster
Chapter 7 351
• You cannot delete an active volume group from the cluster
configuration. You must halt any package that uses the volume
group and ensure that the volume is inactive before deleting it.
• 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).
Changes to the package configuration are described in a later section.
Adding Nodes to the Cluster While the Cluster is Running
You can use Serviceguard Manager to add nodes to a running cluster, or
use Serviceguard commands as in the example below.
In this example, nodes ftsys8 and ftsys9 are already configured in a
running cluster named cluster1, and you are adding node ftsys10.
Step 1. Use the following command to store a current copy of the existing cluster
configuration in a temporary file:
cmgetconf -c cluster1 temp.ascii
Step 2. Specify a new set of nodes to be configured and generate a template of
the new configuration. Specify the node name (39 bytes or less) without
its full domain name; for example, ftsys8 rather than
ftsys8.cup.hp.com:
cmquerycl -C clconfig.ascii -c cluster1 \
-n ftsys8 -n ftsys9 -n ftsys10
Step 3. Open clconfig.ascii in an editor and check that the information about
the new node is what you want.
Step 4. Verify the new configuration:
cmcheckconf -C clconfig.ascii
Step 5. Apply the changes to the configuration and distribute the new binary
configuration file to all cluster nodes:
cmapplyconf -C clconfig.ascii