Managing Serviceguard Nineteenth Edition, Reprinted June 2011

IMPORTANT: See “Cluster Configuration Parameters ” (page 105) for important information about
node names.
See “About Cross-Subnet Failover” (page 145) for considerations affecting cross-subnet packages,
which are further explained under “Cross-Subnet Configurations” (page 29). See “Rules for Simple
Dependencies” (page 129) for considerations affecting a package that depends on another package,
or that is depended on.
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.
auto_run should be set to yes if the package depends on another package, or is depended on;
see “About Package Dependencies” (page 128).
For system multi-node packages, auto_run must be set to yes. In the case of a multi-node package,
setting auto_run to yes allows an instance to start on a new node joining the cluster; no means
it will not.
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.
If this parameter is set to yes and one of the following events occurs, Serviceguard will halt the
system (HP-UX system reset) on the node where the control script fails:
• A package subnet fails and no backup network is available
• An EMS resource fails
• Serviceguard is unable to execute the halt function
• The start or halt function times out
NOTE: If the package halt function fails with “exit 1”, Serviceguard does not halt the node,
but sets no_restart for the package, which disables package switching (auto_run), thereby
preventing the package from starting on any adoptive node.
Setting node_fail_fast_enabled to yes ensures that the package can fail over to another
node even if the package cannot halt successfully. Be careful when using
node_fail_fast_enabled, as it will cause all packages on the node to halt abruptly. For more
information, see “Responses to Failures ” (page 85) and “Responses to Package and Service
Failures ” (page 87).
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.
If the package does not complete its startup in the time specified by run_script_timeout,
Serviceguard will terminate it and prevent it from switching to another node. In this case, if
node_fail_fast_enabled is set to yes, the node will be halted (HP-UX system reset).
224 Configuring Packages and Their Services