Managing HP Serviceguard for Linux Ninth Edition, April 2009

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://docs.hp.com -> High Availability ->
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.
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 264). 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
See “Allowable Package States During Reconfiguration ”to determine whether
this step is needed.
2. If it is not already available, you can obtain a copy of the package's configuration
file by using the cmgetconf command, specifying the package name.
cmgetconf -p pkg1 pkg1.conf
3. Edit the package configuration file.
IMPORTANT: Restrictions on package names, dependency names, and service
names have become more stringent as of A.11.18. Packages that have or contain
names that do not conform to the new rules (spelled out under “package_name”
(page 196)) will continue to run, but if you reconfigure these packages, you will
need to change the names that do not conform; cmcheckconf and cmapplyconf
will enforce the new rules.
4. Verify your changes as follows:
cmcheckconf -v -P pkg1.conf
262 Cluster and Package Maintenance