Managing Serviceguard Sixteenth Edition, March 2009

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:
NODE_NAME ftsys9
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.3.17.18
NETWORK_INTERFACE lan0
HEARTBEAT_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
HEARTBEAT_IP 15.13.170.19
NETWORK_INTERFACE lan3
# Possible standby Network Interfaces for lan0, lan1: lan2
3. Verify the new configuration:
cmcheckconf -C clconfig.ascii
4. Apply the changes to the configuration and distribute the new binary configuration
file to all cluster nodes:
cmapplyconf -C clconfig.ascii
If you were configuring the subnet for data instead, and wanted to add it to a package
configuration, you would now need to:
1. Halt the package
2. Add the new networking information to the package configuration file
3. In the case of a legacy package, add the new networking information to the package
control script if necessary
4. Apply the new package configuration, and redistribute the control script if
necessary.
For more information, see “Reconfiguring a Package on a Running Cluster ” (page 350).
Example: Deleting a Subnet Used by a Package
In this example, we are deleting subnet 15.13.170.0 (lan0). This will also mean deleting
lan3, which is a standby for lan0 and not shared by any other primary LAN. Proceed
as follows.
1. Halt any package that uses this subnet and delete the corresponding networking
information: monitored_subnet, ip_subnet, ip_address (page 270).
See “Reconfiguring a Package on a Running Cluster ” (page 350) for more
information.
334 Cluster and Package Maintenance