STP vs RSTP: Convergence, Port Roles, and When to Switch

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

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

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).

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).

Deeper RSTP mechanics

The comparison above is the decision framework. The sections below fold in the deeper RSTP mechanics that used to live in a separate Rapid Spanning Tree article: proposal/agreement handshakes, link types, BPDU behavior, topology-change MAC flushing, the Cisco Rapid PVST+ enablement commands, and when RSTP falls back to slow timers.

Proposal/Agreement: Why RSTP is Sub-Second

The signature RSTP mechanism is the proposal/agreement handshake on point-to-point links. Here is the dance:

1. A new link comes up between two switches that already have RSTP elsewhere.
2. The switch that should be the Designated end sends a BPDU with the proposal flag set.
3. The other switch receives it, recognizes the proposal, places all its other Designated ports into a brief "sync" state (preventing temporary loops), and sends back an agreement BPDU.
4. The Designated switch immediately transitions the new port to Forwarding.
5. The whole exchange takes one BPDU round-trip, typically a few milliseconds.

Compare to 802.1D, which would have waited 30-50 seconds for the same transition. The handshake only works on point-to-point links, which is why RSTP introduces explicit link types.

Link Types: Point-to-Point, Shared, Edge

Cisco IOS XE auto-detects link types from interface duplex (full-duplex = point-to-point, half-duplex = shared). In modern campus deployments every switch-to-switch link is full-duplex, so the auto-detection just works. The exception is when you tunnel STP through a non-RSTP medium; force link-type point-to-point in that case.

Edge ports (host-facing) get explicit treatment via PortFast, which preserves the same fast-transition behavior as classic STP's PortFast extension. RSTP integrates it as part of the standard rather than a Cisco add-on.

BPDU Origination: Now Every Switch

In 802.1D, only the root bridge originates BPDUs and every other switch relays them downstream every Hello. This made non-root BPDUs implicit acknowledgements: as long as you keep relaying, the upstream is fine.

RSTP changes this. Every switch originates its own BPDU every Hello (default 2s) regardless of whether the root has sent something. This is what enables the 3-missed-BPDU rule: if you do not hear from your direct neighbor for 6 seconds (3 x 2s Hello), you consider them down. Compare to 802.1D's Max Age of 20 seconds.

This change has another implication: RSTP can detect upstream link failures faster than 802.1D, because every switch is independently reporting up the tree.

Topology Change: Faster MAC Flushing

When the topology changes, MAC address tables on all switches need to be updated. Otherwise frames going to a host whose path has changed will be sent to the wrong segment.

Classic STP handles this with TCN BPDUs that walk all the way to the root and back. The root sets the TC bit in regular BPDUs, and every switch then ages out MAC entries faster (15s instead of 5 minutes default). It is slow.

RSTP handles it directly. The switch that detected the topology change floods TC BPDUs to all its neighbors immediately, which flush their MAC tables for affected interfaces and propagate the TC. The result: MAC tables converge on the new topology in seconds, not in 15-second-per-hop cascades.

Enabling Rapid PVST+ on Cisco IOS XE

One global command:

Switch(config)# spanning-tree mode rapid-pvst

That is it. Cisco's default has been Rapid PVST+ for over a decade, but if you are inheriting older configs always check. Verify:

Switch# show spanning-tree summary | include mode
Switch is in rapid-pvst mode

For interface settings to ensure fast convergence:

Switch(config)# interface GigabitEthernet1/0/1
Switch(config-if)#  spanning-tree portfast              ! Edge port type
Switch(config-if)#  spanning-tree bpduguard enable      ! Protect edge port

Switch(config)# interface GigabitEthernet1/0/24
Switch(config-if)#  spanning-tree link-type point-to-point

The full configuration walkthrough is in Configuring Rapid PVST+ on Cisco Catalyst Switches.

Reading the show output

The most useful command on a steady-state network:

SW1# show spanning-tree vlan 10

VLAN0010
  Spanning tree enabled protocol rstp
  Root ID    Priority    24586
             Address     0050.7989.aaaa
             Cost        4
             Port        25 (TenGigabitEthernet1/1/1)
             Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec

  Bridge ID  Priority    32778  (priority 32768 sys-id-ext 10)
             Address     0050.7989.bbbb
             Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec
             Aging Time  300 sec

Interface           Role Sts Cost      Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Te1/1/1             Root FWD 4         128.25   P2p
Te1/1/2             Altn BLK 4         128.26   P2p
Gi1/0/5             Desg FWD 19        128.5    Edge P2p

Three things to read off:

• Root ID vs Bridge ID. If they match, this switch is the root. If not, the Root ID tells you which switch the topology has elected.
• Role column. Root, Designated (Desg), Alternate (Altn), Backup. The pattern of roles tells you the active topology.
• Type column. "P2p" means RSTP is treating it as a point-to-point link (enables fast handshake). "Shr" means shared media (slow). "Edge" means it is an edge port (PortFast).

Convergence Numbers: What to Expect

The big win is direct-failure convergence on point-to-point links, which is the most common topology change in modern campuses.

When RSTP Convergence Falls Back to Slow

RSTP only achieves sub-second convergence under specific conditions. If any are missing, you fall back closer to 802.1D timers:

• Link must be point-to-point. Half-duplex or shared link types disable proposal/agreement.
• Both ends must be RSTP-capable. A neighbor running 802.1D forces fallback on that link.
• BPDUs must not be filtered. Aggressive BPDU Filter on a non-edge port breaks RSTP entirely.
• Hardware must process BPDUs in time. A switch with high CPU may delay BPDU origination/processing past the 3-Hello boundary, triggering false timeouts.

The full convergence troubleshooting walkthrough is in Troubleshooting STP Convergence Problems and Slow Failover.

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 for the full operational picture, and the RSTP deep dive for the protocol-level details of what changed.