Managing HP Serviceguard A.11.20.00 for Linux, June 2012

log_level
Determines the amount of information printed to stdout when the package is validated, and to
the script_log_file when the package is started and halted. Valid values are 0 through 5,
but you should normally use only the first two (0 or 1); the remainder (2 through 5) are intended
for use by HP Support.
• 0 - informative messages
• 1 - informative messages with slightly more detail
• 2 - messages showing logic flow
• 3 - messages showing detailed data structure information
• 4 - detailed debugging information
• 5 - function call flow
New for modular packages.
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 159).
• 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 100).
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.
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 100).
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 163).
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
162 Configuring Packages and Their Services