From: Tim Fletcher (tim@fletchmail.net)
Date: Wed Feb 26 2003 - 19:09:35 GMT-3
The link below describes the problem (just above the heading "RR and
Conventional BGP Speakers").
Halabi also explains the problem on p269, but goes on to says "Fortunately,
IOS has removed the full-mesh requirement on route reflector clients.
Currently, clients of a route reflector configured under a peer group are
not required to be fully meshed." But he doesn't say what version. I think
the book was based in 12.1. Does anybody know for certain?
-Tim Fletcher
At 11:34 AM 2/26/2003 -0800, soon ccie wrote:
>Hi, Where did you see that peer-group does not work w/ RR? it works fine
>for me...hope I did not
>miss what could be an important issue then.
>
>
>--- Annu Roopa <annu_roopa@yahoo.com> wrote:
> > David,
> > In addition to what i had said before also note a couple of things:
> > 1. U cannot use Peer-groups with Route-reflectors. If u want to use
> peer groups with route
> > -reflectors then u would have to disable the "route-reflector-client"
> on the RR (which u dont
> > want to bcoz the clients are not fully meshed). Look at thsi BGP link
> under Multiple RRs within
> > a Cluster - last para.Watch the wrap.
> >
> >
>http://www.cisco.com/en/US/tech/tk648/tk365/technologies_tech_note09186a00800c95bb.shtml#routereflectors
> > Also the RR scenario is used to overcome the full -mesh requirements of
> IBGP. So its is used but
> > in ur case since the clients get the routes from RR i guess they get
> only the BGP best path
> > selected by R6 the RR as also mentioned by someone else.
> > Try using two RR such that the lower 2 routers R2 and R5 get their
> routes form 2 RR's and see if
> > it makes a difference.
> > Hope that helps.
> > Annu.
> >
> >
> >
> > ---------------------------------
> > Do you Yahoo!?
> > Yahoo! Tax Center - forms, calculators, tips, and more
>
>
>__________________________________________________
>Do you Yahoo!?
>Yahoo! Tax Center - forms, calculators, tips, more
>http://taxes.yahoo.com/
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:37 GMT-3