Thanks - got it.
On 21 Jan 2005 at 13:57, Christian Theil wrote:
> Hi
>
> I was trying to to set up parent relationships today, and read
> networkreachability.html which told me to add a "parent_hosts"
> option. Nagios kept complaining that the parent_hosts directive was
> invalid.. I found out that now it is simply called "parents" and
> updated networkreachability.html, the diff is below:
>
>
>
> Index: networkreachability.html
> ===================================================================
> RCS file: /cvsroot/nagios/nagios/html/docs/networkreachability.html,v
> retrieving revision 1.2 diff -u -d -r1.2 networkreachability.html ---
> networkreachability.html 15 Oct 2003 23:49:23 -0000 1.2 +++
> networkreachability.html 21 Jan 2005 12:55:10 -0000 @@ -40,7 +40,7 @@
> "Local" hosts are hosts that reside on the same network segment as
> the host running Nagios - no routers or firewalls lay between them. href="#figure1">Figure 1 shows an example network layout. Host A
> is running Nagios and monitoring all other hosts and routers depicted
> in the diagram. Hosts B, C, D, E and F are all considered to be
> "local" hosts in relation to host A.
>
>
> -The <parent_hosts> option in the host definition for a
> "local" host should be left blank, as local hosts have no depencies or
> "parents" - that's why they're local. +The <parents>
> option in the host definition for a "local" host should be left blank,
> as local hosts have no depencies or "parents" - that's why they're
> local.
>
>
>
> @@ -69,7 +69,7 @@
> Notice that some hosts are "farther away" than others. Hosts H, I
> and J are one hop further away from host A than host G (the router)
> is. From this observation we can construct a host dependency tree as
> show below in Figure 2. This tree diagram will
> help us in deciding how to configure each host in Nagios.
>
>
> -The <parent_hosts> option in the host definition for a
> "remote" host should be the short name(s) of the host(s) directly
> above it in the tree diagram (as show below). For example, the parent
> host for host H would be host G. The parent host for host G is host
> F. Host F has no parent host, since it is on the network segment as
> host A - it is a "local" host. +The <parents> option in
> the host definition for a "remote" host should be the short name(s) of
> the host(s) directly above it in the tree diagram (as show below).
> For example, the parent host for host H would be host G. The parent
> host for host G is host F. Host F has no parent host, since it is on
> the network segment as host A - it is a "local" host.
>
>
>
> @@ -83,7 +83,7 @@
>
>
> Checking the status of remote hosts is a bit more complicated that
> for local hosts. If Nagios cannot monitor services on a remote host,
> it needs to determine whether the remote host is down or whether it is
> unreachable. Luckily, the -<parent_hosts> option allows
> Nagios to do this. +<parents> option allows Nagios to do
> this.
>
>
> If a host check command for a remote host returns a non-OK state,
> Nagios will "walk" the depency tree (as shown in the figure above)
> until it reaches the top (or until a parent host check results in an
> OK state). By doing this, Nagios is able to determine if a service
> problem is the result of a down host, an down network link, or just a
> plain old service failure.
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive
> Reporting Tool for open source databases. Create drag-&-drop reports.
> Save time by over 75%! Publish reports on the web. Export to DOC, XLS,
> RTF, etc. Download a FREE copy at
> http://www.intelliview.com/go/osdn_nl
> _______________________________________________ Nagios-devel mailing
> list [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
>
>
Ethan Galstad,
Nagios Developer
---
E
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]