[ CCNA · DOMAIN 2 · SWITCHING · PLAIN-ENGLISH ANSWER ]
STP vs RSTP_
Same job — stop Layer 2 loops — but RSTP does it dramatically faster. Here's what changed and why it matters.
[ ▶ SHORT ANSWER ]
STP (802.1D) and RSTP (802.1w) both prevent Layer 2 switching loops by blocking redundant paths, but they differ mainly in speed. Classic STP moves a port through Blocking, Listening, Learning, and Forwarding states using timers, taking roughly 30-50 seconds to converge after a topology change. RSTP is a faster evolution: it uses a proposal/agreement handshake between switches instead of timers and converges in under a second. RSTP also simplifies port states to Discarding, Learning, and Forwarding, and adds the Alternate and Backup port roles that act as pre-computed standby paths. RSTP is backward-compatible with STP and is the modern default (Cisco's Rapid PVST+).
Both protocols solve the same problem: a redundant Layer 2 topology will loop forever (broadcast storms, MAC flapping) unless something blocks the backup links. STP and RSTP both build a loop-free tree — the difference is how fast they recover when something changes.
Classic STP (802.1D) — slow but reliable
STP walks a port through four states using timers:
Blocking -> Listening (15s) -> Learning (15s) -> Forwarding
Total convergence: ~30s (up to ~50s with max-age delays)
That half-minute outage after a link change is painful on modern networks.
RSTP (802.1w) — sub-second
RSTP keeps the same loop-prevention goal but replaces timers with a proposal/agreement handshake: neighbouring switches negotiate directly and bring ports to forwarding almost instantly. It also collapses the states to three:
Discarding (was Blocking/Listening) -> Learning -> Forwarding
New port roles
STP has Root and Designated ports. RSTP adds two standby roles so recovery is instant:
- Alternate port — a backup path to the root bridge, ready to take over if the root port fails.
- Backup port — a backup to a designated port on the same shared segment.
The bottom line
RSTP is STP, evolved: same loop prevention, far faster convergence, and backward-compatible (it falls back to 802.1D when it detects a legacy neighbour). On Cisco gear you enable it with spanning-tree mode rapid-pvst. There's almost no reason to run classic 802.1D today.
★ RELATED QUESTIONS
[ Is RSTP backward-compatible with STP? ]
Yes. RSTP detects legacy 802.1D switches and falls back to classic STP behaviour on those links, while still running fast convergence everywhere else.
[ How much faster is RSTP? ]
Classic STP takes about 30-50 seconds to converge after a change; RSTP typically converges in under a second by using proposal/agreement instead of listening/learning timers.
[ What port roles does RSTP add? ]
RSTP adds the Alternate port (a pre-computed backup to the root) and the Backup port (a backup to a designated port on a shared segment), on top of STP's Root and Designated roles.
★ READ NEXT
[ ▶ RELATED PLAIN-ENGLISH ANSWERS ]
[ ★ PRACTICE IT, DON'T JUST READ IT ]
Concepts stick when you drill them. Run
today's Daily CCNA Drill to build a streak, or jump straight into the related labs and tools: