Managing Serviceguard Fifteenth Edition, reprinted May 2008

Configuring Packages and Their Services
Choosing Package Modules
Chapter 6 289
IMPORTANT See “Cluster Configuration Parameters” on page 156 for important
information about node names.
See “About Cross-Subnet Failover” on page 191 for considerations when
configuring cross-subnet packages, which are further explained under
“Cross-Subnet Configurations” on page 41.
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” on
page 178.
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