MSA P2000 SAS enclosure

Hi,

You will have to create your own snmp lib I was able to Monitor the Overall Status by Importing the MIB File called fa-mib40.mib (you can get it from the p2000 Download Page at HP)
The only OIDs you will Need are in the Section

1.3.6.1.3.94.1.6.1.1

There you got Connunit state and Connunit Status

1.3.6.1.3.94.1.6.1.5
&
1.3.6.1.3.94.1.6.1.6

But be careful, with the newest Firmware there seems to be a Bug, SNMP doesnt work with it at the Moment, got an open Case with HP already about it.

Best Regards

Hi,

Thanks for your answer. When I enter the OID into the snmptester, I receive the message "No such name (error #2). Is this because of the new firmware?

I also downloaded the fa-mib40.mib, but I don't see the section you describe. (1.3.6.1.3.94.1.6.1.5)

Kind regards,

Evert

When you Import the fa-mib40.mib you have:

conn unit: #[1.3.6.1.3.94.1.6.1.1]

Under this you have:

conn unit state 1.3.6.1.3.94.1.6.1.5
conn unit Status 1.3.6.1.3.94.1.6.1.6

With the current Firmware I am also not able to get an SNMP answer via SNMP Tester. When you use the MIB in PRTG itself you should get "No Response" or something similiar. But of course you have to activate SNMP itself inside the P2000 Management

With the end of the Month HP will release a new Firmware that should resolve the Problem.

Has there been any update to this?

I am also looking to monitor Disk status on an MSA2000 p3.

I'm in the same boat as many others, we'd like to replace HP-SIM with PRTG, but need to be able to get the SNMP hardware monitoring working before we can take the plunge.

I do not want to mess with firmware updates on a production array unless I know the problem is fixed.

As of PRTG 14.1.9, you can use native PRTG sensors to monitor HP SANs via SSH (e.g., the HP P2000):

• SSH SAN Logical Disk Sensor
• SSH SAN Physical Disk Sensor
• SSH SAN System Health Sensor