Octet

Compare a classic three-tier data center design with a spine-leaf design.

Show the answer

Say this first

Three tier is access, aggregation and core. It was built for north-south traffic, runs layer 2 up to the aggregation pair, and relies on STP, which blocks half the links. Spine-leaf is a two-stage Clos: every leaf connects to every spine, any leaf reaches any other leaf in exactly two hops (leaf, spine, leaf), and all links forward at once through ECMP routing. You scale it out by adding leaves for ports and spines for bandwidth.

Go deeper

Three tier

  • Access switches connect servers, aggregation holds the SVIs, the FHRP and often the services (firewalls, load balancers), core routes between aggregation blocks and to the WAN.
  • VLANs stretch from access to aggregation, so STP is in charge of loop prevention and blocks redundant uplinks. Half the bandwidth you paid for sits idle.
  • Server-to-server traffic in different blocks climbs to the core and back down. Latency and available bandwidth depend on where the two servers sit.
  • Oversubscription compounds at every tier, and growth means buying a bigger aggregation chassis (scale up).

Spine-leaf

  • Two layers. Servers, firewalls, routers and storage connect only to leaves. Spines only connect leaves.
  • Leaf to spine links are routed, usually /31 point-to-point. No STP between switches.
  • Every leaf has an equal-cost path through every spine, so ECMP uses all uplinks.
  • Any two servers on different leaves are the same distance apart. Latency is predictable.
  • Losing one spine out of four removes 25% of fabric bandwidth, not half of a block.
  • Layer 2 between racks, when you need it, is rebuilt on top as an overlay (VXLAN with BGP EVPN).
Three tierSpine-leaf
Built forNorth-southEast-west
Loop controlSTP, blocked linksRouting, all links active
Hops leaf to leafVariesAlways two
GrowthScale up chassisScale out with more boxes
Layer 2 reachNative VLANsOverlay (VXLAN)

Traps

  • Saying spine-leaf "needs VXLAN". A pure layer 3 fabric with no overlay is perfectly valid.
  • Connecting servers or firewalls to spines. It breaks the uniform two-hop property and complicates the spine.
How did you do?Book 3.2 Switched EthernetBook 3.1 Switching Basics