Managing Serviceguard 13th Edition, February 2007

Troubleshooting Your Cluster
Monitoring Hardware
Chapter 8348
action in case of a problem. For example, you could configure a disk
monitor to report when a mirror was lost from a mirrored volume group
being used in the cluster
Refer to the manual Using High Availability Monitors for additional
information.
Using EMS (Event Monitoring Service) Hardware
Monitors
A set of hardware monitors is available for monitoring and reporting on
memory, CPU, and many other system values. Some of these monitors
are supplied with specific hardware products.
Hardware Monitors and Persistence Requests
When hardware monitors are disabled using the monconfig tool,
associated hardware monitor persistent requests are removed from the
persistence files. When hardware monitoring is re-enabled, the monitor
requests that were initialized using the monconfig tool are re-created.
However, hardware monitor requests created using Serviceguard
Manager, or established when Serviceguard is started, are not
re-created. These requests are related to the psmmon hardware monitor.
To re-create the persistence monitor requests, halt Serviceguard on the
node, and then restart it. This will re-create the persistence monitor
requests.
Using HP ISEE (HP Instant Support Enterprise
Edition)
In addition to messages reporting actual device failure, the logs may
accumulate messages of lesser severity which, over time, can indicate
that a failure may happen soon. One product that provides a degree of
automation in monitoring is called HP ISEE, which gathers information
from the status queues of a monitored system to see what errors are
accumulating. This tool will report failures and will also predict failures
based on statistics for devices that are experiencing specific non-fatal
errors over time. In a Serviceguard cluster, HP ISEE should be run on all
nodes.