Spine and leaf architecture - connections to leaf switches

Spine and leaf architecture - reducing latency


In a network employing [spine and leaf architecture](/network-design-spine-and-leaf-architecture), spine switches don't need to be connected to each other.  Actually, by definition, **they should not be connected to each other**.  Spine switches should only be directly connected to leaf switches.  Indeed, spine switches should not even have any uplinks either!

Spine switches should only be connected to leaf switches or:

1) When you have a multi-pod environment, where you want to connect two or more datacenters to each other, where both datacenters are part of the same fabric.  In this case, we use what is known as an interpod switch, that can connect spine switches from two different "pods".  But these pods are managed by the same APIC.
2) In a multi-site environment, which is similar to a multi-pod environment.  The only difference is in this case, you have two separate fabrics controlled by two different APICs.
3) A spine switch can also connect to a remote leaf.  A remote leaf enables you to extend your fabric into a satellite site where you don't want spine switches.

If you want to learn more about how to connect leaf switches, check out this note:

[Spine and leaf architecture - connections to leaf switches](/spine-and-leaf-architecture-connections-to-leaf-switches)

One of the reasons why we connect spine switches in a certain way is to reduce latency:

[Spine and leaf architecture - reducing latency](/spine-and-leaf-architecture-reducing-latency)

Links:
https://www.cisco.com/c/en/us/products/cloud-systems-management/application-policy-infrastructure-controller-apic/index.html

https://community.cisco.com/t5/application-centric/what-can-we-connect-to-spine-switches/td-p/4065718


Spine and leaf architecture - connections to spine switches

STP direct vs indirect link failure

STP fine tuning the spanning tree protocol

STP how a switch identifies a BPDU

STP how to find the root bridge

STP interface type

STP prio nbr value

STP topology change process

Security - 802.1x with WLC and AAA server

Security - Cisco AnyConnect Secure Mobility Client

Security - Cisco Secure Client

Security - Cisco VPN Client

Security - Cisco VPN client software

Security - Diffie-Hellman groups

Security - Extensible Authentication Protocol over LAN (EAPOL)

Security - GETVPN

Security - IEEE 802.1X

Security - IOS Usernames and Passwords

Security - IPsec nonce

Security - Kerberos

Security - MAC Authentication Bypass

Security - Network Access Control (NAC)

Security - Next Generation Firewall

Security - Secure Unique Device Identifier (SUDI)

Security - WPA 4-way handshake

Security - WebVPN

Security - accessing VTY from another VRF

Security - assigning privilege levels, syntax and behavior

Security - bogons

Security - broadcast-multicast storm

Security - configuring TACACS from another VRF

Security - privilege levels and command output

Security - privilege levels and enable keyword

Security - public key exchange

Security - root CAs and private keys

Security - spoofing

Security - storm control algorithm

Security IKE policy hash command

Security Trusted Platform Module (TPM)

Security aaa new-model

Security authentication on VTY lines

Security keyrings

Segment Routing

Serial Interface default broadcast address

Session Border Controller

Session Initiation Protocol

Show open TCP-UDP ports on Cisco router

Spanning Tree Protocol (STP)

Split-horizon

StackWise Virtual

Stackwise election process

Stackwise user priority

Subscriber templating

Summarization

Supernetting

Switch configuring a routed port

Switch high availability options

Switch protected port limitations

Switch protected port

Switching - CEF

Switching - Media Access Control (MAC) addresses

Switching - Process switching

Switching - backplane

Switching - cut through

Switching - fast switching

Switching - show cable-diagnostics

Switching - store and forward

Switching - switch fabric

Switching - switched virtual interface (SVI)

Switching - switchport autostate command

Switching

Switchport - IEEE 802.1q

Switchport - ISL

Switchport access

Switchport modes

Switchport trunk configuration ignores access commands

Switchport trunk encapsulation

Switchport trunk

Symmetric Digital Subscriber Line (SDSL)

Syslog - terminal monitor

Syslog relay or proxy

Syslog severity levels

TCP - Congestion control

TCP - Header

TCP - SEQ and ACK values

TCP - Slow start

TCP - Three-way handshake

TCP - Urgent pointer field

TCP - Window Size Scaling

TCP - factors affecting segment size

TCP - role of checksum field

TCP MSS and window size

TCP RST flag

TCP SYN timeout

TCP header options

TCP phantom byte

TCP-IP model

Spine and leaf architecture - connections to spine switches

Links to this page: