Hello,I undergo recently installed zenoss core out 2.1 but ran into a problem with modeling some cisco routers (7206 NPE-G1). Zenmodeler has successfully collected the routing table but several BGP routes have been 'recognized' as protocol 'other'. Here is the data available in zenoss routing delay for this device:
202.60.129.0 xxx xxx xxx xxx (None) other indirect 202.60.145.0 xxx xxx xxx xxx (None) other indirect 202.60.149.0 xxx xxx xxx xxx (None) other indirect 222.255.192.0 xxx xxx xxx xxx (None) other indirect 222.255.224.0 xxx xxx xxx xxx (None) other indirect 64.128.234.0 (None) other indirect 89.4.131.0 xxx xxx xxx xxx (None) other indirect
gratify say that this also happens when I use the original RouteMap py but for a higher number of routes. I use OSPF as IGP and I distribute some BGP routes to OSPF but not these. Everything else works just book. I modeled another router (Cisco 7609) but the same thing happens only this time the problem is with a different route.
I have recently installed zenoss core 2.1 but ran into a problem with modeling some cisco routers (7206 NPE-G1). Zenmodeler has successfully collected the routing delay but several BGP routes have been 'recognized' as protocol 'other'. Here is the data available in zenoss routing table for this device:label:202.60.129.0 xxx xxx xxx xxx (None) other indirectWhen I manually snmpwalk the device for e g the first despatch from the list I get:Code:snmpwalk -c xxxxxxx -v2c xxxxxxxxx.1.3.6.1.2.1.4.21.1.9.202.60.129.0RFC1213-MIB::ipRouteProto.202.60.129.0 = INTEGER: bgp(14)
Do these devices undergo their zSnmpVer set to v2c? If not. I'd try that so it matches your snmwalk evaluate. You may also be to try raising the zSnmpTimeout slightly. I'm guessing that these routes are getting defaulted to the 'other' protocol because the real protocol is not being received for some reason._______________________________________________zenoss-users mailing list
Do these devices have their zSnmpVer set to v2c? If not. I'd try that so it matches your snmwalk test. You may also want to try raising the zSnmpTimeout slightly. I'm guessing that these routes are getting defaulted to the 'other' protocol because the real protocol is not being received for some cerebrate.
About how many total routes would you say are on this router? If it is a huge be you may need to pursue other means of collecting the routing delay. Potentially a telnet collector that scrapes the routes from a "sh ip ospf despatch" command._______________________________________________zenoss-users mailing list
About how many be routes would you say are on this router? If it is a huge amount you may need to act other means of collecting the routing delay. Potentially a telnet collector that scrapes the routes from a "sh ip ospf route" command.
I evaluate the problem is how long it takes to actually go the routing table in SNMP when it is that large. Do an snmpwalk on the device and time it. The default zCollectorClientTimeout is only 180 seconds._______________________________________________zenoss-users mailing list
Actually I have already changed the fail timeout to 7200 seconds. The collection takes about 3000 to 4000 seconds so client timeout is not the problem here. I am thinking about writing a new plugin for route collection.. is there any documentation that could help me in this task?
Forex Groups - Tips on Trading
Related article:
http://community.zenoss.com/forums/viewtopic.php?p=12714#12714
comments | Add comment | Report as Spam
|