A metro design assigns different VNIs to Parks, Utilities, and Public Safety departments. How should architects treat those VNIs in the VXLAN control plane?
Select an answer to reveal the explanation.
Short Explanation
Different VNIs are different neighborhoods in the overlay phone book—Parks traffic should not share Utilities’ flood domain just because they share spines. EVPN and the VXLAN header both key on that VNI identity. Sharing an ASN in the underlay does not glue those broadcast domains together.
Full Explanation
VNIs identify discrete VXLAN segments. EVPN advertisements and VXLAN encapsulation use the VNI (along with route targets / routing-instance policy) so MAC/IP learning stays within the intended overlay broadcast domain. Assigning per-department VNIs is a standard segmentation approach for municipal multitenancy at Layer 2 overlay. Underlay ASN commonality does not merge VNIs, and VNIs are not merely cosmetic—they are fundamental segment identifiers. Correct VLAN-to-VNI mapping at each VTEP remains required for isolation.