From: Joe Martin (jmartin@capitalpremium.net)
Date: Fri Apr 11 2003 - 19:43:44 GMT-3
Danny,
To answer the question as simply as possible, a non-client is any IBGP
neighbor that has not been configured with the route-reflector-client
keyword on it's neighbor statement.
The job of the RR server is to reflect routes from client to client AND
between the clients and all extra-cluster (read "non-client") neighbors.
This reduces the total number of BGP adjacencies needed in the AS. The
whole purpose of Route-reflection is to avoid that full mesh.
The other way to avoid having a full mesh is to configure confederations.
Route-reflection and confederations basically perform the same function.
HTH,
Joe Martin
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Danny Andaluz
Sent: April 11, 2003 2: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