09-06-2013 08:14 AM
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?
05-06-2014 04:48 AM
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).