Re: Redistribution loop avoidance

From: GAURAV MADAN (gauravmadan1177@gmail.com)
Date: Fri Dec 05 2008 - 13:26:55 ARST


Thnx Jason .. got ur point ..

R1 , R2 , R5 were on shared media .
Hence R1 and R2 both were aware of same routes and yes there were external
EIGRP route as well .

SO I just set ospf external distance to 171 on R1 and R2 and it worked.

Thnx again

On Fri, Dec 5, 2008 at 12:25 AM, Jason Madsen <madsen.jason@gmail.com>wrote:

> are R5, R2, and R1 in a hub and spoke topology? ...does R1 already
> know of the routes that R2 will be redistributing into OSPF? If it
> already knows of the routes and considers them "internal", you
> shouldn't have to do anything since EIGRP internal routes have a lower
> admin' distance than external routes learned via another protocol.
>
> if R1 somehow has other EIGRP external (admin distance 170) knowledge
> of the routes R2 is advertising just set your OSPF external distance
> to 171 or greater so that they won't be preferred.
>
> Jason
>
> On 12/4/08, GAURAV MADAN <gauravmadan1177@gmail.com> wrote:
> > Hi friends
> >
> > I have following setup :
> >
> > r5------| =====r2 -----------rr
> > |===== r1 ----------rr2
> >
> > <--EIGRP ------> <------ OSPF--->
> >
> > r5 , r1 , r2 in eigrp
> > r1 , r2 , rr,rr2 in ospf
> > hence r1 and r2 are ASBR also.
> >
> > I am asked to redistribute b/w 2 protocols and redistribution shd be such
> > that EIGRP routes redistributed in OSPF on R2 should not go back in EIGRP
> > via R1 .
> > I am not allowed TAG in this .. (that I can do easily) .. I am asked to
> use
> > administrative distance for the same .
> >
> > Can someone help me in this
> >
> > alas we dont have "match distance " or set distance " in route-maps.
> >
> > Gaurav Madan
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net



This archive was generated by hypermail 2.1.4 : Thu Jan 01 2009 - 12:53:07 ARST