Spanning Tree Protocol Overview

Why Redundant Switch Links Cause Problems

Adding a second, backup cable between two switches sounds like a good reliability measure, but without any protection, it creates a physical loop - and switches, unlike routers, have no built-in mechanism to stop a frame from circulating forever around a loop.

Switch A ====== Switch B
   \\              //
    ==============
    (a redundant second link creates a loop)

The Result: A Broadcast Storm

A single broadcast frame entering a looped topology gets endlessly duplicated and re-forwarded around the loop by both switches, multiplying exponentially until the network's entire bandwidth is consumed - a broadcast storm that can bring down an otherwise healthy network within seconds.

What Spanning Tree Protocol Does

Spanning Tree Protocol (STP) automatically detects redundant paths between switches and logically blocks just enough of them to eliminate any loops, while still keeping the physical backup cable in place, ready to activate if the active path fails.

Switch A ====== Switch B    (active link - forwarding)
   \\              //
    == == == == ==           (redundant link - blocked by STP, but ready as backup)

How STP Decides Which Links to Block

1. Switches elect one switch as the "root bridge" - the reference point for calculating the best paths.
2. Each switch calculates the shortest path back to the root bridge.
3. Any redundant link that would create a loop is put into a blocking state - it stops forwarding regular traffic, but keeps listening in case it's needed.

Why STP Matters in Practice

STP lets network administrators build genuinely redundant networks - with real backup paths for reliability - without the risk of an unintended broadcast storm, automatically re-activating a blocked link if the currently active path ever fails.