Triggering the "Network Outages" display under Tactical Overview

[Marc Powell]

You're actually looking for the 'parents' directive as opposed to host
dependencies --
 
http://nagios.sourceforge.net/docs/1_0/xodtemplate.html#host
 
and
 
http://nagios.sourceforge.net/docs/1_0/networkreachability.html
 
--
Marc 

________________________________

From: Platt, Nicholas [mailto:Nick.Platt at myflorida.com] 
Sent: Wednesday, January 21, 2004 3:01 PM
To: 'Nagios-users at lists.sourceforge.net'
Subject: [Nagios-users] Triggering the "Network Outages" display under
Tactical Overview

Hello:

I've read the documentation and have created a small test scenario to
try and trigger the count under "Network Outages".   I turn of the test
core router and the NMS does only send me one page, but it did not
interpret the failure of the core router and hits child host as a
network failure.  I've looked at this all day and have not been able to
fix the problem.   I'm a newbie and any help will be greatly
appreciated.   See attachment. Thanks

########################################################################
########
# HOST DEPENDENCY DEFINITIONS
#
# SYNTAX:
#
########################################################################
########

define hostdependency{
      host_name               Test-core-router
      dependent_host_name           Test-server
      notification_failure_criteria d,u
      }

define hostdependency{
      host_name               Test-core-router
      dependent_host_name           Test-server2
      notification_failure_criteria d,u
      }




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Nagios-users mailing list
Nagios-users at 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