[quote="cluther"] > I'm trying to find some documentation on how the Networks screen is > populated. I understand that the route tables are built from the > individual routes. My confusion lies in the case were we have route > summarization. > > For example, I have a route in a device of 10.194.62.0/23 pointing > to another device. That other device has a a vlan interface of 62 > with an ip address of 10.194.62.1/24 and a vlan interface of 63 with > an ip address of 10.194.63.1/24. When looking at the vlan > interfaces in Zenoss, it is showing both of those vlans with a / > 23... Where is it getting that /23 from?? And of course, the route > table on this device has the 10.194.62.0/24 subnet and the > 10.194.63.0/24 subnet directly connected. > > It seems like maybe we need to find a way for Zenoss to be able to > compare route table entries of multiple devices and select the most > suitable route... I would be happy to help with this process in any > way I can!! >
This problem is an issue of ordering. The summarization /23 route is discovered first from the aggregate/whatever router so the network is created with the /23 mask. Then when the interfaces, routes and their more specific subnets are discovered they fall into the summarized network. There is a quick fix to this problem once you've discovered your routing infrastructure. You can simply delete all of the networks in the Networks screen, then remodel all interfaces first, then all routing tables by doing to following: zenmodeler run --collect=InterfaceMap ; zenmodeler run -- collect=RouteMap Our IP address/network creation routines could probably due with a refactoring to better handle addition of subnetworks, but this will get you going right now. I have the VMware appliance (2.1.3) and also have this problem. I have tried the suggestion above and it doesn't work for me. My netmasks range from network 10 subnetted down to class B, down to (different) /28 networks. As I understand the documentation, this changeset 7993 ought to be in the 2.1.3 code that I have? How do I tell? I also have issues with discovery in the class B network which again appears to be fixed by a change to AsyncPing.py in the 2.1.3 code but my AsyncPing.py is dated August 07 so I have doubts as to what I actually have - how do I tell? If I am backlevel, what is the recommended procedure for patching up? The VMware appliance is great for getting you started though! Cheers, Jane -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=18803#18803 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
