Leaf-spine architecture is a repeatable way to connect servers, storage and service networks as a data center grows. Top-of-rack (ToR) switches provide rack-level connectivity; leaf switches aggregate endpoint traffic; spine switches provide high-capacity paths between leafs. The exact physical design can combine these roles, but the traffic model and port map must remain explicit.
ToR, leaf and spine: what is the difference?
| Role | Primary function | Design questions |
|---|---|---|
| ToR | Connects servers and devices inside or near a rack | Server port density, cable length, power, management and uplink count |
| Leaf | Aggregates racks or endpoint groups and connects northbound to spines | Uplink speed, oversubscription, routing, MLAG/EVPN/VXLAN and failure domain |
| Spine | Provides predictable high-capacity paths between leaf switches | Port count, fabric capacity, redundancy, optics and growth |
How to build the design
1. Begin with a port map
List every server-facing port, leaf uplink, spine port, management connection and spare. Include speed, connector, fiber/copper medium and the intended failure domain. Port mapping prevents a common design error: choosing a switch by headline throughput before proving that it has the right physical ports.
2. Separate traffic roles
Document production, storage, management, backup and out-of-band traffic. Decide which traffic is routed, bridged or isolated, and identify the required QoS, ACL, multicast and congestion controls.
3. Plan redundancy as a behavior
Redundancy is not only a second cable. Define how links fail, how routing or multi-chassis mechanisms react, how maintenance is performed and how the application sees the event. The SD6881-32H source record lists MLAG, BGP, ECMP/UCMP, VXLAN, PFC and ECN capabilities for review in a data-center role; actual deployment design and software support must be confirmed before selection.
4. Match switch ports to optics
The SD6881-32H is documented with 32×100G QSFP28 interfaces. A 100G QSFP28 SR4 is one possible optical direction, but the final link requires a verified match across port, module, fiber, connector, reach and FEC/interoperability.
When should you use a high-density data center switch?
Use a high-density platform when the port map, traffic model and growth plan justify it. The E681-32C is a three-layer Ethernet switch direction with 10GE, 25GE and 100GE line-rate options in the source record. Compare it with the SD6881-32H against the intended role, port mix, redundancy, software features, optics and operational tooling.
Leaf-spine review checklist
- Every endpoint, uplink and spare port appears in a port map.
- Oversubscription and east-west traffic assumptions are documented.
- Failure domains and maintenance behavior are tested or described.
- Routing, MLAG/EVPN/VXLAN, QoS, ACL, PFC/ECN and telemetry requirements are explicit.
- Optics and fiber are matched to every link, including spares.
- Management access and firmware/support ownership are clear.
Frequently asked questions
Is ToR the same as leaf?
Not always. ToR describes physical placement and rack-level connectivity; leaf describes a fabric role. A ToR switch can serve as a leaf in a design, but the role should be defined by the topology and traffic model.
How many spine switches are required?
That depends on capacity, redundancy, port count and failure-domain requirements. Choose from the port map and availability target rather than a universal number.
What is the most common procurement mistake?
Buying a switch based only on switching capacity while overlooking port type, optics, software features, power, airflow, support and interoperability.