From: Daniel Cisco Group Study (danielcgs@imc.net.au)
Date: Fri Apr 11 2003 - 18:59:26 GMT-3
Danny,
Your assumption about what a RR client is, is correct.
If the RR did not reflect to IBGP Non-Clients, how would they know about the routes coming from RR Clients? The only way would be to peer the RR Clients with the IBGP Non-Clients, which would defeat the purpose of RRs. Therefore the RR needs to reflect routes from RR clients to IBGP non-clients.
Hope this helps.
Daniel
-----Original Message-----
From: Danny Andaluz [mailto:dannyandaluz@comcast.net]
Sent: Saturday, 12 April 2003 06:05
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 email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
This archive was generated by hypermail 2.1.4 : Thu May 01 2003 - 13:35:51 GMT-3