Topologies

Spine-leaf topology

Every leaf connects to every spine, giving predictable latency and easy scale-out.

sp1 ↔ lf1sp1 ↔ lf2sp1 ↔ lf3sp2 ↔ lf1sp2 ↔ lf2sp2 ↔ lf3lf1 ↔ srv1lf2 ↔ srv2DataDataDataDataSpine 110.0.0.1Spine 1 — 10.0.0.1Spine 210.0.0.2Spine 2 — 10.0.0.2Leaf 110.0.1.1Leaf 1 — 10.0.1.1Leaf 210.0.2.1Leaf 2 — 10.0.2.1Leaf 310.0.3.1Leaf 3 — 10.0.3.1Servers A10.0.1.10Servers A — 10.0.1.10Servers B10.0.2.10Servers B — 10.0.2.10
Legend

Current step

East-west flow

Server A to Server B goes leaf 1 → spine → leaf 2: always one spine hop.

The data-centre standard: leaves connect servers, spines only switch. East-west traffic always crosses exactly one spine.

Documentation example: addresses use the RFC 5737 ranges and ASNs use the reserved private range. Nothing here connects to a real network.

Tags

  • topology
  • datacenter
  • spine-leaf

Lessons using this diagram