parent/child relationships once again, but something special to consider. zenoss determines these from the routes it has discovered, and that works well except in certain cases.
virtual IP addresses, for example... VMware guests on a bridged interface, where these guests are "behind" a server but both the parent and children are on the same subnet. route-discovery won't work here. also i use it to follow a parent/child path between two private networks connected by VPN, where their edge-IP, public gateways, their "next hops" from ISPs, are all checked. i have a feeling this private->public->private path will be difficult to model in zenoss so i may continue to need nagios to monitor the edge routers. also, support for the nrpe daemon would be another great way to help migration. zenoss is great, thanks for all the effort ! ------------------------ benjamin9999 -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=11189#11189 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
