Managing Serviceguard 13th Edition, February 2007

Cluster and Package Maintenance
Reconfiguring a Cluster
Chapter 7330
1. Use the following command to store a current copy of the existing
cluster configuration in a temporary file:
# cmgetconf -c cluster1 temp.ascii
2. Specify the new set of nodes to be configured (omitting ftsys10) and
generate a template of the new configuration:
# cmquerycl -C clconfig.ascii -c cluster1 -n ftsys8 -n
ftsys9
3. Edit the file clconfig.ascii to check the information about the
nodes that remain in the cluster.
4. Halt the node you are going to remove (ftsys10 in this example):
# cmhaltnode -f -v ftsys10
5. Verify the new configuration:
# cmcheckconf -C clconfig.ascii
6. From ftsys8 or ftsys9. apply the changes to the configuration and
send the new binary configuration file to all cluster nodes.:
# cmapplyconf -C clconfig.ascii
NOTE If you are attempting to remove an unreachable node that has many
packages dependent on it, especially if the dependent packages use a
large number of EMS resources, 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.
Changing the LVM Configuration While the Cluster is Running
You can do this in Serviceguard Manager, or use HP-UX commands.
You cannot change the cluster lock volume group or physical volume
configuration while the cluster is running.