Hello all, Haven't seen anything explicitly related to this in the forums, but appologies in advance if I've missed something obvious.
I'm trying to create a basic template that informs me if an interface on a switch or router (we use a mix of makes on our network) goes down. I've created data sources for what I assumed were the OIDs for: ifAdminStatus (1.3.6.1.2.1.2.2.1.7) and... ifOperStatus (1.3.6.1.2.1.2.2.1.8) I then created a threshold for those two data points such that if the value of either exceeded 1 (2 is supposed to be down, 3 is a testing state) it would generate a critical alarm. All I got were the following errors: Code: Error reading value for "ifAdminStatus" on <hostname> (oid .1.3.6.1.2.1.2.2.1.7 is bad) and: Code: Error reading value for "ifOperStatus" on <hostname> (oid .1.3.6.1.2.1.2.2.1.8 is bad) Someone here suggested that the OID needed to be one which explicitly points to an interface. For example, if snmpwalk shows ifOperStatus output like the following: Code: [EMAIL PROTECTED]:~> snmpwalk -v 1 -c public -On <device IP address> .1.3.6.1.2.1.2.2.1.8 .1.3.6.1.2.1.2.2.1.8.1 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.2 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.3 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.4 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.5 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.6 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.7 = INTEGER: down(2) .1.3.6.1.2.1.2.2.1.8.8 = INTEGER: down(2) .1.3.6.1.2.1.2.2.1.8.9 = INTEGER: down(2) .1.3.6.1.2.1.2.2.1.8.10 = INTEGER: down(2) .1.3.6.1.2.1.2.2.1.8.11 = INTEGER: down(2) .1.3.6.1.2.1.2.2.1.8.12 = INTEGER: down(2) .1.3.6.1.2.1.2.2.1.8.13 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.14 = INTEGER: down(2) .1.3.6.1.2.1.2.2.1.8.15 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.16 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.17 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.18 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.19 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.20 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.21 = INTEGER: down(2) .1.3.6.1.2.1.2.2.1.8.22 = INTEGER: down(2) .1.3.6.1.2.1.2.2.1.8.23 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.24 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.25 = INTEGER: down(2) .1.3.6.1.2.1.2.2.1.8.26 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.27 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.28 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.29 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.30 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.31 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.32 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.33 = INTEGER: up(1) .1.3.6.1.2.1.2.2.1.8.34 = INTEGER: up(1) ...then I could not just have a generic data source for 1.3.6.1.2.1.2.2.1.8, but I'd have to have a data source for everything from 1.3.6.1.2.1.2.2.1.8.1 all the way through 1.3.6.1.2.1.2.2.1.8.34. This seems kind of inefficient. My assumption was that a data source for 1.3.6.1.2.1.2.2.1.8 would be applied to any OID which began with 1.3.6.1.2.1.2.2.1.8. That would allow me to make a template which could be applied globally to all our routers & switches (we have several hundred!) to look for downed interfaces. Is this the case? Or do I need some kind of a wildcard character at the end of that string? Or do I need to have explicit data sources for every single possible interface OID and manually prune back unused OIDs on a device by device basis? If I have to do the latter it'll be a lot of work - I may cry a little on the inside. Anyway, thanks much for any assistance! Mike -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=19580#19580 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
