Managing Serviceguard Nineteenth Edition, Reprinted June 2011

SUBNET[1] = 15.244.56.0
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 216); for older
packages, see “Configuring a Legacy Package” (page 289).
The cluster, and the package itself, can be either halted or running during package reconfiguration;
see “Reconfiguring a Package on a Running Cluster ” (page 297). The types of changes that can
be made and the times when they take effect depend on whether the package is running or not;
see “Allowable Package States During Reconfiguration ” (page 300).
CAUTION: Be extremely cautious about changing a package's configuration while the package
is running.
If you reconfigure a package online (by executing cmapplyconf on a package while the package
itself is running) it is possible that the package will fail, even if the cmapplyconf succeeds,
validating the changes with no errors.
For example, if a file system is added to the package while the package is running, cmapplyconf
does various checks to verify that the file system and its mount point exist. But the actual file system
check and mount of the file system can only be done after cmapplyconf succeeds; and if one of
these tasks fails in a running package, the entire package will fail.
As a rule of thumb, configuration changes which would have prevented a package that was
changed offline from starting, will very probably cause the package to fail if the changes are made
while the package is running. Be particularly cautious about adding, removing, or changing logical
volumes, volume groups, or file systems.
For any change you intend to make, read the information under “Allowable Package States During
Reconfiguration ” (page 300) carefully, and try out changes on a non-production package before
applying them to a running production package.
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 Migrating Packages from Legacy Style to Modular Style at http://
www.hp.com/go/hpux-serviceguard-docs.
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. It should already be on the system as part of the HP-UX base product.
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. 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):
Reconfiguring a Package 297