Managing Serviceguard Fifteenth Edition, reprinted May 2008

Cluster and Package Maintenance
Reconfiguring a Cluster
Chapter 7 369
Example: Adding a Heartbeat LAN Suppose that a subnet
15.13.170.0 is shared by nodes ftsys9 and ftsys10 in a two-node
cluster cluster1, and you want to add it to the cluster configuration as a
heartbeat subnet. Proceed as follows.
Step 1. Run cmquerycl to get a cluster configuration template file that includes
networking information for interfaces that are available to be added to
the cluster configuration:
cmquerycl -c cluster1 -C clconfig.ascii
NOTE As of Serviceguard A.11.18, cmquerycl -c produces output that includes
commented-out entries for interfaces that are not currently part of the
cluster configuration, but are available.
The networking portion of the resulting clconfig.ascii file looks
something like this:
NODE_NAME ftsys9
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.3.17.18
#NETWORK_INTERFACE lan0
#STATIONARY_IP 15.13.170.18
NETWORK_INTERFACE lan3
# Possible standby Network Interfaces for lan1, lan0: lan2.
NODE_NAME ftsys10
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.3.17.19
#NETWORK_INTERFACE lan0
# STATIONARY_IP 15.13.170.19
NETWORK_INTERFACE lan3
# Possible standby Network Interfaces for lan0, lan1: lan2
Step 2. Edit the file to uncomment the entries for the subnet that is being added
(lan0 in this example), and change STATIONARY_IP to HEARTBEAT_IP: