Insight Remote Support
cancel
Showing results for 
Search instead for 
Did you mean: 

ISEE/WEBES on Tru64 Alpha not Reporting disk failure on MA8K

Govinda
Advisor

ISEE/WEBES on Tru64 Alpha not Reporting disk failure on MA8K

hi,

i have an ISEE?WEBES installed on alpha es40, and the external storage (MA8K) is connected to it. one disk failed in the stogare box but ISEE/WEBES didnt pick any error/incident.

let me know, whether WEBES/ISEE picks the errors from an external storage.

Thanks in advance,
govind.
1 REPLY
Frank Alden Smith
Trusted Contributor

Re: ISEE/WEBES on Tru64 Alpha not Reporting disk failure on MA8K

Govind,

I am not sure if the external storage device reports events to the binary log file (/var/adm/binary.errlog) that SEA (System Event Analyzer - a component of WEBES) monitors for hardware events.

However, here is a way to make sure events that do make it to the log file, will show up as ISEE Incidents that get sent to the HP Support Center.

1) Verify that ISEE notification is configured:

# wsea status

System Event Analyzer for Tru64 UNIX X4.3 (Build 16)
Service Tools Home: /usr/opt/hp/svctools
Service Obligation Start Date: Thu Apr 08 00:00:00 GMT-05:00 2004
Service Obligation End Date: Fri Apr 08 00:00:00 GMT-05:00 2005
SICL/DSNlink notification: disabled.
CSG/QSAP notification: disabled.
ISEE notification: disabled.

2) If ISEE notification is disabled as show in step 1, enable it:

# desta isee on

3) Check again to make sure ISEE notification is now enabled.

# wsea status

System Event Analyzer for Tru64 UNIX X4.3 (Build 16)
Service Tools Home: /usr/opt/hp/svctools
Service Obligation Start Date: Thu Apr 08 00:00:00 GMT-05:00 2004
Service Obligation End Date: Fri Apr 08 00:00:00 GMT-05:00 2005
SICL/DSNlink notification: disabled.
CSG/QSAP notification: disabled.
ISEE notification: enabled.

4) Send a test event.

# wsea test nos

Note: nos bypasses the binary error log file and sends the test event directly to SEA. You can omit nos, however it may take longer for the test event to show up.

5) Browse to the client and look for a new 'SEATEST event callout' incident.

Take care,
frank
All knowing is doing.