Orion Universal Device Poller Question

I am trying to create a couple device pollers in Orion that reference loop protect status of HP switches. The end goal is to have alerts based around these pollers so that techs can be notified whenever a loop is detected on one of the switches that we are monitoring. The two MIBS that I am trying to use are:

hpicfBridgeLoopProtectLoopDetectedNotification (1.3.6.1.4.1.11.2.14.11.5.1.12.1.5.0.1)

hpicfBridgeLoopProtectTrapLoopDetectEnable (1.3.6.1.4.1.11.2.14.11.5.1.12.1.5.1.2)

The first MIB is a notification MIB that signifies that a loop has been detected by the loop protection protocol and relies on the second MIB (which indicates if a notification should be sent when a loop is detected by a port).

The issue that I am having is that when testing the MIBS against my devices I am not getting a valid value returned, instead I receive a message "A value was not returned."

If I test the MIBS against some of my devices during the MIB creation steps values are appropriately displayed. I am wondering what this return message really means, and really if anyone else has attempted to configure loop protect pollers in Orion in the past. Any feedback would be greatly appreciated. Thanks

Find more posts tagged with

loop_protect

trap_viewer_alerts

npm_10

mib

device_poller

Alerts

trap_viewer

Accepted answers

All comments

sean.martinez

Looking at the MIB hpicfBridgeLoopProtectLoopDetectedNotification (1.3.6.1.4.1.11.2.14.11.5.1.12.1.5.0.1), this is a Trap OID that will have to be monitored via the Trap Viewer. Anytime you see a Lightning Bolt in the Browse MIBs tree will denote that this is a Trap OID only.

It appears that this MIB hpicfBridgeLoopProtectTrapLoopDetectEnable (1.3.6.1.4.1.11.2.14.11.5.1.12.1.5.1.2) would work in the Universal Device Poller.

I do not have full information about the message "A value was not returned" without looking at the Wireshark capture of that OID, but I believe that the Error is occurring because it is a Trap OID.

Nakuchar

I have changed my approach to this alert and am going to just use the Trap Viewer and just alert (send out an email) when the loop-protect specific trap is received. This will be the first time that I am going to try and build an alert off of the Trap Viewer and I noticed that it is is very rarely receiving any traps, probably only around five or six in the past six months. This sounds terribly low.

I am wondering if there is any specific configuration that needs to be done so that the Trap Viewer is receiving traps that are generated on switches or if it should be pulling the traps automatically since the device is being monitored. Any feedback from someone who has tired this in the past or is knowledgeable on this subject would be much appreciated.

Nakuchar

Is it possible that the loop-protect MIB is detecting the loop then shutting down the interface and not generating the trap? I don't know why this would happen but I guess I don't have a complete mastery of this OID / traps in general to say otherwise. Just a thought.