Managing Serviceguard 12th Edition, March 2006

Configuring Packages and Their Services
Creating the Package Configuration
Chapter 6284
• LOCAL_LAN_FAILOVER_ALLOWED. Enter YES to permit switching of the
package IP address to a standby LAN, or NO to keep the package
address from switching locally. (Must be NO for multi-node and
system multi-node packages.)
• NODE_FAIL_FAST_ENABLED. If you enter YES, a node will be halted
with a TOC any time a package fails on that node. This prevents
Serviceguard from repeatedly trying (and failing) to start a package
on that node. For system multi-node packages, this must be set to
YES.
• RUN_SCRIPT and HALT_SCRIPT. Specify the pathname of the
package control script (described in the next section). No default is
provided.
TIMEOUT: For the run and halt scripts, enter the number of seconds
Serviceguard should try to complete the script before it
acknowledges failure. If you have timeouts for the halt script, this
value must be larger than all the halt script timeouts added together.
SCRIPT_LOG_FILE. (optional). You can specify a place for the run and
halt script to place 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 ASCII configuration file.
NOTE You should not enter LVM volume groups or VxVM disk groups in
this file.
• If your package has IP addresses associated with it, enter the
SUBNET. This must be a subnet that is already specified in the cluster
configuration, and it can be either an IPv4 or an IPv6 subnet.
Link-local package IPs are not allowed, hence link-local subnets
must not be entered in the package ASCII file.
• If your package contains services, enter the SERVICE_NAME,
SERVICE_FAIL_FAST_ENABLED and SERVICE_HALT_TIMEOUT values.
Enter a group of these three for each service. You can configure no
more than 30 services per package.