Managing Serviceguard 11th Edition, Version A.11.16, Second Printing June 2004

Configuring Packages and Their Services
Creating the Package Configuration
Chapter 6 245
If you want, you can configure your control script yourself. This may be
necessary if you do not use a standard control script. However, once you
edit a control script yourself, Serviceguard Manager will never be able to
see or modify it again. If you choose to edit the control script, you must
also distribute it yourself.
See “Configuring in Stages” on page 245.
Using Serviceguard Commands to Configure a
Package
Use the following procedure to create packages by editing and processing
a package configuration file.
1. First, 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 wish.
2. Next, generate a package configuration template for the package:
# cmmakepkg -p /etc/cmcluster/pkg1/pkg1.config
You can use any file names you wish for the ASCII templates.
3. Edit these template files to specify package name, prioritized list of
nodes (with 31 bytes or less in the name), the location of the control
script, and failover parameters for each package. Include the data
recorded on the Package Configuration Worksheet.
Configuring in Stages
It is recommended you configure packages on the cluster in stages, as
follows:
1. Configure volume groups and mount points only.
2. Apply the configuration.
3. Distribute the control script to all nodes.
4. Run the package and ensure that it can be moved from node to node.
5. Halt the package.
6. Configure package IP addresses and application services in the
control script.