HP EMS HARDWARE S B6191-90028 manual How Does Hardware Monitoring Work?

Page 13

Introduction

Hardware Monitoring Overview

How Does Hardware Monitoring Work?

The following figure shows the basic components involved in hardware monitoring.

Figure 1-1

Components Involved in Hardware Monitoring

The typical hardware monitoring process works as follows:

1.While monitoring its hardware resources, the hardware event monitor detects some type of abnormal behavior on one of the resources.

2.The hardware event monitor creates the appropriate event message, which includes suggested corrective action, and passes it to the Event Monitoring Service (EMS).

3.EMS sends the event message to the system administrator using the notification method specified in the monitoring request.

4.The system administrator (or Hewlett-Packard service provider) receives the messages, corrects the problem, and returns the hardware to its normal operating condition.

5.If the Peripheral Status Monitor (PSM) has been properly configured, events are also processed by the PSM. The PSM changes the device status to DOWN if the event is serious enough. The change in device status is passed to EMS, which in turn alerts MC/ServiceGuard. The DOWN status will cause MC/ServiceGuard to failover any package associated with the failed hardware resource.

NOTE The Difference Between Hardware Event Monitoring and Hardware Status Monitoring

Hardware event monitoring is the detection of events experienced by a hardware resource. It is the task of the EMS Hardware Monitors to detect hardware events. Events are temporary in the sense that the monitor detects them but does not remember them. Of course the event itself may not be temporary—a failed disk will likely remain failed until it is replaced.

Hardware status monitoring is an extension of event monitoring that converts an event to a change in device status. This conversion, performed by the Peripheral Status Monitor, provides a mechanism for remembering the occurrence of an event by storing the resultant status. This persistence provides compatibility with applications such as MC/ServiceGuard, which require a change in device status to manage high availability packages.

Chapter 1

13

Image 13

Contents Manufacturing Part Number B6191-90028 September EMS Hardware Monitors Users GuideLegal Notices Printing History Page Contents Hardware Monitor Configuration Files Using the Peripheral Status MonitorSpecial Procedures Contents About This Manual Related Web Site Introduction Hardware Monitoring Overview What is Hardware Monitoring?Components Involved in Hardware Monitoring How Does Hardware Monitoring Work?Benefits of Hardware Monitoring Products Supported by Hardware Monitors Tips for Hardware Monitoring Hardware Monitoring Terms Hardware Monitoring TermsTerm Definition Hardware Monitoring Terms Introduction Hardware Monitoring Overview Chapter Installing and Using Monitors Steps Involved Steps for Installing and Configuring Hardware Monitoring Supported System Configuration Installing EMS Hardware MonitorsRemoving EMS Hardware Monitors Disk Arrays Checking for Special RequirementsProduct Model/Product Special Number Requirements Tape Products all supported by the Scsi Tape Devices Monitor Disk ProductsFibre Channel Scsi Multiplexers High Availability Storage SystemsFibre Channel Arbitrated Loop FC-AL Hub Fibre Channel AdaptersProduct Model/Product Special Requirements Number Memory Fibre Channel SwitchSystem Others Interface CardsWhat Is a Monitoring Request? Using Hardware Monitoring RequestsSome Monitoring Request Examples Building a Monitoring Request To run the Monitoring Request Manager, type Running the Monitoring Request ManagerEnabling Hardware Event Monitoring 13 Default Monitoring Requests for Each Monitor Default Monitoring RequestsSeverity Levels Notification Method To list the descriptions of available monitors Listing Monitor DescriptionsTo view or show the current monitoring requests Viewing Current Monitoring RequestsTo add a monitoring request Adding a Monitoring RequestSetting Description 14 Monitoring Requests Configuration Settings15 Event Severity Levels Event Description MC/ServiceGuard Severity Response LevelEvent Severity Levels Example of Adding a Monitoring Request == ADD Comment To modify a monitoring request Modifying Monitoring RequestsVerifying Hardware Event Monitoring Events = Checking Detailed Monitoring StatusSample Event Message Retrieving and Interpreting Event MessagesTo delete a monitoring request Deleting Monitoring RequestsDisabling Hardware Event Monitoring To disable hardware event monitoringDetailed Description Hardware Monitoring Architecture Detailed Picture of Hardware MonitoringHardware Monitoring Request Manager Components from Three Different ApplicationsPolling or Asynchronous? EMS Hardware Event MonitorStartup Client Peripheral Status Monitor PSM Event Monitoring Service EMS1File Locations File LocationsDirectories and Files Description Monitoring Startup Process Startup Process in DetailDisabling Monitoring Event Decoding Asynchronous Event Detection in DetailAsynchronous Event Detection Process Event Polling in Detail FC-AL Hub and FC Switch Polling ProcessesMemory Monitor Polling Monitoring Polling Process Memory Monitor Polling Process Detailed Picture of Hardware Monitoring Chapter Using the Peripheral Status Monitor Peripheral Status Monitor Overview How Does the PSM Work? Peripheral Status Monitor PSM States PSM ComponentsPSM Resource Paths PSM StatusHow Does the PSM Work? Chapter To create a package resource dependency Configuring Package Dependencies using SAMResourcepollinginterval Resourceupvalue =UP To create a PSM monitoring request Creating EMS Monitoring Requests for PSMFrom the Actions menu select Add Monitoring Request Setting the Polling Interval Polling Interval Specifying When to Send Event NotifyMonitoring Request Parameters Determining the Frequency of Events OptionsOpcmsg ITO Selecting Protocols for Sending Events Notify ViaCritical Major Minor Normal To set the opcmsg ITOTCP and UDP To set the Snmp trapTo set the TCP or UDP conditions To set for email notificationAdding a Notification Comment Comment Copying Monitoring Requests To change the monitoring parameters of a request To remove monitoring requests Removing Monitoring RequestsTo view the parameters for a monitoring request Viewing Monitoring RequestsFrom the Actions menu select View Monitoring Request To restore the operating state of a resource to UP Using the setfixed Utility to Restore Hardware UP StateExample 4-1 Example of Using setfixed Using the Peripheral Status Monitor Hardware Monitor Configuration Files Monitor Configuration Files Setting Values Description Monitor Configuration File EntriesFile Names File FormatInterval must be a Eventnum must be aFrequency must be a Event Definition Sample Global Configuration FileSeverity Action Polling Interval= Communication Device Sample Monitor-Specific Configuration File#POLLINTERVAL Startup Configuration File Keyword Values Description Startup Configuration File EntriesUDP Default Monitoring Requests Default File EntriesDescription Entry Peripheral Status Monitor PSM Configuration File Considerations for Modifying the PSM Configuration File Monitorresourcename PSM Configuration File FieldsCritical Downseverityope Example File Entries Special Procedures Fibre Channel Arbitrated Loop Hub Monitor Configuring the FC-AL Monitor Configuration File Initial Monitor ConfigurationAdding or Removing an FC-AL Hub Configuration FilesThis setting is required Setting Default Description ValuePSM Configuration File Fibre Channel Switch Monitor Configuring the FC Switch Monitor Configuration File Adding or Removing an FC SwitchChanging the FC Switch Monitoring Configuration 2PSM Configuration File Fields Special Procedures 112 Index 114 115