<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body text="#000099" bgcolor="#ffffff"> I'm trying to figure out the best way to do this, yet keep things as simple as possible. Say I have a server called Saturn running VMWare. I'm monitoring this server with Nagios. I also have three VM's on Saturn: Jupiter, Mars, and Pluto I want to suppress all host and service alerts on Jupiter, Mars, & Pluto if the host Saturn is down (unreachable). I do NOT want to suppress host or service alerts from Jupiter, Mars, and Pluto if the VMWare processes (services) are down on Saturn. Basically, if my VM server is completely unreachable, don't bother me about its client VM's. Am I better off doing this with a host dependency? Something like: <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <pre>define hostdependency { host_name Host B dependent_host_name Host C notification_failure_criteria d,u } </pre> Or am I better off defining Saturn as the parent of the VM's in the host config? Something like: <pre>define host { host_name jupiter use VMs alias jupiter address 172.26.251.60 parents saturn, tpdmzsw1 }</pre> I've successfully used the "parents" directive to define network topology, so I would think this would work. What might be the risks of defining both? <pre class="moz-signature" cols="72">-- A. Davis Email: <a class="moz-txt-link-abbreviated" href="mailto:nccomp@gmail.com">nccomp@gmail.com</a> "There is no limit to what a man can accomplish if he doesn't care who gets the credit." - Ronald Reagan </pre> </body> </html>