HP EMS HARDWARE S B6191-90028 manual EMS Hardware Event Monitor, Polling or Asynchronous?

Page 54

Detailed Description

The Detailed Picture of Hardware Monitoring

EMS Hardware Event Monitor

The EMS hardware event monitor is the key component in the event monitoring architecture. An event monitor is a daemon process, running in the background continuously. The event monitor watches all instances of the hardware resources it supports, waiting for the occurrence of any failures or other unusual events. The monitor may use polling, asynchronous event detection, or both.

When an event occurs, the monitor alerts EMS and passes it the appropriate event message. The event monitor also tells the PSM about the event. If the event is serious enough the PSM will change the status of the hardware to DOWN.

Two configuration files control the operation of each hardware event monitor:

•Global monitor configuration file. The settings defined in this file are used for all hardware event monitors, unless overridden by a monitor-specific file.

•Monitor-specific configuration file. Each monitor includes its own configuration file with optimized settings. The settings defined in the monitor-specific file override corresponding settings defined in the global configuration file.

NOTE

The settings defined by the monitor-specific configuration file have been carefully selected to

 

meet the needs of most users. It is possible to alter these settings, but it is not recommended

 

unless you fully understand the implications of doing so. For information on modifying the

 

monitor-specific configuration files, see Chapter 5, “Hardware Monitor Configuration Files.”

 

 

 

 

NOTE

As of the June 2000 release, several of the hardware monitors have been converted to be

 

“multiple-view” (Predictive-enabled). These monitors use a different file for configuration, the

 

Client Configuration File.

 

 

Polling or Asynchronous?

Hardware event monitors employ two methods of tracking events: polling and asynchronous event detection. A monitor may use one or both of the methods to detect events.

Using polling, a monitor checks the status of its hardware resources at regular intervals, typically 60 minutes. Any unusual condition reported by the hardware will trigger an event by the monitor. The polling interval is selected to provide reasonable detection without impacting system performance. The main disadvantage of polling is that an event will not be detected until the next time the resource is polled, which makes the system vulnerable to another hardware failure.

Asynchronous detection allows a monitor to detect an event when it occurs, usually during an I/O to the device. An event typically results in a log entry made by the hardware device driver. The monitor detects the log entry and initiates the event notification. Asynchronous event monitoring allows immediate notification and response to a critical situation.

Startup Client

The startup client launches and configures the hardware event monitors each time the system is started, or following the execution of the IOSCAN utility. The startup client starts each monitor and configures its hardware resources using a set of default monitoring requests.

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,

54

Chapter 3

Page 53 Page 55
Image 54
Page 53 Page 55
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 Resource Paths PSM ComponentsPSM States 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 Monitoring Request Parameters Specifying When to Send Event NotifySetting the Polling Interval Polling Interval Determining the Frequency of Events OptionsCritical Major Minor Normal Selecting Protocols for Sending Events Notify ViaOpcmsg ITO To set the opcmsg ITOTo set the TCP or UDP conditions To set the Snmp trapTCP and UDP 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 File Names Monitor Configuration File EntriesSetting Values Description File FormatEventnum must be a Interval must be aFrequency must be a Severity Action Sample Global Configuration FileEvent Definition 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
Top Page Image Contents