How do you create an alert to reference a MIB Table?

I have been trying to build an alert that will trigger when a port on one of my HP devices detects a loop. I am using the MIB hpicfBridgeLoopProtectPortLoopDetected (1.3.6.1.4.1.11.2.14.11.5.1.12.1.5.2.1.1.2). The thing about this MIB is that it returns in a table. Each interface on the device listed generic number with a "1" or "2" next to it corresponding to True and False.

My real question, how do I take the values returned in this table and alert when only a specific value turns from say 2 (FALSE) to 1(TRUE)? I am not sure of the exact variables and order of logic that would be required.

I am also curious about what would be required to take the specific interface that has the condition and put it into an email along with the device name and other information as a proactive warning? Has anyone tried to alert on a MIB table before and have some advice? Any feedback would be great. Thank you in advance.

Find more posts tagged with

custom_poller

npm_10

mib

Alerting

custom_poller_alert

Accepted answers

All comments

Nakuchar

Am I the first person to attempt to do something like this? Is there a better way without using a MIB table?

d09h

I went down this road with my polling of port security. While I could poll the table for a node, I ended up assigning an inteface MIB poller to each and every interface solely because I could then alert easier. I added a custom property to the interfaces I wished to monitor to help me assign the poller. I only had about a dozen switches with port security configured, so scalability was not much of an issue.

If you do as I said, and then create an alert when that MIB 1) has changed and 2) equals 1, you should be able to alert. I do it for my port security and duplex status.

Can you poll interfaces instead? Perhaps a MIB walk of your HP switches will show you an entry for each of your interfaces and you could specify the part of the OID that is common. It would probably differ only in the very last number, which should match an interface number. Something like 1.2.3.4.5.6.7.8.9.1 for inteface 1 and 1.2.3.4.5.6.7.8.9.2 for interface 2...etc.

Not sure if this solution would scale for you and how many interfaces you've got to work with. Custom properties may make assigning the poller to interfaces easier if dealing with a large number of switches. Especially so if using the Custom Property Editor as an app on the Orion server or filtering your admin view by interfaces of the appropriate custom property.