Spine-Leaf vs Three-Tier: Data Center Network Design

Modern cloud and virtualization workloads — VM mobility, containerized microservices, big data replication — have made east-west traffic the dominant flow in data centers, and the classic three-tier design is struggling to keep up. Spine-leaf (Clos) architectures flatten the network to two layers, remove Spanning Tree from the equation, and give every leaf the same number of hops to every other leaf. Based on Lenovo Press's introduction to spine-leaf networking designs, this article compares the two approaches and lays out the design rules and oversubscription math you need to size a fabric correctly.

Three-Tier Architecture: Familiar but Limiting

The traditional design has core (L3), aggregation (L2/L3), and access (L2) layers. Its strengths are well known: pod-level fault isolation, security segmentation, and easy scale-out by adding pods. Its weakness is that pod-to-pod (east-west) traffic must traverse multiple layers, adding latency, and the core becomes an expensive, high-speed bottleneck as virtualization drives more east-west traffic.

Spine-Leaf (Clos) Architecture

In a spine-leaf design, every leaf switch connects to every spine switch in a full mesh. The advantages:

• No STP loops — all interconnections are used simultaneously.
• Deterministic latency — east-west traffic is always equidistant (one hop through a spine).
• Fixed configurations — the switch config doesn't change as servers are added or moved.
• Scale-out — add spines for bandwidth, add leaves for server ports, without re-architecting.

The mesh can be implemented at Layer 2 (with TRILL or SPB) or Layer 3 (OSPF or BGP with ECMP). Layer 3 fabrics are increasingly preferred because routed ports now cost no more than switched ports and ECMP load-balances across all spines.

Oversubscription Math and Sizing Rules

Key trade-offs to plan for:

• Each leaf must connect to every spine, so cabling and spine port counts grow quickly.
• Leaves typically have 4–6 spine uplinks; keep the leaf-to-spine oversubscription at 5:1 or better.
• For north-south traffic leaving the fabric, higher oversubscription (up to 100:1) may be acceptable.
• Three rules of thumb: every leaf needs the same number of fabric-facing ports; that count limits the number of spines; and the aggregate spine bandwidth times the oversubscription rate defines fabric edge bandwidth.

Choosing Hardware for Your Fabric

Fixed-form-factor switches dominate the leaf layer (e.g. 32x100G or 64x100G devices), while chassis devices with multiple line cards make high-density spines feasible. Evenly distribute leaf uplinks across spine line cards to reduce fabric-module traffic. For practical fabric examples, see our 400G spine / 100G leaf link consistency article, the VXLAN MP-BGP EVPN design guide, and Arista EOS MLAG explainer for multi-chassis leaf pairs.

原文链接：https://lenovopress.lenovo.com/lp0573.pdf