Managing Serviceguard Nineteenth Edition, Reprinted June 2011

cmgetconf -c <cluster_name> clconfig.ascii
Edit the clconfig.ascii file to include the new value for MAX_CONFIGURED_PACKAGES. Then
use the cmcheckconf command to verify the new configuration. Using the -k or -K option can
significantly reduce the response time.
Use cmapplyconf to apply the changes to the configuration and send the new configuration file
to all cluster nodes. Using -k or -K can significantly reduce the response time.
Configuring a Legacy Package
IMPORTANT: You can still create a new legacy package. If you are using a Serviceguard Toolkit
such as Serviceguard NFS Toolkit, consult the documentation for that product.
Otherwise, use this section to maintain and rework existing legacy packages rather than to create
new ones. The method described in “Configuring Packages and Their Services ” (page 216), is
simpler and more efficient for creating new packages, allowing packages to be built from smaller
modules, and eliminating the separate package control script and the need to distribute it manually.
If you decide to convert a legacy package to a modular package, see “Migrating a Legacy Package
to a Modular Package” (page 297). Do not attempt to convert Serviceguard Toolkit packages.
Creating or modifying a legacy package requires the following broad steps:
1. Generate the package configuration file
2. Edit the package configuration file
3. Generate the package control script
4. Edit the package control script
5. Distribute the control script to the cluster nodes
6. Apply the package configuration file
Each of these tasks is described in the subsections that follow.
Creating the Legacy Package Configuration
The package configuration process defines a set of application services that are run by the package
manager when a package starts up on a node in the cluster. The configuration also includes a
prioritized list of cluster nodes on which the package can run together with definitions of the
acceptable types of failover allowed for the package.
You can create a legacy package and its control script in Serviceguard Manager; use the Help
for detailed instructions. Otherwise, use the following procedure to create a legacy package.
1. Create a subdirectory for each package you are configuring in the /etc/cmcluster
directory:
mkdir /etc/cmcluster/pkg1
You can use any directory names you like.
2. Generate a package configuration file for each package, for example:
cmmakepkg -p /etc/cmcluster/pkg1/pkg1.conf
You can use any file name you like for the configuration file.
3. Edit each configuration file to specify package name, prioritized list of nodes (with 39 bytes
or less in the name), the location of the control script, and failover parameters for each
package. Include the data you recorded on the Package Configuration Worksheet.
Configuring a Package in Stages
It is a good idea to configure failover packages in stages, as follows:
1. Configure volume groups and mount points only.
2. Distribute the control script to all nodes.
Configuring a Legacy Package 289