VXLAN BGP EVPN: Packet Walk (Episode 3)
HTML-код
- Опубликовано: 12 сен 2021
- In this video, I try to summarize our learnings on BGP EVPN (L2VNI, L3VNI ) and do packet walks while looking at useful show commands that will help us understand the inner workings much better.
Наука
There can no better way than this to explain packetwalk. Very much delighted as gave me an in depth understanding on VXLAN EVPN !!!
great
Is it possible to have the whole copy of the configure of the Spine11 and maybe one of the Leafs ? if not, it is possible to get the anycast RP configuration of the spine (seems you are using SSM bidir so wanted to see how you configure that on the RP) thanks!
Appericiate your effort to drive this technology. Vxlan tshoot much harder before watching your video , now i feel bit comport. Thanks keep post further video. i am eager to watch it.👍
Great video as always! Off topic but how did you create the clear button in your secureCRT?
in symmetric case where l3 vni is used what would be destination mac in the inner ethernet header ?
As mentioned in Video there are 2 types of routes carried in L2 RIB such as MAC only and MAC+IP route, MAC route will be carried with single RT with L2 VNI and but MAC+IP is carried with 2 RT - L2 VNI and L3 VNI.
In your 1st video of L2-VNI in this series, we have not configured the L3 VNI ID in that case how MAC+IP route is installed in L2 RIB of source leaf ? Where that Mapping will happen ? Then only it will be advertised to remote peer.
Though I have this query, video content and explanation is top quality. It will be great if anyone can help with answer for above query at the earliest.
Thank you.
Hey Akshay, good question.
If you are running just L2VNI like in my first video, you will still have the MAC+IP route but the RT will just be L2VNI. Remember if you are running just L2VNI, you will be able to communicate only within the VNIs which is nothing but bridging and inter-VNI communication will not be possible.
@@BitsPlease Thank you for your reply, I understood that L2 VNI ID will carry MAC+IP route but concern is how that MAC + IP is populated in source leaf table only. Source switch will learn the MAC ( L2FWDR --> L2RIB -- > BGP Instance --> BGP Address Family --> Route Reflector). How that MAC + IP entry will be populated in L2 RIB cause L2FWDR will have only MAC entry.
@@aki2452 I talk about it in the video at the timestamp - 45:37
In short, Nexus 9kv uses host mobility manager to update the MAC+IP route to L2RIB and L3RIB. Physical nexus platforms mostly has the adjacency manager that does the same job. You can run "show fabric forwarding ip local-host-db" to see the HMM table.
@@BitsPlease Yes, I heard that as well but still wanted to confirm once again. Thank you for your quick reply and efforts put in for quality content.
Hope I could give you million likes. ☺
Thank you !
Can you send us the command summary?
You can find it on my GitHub. The link to my GitHub is on the bottom right of my youtube banner