Server Management - Systems Insight Manager
1833458 Members
3249 Online
110052 Solutions
New Discussion

Re: Email Notification of Disk Status Changes not working

 
Pat Wilson
Valued Contributor

Email Notification of Disk Status Changes not working

I have been trying to set up an Auto Event Handler to email me when the disk status changes. When I set up a rule to mail EVERY event to me, I can see the following when the disk status changes:

--------------------------

Event Name: Logical Drive Status Change
Event originator: DC4IM7TEST
Event Severity: Critical
Event received: 01-Mar-2004, 07:47:23

Event description: Logical Drive Status Change. This trap signifies that the agent has detected a change in the status of a drive array logical drive. The variable cpqDaLogDrvStatus indicates the current logical drive status.

Location: Slot 6
Board Status: ok

--------------------------

When I use the selection criteria specified in the attached screen capture, I don't receive any notification at all.

What am I missing?
4 REPLIES 4
Rob Buxton
Honored Contributor

Re: Email Notification of Disk Status Changes not working

Just some questions or suggestions.
Why are there two entries for each?

Maybe try limiting it to just the Logical Drive Status, so you only have the one construct, no "or" statements.
Pat Wilson
Valued Contributor

Re: Email Notification of Disk Status Changes not working

The reason the seem to be two entries sometimes is I have specified ver 1 & ver 2 to try and catch all the disk trap notifications (the drop-down window dynamically expands when you roll over it).
Rob Buxton
Honored Contributor

Re: Email Notification of Disk Status Changes not working

Pat,
There were some discussions about some constructs not working in the Event Notifications. You might want to have a bit of a search through the forums. I'm not sure if they relate to what you're seeing though.
Pat Wilson
Valued Contributor

Re: Email Notification of Disk Status Changes not working

Well, I searched and did not see anything specific. For now I have resolved this by notifying on event received in the 'Proliant Storage Events' category.