HP EMS HARDWARE S B6191-90028 manual Event Severity Levels

Page 41

Installing and Using Monitors

Adding a Monitoring Request

Table 2-14 Monitoring Requests Configuration Settings

Setting

Description

 

 

Notification

The following notification methods are available.

Method

EMAIL* - sends notification to the specified email address

 

 

TEXTLOG* - sends notification to specified file

 

SNMP - sends notification using SNMP traps

 

CONSOLE - sends notification to the system console

 

TCP - sends notification to the specified target host and port

 

UDP - sends notification to the specified target host and port

 

OPC - sends notification to OpenView ITO applications (available

 

only on systems with OpenView installed).

 

SYSLOG - sends notification to the system log

 

Only one notification method can be selected for each monitor

 

request, consequently you will need to create multiple requests to

 

direct event notification to different targets. * These are the only

 

methods that deliver the entire content of the event message. The

 

remaining methods alert you to the occurrence of an event, but

 

require you to retrieve the complete message content using resdata

 

explained later in this chapter.

 

 

Table 2-15 Event Severity Levels

Event

Description

MC/ServiceGuard

Severity

 

Response

Level

 

 

 

 

 

Critical

An event that will or has already

If MC/ServiceGuard is

 

caused data loss, system down time,

installed and this is a

 

or other loss of service. System

critical component, a

 

operation will be impacted and

package fail-over WILL

 

normal use of the hardware should

occur.

 

not continue until the problem is

 

 

corrected. Immediate action is

 

 

required to correct the problem.

 

 

 

 

Serious

An event that may cause data loss,

If MC/ServiceGuard is

 

system down time, or other loss of

installed and this is a

 

service if left uncorrected. System

critical component, a

 

operation and normal use of the

package fail-over WILL

 

hardware may be impacted. The

occur.

 

problem should be repaired as soon as

 

 

possible.

 

 

 

 

Major

An event that could escalate to a

If MC/ServiceGuard is

Warning

Serious condition if not corrected.

installed and this is a

 

System operation should not be

critical component, a

 

impacted and normal use of the

package fail-over WILL

 

hardware can continue. The problem

NOT occur.

 

should be repaired at a convenient

 

 

time.

 

 

 

 

Chapter 2

41

Image 41
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 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 MonitorsRemoving 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 ProductsFibre Channel Scsi Multiplexers High Availability Storage SystemsProduct Model/Product Special Requirements Number Fibre Channel AdaptersFibre Channel Arbitrated Loop FC-AL Hub System Fibre Channel SwitchMemory Others Interface CardsSome 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 ManagerEnabling 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 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 ApplicationsStartup Client EMS Hardware Event MonitorPolling or Asynchronous? Peripheral Status Monitor PSM Event Monitoring Service EMSDirectories and Files Description File Locations1File Locations Monitoring Startup Process Startup Process in DetailDisabling Monitoring Event Decoding Asynchronous Event Detection in DetailAsynchronous 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 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 From the Actions menu select Add Monitoring Request Creating EMS Monitoring Requests for PSMTo create a PSM 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 RequestsFrom 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 Setting Values Description Monitor Configuration File EntriesFile Names File FormatFrequency must be a Eventnum must be aInterval 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 Description Entry Default File EntriesDefault Monitoring Requests 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