Managing HP Serviceguard A.11.20.20 for Linux, March 2014

Reconfiguration ” (page 242). 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 175)) 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
5. Distribute your changes to all nodes:
cmapplyconf -v -P pkg1.conf
6. If this is a legacy package, copy the package control script to all nodes that can run the
package.
7.8.3 Renaming or Replacing an External Script Used by a Running Package
In most cases, you can rename an external_script (page 190) while the package that uses it
is running, but you need to be careful; follow the instructions below.
1. Make a copy of the old script, save it with the new name, and edit the copy as needed.
2. Edit the package configuration file to use the new name.
3. Distribute the new script to all nodes that are configured for that package.
Make sure you place the new script in the correct directory with the proper file modes and
ownership.
4. Run cmcheckconf to validate the package configuration with the new external script.
CAUTION: If cmcheckconf fails, do not proceed to the next step until you have corrected
all the errors.
5. Run cmapplyconf on the running package.
This will stop any resources started by the original script, and then start any resources needed
by the new script.
6. You can now safely delete the original external script on all nodes that are configured to run
the package.
7.8.4 Reconfiguring a Package on a Halted Cluster
You can also make permanent changes in the package configuration while the cluster is not running.
Use the same steps as in “Reconfiguring a Package on a Running Cluster ”.
7.8 Reconfiguring a Package 241