Rapid Spanning Tree Protocol (RSTP): What Changed from 802.1D STP

Rapid Spanning Tree Protocol (RSTP, IEEE 802.1w) is the 2001 update to classic 802.1D Spanning Tree. Every modern Cisco campus runs Rapid PVST+ (Cisco's per-VLAN flavor of RSTP), and the reason is simple: classic STP takes 30-50 seconds to converge after a topology change, RSTP takes a fraction of a second. If you have ever waited for a switch to pass DHCP at boot, that 30-second wait was 802.1D port states burning Forward Delay timers; RSTP made that obsolete.

This article is the deep-dive on what changed between 802.1D and 802.1w, why those changes produce sub-second convergence, and how to deploy Rapid PVST+ on Cisco IOS XE without tripping over the few legacy gotchas. If you are studying for CCNP, designing a campus, or migrating from PVST+ to Rapid PVST+, this is what you need to know.

Why Classic STP Was Too Slow

Classic 802.1D was designed in 1990, when Ethernet ran at 10 Mbps and applications were tolerant of brief outages. Its convergence model uses three timers (Hello at 2s, Forward Delay at 15s, Max Age at 20s) and relies on those timers expiring before a port can transition through the Listening, Learning, and Forwarding states.

For a port to go from Blocking to Forwarding after a topology change, it must wait Max Age (20s) for the old BPDU to age out, then Forward Delay (15s) in Listening, then Forward Delay (15s) in Learning. That is 50 seconds. Even ports that come up fresh (no Max Age wait) need 30 seconds for the two Forward Delay states. By the early 2000s, with VoIP, real-time apps, and gigabit Ethernet, that was no longer acceptable.

The fix was not to shorten the timers. The fix was to redesign the protocol so it does not need them in the first place.

Key Changes in 802.1w

RSTP keeps the same core concept (one spanning tree, one root bridge, one root port per non-root switch, one designated port per segment) but rebuilds the convergence machinery around explicit handshaking instead of timers:

From Five States to Three

RSTP collapses the classic state machine. The five 802.1D states map to three RSTP states:

The collapsed states matter because under RSTP, ports do not generally walk through them on a timer. They jump directly from Discarding to Forwarding via the proposal/agreement handshake, which takes one BPDU round-trip on a point-to-point link.

Two New Port Roles: Alternate and Backup

Classic STP only has Root and Designated; everything else is "Non-Designated" and Blocking. RSTP elevates two specific Non-Designated cases to first-class roles:

• Alternate Port (AP). An immediate backup to the Root Port. If the Root Port goes down, the Alternate is pre-computed and ready to take over instantly. The classic equivalent would have re-run the entire root election process.
• Backup Port (BP). An immediate backup to a Designated Port on the same shared segment. Only exists on shared (hub) segments, which barely exist in modern networks.

The Alternate Port is the headline upgrade. It is what makes RSTP feel "fast": every non-root switch already has a pre-determined replacement Root Port standing by, in Discarding state, ready to forward as soon as the current Root Port fails.

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.

Cisco's Rapid PVST+: RSTP Per VLAN

The IEEE 802.1w standard runs one spanning tree across the whole switching domain (CST). Cisco's PVST+ runs one STP instance per VLAN, which lets you load-balance traffic by making different switches root for different VLANs. Rapid PVST+ is the same per-VLAN model, but each instance is RSTP rather than 802.1D.

The trade-off is overhead: 100 VLANs means 100 STP instances, 100 sets of BPDUs every 2 seconds, and 100 SPF calculations on every topology change. For most campus networks this is fine. For very large networks (thousands of VLANs), MST is the answer instead. MST configuration is in a separate article.

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.

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.

Backwards Compatibility with 802.1D

RSTP is fully backwards compatible. If a switch running RSTP receives 802.1D-format BPDUs (no flags, no proposal/agreement), it falls back to legacy mode for that specific port and uses 802.1D-style timer-based transitions. The rest of the network continues to use RSTP normally.

This means you can mix 802.1D and 802.1w switches during a migration. The downside: any port that falls back to legacy mode does not benefit from sub-second convergence on that link. Migrate the whole topology to RSTP-capable equipment to get the full benefit.

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

RSTP (802.1w) is what made spanning tree usable for modern enterprise networks. The five state-machine changes (collapsed states, new port roles, proposal/agreement, faster topology change, every-switch BPDU origination) work together to convert classic STP's 30-50 second convergence into sub-second behavior on healthy point-to-point links.

Every modern Cisco campus should run Rapid PVST+ or MST, never classic 802.1D / PVST+. The configuration is one global command. The hardening (PortFast on edge ports, BPDU Guard with PortFast, Root Guard at distribution-facing-access, Loop Guard on point-to-point trunks) is in the Spanning Tree Protocol pillar. If you are seeing 30-second failover in a network that runs Rapid PVST+, something is forcing fallback to 802.1D and that is the first thing to investigate.