HP Serviceguard Version A.11.18 Release Notes, September 2008

operation_sequence
Defines the order in which the scripts defined by the package’s component modules
will start up. See the package configuration file for details.
This parameter is not configurable; do not change the entries in the configuration file.
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:
• 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
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. Can
be used in both modular and legacy packages.
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.
For more information, see “About Package Dependencies” in Chapter 4 of Managing
Serviceguard.
monitored_subnet_access
In cross-subnet configurations, specifies whether each monitored_subnet is accessible
on all nodes in the package’s node list, or only some. Valid values are PARTIAL, meaning
that at least one of the nodes has access to the subnet, but not all; and FULL, meaning
that all nodes have access to the subnet. The default is FULL, and it is in effect if
monitored_subnet_access is not specified.
See also “ip_subnet_node” and “About Cross-Subnet Configurations” (page 40).
New for modular packages. For legacy packages, see “Configuring Cross-Subnet
Failover” in Chapter 7 of Managing Serviceguard.
32 Serviceguard Version A.11.18 Release Notes