From: OhioHondo (ohiohondo@columbus.rr.com)
Date: Fri Apr 11 2003 - 21:30:46 GMT-3
Danny
When you use route reflectors, all RR's and non-clients have to be in a full
mesh. The RR clients "hang" off of the RR's. In your scenario you have a RR
with 2 RR clients. The RR is also connected to a non-client (a BGP router in
the same AS that is another RR or just has IBGP sessions with non-clients).
Since you only have 2 non-clients, you have a full mesh.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Danny Andaluz
Sent: Friday, April 11, 2003 4:05 PM
To: ccielab@groupstudy.com
Subject: BGP question
I have a question about non-clients in a route-reflector topology.
Assuming all routers are in the same AS, you have a hub and spoke topology
where the RR has three peerings with three different routers. Only two of
those neighbors are configured as route-reflector-clients. In Doyle's
routing TCPIP V. 2 pg. 127, it says that if a RR learns a route from a
RR-client that route will be sent to the other RR-client as well as the
non-client. I am under the impression that a non-client is simply a
neighbor that is not configured as a RR-client in the RR. If this
non-client was in a different AS, I can see this happening because that is
EBGP, but IBGP assumes a full mesh, so how could the RR send this route to
the non-client? Of course, I'm going on the assumption that a non-client is
what I described previously. So I guess my question really is, what is a
non-client?
TIA,
Danny
This archive was generated by hypermail 2.1.4 : Thu May 01 2003 - 13:35:51 GMT-3