> ## Content Index > Fetch the complete content index at: https://www.pinglabz.com/llms.txt > Use this file to discover other available public pages before exploring further. # STP vs RSTP: Convergence, Port Roles, and When to Switch - URL: https://www.pinglabz.com/stp-vs-rstp/ - Published: 2026-04-25T06:08:49.000Z - Updated: 2026-06-13T20:08:44.000Z - Description: Classic 802.1D STP vs 802.1w RSTP. The convergence differences (30s vs sub-second), the port state and role changes, and the one-command Cisco migration from PVST+ to Rapid PVST+. - Author: Jaime - Tags: STP, #Import 2026-08-01 19:54 Classic Spanning Tree Protocol (802.1D STP) and Rapid Spanning Tree Protocol (802.1w RSTP) solve the same problem in fundamentally different ways. STP was the 1990 design built around timers; RSTP is the 2001 redesign built around explicit handshaking. Most modern switches default to RSTP-based flavors (Cisco's Rapid PVST+, MST), but plenty of production networks still run with classic STP semantics because someone never enabled the modern mode. This article is a side-by-side comparison: what is identical, what is different, why the differences matter, and how to tell which one your network is actually running. If you are studying for CCNP, planning a migration, or trying to figure out why convergence in one part of your network takes 30 seconds while another part is sub-second, this is the comparison. ## What's the Same Both protocols share the same goal: maintain exactly one active path between any two switches in a Layer 2 network, with the others ready to take over if the active one fails. Both elect a Root Bridge, both compute Root Ports and Designated Ports, both forward only along the resulting tree, and both block the redundant ports until needed. The election rules are identical. Bridge ID = priority + system ID extension + base MAC. Lowest bridge ID wins the root election. Lowest cost path wins the Root Port election. Designated Port tiebreakers walk the same list in both protocols. BPDU format is mostly compatible. RSTP uses a slightly different BPDU type (version 2, with additional flags), but a switch running RSTP that receives a 802.1D version-0 BPDU falls back to legacy mode for that specific port. The two protocols can coexist on the same network during a migration. ## The Side-by-Side Comparison Standard year 802.1D STP1990 802.1w RSTP2001 Convergence on direct failure (Alternate available) 802.1D STP30-50 seconds 802.1w RSTPSub-second Convergence on indirect failure 802.1D STP 50 seconds (Max Age + 2x Forward Delay) 802.1w RSTP \~6 seconds (3 missed BPDUs) Port states 802.1D STP 5 (Disabled, Blocking, Listening, Learning, Forwarding) 802.1w RSTP 3 (Discarding, Learning, Forwarding) Port roles 802.1D STP 3 (Root, Designated, Non-Designated) 802.1w RSTP 5 (Root, Designated, Alternate, Backup, Disabled) BPDU origination 802.1D STP Only the root sends; non-root relays 802.1w RSTP Every switch sends every Hello BPDU loss tolerance 802.1D STP Max Age (20s = 10 missed BPDUs) 802.1w RSTP3 missed BPDUs (\~6s) Topology change handling 802.1D STP TCN walks to root, root sets TC bit, all flush MACs 802.1w RSTP Originator floods TC to neighbors directly Proposal/Agreement handshake 802.1D STPNone 802.1w RSTP Yes, on point-to-point links Edge port treatment 802.1D STP Cisco PortFast extension only 802.1w RSTP Built into the standard as edge port type Link types 802.1D STPImplicit 802.1w RSTP Explicit (point-to-point, shared, edge) Default Cisco mode 802.1D STPWas PVST+ pre-IOS 12.2 802.1w RSTP Rapid PVST+ since IOS 12.2(25)SEC ## The Convergence Story Classic STP convergence is timer-driven. After a topology change: 1. **Max Age (20s).** Wait for the old BPDU to age out from the LSDB. 2. **Listening state (15s, Forward Delay).** Send/receive BPDUs but do not yet learn MACs or forward data. 3. **Learning state (15s, Forward Delay).** Now learn MACs but still do not forward. 4. **Forwarding state.** Finally pass data. Total: 50 seconds for a port that was Blocking when the change happened. Even ports that just came up only skip step 1, leaving 30 seconds of pre-Forwarding states. RSTP eliminates the timers entirely on point-to-point links. The Alternate Port concept means every non-root switch already has a pre-computed backup Root Port standing by in Discarding state, ready to forward immediately when the current Root Port fails. The proposal/agreement handshake replaces the listening/learning timers with a one-BPDU-round-trip exchange that takes milliseconds. The result: classic STP takes 30-50 seconds to converge on any non-trivial topology change. RSTP converges in tens of milliseconds for direct failures, and tens of milliseconds plus 6 seconds (the 3-missed-BPDU window) for indirect failures. ## Port States: 5 to 3 Discarding Maps to 802.1D Disabled, Blocking, Listening Forwards data?No Learns MACs?No Learning Maps to 802.1DLearning Forwards data?No Learns MACs?Yes Forwarding Maps to 802.1DForwarding Forwards data?Yes Learns MACs?Yes The state-machine collapse matters because under RSTP a port does not normally walk through these states on a timer. It transitions directly from Discarding to Forwarding via the proposal/agreement handshake (on point-to-point) or via PortFast edge type (on host links). The fewer states are not just cosmetic; they enable the fast convergence model. ## Port Roles: 3 to 5 Classic STP has three roles: Root Port, Designated Port, and "Non-Designated" (a generic catch-all for any port not actively forwarding). RSTP elevates two specific Non-Designated cases to first-class roles: - **Alternate Port.** An immediate backup to the Root Port. If the Root Port fails, the Alternate is pre-computed and can take over instantly. - **Backup Port.** A backup to a Designated Port on the same shared segment. Only exists on multi-access (hub) segments. Rare in modern networks. The Alternate Port is the headline upgrade. It is what makes RSTP "fast" in practice: every non-root switch already knows what to do if its current Root Port goes down, no recomputation needed. ## How to Tell Which One You're Running Cisco command: ``` Switch# show spanning-tree summary | include mode Switch is in rapid-pvst mode ``` Possible outputs: - `pvst` \- Cisco PVST+ (per-VLAN, but classic 802.1D semantics; slow) - `rapid-pvst` \- Cisco Rapid PVST+ (per-VLAN, RSTP semantics; fast) - `mst` \- Multiple Spanning Tree (instances mapped to VLANs; RSTP-based) If you see `pvst`, you are running classic STP semantics regardless of how modern your hardware is. Switch to `rapid-pvst` with one command: ``` Switch(config)# spanning-tree mode rapid-pvst ``` Cisco's default has been Rapid PVST+ since around 2007\. Anything still running plain PVST+ is likely a legacy configuration that was never updated. ## Running Mixed (RSTP and STP on the Same Network) Yes, you can. RSTP includes 802.1D backward compatibility: when an RSTP switch receives a classic 802.1D BPDU, it falls back to legacy mode for that specific port and uses 802.1D timers. Other ports on the same switch still use RSTP. The implication: you can migrate a network from PVST+ to Rapid PVST+ one switch at a time. The downside is that any port that falls back to legacy loses the RSTP fast-convergence benefit. The whole topology only converges fast when all switches run RSTP. The migration recipe: 1. Audit the current state. `show spanning-tree summary` on every switch. 2. Plan the order. Start with edge switches (least disruptive if something goes wrong). 3. Per switch: `spanning-tree mode rapid-pvst`. Verify with `show spanning-tree summary` and `show spanning-tree vlan X`. 4. Watch for unexpected reconvergence on neighbor switches; classic STP will see new BPDU formats and may briefly recompute. 5. Continue until the whole topology is on Rapid PVST+. ## When You'd Still Run Classic STP Almost never. The only reasons to keep classic 802.1D / PVST+ in 2026: - **Equipment too old for RSTP.** Truly ancient kit (pre-2003 Cisco IOS, deeply legacy unmanaged switches). Replace it. - **Vendor compatibility issues.** Some old non-Cisco gear handles RSTP poorly during interop. Has been mostly fixed. - **Deliberate testing.** Lab scenarios where you want to demonstrate the convergence difference. Otherwise, run Rapid PVST+ or MST. The configuration is one global command, and the convergence improvement is multiple orders of magnitude. ## RSTP / Rapid PVST+ vs MST: The Next Decision Once you have decided not to run classic STP, the next decision is whether to run Rapid PVST+ (one RSTP instance per VLAN) or MST (multiple VLANs mapped to a small number of RSTP instances). Standard Rapid PVST+Cisco-proprietary MSTIEEE 802.1s Number of instances Rapid PVST+One per VLAN MST1-65 (typically 1-16) Per-VLAN load balancing Rapid PVST+ Easy (per-VLAN root manipulation) MSTCoarser (per-instance) CPU overhead at scale Rapid PVST+ High (one BPDU per VLAN per Hello) MST Low (one BPDU per instance) Configuration complexity Rapid PVST+Low MST Higher (regions, instance mapping) Vendor interop Rapid PVST+Cisco-only effectively MSTUniversal Rule of thumb: if you have more than 50 VLANs, MST is worth the configuration effort. Below that, Rapid PVST+ is simpler and fine. Detail in [Configuring Multiple Spanning Tree (MST)](https://www.pinglabz.com/configure-mst-cisco-switches/). ## Summary STP and RSTP solve the same problem (loop-free Layer 2) with the same election rules but radically different convergence. STP takes 30-50 seconds to converge on a topology change because it relies on timers; RSTP takes sub-second on point-to-point links because it relies on explicit handshaking and pre-computed Alternate Ports. If your network is running plain PVST+ in 2026, switch to Rapid PVST+ today. The configuration is one global command and the convergence improvement is real. If you have more than 50 VLANs, look at MST for the per-instance scalability. Bookmark the [Spanning Tree Protocol pillar](https://www.pinglabz.com/spanning-tree-protocol/) for the full operational picture, and the [RSTP deep dive](https://www.pinglabz.com/rapid-spanning-tree-protocol-rstp/) for the protocol-level details of what changed.