Managing HP Serviceguard for Linux Ninth Edition, April 2009

failover_policy
Specifies how Serviceguard decides where to start the package, or restart it if it fails.
Can be set to configured_node or min_package_node. The default is
configured_node.
• configured_node means Serviceguard will attempt to start the package on the
first available node in the list you provide under node_name (page 197).
• min_package_node means Serviceguard will start the package on whichever
node in the node_name list has the fewest packages running at the time.
This parameter can be set for failover packages only. If this package will depend on
another package or vice versa, see also “About Package Dependencies” (page 121).
failback_policy
Specifies whether or not Serviceguard will automatically move a package that is not
running on its primary node (the first node on its node_name list) when the primary
node is once again available. Can be set to automatic or manual. The default is
manual.
• manual means the package will continue to run on the current node.
• automatic means Serviceguard will move the package to the primary node as
soon as that node becomes available, unless doing so would also force a package
with a higher priority to move.
This parameter can be set for failover packages only. If this package will depend on
another package or vice versa, see also “About Package Dependencies” (page 121).
priority
Assigns a priority to a failover package whose failover_policy is configured_node.
Valid values are 1 through 3000, or no_priority. The default is no_priority. See
also the dependency_ parameter descriptions (page 202).
priority can be used to satisfy dependencies when a package starts, or needs to fail over
or fail back: a package with a higher priority than the packages it depends on can force
those packages to start or restart on the node it chooses, so that its dependencies are
met.
If you assign a priority, it must be unique in this cluster. A lower number indicates a
higher priority, and a numerical priority is higher than no_priority. HP recommends
assigning values in increments of 20 so as to leave gaps in the sequence; otherwise you
may have to shuffle all the existing priorities when assigning priority to a new package.
Choosing Package Modules 201