Managing Serviceguard Nineteenth Edition, Reprinted June 2011

• auto_run. For failover packages, enter yes to allow Serviceguard to start the package on
the first available node specified by node_name, and to automatically restart it later if it fails.
Enter no to keep Serviceguard from automatically starting the package.
• node_fail_fast_enabled. Enter yes to cause the node to be halted (system reset) if the
package fails; otherwise enter no.
For system multi-node packages, you must enter yes.
• run_script_timeout and halt_script_timeout. Enter the number of seconds
Serviceguard should wait for package startup and shutdown, respectively, to complete; or
leave the default, no_timeout; see (page 224).
• successor_halt_timeout. Used if other packages depend on this package; see “About
Package Dependencies” (page 128).
• script_log_file (page 225).
• log_level (page 226).
• failover_policy (page 226). Enter configured_node or min_package_node.
(This parameter can be set for failover packages only.)
• failback_policy (page 227) Enter automatic or manual.
(This parameter can be set for failover packages only.)
• If this package will depend on another package or packages, enter values for
dependency_name, (page 227)dependency_condition, dependency_location, and
optionally priority.
See “About Package Dependencies” (page 128) for more information.
NOTE: The package(s) this package depends on must already be part of the cluster
configuration by the time you validate this package (via cmcheckconf(1m); see “Verifying
and Applying the Package Configuration” (page 245)); otherwise validation will fail.
• To configure package weights, use the weight_name and weight_value parameters
(page 229). See “About Package Weights” (page 135) for more information.
• local_lan_failover_allowed. Enter yes to permit switching of the package IP address
to a standby LAN card on the local node, or no to keep the package address from switching
locally.
For multi-node packages, you must enter no.
• Use the monitored_subnet parameter to specify a subnet that is to be monitored for this
package. If there are multiple subnets, repeat the parameter as many times as needed, on a
new line each time.
In a cross-subnet configuration, configure the additional monitored_subnet_access
parameter for each monitored_subnet as necessary; see “About Cross-Subnet Failover”
(page 145) for more information.
• If this is a Serviceguard Extension for Oracle RAC (SGeRAC) installation, you can use the
cluster_interconnect_subnet parameter(page 230).
• If your package will use relocatable IP addresses, enter the ip_subnet and ip_address
addresses. See the parameter descriptions (page 231) for rules and restrictions.
In a cross-subnet configuration, configure the additional ip_subnet_node parameter for
each ip_subnet as necessary; see “About Cross-Subnet Failover” (page 145) for more
information.
Editing the Configuration File 243