Managing HP Serviceguard for Linux, Tenth Edition, September 2012

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 281).
Example: Deleting a Subnet Used by a Package
In this example, we are deleting subnet 15.13.170.0 (lan0). Proceed as follows.
1. Halt any package that uses this subnet and delete the corresponding networking
information (monitored_subnet, ip_subnet, ip_address; see the descriptions
for these parameters starting with monitored_subnet (page 212)).
See “Reconfiguring a Package on a Running Cluster ” (page 281) for more information.
2. Run cmquerycl to get the cluster configuration file:
cmquerycl -c cluster1 -C clconfig.conf
3. Comment out the network interfaces lan0 and lan3 and their network interfaces,
if any, on all affected nodes. The networking portion of the resulting 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
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 43) for important information.
270 Cluster and Package Maintenance