On Tue, Mar 11, 2008 at 7:00 PM, Adam65535 <[EMAIL PROTECTED]> wrote: > I mistakenly it seems figured that the PING service would use the host > dependency config before sending a notification since a latency problem with > a remote office would cause every host at the remote office to spawn a PING > latency notification. I found out today that is not the case with nagios > (using 2.9). Do I have to keep replicating all my hosts dependencies into a > separate ping service dependency or am I missing something somewhere?
In Nagios 3.x you can use host groups for service and host dependencies, but even then I think that this isn't the best way to handle this situation. I think the best resolution for for this one is something like the following. I had a switch port that was attached to a VPN device I wasn't allowed to monitor, this port serves as the connection between our local and remote office, so I just created a fake host for the VPN, put the SNMP port and traffic status checks as the services for the VPN host , and then made the fake VPN 'host' the parent to our core router and the child to the remote office router .. so now when the VPN connection goes down or times out the remote map gets turned unreachable. Does that make sense? - Max ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null