Managing HP Serviceguard A.11.20.10 for Linux, December 2012

1. Use the following command to store a current copy of the existing cluster configuration in a
temporary file:
cmgetconf -c cluster1 temp.conf
2. Specify the new set of nodes to be configured (omitting ftsys10) and generate a template
of the new configuration:
cmquerycl -C clconfig.conf -c cluster1 -n ftsys8 -n ftsys9
3. Edit the file clconfig.conf to check the information about the nodes that remain in the
cluster.
4. Halt the node you are going to remove (ftsys10in this example):
cmhaltnode -f -v ftsys10
5. Verify the new configuration:
cmcheckconf -C clconfig.conf
6. From ftsys8 or ftsys9, apply the changes to the configuration and distribute the new
binary configuration file to all cluster nodes.:
cmapplyconf -C clconfig.conf
NOTE: If you are trying to remove an unreachable node on which many packages are configured
to run, 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.
7.6.4 Changing the Cluster Networking Configuration while the Cluster Is Running
7.6.4.1 What You Can Do
Online operations you can perform include:
• Add a network interface and its HEARTBEAT_IP or STATIONARY_IP.
• Delete a network interface and its HEARTBEAT_IP or STATIONARY_IP.
• Change a HEARTBEAT_IP or STATIONARY_IP interface from IPv4 to IPv6, or vice versa.
• Change the designation of an existing interface from HEARTBEAT_IP to STATIONARY_IP,
or vice versa.
• Change the NETWORK_POLLING_INTERVAL.
• Change IP Monitor parameters: SUBNET, IP_MONITOR, POLLING TARGET; see the entries
for these parameters under“Cluster Configuration Parameters ” (page 86) for more information.
• A combination of any of these in one transaction (cmapplyconf), given the restrictions below.
7.6.4.2 What You Must Keep in Mind
The following restrictions apply:
• You must not change the configuration of all heartbeats at one time, or change or delete the
only configured heartbeat.
At least one working heartbeat must remain unchanged.
• You cannot add interfaces or modify their characteristics unless those interfaces, and all other
interfaces in the cluster configuration, are healthy.
There must be no bad NICs or non-functional or locally switched subnets in the configuration,
unless you are deleting those components in the same operation.
7.6 Reconfiguring a Cluster 221