Managing Serviceguard A.11.20, March 2013

Table 8 Package Failover Behavior
Parameters in Configuration FileSwitching Behavior
Package switches normally after detection of
service, network, generic resource failure, or
• node_fail_fast_enabled set to no. (Default)
• service_fail_fast_enabled set to NO for all services. (Default)
EMS failure, or when a configured resource
dependency is not met. Halt script runs before
switch takes place. (Default)
• auto_run set to yes for the package. (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.
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)
All packages switch following a system reset
(an immediate halt without a graceful
• service_fail_fast_enabled set to yes for a specific service.
• auto_run set to yes for all packages.
shutdown) on the node when a specific
service fails. Halt scripts are not run.
All packages switch following a system reset
on the node when any service fails. An
• service_fail_fast_enabled set to yes for all services.
• auto_run set to yes for all packages.
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. To manage this behavior, use the
parameter local_lan_failover_allowed (page 245) in the package configuration file. (yes,
meaning enabled, is the default.)
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 will be
dependent on.
• generic_resource_name: defines the logical name used to identify a generic resource in
a package.
• generic_resource_evaluation_type: defines when the status of a generic resource
is evaluated. This can be set to during_package_start or before_package_start.
If not specified, default during_package_start is considered.
◦ during_package_start means the status of generic resources are evaluated during
the course of start of the package.
◦ before_package_start means resource monitoring must be started before the package
start and all the configured resources have to be UP on a given node for the package to
be started on that node.
• generic_resource_up_criteria: defines a criterion to determine the 'up' condition for
a generic resource. It also determines whether a generic resource is a simple resource or an
extended resource. This parameter requires an operator and a value. The operators ==, !=,
>, <, >=, and <= are allowed. Values must be positive integer values ranging from 1 to
2147483647.
138 Planning and Documenting an HA Cluster