A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
Classic STP converges in 30–50 seconds. RSTP converges in under a second on point-to-point links. That's not a tweak — it's the difference between a blip users notice and an outage they call the helpdesk about. Every modern switch runs RSTP by default.
RSTP (802.1w) isn't a different protocol — it's an evolution of STP that uses the same BPDU structure and cost calculations. The big changes are in convergence speed and port role semantics.
| Feature | Classic STP | RSTP |
|---|---|---|
| Port states | 5 (Blocking, Listening, Learning, Forwarding, Disabled) | 3 (Discarding, Learning, Forwarding) |
| Convergence | 30–50 seconds | Under 1 second on point-to-point |
| Port roles | Root, Designated, Blocked | Root, Designated, Alternate, Backup |
| BPDU handling | Only root sends, others forward | Every switch sends BPDUs from every port |
| Link type awareness | No | Yes — point-to-point vs. shared |
The BPDU handling change is the biggest. In STP, only the root originates BPDUs and non-root switches relay them. In RSTP, every switch sends BPDUs from every port every Hello interval (2 seconds). The flood of BPDUs is heavier, but the state machine has better information to work with.
The handshake works like this: SW1 sends a Proposal on a port it wants to bring to Forwarding. SW2 receives it, immediately puts all other ports into Sync (blocking state), then sends an Agreement back. SW1 gets the Agreement and moves its port to Forwarding. The whole exchange takes milliseconds — no waiting for timers.
The Alternate role replaces 'Blocked' from classic STP, and it's a genuine upgrade — alternate ports are actively maintained as standby candidates, ready to become root ports immediately if the current root port fails.
! RSTP is default on modern Cisco switchesSW1(config)# spanning-tree mode rapid-pvst! VerifySW1# show spanning-tree | include protocol
`rapid-pvst` gives you RSTP behavior per VLAN. `pvst` forces classic STP per VLAN. `mst` runs Multiple Spanning Tree (MST), which groups VLANs into instances for scalability. Modern deployments use either `rapid-pvst` (common) or `mst` (large networks).
RSTP and classic STP interoperate — an RSTP switch falls back to classic STP behavior on ports connected to a classic STP neighbor. But you lose the fast convergence. Check that every switch in the topology runs RSTP for maximum benefit.
| RSTP state | Classic STP equivalent | Forwards? |
|---|---|---|
| Discarding | Disabled + Blocking + Listening | No |
| Learning | Learning | No |
| Forwarding | Forwarding | Yes |
RSTP collapsed the classic five states into three. Listening and Blocking both become Discarding. The distinction matters less because RSTP doesn't sit in those states for fixed timers — it transitions based on the proposal/agreement handshake.
SW3 has two uplinks: Gi0/1 (root port) and Gi0/2 (alternate port). Gi0/1's link fails. In classic STP, how long until Gi0/2 starts forwarding? In RSTP?
Select the safest next action.
Finish the lesson once you have worked through the material. This awards ★ 35 XP.