HP EMS HARDWARE S B6191-90028 manual PSM Components, PSM States, PSM Resource Paths, PSM Status

Page 69

Using the Peripheral Status Monitor

How Does the PSM Work?

PSM Components

The PSM comprises the following components, which are installed along with the hardware event monitors. Each component has its own man page containing detailed information about its operation.

•psmctd - the Peripheral Status Client/Target daemon used to monitor the state of hardware resources.

•psmmon - the utility used to monitor the state of resources recognized by the psmctd daemon.

•set_fixed - the utility used to manually change the status of a hardware resource from DOWN to UP. Used only for monitors that do not the have capability to perform this operation automatically.

PSM States

The PSM can assume the three status conditions shown in the following table. These are the values you can use to define a monitoring request.

Table 4-1

PSM Status

 

 

 

 

 

Condition

Interpretation

 

 

 

 

Up

The hardware is operating normally.

 

 

 

 

Down

An event has occurred that indicates a

 

 

failure with the hardware.

 

 

 

 

Unknown

Cannot determine the state of the

 

 

hardware. This state is treated as DOWN by

 

 

the PSM.

 

 

 

PSM Resource Paths

Selecting a hardware resource for PSM monitoring requires the selection of the correct resource path. The resource class path is the means by which EMS identifies system resources. Resources are divided into classes and subclasses based on their type or function. For example, the resource classes for PSM monitoring include adapters, connectivity, and storage.

The resource path ends with the resource instance, which uniquely identifies a hardware resource. There is an instance for each individual hardware resource supported by the monitor. The resource instance is typically the hardware path to the device (e.g., 10_12_5.0.0), but it may also be a device name as in the case of AutoRAID disk arrays.

EMS monitoring requests are applied at the resource instance level. This is unlike event monitoring requests created using the Hardware Monitoring Request Manager, which are applied at the monitor level. Thus when creating an EMS monitoring request you must select the specific resource you want to monitor. An all (*) option allows you to apply a PSM monitoring request to all current instances of the hardware. A monitoring request will not be applied to new hardware added to the system after the request is created.

PSM resource class path names are structured as follows:

/top_level_resource_class/status/subclass/subclass/instance

For example, the PSM resource class path for a SCSI tape device at hardware path 10_12_5.0.0 would be:

/storage/status/tapes/SCSI_tape/10_12_5.0.0

The PSM resource class path for an AutoRAID disk array with an ID of 000000105781 would be:

/storage/status/disk_arrays/AutoRAID/000000105781

Chapter 4

69

Page 68 Page 70
Image 69
Page 68 Page 70
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
Top Page Image Contents