Filter
Top Products
Chapter 3
Detailed Description
The Detailed Picture of Hardware Monitoring
63
Each monitor has its own startup configuration file, which contains the default monitoring requests and
any customized requests created using the Hardware Monitoring Request Manager. During system startup,
following the execution of the IOSCAN utility (thus performing a real/hard ioscan), or when managing
requests using the Hardware Monitoring Request Manager, the startup client reads each configuration file
and creates the monitoring requests defined by the entries in the file. The Hardware Monitoring Request
Manager updates the contents of the startup configuration file when you add or modify monitoring requests.
Peripheral Status Monitor (PSM)
The sole purpose of the peripheral status monitor (PSM) is to convert events detected by a hardware event
monitor to changes in hardware resource status. This conversion is required for use with MC/ServiceGuard in
controlling package failover. When an event occurs, the PSM determines if it is serious enough to warrant a
change in hardware resource status to DOWN. If it is, the PSM alerts EMS, which then informs
MC/ServiceGuard.
More information about the PSM is included in Chapter 4, “Using the Peripheral Status Monitor.”
Event Monitoring Service (EMS)
The event monitoring service (EMS) provides the framework within which hardware monitoring takes
place. EMS manages the monitoring requests created for each monitor. When an event occurs, the associated
monitor alerts EMS and passes it an event message. EMS then uses the monitoring request to determine how
(or if) the event message should be delivered. EMS manages all hardware event notification.
EMS also provides the graphical interface for creating and managing PSM monitoring requests. Like event
monitoring requests, all PSM monitoring requests are managed by EMS.
Other system monitors are available for EMS at additional cost. For more information on EMS and available
monitors, see Using EMS HA Monitors (B5735-90001).