You are setting up a single EVPN VXLAN fabric for a data center. A customer has one ESXi cluster in racks 1-3 that uses VLAN 10 for VMs in subnet 10.1.10.0/24. The customer has another ESXi cluster…

Question

Options

• AYou can map VLAN 10 to different VNIs on the same switches if you place VLAN 10 in multiple
• BYou must tell the customer to change the VLAN ID in racks 4-6 to a unique ID
• CYou can use subnets rather than VLANs for VNI mappings so you can use the same configuration
• DYou can map VLAN 10 to one VNI on switches in racks 1-3 and to a different VNI on switches in

• A
  11% (4)
• B
  3% (1)
• C
  22% (8)
• D
  65% (24)

Explanation

In EVPN VXLAN, VLAN IDs are locally significant to each leaf switch - they only have meaning on the device where they're configured. Option D is correct because the leaf switches in racks 1-3 can map their local VLAN 10 to one VNI (e.g., VNI 10010), while the leaf switches in racks 4-6 map their local VLAN 10 to a completely different VNI (e.g., VNI 20010), keeping the two subnets logically isolated across the same fabric.

Option A is wrong because a single switch cannot map the same VLAN ID to two different VNIs simultaneously - one VLAN maps to one VNI per device. Option B is wrong because there's no need to renumber VLANs; since the racks use separate leaf switches, VLAN 10 can coexist independently on each group. Option C is wrong because VNI mappings in EVPN VXLAN operate at the VLAN level, not the subnet level - subnets don't replace VLANs in the local-to-VNI binding.

Memory tip: Think of VLANs as local nicknames and VNIs as the globally unique postal codes of the fabric. Two switches in different buildings can both have a room called "VLAN 10," but they can ship packets to completely different destinations (VNIs) - the local name doesn't dictate the global address.

No community discussion yet for this question.