Managing HP Serviceguard A.11.20.10 for Linux, December 2012

7.7.5.3.1 Control-script entries for nodeA and nodeB
IP[0] = 15.244.65.82
SUBNET[0] 15.244.65.0
IP[1] = 15.244.65.83
SUBNET[1] 15.244.65.0
7.7.5.3.2 Control-script entries for nodeC and nodeD
IP[0] = 15.244.56.100
SUBNET[0] = 15.244.56.0
IP[1] = 15.244.56.101
SUBNET[1] =15.244.56.0
7.8 Reconfiguring a Package
You reconfigure a package in much the same way as you originally configured it; for modular
packages, see Chapter 6: “Configuring Packages and Their Services ” (page 163); for older
packages, see “Configuring a Legacy Package” (page 225).
The cluster can be either halted or running during package reconfiguration, and in some cases
the package itself can be running; the types of change you can make and the times when they
take effect depend on whether the package is running or not.
If you reconfigure a package while it is running, it is possible that the package could fail later,
even if the cmapplyconf succeeded.
For example, consider a package with two volume groups. When this package started, it activated
both volume groups. While the package is running, you could change its configuration to list only
one of the volume groups, and cmapplyconf would succeed. If you issue cmhaltpkg command,
however, the halt would fail. The modified package would not deactivate both of the volume groups
that it had activated at startup, because it would only see the one volume group in its current
configuration file.
For more information, see “Allowable Package States During Reconfiguration ” (page 234).
7.8.1 Migrating a Legacy Package to a Modular Package
The Serviceguard command cmmigratepkg automates the process of migrating legacy packages
to modular packages as far as possible. Many, but not all, packages can be migrated in this way;
for details, see the white paper Package Migration from Legacy Style to Modular Style at http://
www.hp.com/go/hpux-serviceguard-docs (Select HP Serviceguard -> White Papers).
Do not attempt to convert Serviceguard Toolkit packages.
NOTE: The cmmigratepkg command requires Perl version 5.8.3 or higher on the system on
which you run the command.
7.8.2 Reconfiguring a Package on a Running Cluster
You can reconfigure a package while the cluster is running, and in some cases you can reconfigure
the package while the package itself is running; see “Allowable Package States During
Reconfiguration ” (page 234). You can do this in Serviceguard Manager (for legacy packages), or
use Serviceguard commands.
To modify the package with Serviceguard commands, use the following procedure (pkg1 is used
as an example):
1. Halt the package if necessary:
cmhaltpkg pkg1
232 Cluster and Package Maintenance