Hi people,
Have been fiddling with great joy in zenoss, but I have stumbled in a serious issue that can lead me to abandon zenoss. I'm trying to monitor/model a network composed mainly by Nortel Networks (8600) equipments (almost 70) and zenoss is not properly modelling it in terms of assigning ip addresses to interfaces when using snmp (with cisco equipment it works great). Having done some research with snmpwalk I have figured out that Nortel snmp interface index are different at the physical level and ip level and therefore a correlation between interface and ip address cannot be done directly. Nortel uses a different interface index for routing purposes (ip address, masks, route tables) than for the physical interfaces and so zenoss cannot modell it properly (as you can see in the modeller log). But I think there is a way that zenoss can assing ip address to interfaces using the vlan indexes), as you can seen by the snmpwalk traces showed below. But that involves a tweak in the actual InterfaceMap collector plugin or develop a new one based on that one, which due to my "zeroness" in python programming will take me a huge effort. Is there any chance anyone can help me on that (a patch, a new InterfaceMap.py modeller script)? Thanks for the attention, and make myself at disposal for getting extra snmpwalks dumps that anyone needs for developing such a patch. Regards Luís Palma PS: I know there is an error at the end but I think it is relationed to a zenoss instalation on top of a previous zenoss instalation ========================== Zennoss Modeller LOG =========================== 2007-11-06 14:10:57 INFO zen.Device Executing command: /opt/zenoss/bin/zenmodeler run --now -F -d removed.net.inet --weblog 2007-11-06 14:11:02 INFO zen.ZenModeler starting collector loop 2007-11-06 14:11:02 INFO zen.ZenModeler collecting for device removed.net.inet 2007-11-06 14:11:03 INFO zen.ZenModeler no cmd plugins found for removed.net.inet 2007-11-06 14:11:03 INFO zen.ZenModeler snmp collection device removed.net.inet 2007-11-06 14:11:03 INFO zen.ZenModeler plugins: zenoss.snmp.DeviceMap, zenoss.snmp.InterfaceMap, zenoss.snmp.NewDeviceMap, zenoss.snmp.RouteMap 2007-11-06 14:11:03 INFO zen.ZenModeler no portscan plugins found for swtbbalmo1.net.inet 2007-11-06 14:11:10 INFO zen.SnmpClient snmp client finished collection for swtbbalmo1.net.inet 2007-11-06 14:11:10 INFO zen.ApplyDataMap processing zenoss.snmp.DeviceMap for device removed.net.inet 2007-11-06 14:11:10 INFO zen.ApplyDataMap processing zenoss.snmp.InterfaceMap for device removed.net.inet 2007-11-06 14:11:10 WARNING zen.ApplyDataMap skipping 192.168.93.254 points to missing ifindex 2055 2007-11-06 14:11:10 WARNING zen.ApplyDataMap skipping 192.168.168.168 points to missing ifindex 320 2007-11-06 14:11:10 WARNING zen.ApplyDataMap skipping 10.58.116.1 points to missing ifindex 2052 2007-11-06 14:11:10 WARNING zen.ApplyDataMap skipping 10.58.135.1 points to missing ifindex 2060 2007-11-06 14:11:10 WARNING zen.ApplyDataMap skipping 10.58.136.1 points to missing ifindex 2061 2007-11-06 14:11:10 WARNING zen.ApplyDataMap skipping 10.58.126.1 points to missing ifindex 2057 2007-11-06 14:11:10 WARNING zen.ApplyDataMap skipping 10.58.127.254 points to missing ifindex 2058 2007-11-06 14:11:10 WARNING zen.ApplyDataMap skipping 10.58.117.254 points to missing ifindex 2053 2007-11-06 14:11:10 WARNING zen.ApplyDataMap skipping 10.58.115.1 points to missing ifindex 2051 2007-11-06 14:11:10 WARNING zen.ApplyDataMap skipping 10.1.5.118 points to missing ifindex 2050 2007-11-06 14:11:10 WARNING zen.ApplyDataMap skipping 10.58.129.254 points to missing ifindex 2059 2007-11-06 14:11:10 WARNING zen.ApplyDataMap skipping 10.58.119.254 points to missing ifindex 2054 2007-11-06 14:11:10 WARNING zen.ApplyDataMap skipping 10.58.125.1 points to missing ifindex 2056 2007-11-06 14:11:10 WARNING zen.ApplyDataMap skipping 10.58.139.254 points to missing ifindex 2063 2007-11-06 14:11:10 WARNING zen.ApplyDataMap skipping 10.58.137.254 points to missing ifindex 2062 2007-11-06 14:11:12 INFO zen.ApplyDataMap processing zenoss.snmp.NewDeviceMap for device swtbbalmo1.net.inet 2007-11-06 14:11:12 INFO zen.ApplyDataMap processing zenoss.snmp.RouteMap for device swtbbalmo1.net.inet 2007-11-06 14:11:24 WARNING zen.IpRouteEntry interface index:2050 not found 2007-11-06 14:11:31 WARNING zen.IpRouteEntry interface index:2050 not found 2007-11-06 14:11:32 WARNING zen.IpRouteEntry interface index:2050 not found 2007-11-06 14:11:33 WARNING zen.IpRouteEntry interface index:2050 not found 2007-11-06 14:11:34 WARNING zen.IpRouteEntry interface index:2050 not found 2007-11-06 14:11:35 WARNING zen.IpRouteEntry interface index:2050 not found 2007-11-06 14:11:35 WARNING zen.IpRouteEntry interface index:2050 not found ... ... 2007-11-06 14:11:36 WARNING zen.IpRouteEntry interface index:2050 not found 2007-11-06 14:11:37 WARNING zen.IpRouteEntry interface index:2050 not found 2007-11-06 14:11:38 WARNING zen.IpRouteEntry interface index:2050 not found 2007-11-06 14:11:40 WARNING zen.IpRouteEntry interface index:2050 not found 2007-11-06 14:11:41 WARNING zen.IpRouteEntry interface index:2050 not found 2007-11-06 14:11:42 WARNING zen.IpRouteEntry interface index:2050 not found 2007-11-06 14:11:43 WARNING zen.IpRouteEntry interface index:2050 not found 2007-11-06 14:11:43 WARNING zen.IpRouteEntry interface index:2050 not found 2007-11-06 14:21:42 INFO zen.ApplyDataMap changes applied 2007-11-06 14:22:06 INFO zen.DeviceLoader device removed.net.inet loaded! 2007-11-06 14:22:09 ERROR zen.ApplyDataMap plugin zenoss.snmp.RouteMap device removed.net.inet Traceback (most recent call last): File "/opt/zenoss/Products/DataCollector/ApplyDataMap.py", line 111, in processClient trans.commit() File "/opt/zenoss/lib/python/transaction/_transaction.py", line 381, in commit self._saveCommitishError() # This raises! File "/opt/zenoss/lib/python/transaction/_transaction.py", line 379, in commit self._commitResources() File "/opt/zenoss/lib/python/transaction/_transaction.py", line 424, in _commitResources rm.commit(self) File "/opt/zenoss/lib/python/ZODB/Connection.py", line 462, in commit self._commit(transaction) File "/opt/zenoss/lib/python/ZODB/Connection.py", line 495, in _commit raise ConflictError(object=obj) ConflictError: database conflict error (oid 0x757f, class Products.ZenModel.IpNetwork.IpNetwork) 2007-11-06 14:22:09 INFO zen.ZenModeler scan time: 666.98 seconds 2007-11-06 14:22:09 INFO zen.ZenModeler stopping... ============================================= snmpwalk that lead to errors ==================================== snmpwalk -v1 -O n -c removed nortel8600.net.inet .1.3.6.1.2.1.2.2.1.1 | more .1.3.6.1.2.1.2.2.1.1.64 = INTEGER: 64 .1.3.6.1.2.1.2.2.1.1.65 = INTEGER: 65 .1.3.6.1.2.1.2.2.1.1.66 = INTEGER: 66 .1.3.6.1.2.1.2.2.1.1.67 = INTEGER: 67 .1.3.6.1.2.1.2.2.1.1.68 = INTEGER: 68 .1.3.6.1.2.1.2.2.1.1.69 = INTEGER: 69 .1.3.6.1.2.1.2.2.1.1.70 = INTEGER: 70 .1.3.6.1.2.1.2.2.1.1.71 = INTEGER: 71 snmpwalk -v1 -O n -c removed nortel8600.net.inet .1.3.6.1.2.1.4.20.1.2 | more .1.3.6.1.2.1.4.20.1.2.10.1.5.118 = INTEGER: 2050 .1.3.6.1.2.1.4.20.1.2.10.58.115.1 = INTEGER: 2051 .1.3.6.1.2.1.4.20.1.2.10.58.116.1 = INTEGER: 2052 .1.3.6.1.2.1.4.20.1.2.10.58.117.254 = INTEGER: 2053 .1.3.6.1.2.1.4.20.1.2.10.58.119.254 = INTEGER: 2054 .1.3.6.1.2.1.4.20.1.2.10.58.125.1 = INTEGER: 2056 .1.3.6.1.2.1.4.20.1.2.10.58.126.1 = INTEGER: 2057 .1.3.6.1.2.1.4.20.1.2.10.58.127.254 = INTEGER: 2058 .1.3.6.1.2.1.4.20.1.2.10.58.129.254 = INTEGER: 2059 .1.3.6.1.2.1.4.20.1.2.10.58.135.1 = INTEGER: 2060 .1.3.6.1.2.1.4.20.1.2.10.58.136.1 = INTEGER: 2061 .1.3.6.1.2.1.4.20.1.2.10.58.137.254 = INTEGER: 2062 .1.3.6.1.2.1.4.20.1.2.10.58.139.254 = INTEGER: 2063 .1.3.6.1.2.1.4.20.1.2.192.168.93.254 = INTEGER: 2055 .1.3.6.1.2.1.4.20.1.2.192.168.168.168 = INTEGER: 320 snmpwalk -v1 -O n -c removed nortel8600.net.inet .1.3.6.1.2.1.4.20.1.1 | more .1.3.6.1.2.1.4.20.1.1.10.1.5.118 = IpAddress: 10.1.5.118 .1.3.6.1.2.1.4.20.1.1.10.58.115.1 = IpAddress: 10.58.115.1 .1.3.6.1.2.1.4.20.1.1.10.58.116.1 = IpAddress: 10.58.116.1 .1.3.6.1.2.1.4.20.1.1.10.58.117.254 = IpAddress: 10.58.117.254 .1.3.6.1.2.1.4.20.1.1.10.58.119.254 = IpAddress: 10.58.119.254 .1.3.6.1.2.1.4.20.1.1.10.58.125.1 = IpAddress: 10.58.125.1 .1.3.6.1.2.1.4.20.1.1.10.58.126.1 = IpAddress: 10.58.126.1 .1.3.6.1.2.1.4.20.1.1.10.58.127.254 = IpAddress: 10.58.127.254 .1.3.6.1.2.1.4.20.1.1.10.58.129.254 = IpAddress: 10.58.129.254 .1.3.6.1.2.1.4.20.1.1.10.58.135.1 = IpAddress: 10.58.135.1 .1.3.6.1.2.1.4.20.1.1.10.58.136.1 = IpAddress: 10.58.136.1 .1.3.6.1.2.1.4.20.1.1.10.58.137.254 = IpAddress: 10.58.137.254 .1.3.6.1.2.1.4.20.1.1.10.58.139.254 = IpAddress: 10.58.139.254 .1.3.6.1.2.1.4.20.1.1.192.168.93.254 = IpAddress: 192.168.93.254 .1.3.6.1.2.1.4.20.1.1.192.168.168.168 = IpAddress: 192.168.168.168 ========================================== Possible resolution needed to be coded in collector Plugin ================= Possible way to assign an IP to an physical interface using rapid city - nortel MIB find ifIndex -> with ifIndex find VLAN number -> with VLAN number find "routing interface" -> routing interface figure IP address # snmpwalk -v1 -c removed passport8600.net.inet .1.3.6.1.2.1.2.2.1.1 IF-MIB::ifIndex.64 = INTEGER: 64 IF-MIB::ifIndex.65 = INTEGER: 65 IF-MIB::ifIndex.66 = INTEGER: 66 IF-MIB::ifIndex.67 = INTEGER: 67 IF-MIB::ifIndex.68 = INTEGER: 68 IF-MIB::ifIndex.69 = INTEGER: 69 IF-MIB::ifIndex.70 = INTEGER: 70 IF-MIB::ifIndex.71 = INTEGER: 71 snmpwalk -v1 -c removed passport.net.inet .1.3.6.1.4.1.2272.1.3.3.1.7 SNMPv2-SMI::enterprises.2272.1.3.3.1.7.64 = INTEGER: 167 SNMPv2-SMI::enterprises.2272.1.3.3.1.7.65 = INTEGER: 1 SNMPv2-SMI::enterprises.2272.1.3.3.1.7.66 = INTEGER: 1 SNMPv2-SMI::enterprises.2272.1.3.3.1.7.67 = INTEGER: 1 SNMPv2-SMI::enterprises.2272.1.3.3.1.7.68 = INTEGER: 1357 SNMPv2-SMI::enterprises.2272.1.3.3.1.7.69 = INTEGER: 1347 SNMPv2-SMI::enterprises.2272.1.3.3.1.7.70 = INTEGER: 1317 SNMPv2-SMI::enterprises.2272.1.3.3.1.7.71 = INTEGER: 1322 [EMAIL PROTECTED] ~]# snmpwalk -v1 -c removed passport.net.inet .1.3.6.1.4.1.2272.1.3.2.1.6 SNMPv2-SMI::enterprises.2272.1.3.2.1.6.0 = INTEGER: 0 SNMPv2-SMI::enterprises.2272.1.3.2.1.6.1 = INTEGER: 2049 SNMPv2-SMI::enterprises.2272.1.3.2.1.6.167 = INTEGER: 2050 SNMPv2-SMI::enterprises.2272.1.3.2.1.6.1315 = INTEGER: 2051 SNMPv2-SMI::enterprises.2272.1.3.2.1.6.1316 = INTEGER: 2052 SNMPv2-SMI::enterprises.2272.1.3.2.1.6.1317 = INTEGER: 2053 SNMPv2-SMI::enterprises.2272.1.3.2.1.6.1319 = INTEGER: 2054 SNMPv2-SMI::enterprises.2272.1.3.2.1.6.1322 = INTEGER: 2055 SNMPv2-SMI::enterprises.2272.1.3.2.1.6.1345 = INTEGER: 2056 SNMPv2-SMI::enterprises.2272.1.3.2.1.6.1346 = INTEGER: 2057 SNMPv2-SMI::enterprises.2272.1.3.2.1.6.1347 = INTEGER: 2058 SNMPv2-SMI::enterprises.2272.1.3.2.1.6.1349 = INTEGER: 2059 SNMPv2-SMI::enterprises.2272.1.3.2.1.6.1355 = INTEGER: 2060 SNMPv2-SMI::enterprises.2272.1.3.2.1.6.1356 = INTEGER: 2061 SNMPv2-SMI::enterprises.2272.1.3.2.1.6.1357 = INTEGER: 2062 SNMPv2-SMI::enterprises.2272.1.3.2.1.6.1359 = INTEGER: 2063 [EMAIL PROTECTED] ~]# snmpwalk -v1 -c removed passport.net.inet .1.3.6.1.2.1.4.20.1.2 IP-MIB::ipAdEntIfIndex.10.1.5.118 = INTEGER: 2050 IP-MIB::ipAdEntIfIndex.10.58.115.1 = INTEGER: 2051 IP-MIB::ipAdEntIfIndex.10.58.116.1 = INTEGER: 2052 IP-MIB::ipAdEntIfIndex.10.58.117.254 = INTEGER: 2053 IP-MIB::ipAdEntIfIndex.10.58.119.254 = INTEGER: 2054 IP-MIB::ipAdEntIfIndex.10.58.125.1 = INTEGER: 2056 IP-MIB::ipAdEntIfIndex.10.58.126.1 = INTEGER: 2057 IP-MIB::ipAdEntIfIndex.10.58.127.254 = INTEGER: 2058 IP-MIB::ipAdEntIfIndex.10.58.129.254 = INTEGER: 2059 IP-MIB::ipAdEntIfIndex.10.58.135.1 = INTEGER: 2060 IP-MIB::ipAdEntIfIndex.10.58.136.1 = INTEGER: 2061 IP-MIB::ipAdEntIfIndex.10.58.137.254 = INTEGER: 2062 IP-MIB::ipAdEntIfIndex.10.58.139.254 = INTEGER: 2063 IP-MIB::ipAdEntIfIndex.192.168.93.254 = INTEGER: 2055 IP-MIB::ipAdEntIfIndex.192.168.168.168 = INTEGER: 320 _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
