EVPN-VXLAN
EVPN-VXLAN combines EVPN for Ethernet VPN control-plane signaling with VXLAN encapsulation for overlay forwarding across an IP underlay.
Key facts
- RFC 7432 (EVPN) and RFC 7348 (VXLAN) are primary public references
- Needs a stable ECMP underlay
- Not required for every small campus
Use cases
- Multi-tenant data centers
- Large campus segmentation
- Workload mobility within controlled domains
Design rules
- Prove underlay before overlays
- Account for VXLAN MTU overhead
- Keep border policy explicit
Limitations
Operational complexity rises; unsuitable where hardware lacks EVPN feature parity.
Best practices
Standardize loopback/VTEP addressing and document VNI/VRF maps.
References
Related guides
- EVPN fabric overview — Spine-leaf EVPN-VXLAN fabric roles, fit criteria, and verification outline.
- Spine-leaf underlay pattern — Equal-cost multipath leaf-spine underlay used beneath overlays such as EVPN-VXLAN.
- Campus network reference architecture — Layered campus design: access, distribution/core, services edge.
Owner: Novatelia Engineering / AEO Program. Reviewed: 2026-07-22. Doc version: 2026.07. Change log: Phase 6 technical authority pilot.
No datasheet copies, fabricated benchmarks, or unverified vendor authorizations appear in this document.