Managing Serviceguard Eighteenth Edition, September 2010

Metrocluster (additional HP software); see the documents listed under
“Cross-Subnet Configurations” (page 41) for more information.
• site_preferred_manual means Serviceguard will try to fail the package over
to a node on the local SITE. If there are no eligible nodes on the local SITE, the
package will halt with global switching enabled. You can then restart the package
locally, when a local node is available, or start it on another SITE. This policy can
be configured only in a site-aware disaster-tolerant cluster, which requires
Metrocluster (additional HP software); see the documents listed under
“Cross-Subnet Configurations” (page 41) for more information.
This parameter can be set for failover packages only. For a package that will depend
on another package or vice versa, see also “About Package Dependencies” (page 179).
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 293) 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 179). If
the package has a configured weight, see also “About Package Weights” (page 187).
priority
Assigns a priority to a failover package whose failover_policy (page 292) is
configured_node. Valid values are 1 through 3000, or no_priority. The
default is no_priority. See also the dependency_ parameter descriptions (page 294).
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 179) for more information.
Choosing Package Modules 293