HP EMS HARDWARE S B6191-90028 Retrieving and Interpreting Event Messages, Sample Event Message

Page 48

Installing and Using Monitors

Retrieving and Interpreting Event Messages

Retrieving and Interpreting Event Messages

Event messages generated by hardware monitoring can be delivered using a variety of notification methods. To simplify receiving event messages you may want to use the email and/or textfile notification methods. Both of these methods, which are included in the default monitoring, receive the entire content of the message so you can read it immediately.

Methods such as console, syslog, and SNMP alert you to the occurrence of an event but do not deliver the entire message. You are required to retrieve it using the resdata utility. For these methods, the event notification will include a message similar to the following:

Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 392036357 -r /storage/events/tapes/SCSI_tape/10_12_5.0.0 -n 392036353 -a

It is important that you execute the command exactly as indicated, including the two critical number fields that are indexes for the resdata entries.

Sample Event Message

The following is a portion of a sample event message.

>Event Monitoring Service Event Notification %<

Notification Time: Wed Sep 9 10:48:30 1998

hpbs8684 sent Event Monitor notification information:

/storage/events/disks/default/10_4_4.0.0 is >= 1. Its current value is CRITICAL(5).

Event data		from monitor:
Event Time		: Wed Sep 9 10:48:30 1998
Hostname :		hpbs8684.boi.hp.com	IP Address	: 15.62.120.25
Event Id	:	0x0035f6b15e00000000	Monitor	: disk_em
Event #	:	100037	Event Class : I/O
Severity :		CRITICAL

Disk at hardware path 10/4/4.0.0 : Media failure

Associated OS error log entry id(s):

000000000000000000

Description of Error:

The device was unsuccessful in reading data for the current I/O request due to an error on the medium. The data could not be recovered. The request was likely processed in a way which could cause damage to or loss of data.

Probable Cause / Recommended Action:

The medium in the device is flawed. If the medium is removable, replace the medium with a fresh one. Alternatively, if the medium is not removable, the device has experienced a hardware failure.

Repair or replace the device, as necessary.

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

48

Chapter 2

Image 48

Contents EMS Hardware Monitors Users Guide Manufacturing Part Number B6191-90028 SeptemberLegal Notices Printing History Page Contents Using the Peripheral Status Monitor Hardware Monitor Configuration FilesSpecial Procedures Contents About This Manual Related Web Site Introduction What is Hardware Monitoring? Hardware Monitoring OverviewHow Does Hardware Monitoring Work? Components Involved in Hardware MonitoringBenefits 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 Installing EMS Hardware Monitors Supported System ConfigurationRemoving EMS Hardware Monitors Checking for Special Requirements Disk ArraysProduct Model/Product Special Number Requirements Disk Products Tape Products all supported by the Scsi Tape Devices MonitorHigh Availability Storage Systems Fibre Channel Scsi MultiplexersFibre Channel Adapters Fibre Channel Arbitrated Loop FC-AL HubProduct Model/Product Special Requirements Number Fibre Channel Switch MemorySystem Interface Cards OthersUsing Hardware Monitoring Requests What Is a Monitoring Request?Some Monitoring Request Examples Building a Monitoring Request Running the Monitoring Request Manager To run the Monitoring Request Manager, typeEnabling Hardware Event Monitoring Default Monitoring Requests 13 Default Monitoring Requests for Each MonitorSeverity Levels Notification Method Listing Monitor Descriptions To list the descriptions of available monitorsViewing Current Monitoring Requests To view or show the current monitoring requestsAdding a Monitoring Request To add a monitoring request14 Monitoring Requests Configuration Settings Setting DescriptionEvent Description MC/ServiceGuard Severity Response Level 15 Event Severity LevelsEvent Severity Levels Example of Adding a Monitoring Request == ADD Comment Modifying Monitoring Requests To modify a monitoring requestVerifying Hardware Event Monitoring Checking Detailed Monitoring Status Events =Retrieving and Interpreting Event Messages Sample Event MessageDeleting Monitoring Requests To delete a monitoring requestTo disable hardware event monitoring Disabling Hardware Event MonitoringDetailed Description Detailed Picture of Hardware Monitoring Hardware Monitoring ArchitectureComponents from Three Different Applications Hardware Monitoring Request ManagerEMS Hardware Event Monitor Polling or Asynchronous?Startup Client Event Monitoring Service EMS Peripheral Status Monitor PSMFile Locations 1File LocationsDirectories and Files Description Startup Process in Detail Monitoring Startup ProcessDisabling Monitoring Asynchronous Event Detection in Detail Event DecodingAsynchronous Event Detection Process FC-AL Hub and FC Switch Polling Processes Event Polling in DetailMemory 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 Components PSM StatesPSM Resource Paths PSM StatusHow Does the PSM Work? Chapter Configuring Package Dependencies using SAM To create a package resource dependencyResourcepollinginterval Resourceupvalue =UP Creating EMS Monitoring Requests for PSM To create a PSM monitoring requestFrom the Actions menu select Add Monitoring Request Specifying When to Send Event Notify Setting the Polling Interval Polling IntervalMonitoring Request Parameters Determining the Frequency of Events OptionsSelecting Protocols for Sending Events Notify Via Opcmsg ITOCritical Major Minor Normal To set the opcmsg ITOTo set the Snmp trap TCP and UDPTo 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 Removing Monitoring Requests To remove monitoring requestsViewing Monitoring Requests To view the parameters for a monitoring requestFrom the Actions menu select View Monitoring Request Using the setfixed Utility to Restore Hardware UP State To restore the operating state of a resource to UPExample 4-1 Example of Using setfixed Using the Peripheral Status Monitor Hardware Monitor Configuration Files Monitor Configuration Files Monitor Configuration File Entries Setting Values DescriptionFile Names File FormatEventnum must be a Interval must be aFrequency must be a Sample Global Configuration File Event DefinitionSeverity Action Polling IntervalSample Monitor-Specific Configuration File = Communication Device#POLLINTERVAL Startup Configuration File Startup Configuration File Entries Keyword Values DescriptionUDP Default File Entries Default Monitoring RequestsDescription Entry Peripheral Status Monitor PSM Configuration File Considerations for Modifying the PSM Configuration File PSM Configuration File Fields MonitorresourcenameCritical Downseverityope Example File Entries Special Procedures Fibre Channel Arbitrated Loop Hub Monitor Initial Monitor Configuration Configuring the FC-AL Monitor Configuration FileConfiguration Files Adding or Removing an FC-AL HubSetting Default Description Value This setting is requiredPSM Configuration File Fibre Channel Switch Monitor Adding or Removing an FC Switch Configuring the FC Switch Monitor Configuration FileChanging the FC Switch Monitoring Configuration 2PSM Configuration File Fields Special Procedures 112 Index 114 115