NEWPractise supported commands in browser simulations, alongside the lesson.Try a browser practice exercise.Try a lab♥ Codelivly is 100% free, no paywall. If it helped you, chip in to keep it running.100% free. Help keep it so.Support us
Endpoint & Network Security Monitoring
Dive into the critical telemetry that powers modern threat detection. The Endpoint & Network Security Monitoring module
ViewNetwork Forensics
Network traffic is the nervous system of any organization, and for attackers, it is the highway used for initial access,
ViewDFIR Reporting and Case Management
Effective incident response doesn't end when the threat is eradicated; it concludes with clear, actionable reporting and
ViewPreview · 30 min
Learn how Spanning Tree Protocol (STP) prevents Layer 2 loops and broadcast storms. Master Root Bridge elections, BPDUs, and port states in this networking module.
Imagine a city with a network of roads. More roads between neighbourhoods are a good idea: they give alternate routes when one road is closed for construction. But what if those roads form a perfect circle with no stop signs or traffic lights? Cars drive around the circle forever, and more cars join at every intersection, until the whole city gridlocks and comes to a complete halt.
In computer networking, this gridlock is called a Layer 2 loop. The Spanning Tree Protocol (STP) is the traffic control system that prevents this disaster while still allowing redundant, backup paths.
To understand why Spanning Tree matters, you must understand the problem it solves.
Switches are fantastic at forwarding traffic, but with one cable between them they rely on a single active path. If a cable is unplugged or a switch fails, the network segments behind that link go completely dark.
The obvious solution is to add redundant links. With several cables between switches you create backup paths: if one cable fails, traffic can use the other.
But this introduces a fatal flaw at Layer 2. Switches forward broadcast frames (like ARP requests) out of every port. If there is a physical loop, a broadcast frame enters the loop, Switch A copies it to Switch B, Switch B copies it back to Switch A, and so on, forever. Ethernet frames have no TTL field, so nothing stops them. This is a broadcast storm: it consumes 100 percent of the bandwidth in milliseconds and crashes the entire infrastructure.
Create a free account to unlock the rest of this task, complete tasks, and earn Rep.
Sign in