HP Effective Use of cmapplyconf in Service Guard for CFS Package Management

that can be made online to the modular CFS package parameters, see “Online reconfiguration of modular CFS package parameters” (page 211).

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 314) 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.

For migrating legacy CFS packages to modular CFS packages, see “Migrating from Legacy CFS Packages to Modular CFS Packages ” (page 377).

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):

1.Halt the package if necessary: cmhaltpkg pkg1

CAUTION: Make sure you read and understand the information and caveats under“Allowable Package States During Reconfiguration ” (page 314) before you decide to reconfigure a running package.

2.If it is not already available, 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.

Reconfiguring a Package 311