HP-UX HB v13.00 Ch-15 - Serviceguard

HP-UX Handbook – Rev 13.00 Page 43 (of 108)
Chapter 15 Serviceguard
October 29, 2013
1. Use the following command to store a current copy of the existing cluster configuration
in a temporary file:
root@Node1:/ # cmgetconf -c cluster1 temp.ascii
2. Specify the new set of nodes to be configured (omitting nodeC) and generate a template
of the new configuration:
root@Node1:/ # cmquerycl -C cluster.ascii -c cluster1 -n Node1 –n Node2
3. Edit the file cluster.ascii to check the information about the nodes that remain in the
cluster.
4. Halt the node you are going to remove (nodeC in this example):
root@Node1:/ # cmhaltnode -f -v nodeC
5. Verify the new configuration:
root@Node1:/ # cmcheckconf -C cluster.ascii
6. From Node1 or Node2 apply the changes to the configuration and send the new binary
configuration file to all cluster nodes.:
root@Node1:/ # cmapplyconf -C cluster.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.
Some older versions of Serviceguard do not permit the admin to change any network-related
parameters while the cluster is running. A workaround to this is to remove the node from the
cluster and re-add it with new network parameters and configurations (assuming the subnets
match the other nodes in the cluster). In order to do this however, the node must also be
removed from package configurations.
Changing the LVM Configuration While the Cluster is Running
On newer versions of Serviceguard, you can change the cluster lock volume group or physical
volume configuration while the cluster is running.
If you are removing a volume group from the cluster configuration, make sure that you also
modify or delete any legacy package control script or modular package configuration file that