HP EMS HARDWARE S B6191-90028 manual #Pollinterval

Page 91

Hardware Monitor Configuration Files

Monitor Configuration Files

#POLL_INTERVAL

5

#

polling interval in

minutes

#REPEAT_FREQUENCY

1440

#

in minutes, for one

day

#****************************************************************************#

#* This list of default

actions for each

severity also

appears in the

*#

#*

global configuration

file, and should

not generally

appear here.

*#

#*

It is shown for documentation purposes.

 

*#

#****************************************************************************#

#SEVERITY_ACTION

INFORMATION

NOTIFY

#SEVERITY_ACTION

MINOR_WARNING

NOTIFY

#SEVERITY_ACTION

MAJOR_WARNING

NOTIFY

#SEVERITY_ACTION

SERIOUS

NOTIFY

#SEVERITY_ACTION

CRITICAL

NOTIFY

#****************************************************************************# #* cfg-verb event# severity- action- -description- *# #****************************************************************************#

DEFINE_EVENT

101

CRITICAL

DEFAULT # The disk is

indicating a fault

DEFINE_EVENT

102

CRITICAL

DEFAULT # The disk is

not on the FC link

DEFINE_EVENT

201

CRITICAL

DEFAULT # The power supply has faulted

DEFINE_EVENT

202

CRITICAL

DEFAULT # The power supply is not recieving adequate AC

DEFINE_EVENT

301

CRITICAL

DEFAULT # The fan is not providing cooling

DEFINE_EVENT

302

CRITICAL

DEFAULT # Temperature

has exceeded critial threshold

DEFINE_EVENT

303

MAJOR_WARNING

DEFAULT # Temperature

has exceeded warning threshold

DEFINE_EVENT

304

CRITICAL

DEFAULT # Temperature

has exceeded low critial threshold

DEFINE_EVENT

305

MAJOR_WARNING DEFAULT # Temperature

has exceeded low warning threshold

DEFINE_EVENT

306

MAJOR_WARNING

DEFAULT # Temperature

sensor may have failed

DEFINE_EVENT

401

CRITICAL

DEFAULT # The enclosure services controller has failed

DEFINE_EVENT

501

CRITICAL

DEFAULT # The SCSI port/transceiver has lost the link

DEFINE_EVENT

502

CRITICAL

DEFAULT # The transmit signal has been lost

DEFINE_EVENT

601

CRITICAL

DEFAULT # Over voltage critical threshold exceeded

DEFINE_EVENT

602

MAJOR_WARNING

DEFAULT # Over voltage warning threshold exceeded

DEFINE_EVENT

603

CRITICAL

DEFAULT # Under voltage critical threshold exceeded

DEFINE_EVENT

604

MAJOR_WARNING DEFAULT # Under voltage warning threshold exceeded

DEFINE_EVENT

605

MAJOR_WARNING DEFAULT # Voltage sensor may have failed

Chapter 5

91

Image 91
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 Status PSM ComponentsPSM States PSM Resource PathsHow 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 Determining the Frequency of Events Options Specifying When to Send Event NotifySetting the Polling Interval Polling Interval Monitoring Request ParametersTo set the opcmsg ITO Selecting Protocols for Sending Events Notify ViaOpcmsg ITO Critical Major Minor NormalTo set for email notification To set the Snmp trapTCP and UDP To set the TCP or UDP conditionsAdding 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 File Format Monitor Configuration File EntriesSetting Values Description File NamesInterval must be a Eventnum must be aFrequency 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 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