Managing Serviceguard A.11.20, March 2013

that can be made online to the modular CFS package parameters, see “Online reconfiguration of
modular CFS package parameters” (page 215).
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 319) 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
Modular style of packaging in Serviceguard allows you to consolidate multiple packages into a
single package providing easy administration of the package. It offers flexibility and can be
managed better compared to legacy packages. For more information about modular packages,
see the following sections:
• “Modular CFS packages v/s Legacy CFS packages” (page 204)
• “Managing Disk Groups and Mount Points Using Modular Packages” (page 209)
• “Creating Modular Disk Group and Mount Point Packages” (page 210)
• CVM 4.1 and later with CFS section under “Planning Veritas Cluster Volume Manager (CVM)
and Cluster File System (CFS)” (page 132)
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.
You can use the cmeasymigrate(1m) command to convert Serviceguard legacy toolkit packages
to modular packages. Using this command you can also migrate or consolidate multiple
legacy/modular CFS packages into a single modular package.
For details, see the white paper Migrating Packages from Legacy Style to Modular Style at http://
www.hp.com/go/hpux-serviceguard-docs and the man pages.
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.
For migrating legacy CFS packages to modular CFS packages, see “Migrating from Legacy CFS
Packages to Modular CFS Packages ” (page 383).
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):
316 Cluster and Package Maintenance