From: Roman Rodichev (rodic000@xxxxxxxxxxx)
Date: Wed May 16 2001 - 21:35:56 GMT-3
Very nice! I like it. But you can't do it.
As soon as R1-R2 connections is gone, Area 1 and Area 2 need some way of
connecting to area 0. You can only do it with a virtual link. But virtual
link will never run over the interface that is not running OSPF :)
try enabling ospf demand-circuit on the bri and tell us how it works out
>From: "Theodore TZEVELEKIS" <theodore_tzevelekis@yahoo.com>
>Reply-To: "Theodore TZEVELEKIS" <theodore_tzevelekis@yahoo.com>
>To: "ccie-groupstudy" <ccielab@groupstudy.com>
>Subject: Question: OSPF, DDR, backup routes
>Date: Thu, 17 May 2001 01:43:37 +0200
>
>Hi all,
>
>I've been trying to find a way to solve a very specific problem... wihtout
>any luck:
>
>You have 3 routers running OSPF:
>R1 (e0-area0, e1-area1, bri1 -> R3, virtual-link to R2)
>R2 (e0-area1, e1-area2(nssa), e3-area1, virtual-link to R1)
>R3 (e0-area2(nssa), BRI1 -> R1)
>
>OSPF is NOT running on ISDN.
>I inject a default route from R2 into area 3 therefore to R3, pointing to
>itself (R2) - default-information yada yada.
>
>Now what I want, is with just one default on R3, and statics on R1
>(floating
>in both occasions) to be able to access R2-e3 through the ISDN in the event
>of (R1-e1)<->(R2-e0) failure.
>
>What this means is that I have to somehow inject a default route into R2
>when the ISDN comes up (Reminder: in normal circumstabnce, R2 is injecting
>a
>default route into R3). Furthermore, OSPF does NOT redistribute static
>default routes. The only way I have found so far is to actually generate a
>default-info yada yada on R3 when the link comes up. BUT! as soon as R2
>receives this, it, in turn, generates a new default-info and injects it
>back
>into R3.
>
>Also, as the virtual link is down, I have to find a way to inject that
>route
>into the OSPF neighbors in area 1 hanging out of R2-e3.
>
>Any ideas?
>
>Thanks
>
>Theo
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:42 GMT-3