[prev in list] [next in list] [prev in thread] [next in thread] 

List:       isp-bgp
Subject:    [isp-bgp] RE: Problem with RRs
From:       "Kaliraj V - CTD, Chennai." <kalirajv () ctd ! hcltech ! com>
Date:       2004-06-22 10:24:12
Message-ID: 68C9DA8F50019B4E8622C53811BEE1D60113B2BF () kavithai ! ctd ! hcltech ! com
[Download RAW message or body]

I guess you can make the RR select route given by R1 by applying some kind
of policy. So that RR will select R1's route and advertise it to R3. In case
R1 becomes unavailable, route from R2 would get selected at RR and thus
traffic from R3 will start flowing thru R2 instead of R1. 

In either case, traffic would-not flow thru RR assuming routes advtd by R1
and R2 say that they are nexthops. So, RR doesnt need to come in the
forwarding path, which is never mandatory!

The kind of policy you can apply at the RR can be like tweaking the
local-preference or weight attributes so-as-to give more preference to R1
than R2.

Kaliraj.

-----Original Message-----
From: Tulip Rasputin [mailto:tulip_rasputin@yahoo.ca]
Sent: Tuesday, June 15, 2004 5:15 PM
To: isp-bgp@isp-bgp.com
Subject: [isp-bgp] Problem with RRs


Hi,

I have a Route Reflector (RR) in my topology. It receives two equal cost BGP
routes (from clients R1 and R2) but it announces just one to its downstream
peer R3. The RR is selecting R2 based on the lower Router ID. So, it just
announces the route it learns from R2. R3 thus ends up sending all its
traffic to R2. For R3, R1 is closer than R2. Is there a way i can have R3
sending all the traffic to R1. Also note that in my network, R3 can
independently reach both R1 and R2 and it need not go through RR for this.

 R1         R2
   |__RR__|
         |
       R3

I did talk to some folks and they said that i should set the "nexthop self"
on the RR, so that all the traffic flows via the RR, which can split the
load between R2 and R3.

Is this the only solution? Or is it mandated that the RR come in the
forwarding path?

Thanks,
Rasputin




_______________  The ISP-BGP Discussion List  ______________
To Join: mailto:join-isp-bgp@isp-bgp.com
To Remove: mailto:remove-isp-bgp@isp-bgp.com
Archives: http://isp-lists.isp-planet.com/isp-bgp/archives/
************************************************
ISPCON FALL 2004 - Santa Clara Convention Center
************************************************
      New Keynote Speakers just announced:
   Jeff Pulver, President & CEO of Pulver.com
Nigel Ballard, Wireless Director, Matrix Networks

 Use discount code EBF04 now and pay only $350!
      REGISTER TODAY at www.ispcon.com

To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016

Please include the email address which you have been contacted with.


_______________  The ISP-BGP Discussion List  ______________
To Join: mailto:join-isp-bgp@isp-bgp.com
To Remove: mailto:remove-isp-bgp@isp-bgp.com
Archives: http://isp-lists.isp-planet.com/isp-bgp/archives/
************************************************
ISPCON FALL 2004 - Santa Clara Convention Center
************************************************
      New Keynote Speakers just announced:
   Jeff Pulver, President & CEO of Pulver.com
Nigel Ballard, Wireless Director, Matrix Networks

 Use discount code EBF04 now and pay only $350!
      REGISTER TODAY at www.ispcon.com

To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016

Please include the email address which you have been contacted with.

[prev in list] [next in list] [prev in thread] [next in thread]