Managing Serviceguard Fifteenth Edition, reprinted May 2008

Cluster and Package Maintenance
Reconfiguring a Cluster
Chapter 7 367
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 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.
• 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, preferably with a standby, must
remain unchanged.
• In a CVM configuration, you can add and delete only data LANs and
IP addresses.
You cannot change the heartbeat configuration while a cluster that
uses CVM is running.
• 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.
• You cannot change the designation of an existing interface from
HEARTBEAT_IP to STATIONARY_IP, or vice versa, without also making
the same change to all peer network interfaces on the same subnet
on all other nodes in the cluster.