chet wrote: > > My interim solution was this: > 1. Delete all my networks. > 2. Set the zDefaultNetworkTree on /Networks to: > 8 > 16 > 24 > 32 > 3. Run zenmodeler to rebuild all of the networks.
That doesn't fix the issue, it only hides it's true ugliness. If I create the correct supernet, then move the individual networks into the supernet, then zendisc breaks, complaining about networks not existing or some such. What's even more interesting, is that you can't have 192.168.0.0/16 and 192.168.0.0/24 in the same level of the tree - even though they are different networks for the intents of this feature... -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=6049#6049 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
