Configuring Monitors with the EMS GUI

Most of the EMS hardware monitors are configured by running monitoring request manager: /etc/opt/resmon/lbin/monconfig.

The Kernel Resource (krmond) and the Peripheral Status Monitor (PSM) are configured differently. To configure these two monitors, you use the EMS graphical user interface (GUI).

An overview of the process is given in this Web page. For details, see the manual, "Using the Event Monitoring Service" (Part Number B7612-90015) available at: http://docs.hp.com/hpux/ha/index.html

Procedure

Use the EMS GUI, found in the Resource Management area of SAM, to create monitoring requests for resources and targets. The EMS GUI starts from the graphical version of SAM. Click through and select from the various screens to define your monitoring request. The options include:

1. Select resources to be monitored. The full path of a resource includes the resource class hierarchy and instance.
   • The Kernel Resource Monitor (krmond). Examples of the kernel parameters you can monitor and the path you need to specify to control the monitor:

     Parameter                      Path
     ncallout  /system/kernel_resource/misc/ncallout
     nfile     /system/kernel_resource/file_system/nfile
     nflocks   /system/kernel_resource/file_system/nflocks
     nproc     /system/kernel_resource/process_management/nproc
     

   • Peripheral Status Monitor (PSM). In almost all cases, the resource names for PSM are exactly the same resource names as for the hardware monitors, but with the "events" part of the path changed to "status." See the resource names on the EMS monitors datasheets; there will be instances below these.

     The specific resource instance is almost always a hardware path to a device, although in some cases it is a serial number for a device, a WWN for a device, the IP address of a device, the hostnmae of a system, etc. It depends on what devices are on the system and how you have configured the hardware monitors that are to be watched.

     For example: a disk resource for hardware monitors would be /storage/events/disksk/default/X_X_X.x.x, where X_X_X.x.x is a specific hardware path. The PSM resource name would be: /storage/status/disksk/default/X_X_X.x.x

2. Specify when to collect value. Select either and/or all:
   • When value is ...

     If you are setting up a request for an asynchronous monitor, this is the only option available.

   • When value changes
   • At each interval

     Select this option to send an event periodically, regardless of the value.

     Define a polling interval that is appropriate to your system performance and reaction time needs. See next step.

3. Specify a polling interval for how often the monitor checks the resource and reports the value.

   This applies only to non-asynchronous monitors.

4. Specify how often the monitor should check and send notification about the resource:
   • the Initial option immediately checks and returns the resource value regardless of threshold conditions
   • the Repeat option checks and returns the resource value at each polling interval if threshold conditions have been met.
   • the Return option checks and returns the resource value after a threshold condition has been resolved and the threshold condition is no longer true.
5. Specify the notification protocols. Notification protocols include such methods as:
   • opcmsg (IT/O), by severity or map severity from values listed
   • TCP or UDP
   • SNMP trap, by severity or map severity from values listed
   • email
   • console
   • syslog
   • textlog

/ Diagnostics HOME