On Feb 22, 2008, at 8:19 PM, <[EMAIL PROTECTED]> wrote: > > Dear Folks, > > I am writing to request comments on a proposal to reduce the risk of > loss of Network visibility/spurious alerts etc caused by the failure > of the Nagios host's default gateway. > > When the Nagios host is connected via multiple links, it is still > necessary to ensure that data flow either both links or that somehow > traffic is diverted to the other links. > > Solutions I have rejected include > > 1 Link teaming/bonding - immature in Linux > Don't dismiss this out-of-hand. This is used extensively in our Communications Provider grade hosted VOIP systems, with 99.99% guaranteed uptime, and it's worked like a champ through all our testing. It's used in failover mode to provide for hot-standby systems.
> Here is what I think is the best fit: an application layer (non > kernel) fault tolerant router. > > This could be implemented by > > 1 a Nag service check of the reachability of the default router > > 2 an event handler (run by sudo) that replaces the default router if > the check returns CRITICAL HARD. > Straightforward and no immediately obvious issues with it. You could use the same event handler to fall back when it recovered. -- 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 [email protected] 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
