Managing Serviceguard A.11.20, March 2013

Table 15 Types of Changes to the Cluster Configuration (continued)
Required Cluster StateChange to the Cluster Configuration
Change the Quorum Configuration Online” (page 50), and the
NOTE below this table.
Cluster can be running. See “Changing the Cluster Networking
Configuration while the Cluster Is Running” (page 302).
Add NICs and their IP addresses, if any, to the cluster
configuration
Cluster can be running.Delete NICs and their IP addresses, if any, from the
cluster configuration
“Changing the Cluster Networking Configuration while the
Cluster Is Running” (page 302).
If removing the NIC from the system, see “Removing a LAN or
VLAN Interface from a Node” (page 305).
Cluster can be running. See “Changing the Cluster Networking
Configuration while the Cluster Is Running” (page 302).
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 302)
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.
Reconfigure IP addresses for a NIC used by the cluster
See “What You Must Keep in Mind” (page 303). Cluster can be
running throughout.
Cluster can be running.Change NETWORK_FAILURE_DETECTION parameter
(see “Monitoring LAN Interfaces and Detecting Failure:
Link Level” (page 70))
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 114) 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.Change capacity and weight parameters.
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).
NOTE: If you are using CVM or CFS, you cannot change MEMBER_TIMEOUT or
AUTO_START_TIMEOUT while the cluster is running. This is because they affect the aggregate
failover time, which is only reported to the CVM stack on cluster startup. You also cannot change
the quorum configuration while SG-CFS-pkg is running.
Previewing the Effect of Cluster Changes
Many variables affect package placement, including the availability of cluster nodes; the availability
of networks and other resources on those nodes; failover and failback policies; and package
weights, dependencies, and priorities, if you have configured them. You can preview the effect
on packages of certain actions or events before they actually occur.
For example, you might want to check to see if the packages are placed as you expect when the
cluster first comes up; or preview what happens to the packages running on a given node if the
node halts, or if the node is then restarted; or you might want to see the effect on other packages
Reconfiguring a Cluster 297