Managing HP Serviceguard for Linux Ninth Edition, April 2009

NODE_NAME ftsys9
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.3.17.18
# NETWORK_INTERFACE lan0
# STATIONARY_IP 15.13.170.18
# NETWORK_INTERFACE lan3
NODE_NAME ftsys10
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.3.17.19
# NETWORK_INTERFACE lan0
# STATIONARY_IP 15.13.170.19
# NETWORK_INTERFACE lan3
4. Verify the new configuration:
cmcheckconf -C clconfig.conf
5. Apply the changes to the configuration and distribute the new binary configuration
file to all cluster nodes.:
cmapplyconf -C clconfig.conf
Updating the Cluster Lock LUN Configuration Online
Proceed as follows.
IMPORTANT: See “What Happens when You Change the Quorum Configuration
Online” (page 48) for important information.
1. In the cluster configuration file, modify the value of CLUSTER_LOCK_LUN for
each node.
2. Run cmcheckconf to check the configuration.
3. Run cmapplyconf to apply the configuration.
If you need to replace the physical device, see “Replacing a Lock LUN” (page 273).
Changing MAX_CONFIGURED_PACKAGES
As of Serviceguard A.11.18, you can change MAX_CONFIGURED_PACKAGES while
the cluster is running. The default for MAX_CONFIGURED_PACKAGES is the maximum
number allowed in the cluster. You can use Serviceguard Manager to change
MAX_CONFIGURED_PACKAGES, or Serviceguard commands as shown below.
Use the cmgetconf command to obtain a current copy of the cluster's existing
configuration, for example:
cmgetconf -C <cluster_name> clconfig.conf
Edit the clconfig.conf file to include the new value for
MAX_CONFIGURED_PACKAGES. Then use the cmcheckconf command to verify
the new configuration. Using the -k or -K option can significantly reduce the response
time.
Reconfiguring a Cluster 251