Managing HP Serviceguard for Linux, Tenth Edition, September 2012

Table 9 Types of Changes to the Cluster Configuration (continued)
Required Cluster StateChange to the Cluster Configuration
Cluster can be running. See “Updating the Cluster Lock
LUN Configuration Online” (page 270) and“What
Change Cluster Lock Configuration (lock LUN)
Happens when You Change the Quorum Configuration
Online” (page 43).
Cluster can be running. See “Changing the Cluster
Networking Configuration while the Cluster Is Running”
(page 267).
Add NICs and their IP addresses to the cluster
configuration
Cluster can be running. See“Changing the Cluster
Networking Configuration while the Cluster Is Running”
(page 267).
Delete NICs and their IP addresses, from the
cluster configuration
Cluster can be running. See “Changing the Cluster
Networking Configuration while the Cluster Is Running”
(page 267).
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 267)
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
Reconfigure IP addresses for a NIC used by the
cluster
configuration. See “What You Must Keep in Mind”
(page 267). Cluster can be running throughout.
Cluster can be running.Change NETWORK_POLLING_INTERVAL
Cluster can be running. See the entries for these
parameters under “Cluster Configuration Parameters ”
(page 103)for more information.
Change IP Monitor parameters: SUBNET,
IP_MONITOR, POLLING TARGET
Cluster can be running.Change MEMBER_TIMEOUT and
AUTO_START_TIMEOUT
Cluster and package can be running.Change Access Control Policy
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 if another, currently disabled, package is enabled, or if a
Reconfiguring a Cluster 261