From owner-freebsd-isp Mon Jun 29 20:29:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16252 for freebsd-isp-outgoing; Mon, 29 Jun 1998 20:29:41 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from NIH2WAAE (smtp5.site1.csi.com [149.174.183.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA16230 for ; Mon, 29 Jun 1998 20:29:32 -0700 (PDT) (envelope-from lem@cantv.net) Received: from mail pickup service by csi.com with Microsoft SMTPSVC; Mon, 29 Jun 1998 23:28:57 -0400 Received: from lem (sf-dnpqj-007.compuserve.net [206.175.228.7]) by hil-img-ims-3.compuserve.com (8.8.6/8.8.6/IMS-1.3) with SMTP id XAA28066; Mon, 29 Jun 1998 23:28:16 -0400 (EDT) Message-Id: <3.0.5.32.19980629232117.03a1f2d0@pop.cantv.net> X-Sender: lem@pop.cantv.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 29 Jun 1998 23:21:17 -0400 To: Tim Tsai From: Luis Munoz Subject: Re: cisco Cc: Bo Fussing , Luis Munoz , Evren Yurtesen , freebsd-isp@FreeBSD.ORG In-Reply-To: <19980629203659.50524@futuresouth.com> References: <19980629194051.08954@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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