<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=us-ascii"> <META content="MSHTML 6.00.2900.2722" name=GENERATOR></HEAD> <BODY text=#000000 bgColor=#ffffff> <DIV dir=ltr align=left>Oops, forgot to send this to the list.</DIV> <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left> <HR tabIndex=-1> From: nagios-users-admin@lists.sourceforge.net [mailto:nagios-users-admin@lists.sourceforge.net] On Behalf Of Rossz Vamos-Wentworth Sent: Friday, October 21, 2005 10:18 AM To: Nagios-users@lists.sourceforge.net Subject: [Nagios-users] parent/child pains </DIV> <DIV></DIV> <DIV class=moz-text-flowed lang=x-western style="FONT-SIZE: 13px; FONT-FAMILY: -moz-fixed">I guess I'm misunderstanding how this works. I'm running Nagios 1.2 on Debian. I configured the remote servers to have my local router as their parent. The router status is tested by checking for an internet connection from the nagios server. The idea being when my nagios host looses its internet connection I won't receive a ton of notifications. I have one of the remote systems monitoring my nagios server just so it can alert me when there is a connectivity problem. This morning the nagios server lost its internet connection and queued up a mess of alerts for all the remote services it is monitoring. It couldn't actually send them out since that requires an internet connection. When connectivity returned all those "down" alerts went out, followed closely by the "Up" alerts. I did receive the notification from the remote system letting me know my nagios server had a problem and recovered, so at least something worked right. </DIV> <DIV class=moz-txt-sig lang=x-western style="FONT-SIZE: 13px; FONT-FAMILY: -moz-fixed">-- Rossz </DIV></BLOCKQUOTE> <DIV class=moz-txt-sig lang=x-western dir=ltr style="FONT-SIZE: 13px; FONT-FAMILY: -moz-fixed">I think of parents as "previous hop" from the perspective of the Nagios server doing the checking.</DIV> <DIV class=moz-txt-sig lang=x-western dir=ltr style="FONT-SIZE: 13px; FONT-FAMILY: -moz-fixed"> </DIV> <DIV class=moz-txt-sig lang=x-western dir=ltr style="FONT-SIZE: 13px; FONT-FAMILY: -moz-fixed">I'm not sure I've got the right picture of your setup, but I'll take a stab at it.</DIV><PRE class=moz-txt-sig lang=x-western dir=ltr style="FONT-SIZE: 13px; FONT-FAMILY: -moz-fixed">Your Nagios --- Router --- Internet --- Remote Nagios +-------- Remote service 1 +-------- Remote service 2 +-------- Remote service 3</PRE> From the perspective of "Your nagios", Router has no parent Internet's parent is Router Remote Nagios and Remote service 1-3's parent is Internet If you don't already have an "Internet" host, make one and set its address to the first hop after your router when you do a traceroute out from "Your Nagios" (operating on the assumption that if the first hop is the first router after your DSL/Cable/T1/whatever line). From the perspective of "Remote Nagios", Internet has no parent (you'll want to use a different address, since Remote Nagios' first hop won't be the same as Your Nagios's) Router's parent is Internet Remote service 1-3's parent is Internet (unless the Remote services are behind the same connection as Remote Nagios, in which case they will have no parents) Your Nagios' parent is Router --Ludwig Pummer </BODY></HTML>