TTR Networks

Advanced · EVPN and VXLAN: layer 2 over a routed fabric · section 5 of 6

Checklist and troubleshooting

✓ Lab-tested 18 October 2026 on FRR 10.2.1

Checklist

  • Underlay first: every leaf loopback reachable from every other, over every path.
  • EVPN address family on every session; advertise-all-vni on the leaves.
  • Spines with eBGP: attribute-unchanged next-hop for EVPN.
  • VXLAN interfaces sourced from the loopback, with nolearning, attached to the VNI's bridge.
  • Route targets explicit in mixed-vendor fabrics.
  • MTU: VXLAN adds 50 bytes. Raise the underlay MTU (9000 is common) so 1500-byte host frames fit.

When it doesn't work

SymptomLook atUsual cause
No EVPN routes at allshow bgp l2vpn evpn summaryAddress family not activated, or advertise-all-vni missing
VNI missing from show evpn vniThe kernel: ip -d link show vxlan100VXLAN interface down or not in a bridge
Remote MACs present, no trafficUnderlay ping between loopbacksVTEP addresses not reachable
Traffic goes via the spine, or not at allNext hop on received EVPN routesSpine rewrote the next hop
Routes received but not importedshow bgp l2vpn evpn vni <n>Route targets don't match
Small packets work, big ones don'tUnderlay MTU50 bytes of VXLAN overhead