leaf-spine (leaf-spine architecture)

Contributor(s): Sharon Zaharoff

Leaf-spine is a two-layer network topology composed of leaf switches and spine switches.

Leaf-spine is a two-layer data center network topology that's useful for data centers that experience more east-west network traffic than north-south traffic. The topology is composed of leaf switches (to which servers and storage connect) and spine switches (to which leaf switches connect). Leaf switches mesh into the spine, forming the access layer that delivers network connection points for servers.

Every leaf switch in a leaf-spine architecture connects to every switch in the network fabric. No matter which leaf switch a server is connected to, it has to cross the same number of devices every time it connects to another server. (The only exception is when the other server is on the same leaf.) This minimizes latency and bottlenecks because each payload only has to travel to a spine switch and another leaf switch to reach its endpoint. Spine switches have high port density and form the core of the architecture.

Content Continues Below

A leaf-spine topology can be layer 2 or layer 3 depending upon whether the links between the leaf and spine layer will be switched or routed. In a layer 2 leaf-spine design, Transparent Interconnection of Lots of Links or shortest path bridging takes the place of spanning-tree. All hosts are linked to the fabric and offer a loop-free route to their Ethernet MAC address through a shortest-path-first computation. In a layer 3 design, each link is routed. This approach is most efficient when virtual local area networks are sequestered to individual leaf switches or when a network overlay, like VXLAN, is working.

This was last updated in April 2016

Continue Reading About leaf-spine (leaf-spine architecture)

Dig Deeper on SDN and other network strategies

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

Is you picture for this article accurate?
Would not all the spine switches have connections to the core switches?
Unless some traffic goes leaf-spine-leaf-spine-core?
Thank you Kirk! The correct illustration should be displaying now.
found out mostly no cause costly.. usually utilize 2 streamline with load balancing or active-passive
Has your data center adopted the leaf-spine network model? Why or why not?
We are currently entertaining this topology since we are in the middle of a reconfiguration. What benefits have others seen do far?

Extensiones de Documento y Formatos de Documento

Accionado por: