Managing Serviceguard Nineteenth Edition, Reprinted June 2011

• Enter the SUBNET or MONITORED_SUBNETs that are to be monitored for this package. They
can be IPv4 or an IPv6 subnets, but must not be link-local subnets (link-local package IPs are
not allowed).
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 105) for more
information.
See also “Stationary and Relocatable IP Addresses ” (page 64) and monitored_subnet
(page 229).
IMPORTANT: For cross-subnet configurations, see “Configuring Cross-Subnet Failover”
(page 295).
• If your package runs services, enter the SERVICE_NAME (page 232) and values for
SERVICE_FAIL_FAST_ENABLED (page 233) and SERVICE_HALT_TIMEOUT(page 233).
Enter a group of these three for each service.
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 128), and the
resource_ parameter descriptions (page 233).
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 240), and “Controlling
Access to the Cluster” (page 183), 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 227), and “About
Package Dependencies” (page 128).
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.
Configuring a Legacy Package 291