We've recently added an MPLS circuit between two of our sites. We have two identical Cisco model routers on each side of the MPLS link. The router serial and fast ethernet interfaces between two sites are either 29 or 30 bit masked. When I run an inventory of the routers, however, Zenoss places them in a 24 bit subnet (which tramples a number of existing subnets). If i run snmpwalk on the routers, the IF-MIB entries show the appropriate interface subnets.
IP-MIB::ipAdEntNetMask.10.xxx.xxx.xxx = IpAddress: 255.255.255.248 IP-MIB::ipAdEntNetMask.10.xxx.xxx.xxx = IpAddress: 255.255.255.248 IP-MIB::ipAdEntNetMask.172.xxx.xxx.xxx = IpAddress: 255.255.255.252 When I inventory the core switches that are now connected by the routers (which have been in our Zenoss system for years) , the VLAN and FastEthernet interfaces belong to the appropriate 29 bit subnets. I don't know if this is a device model related issue, or if it is a flaw introduced in the 2.3.3 code for new devices. I am also seeing similar messages to those below in the zenhub log. I am seeing them for most of my devices (not just the routers in question), since the upgrade to 2.3.x. |2009-04-08 11:54:07 INFO zen.ZenHub: Worker reports WARNING:zen.ZenStatus:device '172.xxxx.xxx.xxx' network '172.xxx.xxx.xxx/30' not in topology 2009-04-08 11:54:07 INFO zen.ZenHub: Worker reports WARNING:zen.ZenStatus:device '172.||xxx.xxx.xxx||' network '172.||xxx.xxx.xxx||/30' not in topology 2009-04-08 11:54:07 INFO zen.ZenHub: Worker reports WARNING:zen.ZenStatus:device 'hostname.domain.com' network '10.xxx.xxx.xxx/29' not in topology| Any help? _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
