Managing HP Serviceguard A.11.20.10 for Linux, December 2012

IMPORTANT: Each subnet specified here must already be specified in the cluster configuration
file via the NETWORK_INTERFACE parameter and either the HEARTBEAT_IP or
STATIONARY_IP parameter. See “Cluster Configuration Parameters ” (page 86) for more
information.
See also “Stationary and Relocatable IP Addresses and Monitored Subnets” (page 59) and
monitored_subnet (page 175).
IMPORTANT: For cross-subnet configurations, see “Configuring Cross-Subnet Failover”
(page 231).
• If your package runs services, enter the SERVICE_NAME as described under service_name
(page 177) and values for SERVICE_FAIL_FAST_ENABLED as described under
service_fail_fast_enabled (page 178) and SERVICE_HALT_TIMEOUT as described
under service_halt_timeout (page 178). Enter a group of these three for each service.
IMPORTANT: Note that the rules for valid SERVICE_NAMEs are more restrictive as of
Serviceguard A.11.18.
• ACCESS_CONTROL_POLICY. You can grant a non-root user PACKAGE_ADMIN privileges for
this package.
See the entries for user_name, user_host, and user_role user_name (page 184), and
“Controlling Access to the Cluster” (page 152), for more information.
• If the package will depend on another package, enter values for DEPENDENCY_NAME,
DEPENDENCY_CONDITION, and DEPENDENCY_LOCATION.
For more information, see the corresponding parameter descriptions starting on (page 174),
and “About Package Dependencies” (page 107).
7.7.2 Creating the Package Control Script
For legacy packages, the package control script contains all the information necessary to run all
the services in the package, monitor them during operation, react to a failure, and halt the package
when necessary. You can use Serviceguard Manager, Serviceguard commands, or a combination
of both, to create or modify the package control script.
Each package must have a separate control script, which must be executable.
For security reasons, the control script must reside in a directory with the string cmcluster in the
path. The control script is placed in the package directory and is given the same name as specified
in the RUN_SCRIPT and HALT_SCRIPT parameters in the package configuration file. The package
control script template contains both the run instructions and the halt instructions for the package.
You can use a single script for both run and halt operations, or, if you wish, you can create separate
scripts.
Use cmmakepkg to create the control script, then edit the control script. Use the following procedure
to create the template for the sample failover package pkg1.
First, generate a control script template, for example:
cmmakepkg -s $SGCONF/pkg1/pkg1.sh
Next, customize the script; see “Customizing the Package Control Script ”.
7.7 Configuring a Legacy Package 227