Verifying EMS Hardware Monitors

You can verify the operation of some EMS Hardware Monitors by executing the command:

/opt/resmon/bin/send_test_event -v MONITOR_NAME

where MONITOR_NAME is the name of the executable file for the monitor (for example: dm_memory, disk_em, etc.) You can find the names of the executables with the command:

ls /usr/sbin/stm/uut/bin/tools/monitor

IF THE OPERATION IS SUCCESSFUL...

then event 103 (with a severity level of 1 "INFORMATION") will be generated.

The send_test_event command (with the -v parameter) will send progress messages ending with lines such as the following:

There is one resource configured below /system/events/core_hw:
Resource Class
        /system/events/core_hw/core_hw

An entry for this test event will be added to the event log at /var/opt/resmon/log/event.log. (All events are logged to this file.) You can view this event entry with the command:

vi /var/opt/resmon/log/event.log

If the monitor has been configured so that events of severity level = 1 (INFORMATION) will send messages to other notification targets (for example email to the "root" user), then messages for the event should appear at those targets as well.

IF THE OPERATION IS NOT SUCCESSFUL...

• The MONITOR_NAME you entered may not exist. The send_test_event error message will read something like:

  send_test_event: Failed to find monitor name in sapcfg files.
  

  You must use the name of the executable for the EMS Hardware Monitor. These names appear in /usr/sbin/stm/uut/bin/tools/monitor .
• The MONITOR_NAME you entered may not support the send_test_event command. You will not find an entry for the test event in the log /var/opt/resmon/log/event.log.

  Only monitors which are "Multiple-view" (Predictive-enabled) will respond to the send_test_event command. This feature was added to some monitors in the June 2000 release of the diagnostics. With each new release, more monitors are updated to support this feature.

  The monitors which are Multiple-view (Predictive-enabled) have a *.clcfg file in the /var/stm/config/tools/monitor/ directory. You can see these files with the command:

  ls  /var/stm/config/tools/monitor/*clcfg
  

• The MONITOR_NAME you entered may not be running. For send_test_event to work, monitors must be enabled and configured; and there must be hardware on the system for which the monitor was designed. For example, if there is no Uninterruptible Power Supply (UPS), then the dm_ups monitor won't be running. If this is the case, you may see output from send_test_event like:

  TYPE:   /system/events/ups is not a valid resource name
  

  And You will not find an entry for the test event in the log /var/opt/resmon/log/event.log.

  To verify whether a monitor is running, execute monconfig with the command:

   
  /etc/opt/resmon/lbin/monconfig
  

  The initial display tells you whether monitoring is enabled. Enter a Check (C) command at the monconfig prompt to display a list of which monitors are running. If a monitor is not running, you will see an entry like:

  >/system/events/ups ... NOT MONITORING.
    (Possibly there is no hardware to monitor.)
  

  For more information, see the man page for send_test_event:

      man send_test_event
  

  (END of PROCEDURE)

/ Diagnostics HOME