SNMP MIBs and SANs

[John_712]

I've installed/configured System Insight Manager v7.2 on a W2K/SP4/DL320. We compiled (mcompile/mxmib) the MIBs for two XIOtech SANs, Magnitude (v1 MIB) and Magnitude 3D (v2 MIB).

We are able to view traps from the v1 device MIB but the v2 device MIB is showing up as a v1 device in SIM. The documentation says that you support receiving traps from v1 and v2 devices.

I know that the v2 MIB is sending out traps because I can use some freeware tools to see the traps.

Is there a way to recompile the v2 MIB as v1 so I can receive the traps or when will you support v2 MIBs..

Any help is appreciated.
Thanks,
John

[David Claypool]

Note: HP Insight Manager 7 and HP Systems Insight Manager are two separate products with hpSIM being the replacement for IM7.

IM7 has ceased development. hpSIM supports SNMP v2 which IM7 does not.

[John_712]

I mistyped in my first email, I am working with HP Systems Insight Manager v4.

I called your first level support and they said that you support 100% of the v1 MIBs and 90% of the v2 MIBs. I was escalated to the Insight team and they said that they don't support v2 at this time and won't for awhile.

Not sure what the real answer is...
Thanks,
John

[David Claypool]

See the new whitepaper "Compiling and Customizing SNMP MIBs with HP Systems Insight Manager" at http://www.hp.com/servers/manage --> HP Systems Insight Manager --> Information Library

From the overview:

"HP Systems Insight Manager provides the capability of managing devices via SNMP and by receiving incoming SNMP trap events. This paper will discuss the tools provided by HP Systems Insight Manager to integrate 3rd party (non-HP) ____SNMP v1/v2 MIBs____ into HP Systems Insight Manager to provide support for processing and displaying traps from other devices. This paper will also discuss the MIB syntax extensions supported by HP Systems Insight Manager that provide additional value in customizing specific trap information. Finally, this paper will discuss the set of MIBs included"

I'll inform the support team that some "re-education" is in order...

[John_712]

Yep, I am familiar with that whitepaper, that help me learn how to mcompile and mxmib our mib.

But according to your support, you don't really support v2 MIBs.

In fact, the device (system) is showing up as a v1 MIB in the display.

Can you confirm that you can definately recv traps from a v2 SAN Device (MIB) in HP Systems Insight Manager 4.0?

[David Claypool]

Direct from the dev team:

"We support both v1 and v2 syntax MIBs in HPSIM via mcompile and mxmib. As with all MIB support, the MIB needs to be well written and there are a bunch of gotchas with MIB syntax that can trip us up."

However, don't confuse v2 syntax MIBs with the v2 protocol. We compile v2 MIBs, but your device needs to format traps to send them using the v1 protocol.

[John_712]

So..in response to the message from the dev team, what are the gotcha's/potential gotcha's that can trip you up?

If I sent you the MIB, can they take a look at the file and make any recommendations?

If I understand your last statement correctly, although you will compile our v2 MIB the traps need to be sent via the v1 protocol.

Is there any timeframe on when you'll will send traps via the v2 protocol? How about in v4.1?

Thanks,

[David Claypool]

The "trip you up" part will be detected in the MIB compile. If that goes fine, you should have no problems.

As far as traps actually being carried along by v2, the v2 spec defined some additional goodies that virtually no one has chosen to implement. In the few instances we have run into devices that are capable of sending v2 protocol traps, they all have the option to be set to v1.

V1 carries all the information we need, so there are no plans to change that in a future version. In fact, due to overwhelming customer demand, we are making every effort to reduce our dependence on SNMP in favor particularly of WBEM (including WMI) and some of its derivatives such as SMI-S (which should be of particular interest to you since this thread is about SANs).