From: Theodore TZEVELEKIS (theodore_tzevelekis@xxxxxxxxx)
Date: Sun May 20 2001 - 16:57:16 GMT-3
Thank you everybody for your answers.
All these options (ospf demand, floating statics,
subinterfaces... ) I have considered and yes, all of them
are valid workarounds (I implemented all of them). This is
mainly an academic question, less a practical one.
So I guess the answer is no... :-)
-----Original Message-----
From: Sean Reilly [mailto:skreilly@earthlink.net]
Sent: Sunday, May 20, 2001 9:47 PM
To: Theodore TZEVELEKIS; ccielab@groupstudy.com
Subject: Re: dlci nackup
Theo,
How about using a floating static route.
ip route 0.0.0.0 0.0.0.0 "next hop BRI" 220
This way if the link or DLCI goes down, all routes not in
the routing table
will be forwarded to the next hop BRI.
----- Original Message -----
From: Theodore TZEVELEKIS <theodore_tzevelekis@yahoo.com>
To: <ccielab@groupstudy.com>
Sent: Sunday, May 20, 2001 1:50 PM
Subject: dlci nackup
> Hi,
>
> How can one backup a single DLCI to a BRI.
>
> For example you have a serial with one or more dlci's
> configured. If the DLCI is killed from the other side, you
> want to back it up with the BRI. However, if you use the
> backup interface command on the main interface, as the
> latter does not go down (unless it is a subint, but I
don't
> want to use subints), backup does not work.
>
> TO make myself clear: If the DLCI goes down, the main
> interface still stays up so backup does not work.
> I'm looking for a wat to backup on a per DLCI basis.
>
> Any ideas?
>
> Cheers,
> Theo
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:46 GMT-3