Managing Serviceguard A.11.20, March 2013

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 141) 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. For e.g., a generic resource "sfm_disk" cannot be a simple resource in package
pkg1 and extended resource in another package pkg2. It must be either simple generic resource
in all packages or extended generic resource in all packages.
See also “Using Generic Resources to Monitor Volume Groups” (page 106).
Using the Event Monitoring Service
Basic package resources include cluster nodes, LAN interfaces, and services, which are the
individual processes within an application. All of these are monitored by Serviceguard directly. In
addition, you can use the Event Monitoring Service registry through which add-on monitors can
be configured. This registry allows other software components to supply monitoring of their resources
for Serviceguard. Monitors currently supplied with other software products include EMS (Event
Monitoring Service) High Availability Monitors, and an ATM monitor.
If a monitored resource is configured in a package, the package manager calls the resource
registrar to launch an external monitor for the resource. Resources can be configured to start up
either at the time the node enters the cluster or at the end of package startup. The monitor then
sends messages back to Serviceguard, which checks to see whether the resource is available
before starting the package. In addition, the package manager can fail the package to another
node or take other action if the resource becomes unavailable after the package starts.
You can specify a monitored resource for a package in Serviceguard Manager, or on the HP-UX
command line by using the command /opt/resmon/bin/resls. For additional information,
see the manpage for resls(1m).
Using the EMS HA Monitors
The EMS (Event Monitoring Service) HA Monitors, available as a separate product, can be used
to set up monitoring of disks and other resources as package resource dependencies. Examples
of resource attributes that can be monitored using EMS include the following:
• Logical volume status
• Physical volume status
• System load
• Number of users
• File system utilization
• LAN health
Once a monitor is configured as a package resource dependency, the monitor will notify the
package manager if an event occurs showing that a resource is down. The package may then be
failed over to an adoptive node.
The EMS HA Monitors can also be used to report monitored events to a target application for
graphical display or for operator notification. For more information, see the latest Event Monitoring
Service release notes and other documents at http://www.hp.com/go/hpux-ha-monitoring-docs.
See also “Using EMS to Monitor Volume Groups” (page 106).
60 Understanding Serviceguard Software Components