Predictive drive failure severity Warning (1341 Views)
Occasional Visitor
Posts: 1
Registered: ‎09-06-2013
Message 1 of 4 (1,341 Views)

Predictive drive failure severity Warning

I recently had a predictive physical drive failure on a server that was missed due to the severity level.  The event was (SNMP) Physical Drive Status Change (3046).  The event severity was Warning  The event shows the Event trap as cpqdaphysdrvstatus.  In SNMP Trap Settings I find the matching Event Type under Trap Name dpqda7physdrivestatuschange, and the severity is set to Critical.   How do I get this to show up as a critical event?

Please use plain text.
Occasional Contributor
Posts: 6
Registered: ‎12-18-2012
Message 2 of 4 (126 Views)

Re: Predictive drive failure severity Warning

I got excatly the same issue. Any idea ?

Please use plain text.
Valued Contributor
Posts: 178
Registered: ‎02-20-2012
Message 3 of 4 (120 Views)

Re: Predictive drive failure severity Warning

[ Edited ]

edit: i didn't read the question correctly so my answer was wrong ;)

Please use plain text.
Trusted Contributor
Posts: 286
Registered: ‎09-04-2012
Message 4 of 4 (114 Views)

Re: Predictive drive failure severity Warning

The solution provided does not fully affect the "status change" traps from drives and cache batteries..


See this thread:


There is no way to granually change the severities on the "underlying" statuses.  So, PFAs will always be warnings, failures always critical no matter what you set the main trap to be (trap 3046, for example).


You can, in the MIB apparently, change the severity to ALWAYS be the same for ANY status change, but i highly doubt you want a "good" status to also be "critical" severity along with PFAs and actual failures.


See the thread above, i had to create another event collection specifically for drive status changes and generate events on minor/warnings to catch all the conditions (in addition to major/critical that the normal event collections catch).


Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation