Managing Serviceguard 12th Edition, March 2006

Understanding Serviceguard Software Components
How the Package Manager Works
Chapter 3 85
Choosing Package Failover Behavior
To determine failover behavior, you can define a package failover policy
that governs which nodes will automatically start up a package that is
not running. In addition, you can define a failback policy that determines
whether a package will be automatically returned to its primary node
when that is possible.
The following table describes different types of failover behavior and the
settings in Serviceguard Manager or in the package configuration file
that determine each behavior.
Table 3-3 Package Failover Behavior
Switching Behavior
Options in
Serviceguard
Manager Parameters in ASCII File
Package switches
normally after
detection of service,
network, or EMS
failure, or when a
configured dependency
is not met. Halt script
runs before switch
takes place. (Default)
•Package
Failfast set to
Disabled.
(Default)
• Service Failfast
set to Disabled
for all services.
(Default)
•Automatic
Switching set to
Enabled for the
package.
(Default)
• NODE_FAIL_FAST_ENABLED set to
NO. (Default)
• SERVICE_FAIL_FAST_ENABLED
set to NO for all services.
(Default)
• AUTO_RUN set to YES for the
package. (Default)
Package fails over to
the node with the
fewest active
packages.
• Failover policy
set to Minimum
Package Node.
• FAILOVER_POLICY set to
MIN_PACKAGE_NODE.
Package fails over to
the node that is next
on the list of nodes.
(Default)
• Failover policy
set to
Configured
Node. (Default)
• FAILOVER_POLICY set to
CONFIGURED_NODE. (Default)