In this video you'll see how route reflectors operate. We will also analyze in depth the function of the attributes that this functionality introduces, which are the Originator-ID and the Cluster-ID as well as some design implications.

Loading video...

NOTE: You can only see a limited low resolution version of the video, if you want to view the full version please sign up and get any of our plans!

Video Description

They provide a mechanism in which we can circumvent the iBGP rules of not announcing iBGP learned prefixes to iBGP peers. This is achieved by using new attributes (Originator-id y cluster-id), this ensures a loop free topology within the same AS.

Only the best route is reflected (as in all the BGP routers) 

The RR shouldn't modify the attributes of the reflected routes. 

The routers are divided in three groups: Route Reflectors (RR), clients y non-clients

All routes received are reflected (the best for the same destination) to all the routers that the RR has an established session with, except the ones that are from non-client routers to non-client routers. 

On some cases, introducing a RR doesn't simplify the network design and using a full-mesh topology would reduce the complexity.



Watch video in playlist

comments powered by Disqus