[nsp] Proper way of doing dial backup for an ethernet(DSL) link

[Krzysztof Adamski]

I guess I should have included the background. I'm the ISP and the other
end is a customer. For this reason I don't really want to run OSPF with
him. BGP is safer.
Based on the responses the watch-group is the correct way, I got this
working. I'm sending the default route, and I'm watching an other route.
And I have a floating default pointing at the dialer with high metric.

Now, what should I do for the connection to switch back to Ethernet, the
only way I can think of is by filtering BGP through the modem. Is there a
better way?

K

On Fri, 2 Aug 2002, Brad Bonin (bbonin) wrote:

> Ospf demand would work...if the ospf neighbor goes down on the Ethernet
> interface, then ospf would reconverge, force the ospf demand circuit to
> come up and exchange new routing information....which would cause routes
> to be preferred over the backup circuit as this circuit is the only
> valid path now...
> 
> Give it a shot....if you are running ospf that is.
> 
> -----Original Message-----
> From: Ezequiel Carson [mailto:ezequiel@ifxnw.com.ar] 
> Sent: Friday, August 02, 2002 9:30 AM
> To: brad@cisco.com
> Cc: 'Krzysztof Adamski'; 'Josh Duffek'; cisco-nsp@puck.nether.net
> Subject: RE: [nsp] Proper way of doing dial backup for an ethernet(DSL)
> link
> 
> 
> i have used  DDR on Serials and when the primary serial is down, the 0/0
> is removed from FIB and then,  0/0 poiting to ASYC interface takes place
> in the FIB.
> 
> But i think that this is not possible if the eth0 never go down :)
> 
> so we need a keepalive method. :)
> 
> 
> On Fri, 2002-08-02 at 11:30, Brad Bonin (bbonin) wrote:
> > Sounds like a question I had on my ccie exam a few years back.
> > 
> > The trick was to use an ospf demand circuit over the backup 
> > connection....
> > 
> > Or you could use another routing protocol and dink around with Admin 
> > Distances....
> > 
> > brad
> > 
> > -----Original Message-----
> > From: cisco-nsp-admin@puck.nether.net 
> > [mailto:cisco-nsp-admin@puck.nether.net] On Behalf Of Ezequiel Carson
> > Sent: Friday, August 02, 2002 6:52 AM
> > To: Krzysztof Adamski
> > Cc: Josh Duffek; cisco-nsp@puck.nether.net
> > Subject: Re: [nsp] Proper way of doing dial backup for an 
> > ethernet(DSL) link
> > 
> > 
> > If your eth0 will never go down, the floating route will not work. so 
> > me be is better to use a simple and FAST routing protocol. (we should 
> > reconfigure protocolo's time)
> > 
> > 
> > 
> > On Thu, 2002-08-01 at 22:29, Krzysztof Adamski wrote:
> > > What I'm asking is, from all the possible ways that are now 
> > > available,
> > 
> > > what is it best way? Running BGP, is this a good thing, or would RIP
> > > be better, or OSPF? Or should I use DDR?
> > > 
> > > K
> > > 
> > >  On Thu, 1 Aug 2002, Josh Duffek wrote:
> > > 
> > > > There is no real way to do this right now, without some dynamic
> > > > routing/floating statics(or dialer watch).  There is a feature 
> > > > request bug for what you want though...CSCds88143...someone is 
> > > > working on it right now.
> > > > 
> > > > josh
> > > > 
> > > > ----- Original Message -----
> > > > From: "Krzysztof Adamski" <k@adamski.org>
> > > > To: <cisco-nsp@puck.nether.net>
> > > > Sent: Thursday, August 01, 2002 4:15 PM
> > > > Subject: [nsp] Proper way of doing dial backup for an 
> > > > ethernet(DSL)
> > > > link
> > > > 
> > > > 
> > > > > I have a DSL link that is terminated as an Ethernet connection, 
> > > > > I
> > > > > would like to setup a dialup failover for it. Since it is an 
> > > > > Ethernet I can't watch the physical interface. I have a cisco
> 1721
> > 
> > > > > on the remote end.
> > > > >
> > > > > One way is to run BGP between the two points and then to "watch"
> 
> > > > > a
> > 
> > > > > route.
> > > > >
> > > > > But what is the best way of doing this, I have full control of
> > > > > both ends, but at the same time I want to protect the central 
> > > > > point from the remote.
> > > > >
> > > > > K
> > > > >
> > > > > _______________________________________________
> > > > > cisco-nsp mailing list  real_name)s@puck.nether.net
> > > > > http://puck.nether.net/mailman/listinfo/cisco-nsp
> > > > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> > > > 
> > > 
> > > _______________________________________________
> > > cisco-nsp mailing list  real_name)s@puck.nether.net
> > > http://puck.nether.net/mailman/listinfo/cisco-nsp
> > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> > > 
> > 
> > 
> > _______________________________________________
> > cisco-nsp mailing list  real_name)s@puck.nether.net 
> > http://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> > 
> > 
> 
> 
>