<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VXLAN on Council of Elrond</title><link>https://songkou.github.io/tags/vxlan/</link><description>Recent content in VXLAN on Council of Elrond</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 19 Jul 2026 12:00:00 +0800</lastBuildDate><atom:link href="https://songkou.github.io/tags/vxlan/index.xml" rel="self" type="application/rss+xml"/><item><title>VXLAN EVPN Architecture</title><link>https://songkou.github.io/posts/vxlan-evpn-architecture/</link><pubDate>Sun, 19 Jul 2026 12:00:00 +0800</pubDate><guid>https://songkou.github.io/posts/vxlan-evpn-architecture/</guid><description>&lt;p&gt;VXLAN EVPN combines a scalable Layer 2 data plane with a standards-based MP-BGP control plane. VXLAN carries Ethernet frames across a routed IP fabric; EVPN distributes endpoint, subnet, and tunnel-reachability information so the fabric does not have to discover everything by flooding.&lt;/p&gt;
&lt;details class="post-toc"&gt;
 &lt;summary&gt;Contents — 22 sections&lt;/summary&gt;
 &lt;nav id="TableOfContents"&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href="#standards-and-implementation-scope"&gt;Standards and implementation scope&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#1-why-overlays-exist"&gt;1. Why overlays exist&lt;/a&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href="#11-layer-2-and-layer-3-overlays"&gt;1.1 Layer 2 and Layer 3 overlays&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#12-problems-vxlan-addresses"&gt;1.2 Problems VXLAN addresses&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
 &lt;li&gt;&lt;a href="#2-vxlan-encapsulation-and-vteps"&gt;2. VXLAN encapsulation and VTEPs&lt;/a&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href="#21-header-fields-and-encapsulation-overhead"&gt;2.1 Header fields and encapsulation overhead&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#22-virtual-tunnel-end-point"&gt;2.2 Virtual Tunnel End Point&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#23-vlan-bridge-domain-and-vni"&gt;2.3 VLAN, bridge domain, and VNI&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
 &lt;li&gt;&lt;a href="#3-underlay-design"&gt;3. Underlay design&lt;/a&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href="#31-underlay-routing-choices"&gt;3.1 Underlay routing choices&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#32-ecmp-behavior"&gt;3.2 ECMP behavior&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#33-multicast-underlay-requirements"&gt;3.3 Multicast underlay requirements&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
 &lt;li&gt;&lt;a href="#4-design-considerations"&gt;4. Design Considerations&lt;/a&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href="#41-ibgp-overlay-with-an-igp-underlay-versus-ebgp-everywhere"&gt;4.1 iBGP overlay with an IGP underlay versus eBGP everywhere&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#42-bum-handling"&gt;4.2 BUM Handling&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
 &lt;li&gt;&lt;a href="#5-vxlan-data-plane-forwarding"&gt;5. VXLAN data-plane forwarding&lt;/a&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href="#51-local-switching"&gt;5.1 Local switching&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#52-known-remote-unicast"&gt;5.2 Known remote unicast&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#53-bum-traffic"&gt;5.3 BUM traffic&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
 &lt;li&gt;&lt;a href="#6-what-evpn-adds"&gt;6. What EVPN adds&lt;/a&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href="#61-route-reflectors"&gt;6.1 Route reflectors&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#62-underlay-versus-overlay-bgp"&gt;6.2 Underlay versus overlay BGP&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#63-evpn-address-family-and-route-installation"&gt;6.3 EVPN address family and route installation&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
 &lt;li&gt;&lt;a href="#7-evpn-building-blocks-rd-rt-and-route-types"&gt;7. EVPN building blocks: RD, RT, and route types&lt;/a&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href="#71-route-distinguisher"&gt;7.1 Route Distinguisher&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#72-route-target"&gt;7.2 Route Target&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#73-important-evpn-route-types"&gt;7.3 Important EVPN route types&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
 &lt;li&gt;&lt;a href="#8-evpn-multihoming-in-detail"&gt;8. EVPN multihoming in detail&lt;/a&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href="#81-ethernet-segment-identifier"&gt;8.1 Ethernet Segment Identifier&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#82-how-route-types-1-and-4-work-together"&gt;8.2 How route types 1 and 4 work together&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#83-aliasing-and-known-unicast-load-balancing"&gt;8.3 Aliasing and known-unicast load balancing&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#84-designated-forwarder-election"&gt;8.4 Designated Forwarder election&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#85-split-horizon"&gt;8.5 Split horizon&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#86-failure-sequences"&gt;8.6 Failure sequences&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
 &lt;li&gt;&lt;a href="#9-endpoint-learning-mobility-and-arp-suppression"&gt;9. Endpoint learning, mobility, and ARP suppression&lt;/a&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href="#91-local-and-remote-learning"&gt;9.1 Local and remote learning&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#92-host-mobility"&gt;9.2 Host mobility&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#93-arp-suppression"&gt;9.3 ARP suppression&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
 &lt;li&gt;&lt;a href="#10-distributed-anycast-gateway-and-irb"&gt;10. Distributed anycast gateway and IRB&lt;/a&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href="#101-same-subnet-forwarding"&gt;10.1 Same-subnet forwarding&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#102-inter-subnet-forwarding"&gt;10.2 Inter-subnet forwarding&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
 &lt;li&gt;&lt;a href="#11-head-end-replication-and-control-plane-suppression"&gt;11. Head-end replication and control-plane suppression&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#12-design-choices-pod-multi-pod-fabric-and-site"&gt;12. Design choices: pod, multi-pod, fabric, and site&lt;/a&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href="#121-pod"&gt;12.1 Pod&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#122-multi-pod"&gt;12.2 Multi-Pod&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#123-multi-fabric-and-multi-site"&gt;12.3 Multi-fabric and Multi-Site&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
 &lt;li&gt;&lt;a href="#13-vxlan-multi-site-architecture"&gt;13. VXLAN Multi-Site architecture&lt;/a&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href="#131-border-gateway-roles"&gt;13.1 Border gateway roles&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#132-underlay-isolation"&gt;13.2 Underlay isolation&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#133-pip-and-multi-site-vip"&gt;13.3 PIP and Multi-Site VIP&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#134-anycast-bgw-and-designated-forwarder"&gt;13.4 Anycast BGW and designated forwarder&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#135-bum-replication-modes"&gt;13.5 BUM replication modes&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#136-selective-advertisement"&gt;13.6 Selective advertisement&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#137-multi-site-control-plane-boundaries"&gt;13.7 Multi-Site control-plane boundaries&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#138-tracking-and-restoration"&gt;13.8 Tracking and restoration&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
 &lt;li&gt;&lt;a href="#14-multi-site-forwarding-walks"&gt;14. Multi-Site forwarding walks&lt;/a&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href="#141-inter-site-bridging"&gt;14.1 Inter-site bridging&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#142-inter-site-routing"&gt;14.2 Inter-site routing&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#143-inter-site-bum"&gt;14.3 Inter-site BUM&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
 &lt;li&gt;&lt;a href="#15-representative-cisco-nx-os-configuration-model"&gt;15. Representative Cisco NX-OS configuration model&lt;/a&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href="#151-enable-features"&gt;15.1 Enable features&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#152-underlay-loopback-and-routed-link"&gt;15.2 Underlay loopback and routed link&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#153-overlay-bgp"&gt;15.3 Overlay BGP&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#154-vlan-to-vni-and-tenant-vrf"&gt;15.4 VLAN-to-VNI and tenant VRF&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#155-anycast-gateway-svi"&gt;15.5 Anycast gateway SVI&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#156-nve-interface"&gt;15.6 NVE interface&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#157-evpn-vni-policy"&gt;15.7 EVPN VNI policy&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#158-multi-site-bgw-pattern"&gt;15.8 Multi-Site BGW pattern&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
 &lt;li&gt;&lt;a href="#16-failure-handling-and-verification"&gt;16. Failure handling and verification&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#17-multi-tenant-connectivity-with-firewall-insertion"&gt;17. Multi-tenant connectivity with firewall insertion&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#18-centralized-route-leaking-and-shared-services"&gt;18. Centralized route leaking and shared services&lt;/a&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href="#181-why-centralize-route-leaking"&gt;18.1 Why centralize route leaking&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#182-shared-internet-model"&gt;18.2 Shared Internet model&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#183-common-route-leaking-failures"&gt;18.3 Common route-leaking failures&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
 &lt;li&gt;&lt;a href="#19-practical-design-checklist"&gt;19. Practical design checklist&lt;/a&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href="#underlay"&gt;Underlay&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#overlay"&gt;Overlay&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#multihoming"&gt;Multihoming&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#gateways-and-services"&gt;Gateways and services&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#multi-site"&gt;Multi-Site&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
 &lt;li&gt;&lt;a href="#20-security-policy-and-operational-hardening"&gt;20. Security, policy, and operational hardening&lt;/a&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href="#201-underlay-and-vtep-protection"&gt;20.1 Underlay and VTEP protection&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#202-endpoint-and-tenant-controls"&gt;20.2 Endpoint and tenant controls&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#203-scale-budgets"&gt;20.3 Scale budgets&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="#204-observability-baseline"&gt;20.4 Observability baseline&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
 &lt;/li&gt;
 &lt;li&gt;&lt;a href="#21-final-mental-model"&gt;21. Final mental model&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
