Managing Serviceguard 14th Edition, June 2007

Understanding Serviceguard Software Components
How the Package Manager Works
Chapter 3 83
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)
Package is
automatically halted
and restarted on its
primary node if the
primary node is
available and the
package is running on
a non-primary node.
• Failback policy
set to
automatic.
• failback_policy set to
automatic.
If desired, package
must be manually
returned to its primary
node if it is running on
a non-primary node.
• Failback Policy
set to Manual.
(Default)
• Failover Policy
set to
configured
node. (Default)
• failback_policy set to manual.
(Default)
• failover_policy set to
configured_node. (Default)
All packages switch
following a system
reset (an immediate
halt without a graceful
shutdown) on the node
when a specific service
fails. An attempt is
made to reboot the
system prior to the
system reset. Halt
scripts are not run.
• Service Failfast
set for a specific
service.
• Auto Run set
for all
packages.
• service_fail_fast_enabled
set to yes for a specific service.
• auto_run set to yes for all
packages.
Table 3-3 Package Failover Behavior (Continued)
Switching Behavior
Options in
Serviceguard
Manager
Parameters in Configuration
File