BGP Route Reflector

Hello Duong

Can you clarify what it is that you are requesting? Can you give us a little more information about the architecture you are trying to create and for what purpose?

Also keep in mind that if you have a suggestion for a lesson, you can always go to the Member Ideas page shown below, and make a suggestion for a particular lesson you’d like to see. You may find that others have made similar suggestions and you can add your voice to theirs.

In the meantime, take a look at this Cisco documentation that describes BGP route reflectors and how they can be incorporated into an ACI Fabric in a data center.

I hope this has been helpful!

Laz

we need lap leaf-spine topology with 2 router reflectors

Hello Duong

I forgot to add the link to the Member Ideas page. Here it is:

You can make your suggestion there, and Rene will take a look…

I hope this has been helpful!

Laz

Hello,

In the last example if all the router in each cluster are connected with each other with IGP would that causes any problem ?

Thank you

Hello Chansaravuth

I believe you are talking about this topology, correct?

As with any BGP AS, all routers within an AS must be reachable in order for BGP to function correctly. Whether you use an RR or not, all routers within AS 123 must have routing established between them. This is typically achieved using an IGP like OSPF or EIGRP. So yes, an IGP should run in the AS to ensure reachability between all routers.

I hope this has been helpful!

Laz

This only is for routes correct? It wouldnt reflect things like the update-source command or next-hop-self correct?

Hello Cameron.

Correct. The next-hop is not changed as the route reflector reflects the update. It’s basically like a mirror. Consider this topology:

R1, R2 and R3 each have networks that correspond to their router number, for ex:
R1 - 10.10.10.10/32
R2 - 20.20.20.20/32
R3 - 30.30.30.30/32

R4 is configured as a route reflector. When R1 advertises its network to R4, R4 will reflect it and the message will look something like this:

BEFORE BEING REFLECTED

AFTER BEING REFLECTED (packet captured from R4 to R3)

Notice how the next-hop wasn’t changed, it still refers to R1. What has changed was the addition of two new path attributes - Cluster List and Originator ID that Rene covers in his lesson.

The originator_ID is the router ID of the router from who the route originates from. It’s used as a loop prevention mechanism. If the router sees its own RID here, it will discard the packet.


(When the reflector reflects the update, it also reflects it back to the originator so you get to nicely capture this in action)

If you have any further questions, feel free to ask.

David

1 Like

Hello Cameron

Yes, route reflectors will only reflect routes. Configurations like update-source and next-hop-self are functions that operate within the confines of the router on which they are configured.

I hope this has been helpful!

Laz