Managing HP Serviceguard A.11.20.10 for Linux, December 2012

If there is a common generic resource that needs to be monitored as a part of multiple packages,
then the monitoring script for that resource can be launched as part of one package and all other
packages can use the same monitoring script. There is no need to launch multiple monitors for a
common resource. If the package that has started the monitoring script fails or is halted, then all
the other packages that are using this common resource also fail.
See the recommendation from HP and an example under “Launching Monitoring Scripts” (page 289).
Generic resources can be of two types - Simple and Extended.
A given generic resource is considered to be a simple generic resource when the up criteria
parameter is not specified.
• For a simple resource, the monitoring mechanism is based on the status of the resource.
• The status can be UP, DOWN, or UNKNOWN.
• The default status is UNKNOWN; UP and DOWN can be set using the cmsetresource(1m)
command.
A given generic resource is considered to be an extended generic resource when the up criteria
parameter is specified.
• For an extended resource, the monitoring mechanism is based on the current value of the
resource.
• The current value is matched with the generic_resource_up_criteria specified for the
resource in a package and this determines whether the generic resource status is UP or DOWN.
• The default current value is 0.
• Valid values are positive integer values ranging from 1 to 2147483647.
NOTE: You can get or set the status/value of a simple/extended generic resource using the
cmgetresource(1m) and cmsetresource(1m) commands respectively. See “Getting and
Setting the Status/Value of a Simple/Extended Generic Resource” (page 106) and the manpages
for more information.
A single package can have a combination of simple and extended resources, but a given generic
resource cannot be configured as a simple resource in one package and as an extended resource
in another package. It must be either simple generic resource or extended generic resource in all
packages.
3.3.3 Using Older Package Configuration Files
If you are using package configuration files that were generated using a previous version of
Serviceguard, HP recommends you use the cmmakepkg command to open a new template, and
then copy the parameter values into it. In the new template, read the descriptions and defaults of
the choices that did not exist when the original configuration was made. For example, the default
for failover_policy is now configured_node and the default for failback_policy is
now manual.
For full details of the current parameters and their default values, see Chapter 6: “Configuring
Packages and Their Services ” (page 163), and the package configuration file template itself.
3.4 How Packages Run
Packages are the means by which Serviceguard starts and halts configured applications. Failover
packages are also units of failover behavior in Serviceguard. A package is a collection of services,
disk volumes, generic resources, and IP addresses that are managed by Serviceguard to ensure
they are available. There can be a maximum of 300 packages per cluster, a total of 900 services
and a total of 100 generic resources per cluster.
3.4 How Packages Run 51