Managing HP Serviceguard A.11.20.10 for Linux, December 2012

When adding packages, be sure not to exceed the value of max_configured_packages as
defined in the cluster configuration file (see “Cluster Configuration Parameters ” (page 86)). You
can modify this parameter while the cluster is running if you need to.
4.8.4 Choosing Switching and Failover Behavior
To determine the failover behavior of a failover package (see “Package Types” (page 41)), you
define the policy that governs where Serviceguard will automatically start up a package that is not
running. In addition, you 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 the package
configuration file that determine each behavior. See “Package Parameter Explanations” (page 168)
for more information.
Table 6 Package Failover Behavior
Parameters in Configuration FileSwitching Behavior
• 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 switches normally after detection of
service or network failure, generic resource
failure or when a configured dependency is
not met. Halt script runs before switch takes
place. (Default)
• failover_policy set to min_package_node.
Package fails over to the node with the fewest
active packages.
• failover_policy set to configured_node. (Default)
Package fails over to the node that is next on
the list of nodes. (Default)
• failback_policy set to automatic.
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 manual. (Default)
• failover_policy set to configured_node. (Default)
Package can be manually returned to its
primary node if it is running on a non-primary
node, but this does not happen automatically.
• service_fail_fast_enabled set to yes for a specific service.
• auto_run set to yes for all packages.
All packages switch following a system reboot
on the node when a specific service fails. Halt
scripts are not run.
• service_fail_fast_enabled set to yes for all services.
• auto_run set to yes for all packages.
All packages switch following a system reboot
on the node when any service fails.
• service_fail_fast_enabled set to yes for a specific service.
• auto_run set to yes for all packages.
All packages switch following a system reset
(an immediate halt without a graceful
shutdown) on the node when a specific
service fails. Halt scripts are not run.
• service_fail_fast_enabled set to yes for all services.
• auto_run set to yes for all packages.
All packages switch following a system reset
on the node when any service fails. An
attempt is first made to reboot the system prior
to the system reset.
Failover packages can be also configured so that IP addresses switch from a failed NIC to a
standby NIC on the same node and the same physical subnet.
4.8.5 Parameters for Configuring Generic Resources
Serviceguard provides the following parameters for configuring generic resources. Configure each
of these parameters in the package configuration file for each resource the package is dependent
on.
4.8 Package Configuration Planning 103