The city enables VXLAN on access devices that cannot speak EVPN while the leaf standard expects EVPN signaling. What problem does that create?
Select an answer to reveal the explanation.
Short Explanation
Turning on VXLAN UDP is not the same as speaking EVPN. If the city’s standard is EVPN and the box only does flood-and-learn or static tunnels, you have a capability mismatch, not a self-upgrading miracle. Plan for the control plane the platform actually supports—or change the platform.
Full Explanation
VXLAN data-plane encapsulation and EVPN control-plane participation are related but distinct capabilities. Platforms that only support flood-and-learn or static VTEPs will not advertise or import EVPN MAC/IP routes simply because UDP/4789 works. Mixing them with an EVPN-standardized leaf tier creates inconsistent learning and operational blind spots. Hardware/software qualification should verify the chosen control plane—EVPN versus multicast/static—before municipal rollout.