Managing HP Serviceguard for Linux Ninth Edition, April 2009

Table 4-1 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,
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.
About Package Dependencies
A package can have dependencies on other packages, meaning the package will not
start on a node unless the packages it depends on are running on that node.
You can make a package dependent on any other package or packages running on the
same cluster node, subject to the restrictions spelled out in Chapter 6, under
“dependency_condition” (page 202).
As of A.11.19, Serviceguard adds two new capabilities: you can specify broadly where
the package depended on must be running, and you can specify that it must be down.
These capabilities are discussed later in this section under “Extended Dependencies”
(page 126). You should read the next section, “Simple Dependencies” (page 121), first.
Simple Dependencies
A simple dependency occurs when one package requires another to be running on the
same node. You define these conditions by means of the parameters dependency_condition
and dependency_location, using the literal values UP and same_node, respectively. (For
Package Configuration Planning 121