2008/11/14 Weetos <[EMAIL PROTECTED]> > Nope you're not - I'm using all kinds of network size, from /16 to /30 with > almost any values in between > > and yes the way zenoss manage subnetworks seems to be buggy > > ie: I have contiguous /30 subnetworks in /24 networks > > x.y.z.0/30 appears in x.y.z.0/24 as expected > x.y.z.4/30 appears as a subnet of x.y.z.0/30 which is wrong > x.y.z.8/30 appears as a subnet of x.y.z.0/30 ans so on > > btw I'm running 2.2.4 (and hopefully I'll update to 2.3) > > > I don't think the new version fixes it. I have something similar starting with a /16 that is subdivided down into /20s and /24s. When a device is modeled it often creates a new subnet under the network it should be placed in.
E.g. The device has a /20 IP. Under the appropriate /20 network object I get a new /18 subnet, under that a /20 and under that the device. Given long enough time for the modeller to get it wrong and I end up with even more repeating networks, e.g. /16 -> /18 -> /20 -> /18 -> /20 -> /16 -> /18 -> /20 I've tried deleting all the errant networks and fixing the layer3 catalog ( http://www.zenoss.com/Members/cluther/fix-a-broken-layer3_catalog), but they keep coming back. The modeller is picking up the wrong network when modelling the device and adding a new subnet to it. -- Regards, Graham Bloice
_______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
