Date: Mon, 29 Jun 1998 23:21:17 -0400 From: Luis Munoz <lem@cantv.net> To: Tim Tsai <tim@futuresouth.com> Cc: Bo Fussing <bmf@gateway.net.hk>, Luis Munoz <lem@cantv.net>, Evren Yurtesen <yurtesen@ispro.net.tr>, freebsd-isp@FreeBSD.ORG Subject: Re: cisco Message-ID: <3.0.5.32.19980629232117.03a1f2d0@pop.cantv.net> In-Reply-To: <19980629203659.50524@futuresouth.com> References: <Pine.LNX.3.96.980630091855.20371D-100000@gate.gateway.net.hk> <19980629194051.08954@futuresouth.com> <Pine.LNX.3.96.980630091855.20371D-100000@gate.gateway.net.hk>
next in thread | previous in thread | raw e-mail | index | archive | help
At 08:36 PM 29/06/1998 -0500, Tim Tsai wrote: >On Tue, Jun 30, 1998 at 09:22:18AM +0800, Bo Fussing wrote: > This is assuming that the primary server completely dies (does not >answer to the IP or MAC address) - which is not necessarily the case >(i.e. perhaps only the proxy application died and not the server). You can combine dynamic routing with some sort of 'self-testing'. If the proxy dies (but not the server), you can arrange for either a proxy restart or a stopping of the dynamic routing (please see my earlier response). Regards. -lem > With policy route you can set the next-hop-ip address but the question >becomes how do you get the backup server to answer to that IP address >correctly, even if the primary server still answers to that IP in someway. >All the setup's I know of involves another additional level (either a >hardware switch that supports virtual IP's or something like Cisco's >localdirector) and the actual proxy servers sit behind this localdirector >type device. > > I suppose with some hardware help you can cut (open circuit) the ethernet >connection or simply power down the failed primary server. > >> Another is to have some remote monitoring of the proxy and notification to >> the system admin (by pager) of the failure. > > We do that but that's hardly what I'd call redundancy. :-) > > Tim > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.5.32.19980629232117.03a1f2d0>