Managing Serviceguard Fifteenth Edition, reprinted May 2008

Cluster and Package Maintenance
Configuring a Legacy Package
Chapter 7 381
• AUTO_RUN. Configure the package to start up automatically or
manually; see auto_run on page 289.
• LOCAL_LAN_FAILOVER_ALLOWED. Enter the policy for
local_lan_failover_allowed (see page 294).
• NODE_FAIL_FAST_ENABLED. Enter the policy for
node_fail_fast_enabled (see page 289).
• 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 290)
and halt_script_timeout (see page 290).
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.
• STORAGE_GROUP. Specify the names of any CVM storage groups that
will be used by this package. Enter each storage group (CVM disk
group) on a separate line. Note that CVM storage groups are not
entered in the cluster configuration file.
NOTE You should not enter LVM volume groups or VxVM disk groups in
this 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. Must
not be a link-local subnet (link-local package IPs are not allowed).
See monitored_subnet on page 294.
IMPORTANT For cross-subnet configurations, see “Configuring Cross-Subnet
Failover” on page 390.