Spine-Leaf Architecture: Modern Data Center Topology

Modern data center networks are built on spine-leaf, a flat two-tier fabric that replaced the classic three-tier core/distribution/access model. The reason is traffic patterns: microservices, virtualization and big-data workloads generate huge east-west traffic, and three-tier oversubscription makes that traffic slow and unpredictable. This article explains the spine-leaf layout, why every leaf-to-leaf path is exactly two hops, how ECMP spreads load across spines, and where VXLAN and EVPN fit on top of the fabric — plus the number-one cabling mistake that breaks the whole design.

The Spine-Leaf Layout

Every leaf switch (top-of-rack) connects directly to every spine switch (backbone). Rules: no leaf-to-leaf uplinks, no spine-to-spine uplinks, every leaf connects to every spine, and spines have uniform port counts so all leaves have equal reach. With 4 spines and 24 leaves that is 96 spine-leaf uplinks. Two servers on different racks always talk over the same two-hop path: server to leaf1, leaf1 to spine, spine to leaf2, server.

Why It Beats Three-Tier in the Data Center

• Latency: 2 hops always, deterministic — versus up to 5 hops in three-tier
• Bandwidth scaling: add another spine (parallel, non-disruptive) instead of upgrading core links
• Port scaling: add another leaf
• Redundancy: any single spine or leaf can fail; all others keep forwarding
• No STP bottleneck: layer 3 to the edge kills classic spanning-tree problems

What Runs on Spine-Leaf in Practice

Layer 3 terminates at every leaf, so no VLANs stretch across leaves. ECMP routing (OSPF, eBGP-in-the-DC, or IS-IS) spreads traffic across all spines. VXLAN overlays extend the L2 segments tenants need over the L3 fabric, letting VMs move between racks without renumbering, and BGP EVPN advertises MAC/IP reachability across the overlay.

When Three-Tier Still Makes Sense

Campus networks with heavy north-south traffic, very small deployments where a collapsed core suffices, and environments with legacy L2 requirements that cannot tolerate L3 boundaries at every rack.

The #1 Mistake

Cabling a spine-leaf like a three-tier network — adding leaf-to-leaf or spine-to-spine uplinks. This creates L3 forwarding loops or convergence issues and destroys the deterministic two-hop property. Spines never talk to each other; leaves never talk to each other directly.

Related: EVPN MAC-VRF validation on ACX7000, Arista MLAG run book, and the SONiC troubleshooting guide.

原文链接：https://packetmentor.com/topics/spine-leaf-architecture