Spanning Tree Protocol

Spanning Tree Protocol (STP) prevents Layer 2 switching loops by automatically blocking redundant paths between switches. Without it, a loop in your switch infrastructure would cause a broadcast storm that brings down the network almost instantly.

Ethernet frames have no TTL like IP packets do — a frame caught in a loop will circulate forever, multiplying with each pass until it consumes all available bandwidth. STP prevents this by designating one path between any two switches as active and blocking others.

The protocol elects a root bridge (the switch that becomes the logical center of the spanning tree), then calculates the shortest path from every other switch to the root. Redundant paths are placed in a blocking state — they carry no traffic but are ready to activate if the active path fails. When a link goes down, STP recalculates and unblocks the redundant path.

RSTP (802.1w) — Rapid Spanning Tree Protocol — reduced failover time from 30-50 seconds (original STP) to under a second. Almost all modern deployments use RSTP or its VLAN-aware variant, MSTP.

The practical implications:

STP is why your "redundant" switch links aren't actually providing double the bandwidth — they're in blocking state, ready for failover, not active. LACP/LAG is how you actually aggregate bandwidth across multiple links while maintaining STP compatibility.

Misconfigured STP (wrong root bridge election, incorrect port configurations) can cause unexpected topology changes that briefly disrupt traffic. Understanding which switch should be the root bridge — typically your core/distribution switch — and configuring it explicitly with the lowest bridge priority is a basic hardening step.