Fabric / AVD
Arista/Cisco EVPN-VXLAN spine-leaf: architect, validate, deploy.
Relevant for:Professional ServicesEnterprise / NetOps
Where to find itCanvas→Device catalog→Arista→AVD Fabric wizard
The fabric wizard builds an EVPN-VXLAN spine-leaf datacenterthe Architect-Validate-Deploy way: describe the fabric (spines, leaf pairs, uplinks, MLAG, services and endpoints) and the wizard materializes the topology on the canvas, cables it, and owns the member devices' configuration — regenerated on every wizard change.
Architect · Validate · Deploy#
| Architect | Pick platforms per tier (e.g. 7280R3 spines, 7050X3 MLAG leafs), uplink counts and speeds, VRFs/VLANs/L2VPNs and where they attach. |
| Validate | AVD designs pass the same whole-design validation as everything else — uplink interface types, bandwidth, SFP/DAC media rules, port capacity — plus fabric-specific checks. |
| Deploy | Generated artifacts follow Arista AVD structure, ready for an AVD/CloudVision pipeline; BOM and cabling schedules include fabric devices like any other node. |
Why
EVPN-VXLAN gives you L2 anywhere over a routed fabric — no STP blocking, ECMP everywhere, and failure domains bounded per leaf. Driving it from a model (rather than per-switch CLI) is the only way fabrics stay consistent at 10+ switches; the wizard enforces that the drawing, the model, and the config never diverge.
Important
Wizard-managed devices are read-only in the properties panel — edit spines, leafs, services and endpoints in the wizard, which re-applies configuration on every reconcile.