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
Preview · 30 min
Learn how Rapid Spanning Tree Protocol (RSTP) achieves subsecond convergence. Understand Proposal and Agreement, Edge Ports, and simplified port states.
Imagine a network outage of nearly a full minute. With Voice over IP, high-frequency trading and real-time video, fifty seconds of downtime is an eternity. Traditional STP was built for a slower, more forgiving era of networking.
Waiting for timers to expire before activating a backup path is simply unacceptable. The industry needed the same loop-free safety as STP, but with near-instant recovery.
Enter Rapid Spanning Tree Protocol (RSTP), defined in IEEE 802.1w. RSTP is the successor to traditional STP and converges in a fraction of a second.
Traditional STP is passive: it relies entirely on timers. After a failure a switch may wait for Max Age (20 seconds), then 15 seconds in Listening and another 15 seconds in Learning.
RSTP changes this. Instead of waiting for timers, it uses an active Proposal and Agreement mechanism: switches negotiate with their neighbours and move ports to Forwarding almost instantly, when it is safe.
RSTP is also fully backward compatible with traditional STP. If an RSTP switch detects a legacy STP switch on a link, it falls back to traditional STP behaviour on that port only, to keep the network stable.
Create a free account to unlock the rest of this task, complete tasks, and earn Rep.
Sign in