HP Serviceguard A.11.20- Managing Serviceguard Twentieth Edition, August 2011

NOTE: Optional parameters are commented out in the configuration file (with a # at the beginning
of the line). In some cases these parameters have default values that will take effect unless you
uncomment the parameter (remove the #) and enter a valid value different from the default. Read
the surrounding comments in the file, and the explanations in this chapter, to make sure you
understand the implications both of accepting and of changing a given default.
In all cases, be careful to uncomment each parameter you intend to use and assign it the value
you want it to have.
• package_name. Enter a unique name for this package. Note that there are stricter formal
requirements for the name as of A.11.18.
• package_type. Enter failover, multi_node, or system_multi_node.
(system_multi_node is reserved for special-purpose packages supplied by HP.) Note that
there are restrictions if another package depends on this package; see “About Package
Dependencies” (page 137).
See “Types of Package: Failover, Multi-Node, System Multi-Node” (page 228) for more
information.
• node_name. Enter the name of each cluster node on which this package can run, with a
separate entry on a separate line for each node.
• 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 236).
• successor_halt_timeout. Used if other packages depend on this package; see “About
Package Dependencies” (page 137).
• script_log_file (page 237).
• log_level (page 237).
• failover_policy (page 237). Enter configured_node or min_package_node.
(This parameter can be set for failover packages only.)
• failback_policy (page 238) 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 238)dependency_condition, dependency_location, and
optionally priority.
See “About Package Dependencies” (page 137) 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 259)); otherwise validation will fail.
• To configure package weights, use the weight_name and weight_value parameters
(page 240). See “About Package Weights” (page 144) for more information.
256 Configuring Packages and Their Services