Simple Question, UNREACHABLE vs DOWN

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Steven Coutts
> Sent: Thursday, September 29, 2005 8:50 AM
> To: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] Simple Question, UNREACHABLE vs DOWN
> 
> (Top posting error corrected!)
> 
> Rob Moss wrote:
> >>
> >> Someone correct me if i'm wrong but my understanding is:
> >>
> >> Unreachable is the first single ping check when nagios is started
up..
> >>
> >> Down is a hard state, after checking X many times (usually 10,
> >> defined in nagios.cfg) it's flagged as down.
> >>
> >> Cheers
> >> rob.
> >>
> Pete Dewell wrote:
> > I agree with the down definition, but I've always thought of
> > unreachable as :
> >
> > Unreachable is when the parent of a host is down. e.g. if host1 is
> > down, then any hosts that have host1 as a parent will be marked as
> > unreachable, since Nagios cannot connect to those hosts to check
them.
> >
> > Pete Dewell
> Ah I see, pretty obvious really!
> 
> Makes sense from my stats, expect one anomaly. One of my switches went
> down, this switch has three other switches hanging off it (all three
> have the correct parent set in my config) but only two have been
marked
> as being unreachable for that period!!

Then I would hazard that either the parents directive is incorrect for
that host or it hasn't been checked yet.

A link to the documentation may prove informative --

http://nagios.sourceforge.net/docs/1_0/networkreachability.html

--
Marc


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
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