clarification on parents and dependencies

Ivan Fetch lists at ivanfetch.com
Mon Apr 12 22:58:20 CEST 2004


Hi Matt - thanks very much for your reply:

> >    1. In order for the Nagios box to ping a particular Sun workstation, it
> > has to go through two switches.  I can specify one switch using the
> > parent directive in the host definition for the Sun workstation, but where
> > should I specify the relationship of the switch which the Nagios box is
> > plugged into?  This seems a bit clugy, but I could specify the switch
>
> Seems like this one is fairly straightforward, if I'm understanding you
> correctly.  By "has to go through two switches" do you mean something like
> this?
>
> Nagios -> Switch A -> Switch B -> Sun Workstation
>
   Yes, exactly.


> If it's the first one, then Switch B is the parent of the Workstation, and
> Switch A is the parent of Switch B.

   Ok, will switch a need to be the parent of all other switches
because the Nagios box is connected to switch a, even if both switch a and
switch b are connected by fiber to the router (vs. fiber connecting the
switches directly)?


> >    2. Our switches are in a different sub net (apparently in order to be
> > trunked), so if something is going wrong with our router, we can not ping
> > the switches.  Would folks out there recommend specifying the router as a
> > parent to
> > each switch's host definition?  I see a kind of loop potential in that
>
> This one is more compex.. it sounds like you've got some VLANs on the switch,
> and the packets pass through the switch a couple of times on their way to
> their destination, right?

Yes, the switches are trunked and getting their vlans from the router, so
even for local trafic on one switch to get where it's going, it looks like
communication with the router is necessary.  IF the router is experiencing
high load or some other problem, local trafic on a switch is still
effected (although none of that traffic should have to go anywhere except
from one fast ethernet port to another).  This makes it difficult for
Nagios to know whether the problem is the switch, the router, or a
host/service.  Since I can not ping the switch in this kind of a situation
(because the switch is in another subnet and has to go through the router)
perhaps incorparating the switches into my monitoring will not be
possible, or will not be very reliable?


Thanks -- Ivan Fetch.



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
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