Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Cluster and Package Maintenance
Configuring a Legacy Package
Chapter 7278
• FAILBACK_POLICY. For failover packages, enter the
failback_policy (see page 214).
• NODE_NAME. Enter the node or nodes on which the package can run;
as described under node_name (see page 210).
• AUTO_RUN. Configure the package to start up automatically or
manually; as described under auto_run (see page 211).
• NODE_FAIL_FAST_ENABLED. Enter the policy as described under
node_fail_fast_enabled (see page 211).
• RUN_SCRIPT and HALT_SCRIPT. Specify the pathname of the
package control script (described in the next section). No default is
provided. Permissions on the file and directory should be set to
rwxr-xr-x or r-xr-xr-x (755 or 555).
(Script timeouts): Enter the run_script_timeout (see page 212)
and halt_script_timeout (see page 212).
SCRIPT_LOG_FILE. (optional). Specify the full pathname of the file
where the RUN_SCRIPT and HALT_SCRIPT will log messages. If you do
not specify a path, Serviceguard will create a file with “.log”
appended to each script path, and put the messages in that file.
• If your package has relocatable IP addresses, enter the SUBNET if you
want it to be monitored (this means the package will stop if the
subnet fails).
This must be a subnet that is already specified in the cluster
configuration, and it can be either an IPv4 or an IPv6 subnet. It must
not be a link-local subnet (link-local package IPs are not allowed).
See monitored_subnet on page 217.
IMPORTANT For cross-subnet configurations, see “Configuring Cross-Subnet
Failover” on page 286.
• If your package runs services, enter the SERVICE_NAME as described
under service_name (see page 219) and values for
SERVICE_FAIL_FAST_ENABLED as described under
service_fail_fast_enabled (see page 221) and
SERVICE_HALT_TIMEOUT as described under
service_halt_timeout (see page 221). Enter a group of these
three for each service.