Hi! On Tue, 27 May 2008, Hugo van der Kooij wrote: >> Unfortunately, Nagios connects multiple parent hosts with >> logical AND, which means that the host only turns UNREACHABLE >> when *both* switches are gone. > > The funny thing with redundant paths is that they are in fact > redundant. So if you loose one you still have connectivity and > nothing becomes unreachable. > > So where is the flaw in this design in Nagios? If breaking a > single link ~ will result in something becoming unreachable > then you do not have true redundancy.
Oh, the machines themselves aren't connected redundantly, only the switches themselves are. Usually the second link is used for connections to database machines and the like. As such, if either links goes down, the machine goes down (from a can-do-its-job perspective). Yes, I can still reach the machine (on convoluted paths since the backend nets are not routed). What I'm after is making a failing switch visible to the admins of such machines (and ideally everybody else), so I'm aiming for the distinction of DOWN vs. UNREACHABLE. I don't really want to make all the switches visible to all admins via the web interface (and I doubt they all are able to tell which switch is "theirs" just by the names). I don't see this behaviour as a *flaw* in Nagios, it's just unfortunate for me that it works this way and I had hoped there was a way around it. Regards, Tobias ------------------------------------------------------------------------- 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
