Managing HP Serviceguard A.11.20.00 for Linux, June 2012

SUBNET Specifies the IP subnets that are to be monitored for the
package.
RUN_SCRIPTand HALT_SCRIPT Use the full pathname of each script.
These two parameters allow you to separate package run
instructions and package halt instructions for legacy
packages into separate scripts if you need to. In this case,
make sure you include identical configuration information
(such as node names, IP addresses, etc.) in both scripts.
In most cases, though, HP recommends that you use the
same script for both run and halt instructions. (When the
package starts, the script is passed the parameter start;
when it halts, it is passed the parameter stop.)
LV The name of a logical volume hosting a file system that will
be mounted by the package.
FS The name of the mount point for a file system to be mounted
by the package.
VGCHANGE As vgchange_cmd (page 169).
Generating the Package Configuration File
When you have chosen the configuration modules your package needs (see “Choosing Package
Modules” (page 153)), you are ready to generate a package configuration file that contains those
modules. This file will consist of a base module (failover, multi-node or system multi-node) plus the
modules that contain the additional parameters you have decided to include.
Before You Start
Before you start building a package, create a subdirectory for it in the $SGCONF directory, for
example:
mkdir $SGCONF/pkg1
(See “Understanding the Location of Serviceguard Files” (page 121) for information about
Serviceguard pathnames.)
cmmakepkg Examples
The cmmakepkg command generates a package configuration file. Some examples follow; see
the cmmakepkg (1m) manpage for complete information. All the examples create an editable
configuration file pkg1.conf in the $SGCONF/pkg1 directory.
174 Configuring Packages and Their Services