We have the same problem, some of our routers have too many routes for the router to spit out before zenoss times out. I investigated some and here' what I sent out in an email list internal to my company: ----------------------------------------------------------- The network modeler for /Devices/Network/Router is zenoss.snmp.RouteMap. That uses RFC1213, which has no way of telling how many routes there are without walking them all.
There is another collector plugin called zenoss.snmp.NewRouteMap that uses RFC2096. That has ipCidrRouteNumber, which does give the number of routes but I don't think zenoss trys that before it discovers that fog obscures a cliff it's about to walk off of. It shouldn't be too hard to add, though. RFC4292, I believe, is the newest. It doesn't have any way to limit responses to just a particular AS or etc. so it still isn't very practical to walk on routers with a lot of routes. Maybe Cisco has a proprietary MIB that could be used. ----------------------------------------------------------- So in other words, a nice feature would be to first check the number of routes with ipCidrRouteNumber and if it's "too big" then give up. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=21527#21527 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
