Parent directive in non blocking network issues
Assaf Flatto
nagios at flatto.net
Wed Aug 4 11:17:57 CEST 2010
John Andrunas wrote:
> In a configuration like the following...
>
> nagios---firewall1----internet---firewall2---host1
> |---host2
> |---host3
>
> if there is an issue at firewall1 that causes packet loss I get
> alerted for everything after firewall1, if firewall1 goes down
> completely I only get an alert on firewall1 since nagios sees it as a
> blocking outage. I have all the parents setup, so is there a way to
> make the packet loss scenario behave more like a outage, so I don't
> get 36 notifications for everything on the other side?
>
>
>
You can set up service dependencies like this
define servicedependency{
host_name firewall
service_description PING - as every check
depends on the fact that you can reach (ping) the "host"
inherits_parent 1
dependent_service_description ( all services on the
firewall ) need to add each one.
execution_failure_criteria u,c,p,w
notification_failure_criteria u,c,p,w
}
This will supress all checks ( and alerts) for all services if the ping
( or equivalent check) fails.
for more information on how it works ,
http://nagios.sourceforge.net/docs/3_0/dependencies.html
--
Never,Ever Cut A Deal With a Dragon
Next year I will be doing the London to Paris bike ride to
raise money for the DogTrust (www.dogtrust.co.uk) .
Please Sponsor me at http://www.justgiving.com/Assaf-Flatto
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
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
More information about the Users
mailing list