bump, I'd love to be able to define my dependencies manually, either by group or location or just on an individual device. My biggest problem is most of our machines have 3 nets, a public net that gets routed to the internet, a management net that is only routed via VPN, and a data network that is only routed within the rack. The biggest problem I have is the data net is the same at each site which seems to confound zenoss (it seems to continually move the IP from one machine to another). Both the public and VPN interfaces depend on unknown and varying routers on the internet which I do not have any control over or insight into. I've tried adding fake routes to the VPNs (zenoss doesn't collect them on its own) but that doesn't seem to work when we see an outage. My ideal would be a simple "needs"/"needed by" flags for each device that would override what Zenoss thinks it knows about the topology, And of course some visual way of verifying the layout.
-------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=29711#29711 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
