STP — Trivia & Interesting Facts¶
Surprising, historical, and little-known facts about Spanning Tree Protocol.
Radia Perlman invented STP and wrote a poem about it¶
Radia Perlman, working at Digital Equipment Corporation, invented the Spanning Tree Algorithm in 1985 (standardized as IEEE 802.1D). She also wrote a poem about it: "I think that I shall never see / A graph more lovely than a tree. / A tree whose crucial property / Is loop-free connectivity." Despite creating one of the most important networking protocols ever, Perlman has said she dislikes the title "Mother of the Internet" that some have given her.
STP was designed to prevent a problem that kills networks in seconds¶
Without STP, a single accidental loop in an Ethernet network creates a broadcast storm that can saturate every link and crash every switch within seconds. Broadcast frames circulate endlessly, multiplying at each switch, consuming 100% of bandwidth. Before STP, a cleaning crew accidentally connecting two Ethernet ports with a cable could — and did — take down entire building networks. STP exists to prevent this specific, catastrophic failure mode.
The original STP convergence time of 50 seconds was considered acceptable in 1985¶
802.1D STP takes approximately 30-50 seconds to converge after a topology change: 20 seconds of max-age timer, then 15 seconds each in listening and forwarding states. In 1985, when networks were small and tolerance for downtime was higher, this was acceptable. By the 2000s, 50 seconds of network outage on every topology change was completely unacceptable, driving the development of Rapid STP (802.1w, 2001) which converges in 1-3 seconds.
RSTP uses a fundamentally different mechanism than STP — proposal/agreement instead of timers¶
RSTP (Rapid Spanning Tree Protocol, 802.1w) doesn't just speed up STP's timers — it uses a completely different convergence mechanism. Switches negotiate port roles using a proposal/agreement handshake that propagates across the network in milliseconds. The edge port concept (PortFast equivalent) also lets access ports forward immediately. RSTP's design was so superior that it was folded back into 802.1D-2004, replacing the original STP entirely.
BPDU guard exists because users keep creating loops¶
BPDU Guard was created specifically because end users plug switches, hubs, and misconfigured devices into access ports. If an access port configured with PortFast receives a BPDU (indicating another switch is connected), BPDU Guard shuts the port down immediately. Without BPDU Guard, a rogue switch could become the root bridge and redirect all traffic through itself — either accidentally causing a loop or intentionally executing a man-in-the-middle attack.
The root bridge election uses the lowest bridge ID, and the default priority ties almost always¶
STP elects the root bridge based on the lowest bridge ID (priority + MAC address). The default priority is 32768 on virtually all switches, which means the switch with the lowest MAC address becomes root. Since MAC addresses are assigned sequentially, the oldest switch in the network often becomes root — typically the least powerful, lowest-bandwidth switch, placed in the worst possible location. This is why manually setting root bridge priority is a critical design step.
PVST+ is a Cisco proprietary extension that runs a separate STP instance per VLAN¶
Per-VLAN Spanning Tree Plus (PVST+) runs an independent spanning tree for each VLAN, allowing different root bridges and different blocked ports per VLAN. This enables load balancing across redundant links by having odd VLANs use one path and even VLANs use another. The downside is scale: 1,000 VLANs means 1,000 STP instances, each generating BPDUs and consuming control plane resources. MST (Multiple Spanning Tree, 802.1s) solved this by mapping multiple VLANs to a smaller number of STP instances.
A single STP misconfiguration caused a 90-minute outage at a major bank¶
In 2012, a major financial institution experienced a 90-minute network outage when a routine switch replacement triggered an unexpected STP reconvergence. The new switch had a lower bridge priority than intended, became the root bridge, and caused every path in the network to recalculate. The resulting reconvergence cascaded across the data center, taking down trading systems during market hours. The postmortem recommended pre-staging switch configurations with correct STP priorities.
Modern data center networks don't use STP at all¶
Leaf-spine architectures with ECMP routing have no Spanning Tree — every link is a routed L3 link, and there are no L2 loops to prevent. The move from STP-managed Layer 2 networks to routed Layer 3 fabrics is one of the most significant architectural shifts in data center networking. STP remains critical in campus and access networks, but in data centers it has been largely eliminated by design.