Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Cluster and Package Maintenance
Reconfiguring a Cluster
Chapter 7 269
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.
Changing the Cluster Networking Configuration
while the Cluster Is Running
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 the designation of an existing interface from HEARTBEAT_IP
to STATIONARY_IP, or vice versa.
Change the NETWORK_POLLING_INTERVAL.
A combination of any of these in one transaction (cmapplyconf),
given the restrictions below.
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.