The >9 network ports fix in Zenoss 2.2.4 is great, however, I found a new bug related to interface index persistence. In our example we're monitoring routers running DD-WRT v24-sp1 (07/27/08) vpn on DSL.
If the router is first powered-on and then added/modeled in Zenoss everything works great. If the PPPoE connection goes down and up then Zenoss will stop monitoring ppp0 and tun0 traffic. The next Zenoss modeling will report WARNING zen.ZenDisc skipping x.x.x.x points to missing ifindex 11 WARNING zen.ZenDisc skipping x.x.x.x points to missing ifindex 10 NOTE: Each time the PPPoE connection goes down and up the ifindex numbers are incremented. Running the snmpwalk command below always yields the same results regardless of how many times the PPPoE bounces and regardless of the ifindex numbers reported in the ZenDisc error log. snmpwalk -v2c -c cnorth routerIPhere 1.3.6.1.2.1.2.2.1.1 IF-MIB::ifIndex.1 = INTEGER: 1 IF-MIB::ifIndex.2 = INTEGER: 2 IF-MIB::ifIndex.3 = INTEGER: 3 IF-MIB::ifIndex.4 = INTEGER: 4 IF-MIB::ifIndex.5 = INTEGER: 5 IF-MIB::ifIndex.6 = INTEGER: 6 IF-MIB::ifIndex.7 = INTEGER: 7 IF-MIB::ifIndex.8 = INTEGER: 8 IF-MIB::ifIndex.9 = INTEGER: 9 I believe this is also happening to some of our Cisco gear. There is work-around for Cisco gear list here http://raabadnetworking.blogspot.com/2008/07/snmp-ifindex-persistence.html I haven't tried it myself. This is probably the source of the 'bad OID' errors. I've tried searching the DD-WRT forums and general Linux forums. Does anyone have an idea of how I could patch Zenoss to fix this? -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=26627#26627 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
