HP Serviceguard A.11.20- Managing Serviceguard Twentieth Edition, August 2011

IMPORTANT: Note that the rules for valid SERVICE_NAMEs are more restrictive as of
A.11.18.
• To configure monitoring for a registered resource, enter values for the following parameters.
RESOURCE_NAME◦
◦ RESOURCE_POLLING_INTERVAL
◦ RESOURCE_UP_VALUE
◦ RESOURCE_START
For more information, see “Parameters for Configuring EMS Resources” (page 136), and the
resource_ parameter descriptions (page 246).
NOTE: For legacy packages, DEFERRED resources must be specified in the package control
script.
• 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 (page 253), and “Controlling
Access to the Cluster” (page 192), 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 (page 238), and “About
Package Dependencies” (page 137).
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, HP-UX 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.
IMPORTANT: Serviceguard automatically creates the necessary control scripts when you create
the multi-node or system multi-node packages for CVM/CFS (version 4.1 and later). HP strongly
recommends that you never edit the configuration or control script files for these packages, although
Serviceguard does not prevent it. For CFS, create and modify the information using cfs
administration commands only. See “Creating a Storage Infrastructure with Veritas Cluster File
System (CFS)” (page 199). For CVM without CFS, see “Creating the Storage Infrastructure with
Veritas Cluster Volume Manager (CVM)” (page 219)
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 /etc/cmcluster/pkg1/pkg1.sh
Next, customize the script; see “Customizing the Package Control Script ”.
Configuring a Legacy Package 305