Managing Serviceguard Eighteenth Edition, September 2010

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 386).
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 296).
See “Reconfiguring a Package on a Running Cluster ” (page 386) for more
information.
2. Run cmquerycl to get the cluster configuration file:
cmquerycl -c cluster1 -C clconfig.ascii
3. Comment out the network interfaces lan0 and lan3 and their network interfaces,
if any, on all affected nodes. The networking portion of the
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
Reconfiguring a Cluster 371