HP MSA2040 SNMP Traps

[Donald J Wood]

Hi, I'm trying to understand what SNMP traps these MSA 2040 will produce when a fault occurrs and how it goes about it.

We will have DL380G8 server with SAS connections to the MSA 2040. In some cases there will be more than one server connected to a MSA.

My question has two parts..

I know you can configured the MSA with trap receivers.

Will the DL380G8 also monitor the MSA via the storage agents and trap when the MSA has a fault?

I understand that there is a msa2000traps.mib that support these devices but I only see 4 traps, 3001-3004.

What about the other components in the MSA like fans, controller, CPU, ect? How are those faults communcated?

[Torsten.]

How about configure mail alerts?

The server won't know about minor problems, the MSA itself will send the traps.

[Donald J Wood]

Email alerts? Absolutely not.

I need to know besides the 3001-3004, what specific hardware traps are to be expected. Is there a document that explains this? WIll the MSA be sending them or the server that is hosting it?

[Torsten.]

The MSA will send the traps.

Have a look at msa2000traps.mib.

Example:

-- Trap annotations are as follows:
--#TYPE "Error storage event"
--#SUMMARY "Error storage event # %d, type %d, description: %s"
--#ARGUMENTS {0,1,2}
--#SEVERITY MAJOR
--#TIMEINDEX 6

[Donald J Wood]

As I say in the beginning, I already know about the msa2000traps.mib. Those are the 3001-3004 traps. What about the other hardware in the MSA like Fans, CPU, NIC.. ect?

[Torsten.]

See the appendix here

http://www.huitongenergy.com/upload/file/120813210947.pdf

(google found this link only)

it is about the older model, but should still apply.

[Donald J Wood]

That link locked up the browser on my computer. Isn't this available via an HP site?

[Torsten.]

This is for G2:

http://h10032.www1.hp.com/ctg/Manual/c01659237.pdf

[Donald J Wood]

Found that right before you posted it. Thanks but, after a quick review it doesn't seem to indicate what (other than 3001-3004) traps are supported.

[Torsten.]

These traps are enough.

Consider this as 4 classes of traps.

from the guide

...

Enterprise event severities are informational, minor, major, and critical. There is a different trap type for
each of these severities. The trap format is represented by the HP enterprise traps MIB,
msa2000traps.mib. Information included is the event ID, the event code type, and a text description
generated from the internal event. Equivalent information can also be sent using email or popup alerts to
users who are logged in to SMU.

...

so each internal event is encapsulted into such trap, these are informational, warning, error or critical (3001 - 3004).

in the appendix - Event code reference - (same guide)

you will find a list of events.

example:

if the system has an internal event

240 - warning - A failure has occurred while flushing the CompactFlash.

you will get the same as a WARNING trap.

So you have several hundred different possible traps.

You can get the same messages by mail, if configured.

If you integrate the device into HP Insight remote support or HP SIM, this will automatically open a case at hp if the device has a hardware related problem.

[EDIT:]

a newer reference guide is linked below

I hope it is more clear now.