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.
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
