Hello,

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 table but several BGP routes have been 'recognized' as protocol 'other'.

Here is the data available in zenoss routing table for this device:


Code:
   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




When I manually snmpwalk the device for e.g. the first route from the list I 
get:


Code:

snmpwalk -c xxxxxxx -v2c xxxxxxxxx .1.3.6.1.2.1.4.21.1.9.202.60.129.0
RFC1213-MIB::ipRouteProto.202.60.129.0 = INTEGER: bgp(14)




I should also mention that I applied a small patch to RouteMap.py in order to 
exclude bgp routes


Code:

diff RouteMap.py RouteMap.py.original 
78,79d77
<           if om.routeproto == 'bgp':
<               continue




Please note 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 redistribute some BGP routes to OSPF but not these. 
Everything else works just fine.

I modeled another router (Cisco 7609) but the same thing happens, only this 
time the problem is with a different route.




-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=12645#12645

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to