Managing Serviceguard 14th Edition, June 2007
Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4184
the first adoptive node name, then the second adoptive
node name, followed, in order of preference, by
additional node names. In case of a failover, control of
the package will be transferred to the next adoptive
node name listed in the package configuration file, or
(if that node is not available or cannot run the package
at that time) to the next node in the list, and so on.
If all nodes in the cluster can run the package, and if
order is not important, you can specify: node_name *
A node name can be up to 39 characters long; more
details in Chapter 6 under node_name (see page 282).
auto_run If auto_run is set to yes, Serviceguard will
automatically start the package on an eligible node if
one is available, and will automatically fail the package
over to another node if it fails. If auto_run is set to no,
Serviceguard will not automatically start the package
up; you must do it manually using the cmrunpkg
command.
When a package starts up, the Package Switching flag
is set to match the auto_run setting, but you can
change this flag while the package is running by means
of the cmmodpkg command.
Default is yes.
node_fail_fast_enabled
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