A vendor VTEP in a shared civic colo uses a nonstandard UDP port while the city’s Juniper leaves expect standard VXLAN port 4789. What is the likely result?
Select an answer to reveal the explanation.
Short Explanation
If one dock expects gate 4789 and the other ships to gate 4790, the freight never clears. VXLAN parameters—especially UDP port and VNI—must match for decap to work. Consistency beats clever one-offs in a shared colo.
Full Explanation
VXLAN data-plane interoperability requires agreeing on encapsulation parameters, notably UDP destination port and VNI usage. A mismatched port causes remote VTEPs to ignore or drop traffic that does not match their expected VXLAN listener. Spines do not generally translate tenant VXLAN UDP ports based on LLDP. Civic interconnection agreements should lock standard port 4789 unless every VTEP is explicitly reconfigured the same way.