Event Decoding | HP EMS HARDWARE S B6191-90028 guide

Detailed Description

The Detailed Picture of Hardware Monitoring

Asynchronous Event Detection (in Detail)

The following steps describe the process involved in asynchronous event detection. The asynchronous detection is illustrated in Figure 3-3 on page 60.

1.A device driver detects an error during an I/O with the device.

2.The device driver passes the error information, including SCSI sense data, to the diag2 pseudo driver, which adds information indicating the instance of the driver logging the error to the message header. The error message is then passed to the diaglogd daemon used by STM to monitor recoverable errors.

3.Diaglogd uses the instance information to retrieve hardware path, product type, product name, and driver name information from the message header. This information is used to determine which monitor, if any, the information should be passed to. The error message is also written to the raw error log (/var/stm/logs/os/log#.raw.cur).

During startup, each asynchronous monitor registered with diaglogd, indicating what types of errors the monitor wants to receive. The monitor may specify a product description, product number, or driver name. If a monitor is registered to receive the error, the message is passed to it.

4.The monitor decodes the error to determine if an event should be reported. If an event should be reported, the monitor passes the event message to Event Monitoring Service (EMS).

5.EMS uses the current monitoring requests for the monitor to determine what action to take. Based on the requests, the event is reported using the specified notification method(s).

Event Decoding

In addition to monitoring hardware, many of the EMS hardware monitors also act as message decoders for logtool, which is used to read the contents of the raw error log. If the error uses an EMS hardware monitor as the decoder, logtool launches a new instance of the monitor to perform the decoding. In this way all events that have occurred on the device, including those IGNORED by the monitor, can be viewed.

Chapter 3

59

Image 59

HP EMS HARDWARE S B6191-90028 manual Asynchronous Event Detection in Detail, Event Decoding

Contents

Manufacturing Part Number B6191-90028 September EMS Hardware Monitors Users Guide Legal Notices Printing History Page Contents Hardware Monitor Configuration Files Using the Peripheral Status Monitor Special 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 Term Definition Hardware Monitoring TermsHardware Monitoring Terms 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 Monitors Removing EMS Hardware Monitors Product Model/Product Special Number Requirements Checking for Special RequirementsDisk Arrays Tape Products all supported by the Scsi Tape Devices Monitor Disk Products Fibre Channel Scsi Multiplexers High Availability Storage Systems Product Model/Product Special Requirements Number Fibre Channel AdaptersFibre Channel Arbitrated Loop FC-AL Hub System Fibre Channel SwitchMemory Others Interface Cards Some Monitoring Request Examples Using Hardware Monitoring RequestsWhat Is a Monitoring Request? Building a Monitoring Request To run the Monitoring Request Manager, type Running the Monitoring Request Manager Enabling Hardware Event Monitoring Severity Levels Notification Method Default Monitoring Requests13 Default Monitoring Requests for Each Monitor To list the descriptions of available monitors Listing Monitor Descriptions To view or show the current monitoring requests Viewing Current Monitoring Requests To add a monitoring request Adding a Monitoring Request Setting Description 14 Monitoring Requests Configuration Settings 15 Event Severity Levels Event Description MC/ServiceGuard Severity Response Level Event Severity Levels Example of Adding a Monitoring Request == ADD Comment To modify a monitoring request Modifying Monitoring Requests Verifying Hardware Event Monitoring Events = Checking Detailed Monitoring Status Sample Event Message Retrieving and Interpreting Event Messages To delete a monitoring request Deleting Monitoring Requests Disabling Hardware Event Monitoring To disable hardware event monitoring Detailed Description Hardware Monitoring Architecture Detailed Picture of Hardware Monitoring Hardware Monitoring Request Manager Components from Three Different Applications Startup Client EMS Hardware Event MonitorPolling or Asynchronous? Peripheral Status Monitor PSM Event Monitoring Service EMS Directories and Files Description File Locations1File Locations Monitoring Startup Process Startup Process in Detail Disabling Monitoring Event Decoding Asynchronous Event Detection in Detail Asynchronous Event Detection Process Memory Monitor Polling FC-AL Hub and FC Switch Polling ProcessesEvent Polling in Detail 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 Status PSM ComponentsPSM States PSM Resource Paths How Does the PSM Work? Chapter To create a package resource dependency Configuring Package Dependencies using SAM Resourcepollinginterval Resourceupvalue =UP From the Actions menu select Add Monitoring Request Creating EMS Monitoring Requests for PSMTo create a PSM monitoring request Determining the Frequency of Events Options Specifying When to Send Event NotifySetting the Polling Interval Polling Interval Monitoring Request Parameters To set the opcmsg ITO Selecting Protocols for Sending Events Notify ViaOpcmsg ITO Critical Major Minor Normal To set for email notification To set the Snmp trapTCP and UDP To set the TCP or UDP conditions Adding a Notification Comment Comment Copying Monitoring Requests To change the monitoring parameters of a request To remove monitoring requests Removing Monitoring Requests From the Actions menu select View Monitoring Request Viewing Monitoring RequestsTo view the parameters for a monitoring request Example 4-1 Example of Using setfixed Using the setfixed Utility to Restore Hardware UP StateTo restore the operating state of a resource to UP Using the Peripheral Status Monitor Hardware Monitor Configuration Files Monitor Configuration Files File Format Monitor Configuration File EntriesSetting Values Description File Names Frequency must be a Eventnum must be aInterval must be a Polling Interval Sample Global Configuration FileEvent Definition Severity Action = Communication Device Sample Monitor-Specific Configuration File #POLLINTERVAL Startup Configuration File Keyword Values Description Startup Configuration File Entries UDP Description Entry Default File EntriesDefault Monitoring Requests Peripheral Status Monitor PSM Configuration File Considerations for Modifying the PSM Configuration File Monitorresourcename PSM Configuration File Fields Critical Downseverityope Example File Entries Special Procedures Fibre Channel Arbitrated Loop Hub Monitor Configuring the FC-AL Monitor Configuration File Initial Monitor Configuration Adding or Removing an FC-AL Hub Configuration Files This setting is required Setting Default Description Value PSM Configuration File Fibre Channel Switch Monitor Configuring the FC Switch Monitor Configuration File Adding or Removing an FC Switch Changing the FC Switch Monitoring Configuration 2PSM Configuration File Fields Special Procedures 112 Index 114 115