Managing Serviceguard Nineteenth Edition, Reprinted June 2011

failback_policy
Specifies what action the package manager should take when a failover package is not running
on its primary node (the first node on its node_name list) and 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 (adoptive) 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
(page 227) to move.
CAUTION: When the failback_policy is automatic and you set the NODE_NAME to '*',
if you add, delete, or rename a node in the cluster, the primary node for the package might change
resulting in the automatic failover of that package.
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 128). If the package has a
configured weight, see also “About Package Weights” (page 135).
priority
Assigns a priority to a failover package whose failover_policy (page 226) is
configured_node. Valid values are 1 through 3000, or no_priority. The default is
no_priority. See also the dependency_ parameter descriptions (page 227).
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 drag those
packages, forcing them 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. 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.
IMPORTANT: Because priority is a matter of ranking, a lower number indicates a higher priority
(20 is a higher priority than 40). A numerical priority is higher than no_priority.
New for A.11.18 (for both modular and legacy packages). See “About Package Dependencies”
(page 128) for more information.
dependency_name
An identifier for a particular dependency that must be met in order for this package to run (or keep
running). It must be unique among this package's dependency_names. The length and formal
restrictions for the name are the same as for package_name (page 222).
IMPORTANT: Restrictions on dependency names in previous Serviceguard releases were less
stringent. Packages that specify dependency_names that do not conform to the above rules will
continue to run, but if you reconfigure them, you will need to change the dependency_name;
cmcheckconf and cmapplyconf will enforce the new rules.
Configure this parameter, along with dependency_condition and dependency_location,
if this package depends on another package; for example, if this package depends on a package
named pkg2 to be running on the same node:
dependency_name pkg2dep dependency_condition pkg2 = UP dependency_location same_node
For more information about package dependencies, see the parameter descriptions that follow,
the cmmakepkg (1m) manpage, and the discussion in this manual “About Package Dependencies”
(page 128).
Choosing Package Modules 227