The Basics of BGP Route Reflection - dummies.
With BGP route-reflection it is crucial to grasp the difference between Control-Plane and Data-Plane(also called Forwarding-Plane). In most MPLS backbones RRs(route-reflectors) are not part of the Forwarding-Plane. -that means there’s no data traffic being forwarded through the RRs.
Configuration of route reflection and verification on Juniper and Cisco routers.
Introduction Description of BGP Route Reflection Route Reflection Configuration Examples Single Cluster with Default Settings Single Cluster with Client-to-client Reflection Disabled Two Clusters, Intra-site and Inter-site Route Reflection Two Clusters, no Client-to-client Reflection Cluster List and Loop Prevention Reflection Between Client and Non-client Intra-cluster Reflection Inter.
The term route reflection is used to describe the operation of a BGP speaker advertising a route that was learned through an iBGP session to another iBGP peer. This practice is prohibited in normal BGP operation because the traditional BGP routing protocol had no safeguards against routing loops within an autonomous system (thus requiring a full mesh of iBGP speakers).
IBGP Next-hop self enabled with Route Reflection does not appear to be working Symptoms: With Next-hop self enabled on the ISG2000 configured as a Route Reflector (RR), the next-hop of the routes in the RIB-in table of the receiving client (SSG5--B) do not get changed to the RR IP (2.2.2.1).
Internet-Draft bgp-optimal-route-reflection August 2017 This further complicated the issue and makes it less likely for the route reflector to select the best path from the client's perspective. It follows that the best path chosen by the route reflector is not necessarily the same as the path which would have been chosen by the client if the client had considered the same set of candidate.
BGP route reflector clients and non-clients. Currently studying for my CCNP and I'm a little hung up on this concept. I am reading that non-clients are connected peers that the RR does not forward routes from. Then reading the rules by which RRs propagate updates, if the RR receives a route from a non-client, the RR reflects these routes to clients only. The only difference I'm seeing between.