Managing Serviceguard Sixteenth Edition, March 2009

5. Verify the new configuration:
cmcheckconf -C clconfig.ascii
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.ascii
NOTE: If you are trying to remove an unreachable node on which many packages
are configured to run (especially if the 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 Cluster Networking Configuration while the Cluster Is Running
What You Can Do
Online operations you can perform include:
• Add a network interface with its HEARTBEAT_IP or STATIONARY_IP.
• Add a standby interface.
• Delete a network interface with its HEARTBEAT_IP or STATIONARY_IP.
• Delete a standby interface.
• 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 the NETWORK_FAILURE_DETECTION parameter.
• Change the NETWORK_AUTO_FAILBACK parameter.
• Change IP Monitor parameters: SUBNET, IP_MONITOR, POLLING TARGET; see
the entries for these parameters under “Cluster Configuration Parameters ”
(page 138) for more information.
• A combination of any of these in one transaction (cmapplyconf), given the
restrictions below.
Reconfiguring a Cluster 331