On Aug 18, 2009, at 9:15 AM, arly arly wrote:
> I am monitoring firewall too, and I am just checking PING to it and
> rount trip time
>
> with
>
> define service{
> use test
> host_name firewall
> service_description PING
> check_command check_ping!200.0,40%!400.0,50%
> }
This is a service check. You probably want to set this check_command
as the host's check_command.
> define hostdependency{
> host_name firewall
> dependent_host_name host_behind_firewall
> notification_failure_criteria d
> }
Host dependencies depend on the host check, not an arbitrary service
check on that host.
> with this I want to stop checkig ( and get just one notification about
> failure ) of host(s) behind firewal in case it is not possible to
> ping firewall .
>
> Then I blocked ping on firewall and it showed as DOWN via nagios web,
> but still I am getting correct information about
> "host behind firewall",
Did the *host* status change to critical or just the service status?
The host's check_command must return a non-OK result for the host
dependency to even trigger. It makes no difference what the status of
any service on that host is if the host is still shown to be OK.
You probably don't want host dependencies at all anyway. It sounds
like the parents directive in the dependent host definitions meets
your needs and is much simpler to use.
http://nagios.sourceforge.net/docs/2_0/networkreachability.html
--
Marc
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
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
