Managing HP Serviceguard A.11.20.10 for Linux, December 2012

• configured_node means Serviceguard will attempt to start the package on the first available
node in the list you provide under node_name (page 170).
• 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.
• site_preferred means Serviceguard will try all the eligible nodes on the local SITE before
failing the package over to a node on another SITE. This policy can be configured only in
a Metrocluster with site aware failover configuration; see the documents listed under
“Cross-Subnet Configurations” (page 27) 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 Metrocluster
with site aware failover configuration; see the documents listed under “Cross-Subnet
Configurations” (page 27) for more information.
NOTE:
• For site_preferred or site_preferred_manual failover_policy to be effective
define the policy in the packages running or configured to run on the cluster with more than
one site configured or more than one site nodes.
• When site_preferred or site_preferred_manual failover_policy is defined
in a package, cmrunpkg -a option cannot be used to run the 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 107).
6.1.4.16 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.
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.
NOTE: When the failover_policy is site_preferred or site_preferred_manual,
failback_policy cannot be set to automatic.
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 107).
6.1.4.17 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 174).
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.
6.1 Choosing Package Modules 173