From: CharlesB (cbalik@adelphia.net)
Date: Fri Aug 25 2006 - 15:24:00 ART
It is mostly about routing loop prevention.
If EBGP process sees it own AS number on a receiving route update, the
process realizes a loop and drops the update.
But IBGP does not have this privilege, because the neighbor is also in the
same AS.
So, to prevent this shortcoming, IBGP peers do not advertise routes learned
from one peer to the other IBGP peer. Think about split horizon like
solution.
But this brings a full mesh topology on the table. Plus on top of this, you
need to consider your physical layer connections between the nodes.
If you have r1----r2----r3, it makes sense to have r2 reflect routes from r1
to r3 and vise versa.
r1 and r3 does not know anything about each other but they learn routes from
each other through r2.
There are many other scenarios and considerations in this topic, it could go
lot deeper but this is what I can come up with in order to give you some
quick start on the concept. I am sure experts in this group could explain
better.
One of the short comings of this solution is that r2 only reflects the best
routes to the clients. Basically it just builds its own route selection and
then reflects.
Implementations of route reflector mostly related to partial mesh and
networks with limited physical layer access between nodes.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of F
R
Sent: Friday, August 25, 2006 10:36 AM
To: ccielab@groupstudy.com
Subject: Route reflector
Dear All,
Please help me to understand about route reflector. when we must to use
route reflector and where we must implement.. i very appreciate for your
help..
regards,
beat
This archive was generated by hypermail 2.1.4 : Fri Sep 01 2006 - 15:41:58 ART