I've done a lot of googling around trying to see if anyone else has stumbled on this, and while I've found a few similar issues, nothing that exactly matches this.
THe issue is more of a nuisance than a real problem, it just appears that OID's specific to Cisco Dot1q interfaces disappear, at least to zenoss (both 2.33 and 2.4 beta 3) and then come back later. The error I get is OID is bad (i'll add some to the bottom of this message). I'm using SNMP version 2c, and I haven't been able to get an snmpget to fail yet when probing the same OID. I am stumped as if this is a Cisco, or a zenoss issue. I have graphs of the sub-interfaces, and am not missing any data. The nusiance is that it displays a grey status for the routers with X number of issues, X being the number of sub interfaces. While I could simply ignore them, if we went production with this, other people might go crazy over it. Tue 4/28/2009 2:06 AM Device: RTR099.MISLAB Component: FastEthernet0/1.702 Severity: Debug Time: 2009/04/28 02:05:20.000 Message: Error reading value for "FastEthernet0/1.702" on RTR099.MISLAB (oid .1.3.6.1.2.1.2.2.1.20.6 is bad) Event Detail Acknowledge Delete Device Events and then the clear; Tue 4/28/2009 6:17 AM Event: 'Error reading value for "FastEthernet0/1.702" on RTR099.MISLAB (oid .1.3.6.1.2.1.2.2.1.20.6 is bad)' Cleared by: '' At: Device: RTR099.MISLAB Component: FastEthernet0/1.702 Severity: Debug Message: Error reading value for "FastEthernet0/1.702" on RTR099.MISLAB (oid .1.3.6.1.2.1.2.2.1.20.6 is bad) Any help and pointers appreciated, thanks and best Regards Adnrew -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=33948#33948 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
