Managing Serviceguard A.11.20, March 2013

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 319) 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.
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 238)) 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.ascii
6. If this is a legacy package, copy the package control script to all nodes that can run the
package.
Renaming or Replacing an External Script Used by a Running Package
In most cases, you can rename an external_script (page 256) 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.
Reconfiguring a Package on a Halted Cluster
You can also make permanent changes in package configuration while the cluster is not running.
Use the same steps as in “Reconfiguring a Package on a Running Cluster ” (page 316).
Reconfiguring a Package 317