Managing HP Serviceguard A.11.20.20 for Linux, March 2014

in the appropriate switching behavior. Power protection is provided by HP-supported uninterruptible
power supplies (UPS).
3.8.3 Responses to Package and Service Failures
In the default case, the failure of a package, a generic resource or service of the package or of a
service within a package causes the package to shut down by running the control script with the
stop parameter, and then restarting the package on an alternate node. A package will also fail
if it is configured to have a dependency on another package, and that package fails.
You can modify this default behavior by specifying that the node should halt (system reset) before
the transfer takes place. You do this by setting failfast parameters in the package configuration
file.
In cases in which package shutdown might hang, leaving the node in an unknown state, failfast
options can provide a quick failover, after which the node will be cleaned up on reboot. Remember,
however, that a system reset causes all packages on the node to halt abruptly.
The settings of the failfast parameters in the package configuration file determine the behavior of
the package and the node in the event of a package or resource failure:
• If service_fail_fast_enabled (page 184) is set to yes in the package configuration
file, Serviceguard will reboot the node if there is a failure of that specific service.
• If node_fail_fast_enabled (page 176) is set to yes in the package configuration file,
and the package fails, Serviceguard will halt (reboot) the node on which the package is
running.
For more information, see “Package Configuration Planning ” (page 104) and Chapter 6 (page 169).
3.8.4 Responses to Package and Generic Resources Failures
In a package that is configured with a generic resource and is running, failure of a resource prompts
the Serviceguard Package Manager to take appropriate action based on the style of the package.
For failover packages, the package is halted on the node where the resource failure occurred and
started on an available alternative node. For multi-node packages, failure of a generic resources
causes the package to be halted only on the node where the failure occurred.
• In case of simple resources, failure of a resource must trigger the monitoring script to set the
status of a resource to 'down' using the cmsetresource command.
• In case of extended resources, the value fetched by the monitoring script can be set using the
cmsetresource command.
The Serviceguard Package Manager evaluates this value against the
generic_resource_up_criteria set for a resource in the packages where it is configured.
If the value that is set (current_value) does not satisfy the generic_resource_up_criteria,
then the generic resource is marked as 'down' on that node.
NOTE: If a simple resource is down on a particular node, it is down on that node for all the
packages using it whereas, in case of an extended resource the resource may be up on a node
for a particular package and down for another package, since it is dependent on the
generic_resource_up_criteria.
Additionally, in a running package configured with a generic resource:
• Any failure of a generic resource of evaluation type "before_package_start" configured in a
package will not disable the node switching for the package.
• Any failure of a generic resource of evaluation type "during_package_start" configured in a
package will disable the node switching for the package.
3.8 Responses to Failures 77