# Lab: More Complex VXLAN Deployment Scenario

DevFeed: [Lab: More Complex VXLAN Deployment Scenario](<https://devfeed.tech/articles/lab-more-complex-vxlan-deployment-scenario-11301.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2025/12/vxlan-complex/>)

Published: 2025-12-05T06:22:00Z

Content type: tutorial

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [VXLAN](<https://devfeed.tech/topics/vxlan.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [networking](<https://devfeed.tech/topics/networking.md>)

Tags: [container](<https://devfeed.tech/tags/container.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [evpn](<https://devfeed.tech/tags/evpn.md>), [github](<https://devfeed.tech/tags/github.md>), [mac](<https://devfeed.tech/tags/mac.md>), [netlab](<https://devfeed.tech/tags/netlab.md>), [vxlan](<https://devfeed.tech/tags/vxlan.md>)

## AI overview

A lab exercise introduces more complex VXLAN concepts, including VTEP-specific flooding lists, mapping multiple VLAN IDs to one VNI, and the scope of VNI and VLAN ID uniqueness. The lab can run on netlab-enabled infrastructure, GitHub Codespaces, or an Apple-silicon Mac.

## Source excerpt

In the first VXLAN lab, we covered the very basics. Now it's time for a few essential concepts (before introducing the EVPN control plane or integrated routing and bridging): Each VXLAN segment could have a different set of VTEPs (used to build the BUM flooding list) While the VXLAN Network Identifier (VNI) must be unique across the participating VTEPs, you could map different VLAN IDs into a single VNI (allowing you to merge two VLAN segments over VXLAN) Neither VXLAN VNI nor VLAN ID has to be globally unique (but it helps to make them unique to remain sane) Read more ...