![]() ![]() Topologyįor this post, we’re going to use the following topology and incrementally add/delete/modify certain aspects of this network. This will also allow you to control whether you want asymmetric or symmetric IRB (see my previous Cumulus blog posts to understand what is asymmetric and symmetric IRB). ![]() So, the goal of this blog is to help understand how L2/元 VNI RTs are exported/imported and how you can control what goes into your customer VRF. It’s always good to learn to drive a stick, before moving to an automatic. But it also doesn’t help you understand much of how route-targets are being imported across and how to completely control this. This makes for a very easy experience (almost plug and play like) when building VXLAN BGP EVPN fabrics. This post assumes that the reader has a general understanding of L2/元 VNIs and asymmetric/symmetric IRB.Ĭumulus, by default, uses auto RTs for L2 and 元 VNIs. ![]() This means that 2 24 (= 16.777.216) unique OUAs can be assigned per OUI.In this post, we look at how route-targets extended communities can be used to control VXLAN BGP EVPN routes in Cumulus Linux.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |