Even with the enterprise product some of my sites may simply not be able to support a local master server. With that said, I would llike to see the ability to add an attribute to a network that would associate it with an organization. The idea being that since these RFC1918 networks are supposed to be private to an organization, this attribute would serve to identify that very organization. From there it should not be too difficult to realize that each organization's use of 192.168.1.0/24 is distinct from the other. Adding this same attribute to all networks would make sense and two RFC1918 networks could only communicate if facilitated by a dual-homed device.
That makes sense. We'd also have to take it another step and associate the organization with device classes/devices with a zProperty so that the modeling plugins that discover IP addresses, networks and routes could associate them with the correct network.
A flag would also have to be added to zendisc so that discovery would place the IPs in the correct place. I've put a ticket in to keep an eye on this issue.
Ticket: http://dev.zenoss.org/trac/ticket/2214 _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
