Managing Serviceguard Eighteenth Edition, September 2010

Table 7-2 Types of Changes to the Cluster Configuration (continued)
Required Cluster StateChange to the Cluster Configuration
Cluster can be running.
“Changing the Cluster Networking Configuration while
the Cluster Is Running” (page 367).
If removing the NIC from the system, see “Removing a
LAN or VLAN Interface from a Node” (page 372).
Delete NICs and their IP addresses, if any, from
the cluster configuration
Cluster can be running. See “Changing the Cluster
Networking Configuration while the Cluster Is
Running” (page 367).
Change the designation of an existing interface
from HEARTBEAT_IP to STATIONARY_IP, or
vice versa
Cluster can be running. See “Changing the Cluster
Networking Configuration while the Cluster Is
Running” (page 367)
Change an interface from IPv4 to IPv6, or vice
versa
Must delete the interface from the cluster configuration,
reconfigure it, then add it back into the cluster
configuration. See “What You Must Keep in Mind”
(page 368). Cluster can be running throughout.
Reconfigure IP addresses for a NIC used by the
cluster
Cluster can be running.Change NETWORK_FAILURE_DETECTION
parameter (see “Monitoring LAN Interfaces
and Detecting Failure: Link Level” (page 92))
Cluster can be running.Change NETWORK_AUTO_FAILBACK
parameter
Cluster can be running.Change NETWORK_POLLING_INTERVAL
Cluster can be running. See the entries for these
parameters under “Cluster Configuration Parameters
” (page 143) for more information.
Change IP Monitor parameters: SUBNET,
IP_MONITOR, POLLING TARGET
Cluster can be running, except in CVM environment;
see the NOTE below this table.
Change MEMBER_TIMEOUT and
AUTO_START_TIMEOUT
Cluster and package can be running.Change Access Control Policy
Cluster can be running.
A change that would cause a running package to fail
will trigger a warning, giving you a chance to cancel
(unless you use cmapplyconf -f).
Change capacity and weight parameters.
360 Cluster and Package Maintenance