--- title: Lab: More Complex VXLAN Deployment Scenario «... description: A hands-on lab exercise covering more advanced VXLAN deployment concepts, including per-segment VTEP sets for BUM flooding lists, mapping multiple VLAN IDs to... canonical: https://daily.dev/posts/lab-more-complex-vxlan-deployment-scenario-ipspace-net-blog-aegw21r1o twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Lab: More Complex VXLAN Deployment Scenario « ipSpace.net blog | daily.dev og:description: A hands-on lab exercise covering more advanced VXLAN deployment concepts, including per-segment VTEP sets for BUM flooding lists, mapping multiple VLAN IDs to... og:url: https://daily.dev/posts/lab-more-complex-vxlan-deployment-scenario-ipspace-net-blog-aegw21r1o og:image: https://api.daily.dev/og/posts/AEgw21r1O.png og:image:alt: Lab: More Complex VXLAN Deployment Scenario « ipSpace.net blog og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Lab: More Complex VXLAN Deployment Scenario « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 1 min read · 0 upvotes · 0 comments ## Summary A hands-on lab exercise covering more advanced VXLAN deployment concepts, including per-segment VTEP sets for BUM flooding lists, mapping multiple VLAN IDs to a single VNI to merge VLAN segments, and the scoping rules for VNI and VLAN ID uniqueness. The lab can be run on netlab-enabled infrastructure, GitHub Codespaces, or Apple Silicon Macs using Arista cEOS containers. It serves as a stepping stone before introducing EVPN control plane and integrated routing and bridging. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Can different VLAN IDs be mapped to the same VXLAN VNI across VTEPs? Yes, different VLAN IDs can be mapped to a single VNI, which allows merging two separate VLAN segments over VXLAN. The VNI itself must be unique across all participating VTEPs, but the VLAN IDs used locally do not need to be globally unique — though keeping them unique across the network is recommended for operational sanity. _Network engineers designing VXLAN overlays track these mapping rules and EVPN updates on daily.dev._ ### Does every VXLAN segment need to use the same set of VTEPs? No, each VXLAN segment can have its own distinct set of VTEPs, which is used to build the BUM (Broadcast, Unknown unicast, Multicast) flooding list for that segment. This allows flexible topology design where different segments span different subsets of the physical underlay. _Engineers building multi-segment VXLAN fabrics find relevant lab walkthroughs and design discussions on daily.dev._ ## Similar posts on daily.dev - [EVPN with SR-MPLS Core « ipSpace.net blog](https://daily.dev/posts/evpn-with-sr-mpls-core-ipspace-net-blog-taobtibzc) · ipSpace.net Blog · 0 upvotes · 0 comments --- Tags: [#bgp](https://daily.dev/tags/bgp) [View this post on daily.dev](https://daily.dev/posts/lab-more-complex-vxlan-deployment-scenario-ipspace-net-blog-aegw21r1o) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Lab: More Complex VXLAN Deployment Scenario « ipSpace.net blog","url":"https://daily.dev/posts/lab-more-complex-vxlan-deployment-scenario-ipspace-net-blog-aegw21r1o","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/lab-more-complex-vxlan-deployment-scenario-ipspace-net-blog-aegw21r1o"},"datePublished":"2026-08-11T08:55:57.343Z","dateModified":"2026-08-11T09:09:18.333Z","description":"A hands-on lab exercise covering more advanced VXLAN deployment concepts, including per-segment VTEP sets for BUM flooding lists, mapping multiple VLAN IDs to...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/312972239b0ad65a2d13b8d3626a0617?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/312972239b0ad65a2d13b8d3626a0617?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"ipSpace.net Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"ipSpace.net Blog","logo":"https://media.daily.dev/image/upload/s--xS7E82MT--/f_auto,q_auto/v1786438303/logos/ipspace?_a=BAMAMicg0","url":"https://daily.dev/sources/ipspace"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/lab-more-complex-vxlan-deployment-scenario-ipspace-net-blog-aegw21r1o","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"bgp","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ipSpace.net Blog","item":"https://daily.dev/sources/ipspace"},{"@type":"ListItem","position":3,"name":"Lab: More Complex VXLAN Deployment Scenario « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/lab-more-complex-vxlan-deployment-scenario-ipspace-net-blog-aegw21r1o#faq","mainEntity":[{"@type":"Question","name":"Can different VLAN IDs be mapped to the same VXLAN VNI across VTEPs?","acceptedAnswer":{"@type":"Answer","text":"Yes, different VLAN IDs can be mapped to a single VNI, which allows merging two separate VLAN segments over VXLAN. The VNI itself must be unique across all participating VTEPs, but the VLAN IDs used locally do not need to be globally unique — though keeping them unique across the network is recommended for operational sanity. Network engineers designing VXLAN overlays track these mapping rules and EVPN updates on daily.dev."}},{"@type":"Question","name":"Does every VXLAN segment need to use the same set of VTEPs?","acceptedAnswer":{"@type":"Answer","text":"No, each VXLAN segment can have its own distinct set of VTEPs, which is used to build the BUM (Broadcast, Unknown unicast, Multicast) flooding list for that segment. This allows flexible topology design where different segments span different subsets of the physical underlay. Engineers building multi-segment VXLAN fabrics find relevant lab walkthroughs and design discussions on daily.dev."}}]} ```