&lt;/nav&gt;
&lt;/details&gt;

&lt;h2 id="standards-and-implementation-scope"&gt;Standards and implementation scope&lt;/h2&gt;
&lt;p&gt;VXLAN EVPN is not defined by one document. The architecture is assembled from a data-plane encapsulation, an EVPN control plane, a mapping between EVPN and network-virtualization overlays, and later IRB and prefix-route extensions:&lt;/p&gt;</description></item><item><title>VXLAN_EVPN_Cumulus_Lab_Test</title><link>https://songkou.github.io/posts/vxlan-evpn-cumulus-5.4-lab-guide/</link><pubDate>Sun, 19 Jul 2026 02:00:00 +0800</pubDate><guid>https://songkou.github.io/posts/vxlan-evpn-cumulus-5.4-lab-guide/</guid><description>&lt;p&gt;This lab builds a VXLAN EVPN fabric on Cumulus Linux 5.4: one BGP spine, an MLAG leaf pair (leaf1/leaf2) acting as a single logical VTEP, and a standalone leaf (leaf3). Linux1 is dual-homed to the MLAG pair over an LACP bond, while Linux21 and Linux22 share a stretched VLAN with a distributed anycast gateway.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Lab requirements&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;VLAN 100: Linux1 &lt;code&gt;192.168.100.10/24&lt;/code&gt;, gateway &lt;code&gt;192.168.100.1&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;VLAN 121: Linux21 &lt;code&gt;192.168.121.21/24&lt;/code&gt;, Linux22 &lt;code&gt;192.168.121.22/24&lt;/code&gt;, anycast gateway &lt;code&gt;192.168.121.1&lt;/code&gt; on all leaves&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="lab-environment"&gt;Lab environment&lt;/h2&gt;
&lt;p&gt;This lab runs in EVE-NG. The four switches (&lt;code&gt;spine&lt;/code&gt;, &lt;code&gt;leaf1&lt;/code&gt;, &lt;code&gt;leaf2&lt;/code&gt;, &lt;code&gt;leaf3&lt;/code&gt;) are Cumulus VX 5.4 nodes, and the three hosts (&lt;code&gt;Linux1&lt;/code&gt;, &lt;code&gt;Linux21&lt;/code&gt;, &lt;code&gt;Linux22&lt;/code&gt;) are lightweight Alpine-style Linux nodes configured through &lt;code&gt;/etc/network/interfaces&lt;/code&gt; and OpenRC&amp;rsquo;s &lt;code&gt;rc-service&lt;/code&gt;. Any emulator that boots Cumulus VX 5.4 with the port mapping in section 2 will work; adjust the host commands if your Linux image uses a different init system or network configuration method.&lt;/p&gt;</description></item></channel></rss>