ISEE/EMS not reporting disk failures

[Tom Gore]

I have a recent occurance of an issue. One of my FC60 disks failed. The failure was not reported by EMS/ISEE. I was informed by HP Tech Support that if you have a Global Hot Spare defined (GHS), EMS/ISEE will not capture certain failures. The error was "state 1 - non-existant". My question is: Is there a way to configure EMS/ISEE to capture these failures? I am trying to avoid having to constantly monitor the system to check for failed drives. I thought that was the purpose of EMS/ISEE.

Thanks

[Frank Alden Smith_5]

Tom,

Tom in order to test if it is possible to see your disk events as ISEE incidents you might like to try the following:

To test the ISEE incident flow from EMS to the support center:

o Check that EMS monitors are running:
# ps -ef | grep stm

o Select an active monitor, e.g., disk_em

o Issue this EMS test command:
# send_test_event -av disk_em

o Browse to the ISEE client interface and look for test incident(s).

o If the ISEE incidents are not there check syslog and root e-mail.

o If test notification makes it the syslog and/or e-mail, you
will have to configure the EMS monitor to send events with INFORMATION severity
or higher to the rstlistener port 1402. To do this use monconfig, the configuration should look like this when you are finished:

>/etc/opt/resmon/lbin/monconfig



============================================================================
=================== Event Monitoring Service ===================
=================== Monitoring Request Manager ===================
============================================================================

EVENT MONITORING IS CURRENTLY ENABLED.
EMS Version : A.03.20.01
STM Version : A.38.00

============================================================================
============== Monitoring Request Manager Main Menu ==============
============================================================================

Note: Monitoring requests let you specify the events for monitors
to report and the notification methods to use.

Select:
(S)how monitoring requests configured via monconfig
(C)heck detailed monitoring status
(L)ist descriptions of available monitors
(A)dd a monitoring request
(D)elete a monitoring request
(M)odify an existing monitoring request
(E)nable Monitoring
(K)ill (disable) monitoring
(H)elp
(Q)uit
Enter selection: [s] c



============================================================================
============== Check Outstanding Monitoring Requests ==============
============================================================================



... snip
For /storage/events/disks/default/0_0_1_1.15.0:
Events >= 1 (INFORMATION) Goto TEXTLOG; file=/var/opt/resmon/log/event.log
Events >= 3 (MAJOR WARNING) Goto SYSLOG
Events >= 3 (MAJOR WARNING) Goto EMAIL; addr=root
Events >= 1 (INFORMATION) Goto TEXTLOG; file=/var/opt/resmon/log/rst.log
Client Configuration File: /var/stm/config/tools/monitor/rst_disk_em.clcfg
Events >= 1 (INFORMATION) Goto TCP; host=localhost port=1402
Comment: RST Request
Client Configuration File: /var/stm/config/tools/monitor/rst_disk_em.clcfg
Events = 5 (CRITICAL) Goto TCP; host=rtcusb port=65200

Let me know how this works out!

Take care,
frank