> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Eric F Crist > Sent: Tuesday, January 15, 2008 10:11 AM > To: <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED]; nagios-users@lists.sourceforge.net > Subject: Re: [Nagios-users] nagios and parenting... > > Tom, > > Thanks for the reply, but my original question is not answered by the > FAQ you linked. That sorta leads me toward the correct answer to a > question I've posted since, but that question was asked in response to > someone's reply to my original question. > > So, apparently I need to re-pose the question I originally asked, > since some seem to be confused. > > In regards to parenting and unreachable notifications, is there any > way to tell the nagios process where within the hierarchy it resides, > or is this figured out automatically? At least in my mind, I'd need > to know where I was on a map to know what was between me and my > destination to figure out if the problem was somewhere in between, or > with my destination.
Nagios assumes it lives as the next hop after the last defined parent in a chain. Nagios <- parent <- parent <- parent <- host If there's something else in-between that you haven't defined as a parent, nagios has no way to figure out that relationship so everything between nagios and the last defined parent will be DOWN (including the last parent) and all others would be UNREACHABLE. Nagios <- (down host) <- down parent <- unreachable parent <- u parent <- u host HTH -- Marc ------------------------------------------------------------------------- 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