Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Understanding Serviceguard Software Components
How the Package Manager Works
Chapter 356
For full details of the current parameters and their default values, see
Chapter 6, “Configuring Packages and Their Services,” on page 191, and
the package configuration file template itself.
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 (for legacy packages) or in the package
configuration file that determine each behavior.
Table 3-3 Package Failover Behavior
Switching Behavior
Options in
Serviceguard
Manager
Parameters in Configuration
File
Package switches
normally after
detection of service or
network failure, or
when a configured
dependency is not met.
Halt script runs before
switch takes place.
(Default)
• Service Failfast
not set (for all
services).
(Default)
• Node Fail Fast
not set.
(Default)
• Auto Run set
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)