HP P2000 MSA G3 SAN-SNMP Trap Setup

snmpstorage-area-networkwindows-server-2012

I'm trying to setup an SNMP trap for an HP P2000 G3 MSA SAN to report on the overall disk performance parameters (mostly I/O rates). We have a server monitor suite running which can use SNMP traps to trigger alerts to be sent to specific emails.

My problem is that I cannot find the specific SNMP walk which will allow me to do this. Both my boss and I tried separately and came to the same result. We found a package of MIB files which seemed to be for our SAN, but when imported into our server monitor it didn't seem to contain the correct OIDs.

I was wondering if anyone had any experience with this, and, if so, which parameter you configured?

If this is not possible with this SAN, is there a separate way to do this? Free is preferable.

As I am very new to SNMP, please excuse any misuse of terms or any misunderstanding of the protocol this post may contain. I'm still learning. In any case, I do appreciate any and all help or suggestions.

Best Answer

You can't pull SNMP performance stats out of the HP P2000 G3 SAN. It's a limitation.

There's a Windows host-based metrics tool available, but you're best off measuring from the consumers of the SAN data. I do believe SNMP traps can be sent for hardware alerts/failures. That configuration is straightforward from the MSA interface.

Related Solutions

Solution to route/proxy SNMP Traps (or Netflow, generic UDP, etc) for network monitoring

A co-worker just showed me samplicator. This tool looks to be just about a perfect solution what I was looking for. From the tool's website:

This simple program listens for UDP datagrams on a network port, and sends copies of these datagrams on to a set of destinations. Optionally, it can perform sampling, i.e. rather than forwarding every packet, forward only 1 in N. Another option is that it can "spoof" the IP source address, so that the copies appear to come from the original source, rather than the relay. Currently only supports IPv4.

It can been used to distribute e.g. Netflow packets, SNMP traps (but not informs), or Syslog messages to multiple receivers.

Simulate SNMP traps to test surveillance

Try the following:

snmptrap.exe -v 2c -c xxxxxxx 192.168.100.65 
'' .1.3.6.1.4.1.5089.1.0.1 .1.3.6.1.4.1.5089.2.0.999 s "123456"

'' <- the first parameter for v2c trap is the agent uptime, it is mandatory and empty parameter will be replaced with current value
.1.3.6.1.4.1.5089.1.0.1 <- trap OID
.1.3.6.1.4.1.5089.2.0.999 <- varbind (this needs to be defined as a string value in MIB)
s <- indicates string
"123456" <- just a random test-string...

This generates a SNMPv2c trap with the following content (as seen in wireshark):

      variable-bindings: 3 items
            1.3.6.1.2.1.1.3.0: 878104
            1.3.6.1.6.3.1.1.4.1.0: 1.3.6.1.4.1.5089.1.0.1 (iso.3.6.1.4.1.5089.1.0.1)
            1.3.6.1.4.1.5089.2.0.999: 31323334353 (this is 123456 octet string)

This output comes from snmptrap on Linux, but it seems to be the same as on Windows.

Best Answer

Related Solutions

Solution to route/proxy SNMP Traps (or Netflow, generic UDP, etc) for network monitoring

Simulate SNMP traps to test surveillance

Related Topic