Managing Serviceguard 14th Edition, June 2007

Configuring Packages and Their Services
Choosing Package Modules
Chapter 6 283
node_name <node1>
node_name <node2>
node_name <node3>
Serviceguard uses the order of priority specified by this list to choose
which node to run the package on.
IMPORTANT See “Cluster Configuration Parameters” on page 154 for important
information about node names.
auto_run Can be set to yes or no. The default is yes.
For failover packages, yes allows Serviceguard to start the package (on
the first available node listed under node_name) on cluster start-up, and
to automatically restart it on an adoptive node if it fails. no prevents
Serviceguard from automatically starting the package, and from
restarting it on another node.
This is also referred to as package switching, and can be enabled or
disabled while the package is running, by means of the cmmodpkg (1m)
command.
For system multi-node packages, auto_run must be set to yes.
node_fail_fast_enabled Can be set to yes or no. The default is no.
yes means the node on which the package is running will be halted
(HP-UX system reset) if the package fails; no means Serviceguard will
not halt the system.
Setting node_fail_fast_enabled to yes prevents Serviceguard from
repeatedly trying (and failing) to start the package on the same node.
For system multi-node packages, node_fail_fast_enabled must be set
to yes.
run_script_timeout The amount of time, in seconds, allowed for the
package to start; or no_timeout. The default is no_timeout. The
maximum is 4294.