HP EMS HARDWARE S B6191-90028 Startup Configuration File Entries, Keyword Values Description

Page 93

Hardware Monitor Configuration Files

Startup Configuration File

Considerations for Modifying the Startup Configuration File Settings

While you can edit the contents of the startup configuration file directly, the better approach is to use the Hardware Monitoring Request Manager (monconfig) to create and manage your monitoring requests. Using the monitoring request manager you can create requests for multiple monitors simultaneously. And the Hardware Monitoring Request Manager ensures that all request entries are formatted correctly.

The only benefit that editing the configuration file offers is that you can use the COMMENT setting to add information that will be included with the event.

Table 5-2

Startup Configuration File Entries

 

 

 

 

 

 

Keyword

Values

Description

 

 

 

 

 

MONITOR (required)

A valid event monitor

Identifies the hardware

 

 

resource path

event monitor to which

 

 

 

the entry applies. All

 

 

 

entries must use the

 

 

 

resource path for the

 

 

 

monitor being

 

 

 

configured.

 

 

 

Note: This must the first

 

 

 

keyword in each entry

 

 

 

 

 

Criteria Threshold (required)

Valid values include:

Defines the severity

 

 

CRITICAL

level used as the

 

 

notification criteria

 

 

SERIOUS

 

 

threshold.

 

 

MAJOR_WARNING

 

 

 

 

 

MINOR_WARNING

 

 

 

INFORMATIONAL

 

 

 

 

 

 

Criteria Operator (required)

Valid operators are:

This value identifies the

 

 

%< (less than)

arithmetic operator

 

 

used with the criteria

 

 

%<= (less than or equal to

 

 

threshold to control

 

 

)

 

 

what events are

 

 

> (greater than)

 

 

reported. The operator

 

 

>= (greater than or equal

 

 

treats each severity

 

 

to)

 

 

level as a numeric value

 

 

! (not equal to)

 

 

assigned as follows:

 

 

 

 

 

 

Critical = 5

 

 

 

Serious = 4

 

 

 

Major warning = 3

 

 

 

Minor warning = 2

 

 

 

Informational = 1

 

 

 

The event severity

 

 

 

received is the left

 

 

 

operand and the

 

 

 

Criteria Threshold value

 

 

 

is the right operand.

 

 

 

 

Chapter 5

93

Image 93
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 Checking for Special Requirements Disk ArraysProduct 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 Adapters Fibre Channel Arbitrated Loop FC-AL HubProduct Model/Product Special Requirements Number Fibre Channel Switch MemorySystem Others Interface CardsUsing Hardware Monitoring Requests What Is a Monitoring Request?Some Monitoring Request Examples Building a Monitoring Request To run the Monitoring Request Manager, type Running the Monitoring Request ManagerEnabling Hardware Event Monitoring Default Monitoring Requests 13 Default Monitoring Requests for Each MonitorSeverity 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 ApplicationsEMS Hardware Event Monitor Polling or Asynchronous?Startup Client Peripheral Status Monitor PSM Event Monitoring Service EMSFile Locations 1File LocationsDirectories and Files Description Monitoring Startup Process Startup Process in DetailDisabling Monitoring Event Decoding Asynchronous Event Detection in DetailAsynchronous 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 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 Creating EMS Monitoring Requests for PSM To create a PSM monitoring requestFrom the Actions menu select Add 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 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 Setting Values Description Monitor Configuration File EntriesFile Names File FormatEventnum must be a Interval must be aFrequency 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 Default File Entries Default Monitoring RequestsDescription 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