Two hosts on the same city leaf communicate, but the same subnet fails to a host on a remote leaf. Where should VXLAN troubleshooting focus first?
Select an answer to reveal the explanation.
Short Explanation
Same-leaf success is like talking across the desk; remote failure means the campus courier path is broken. Don’t reimage the laptops first—check VTEP reachability, VNI join, and the underlay road. Local bridging never needed the truck.
Full Explanation
When two endpoints on one leaf communicate, traffic can switch locally without VXLAN encapsulation. Failure only to remote leaves implicates underlay connectivity, VTEP addressing, VNI membership, or remote decap/learning—not basic NIC health alone. This asymmetry is a classic triage pattern in EVPN-VXLAN fabrics. Municipal NOCs should use it to avoid wasting time on host reimages before fabric-path checks.