Rapid PVST+: why your network converges before you finish blinking

Classic 802.1D spanning tree treated every topology change like a fire drill: freeze, wait through listening and learning, and hope 30 to 50 seconds later everything settles. Rapid PVST+ (based on 802.1w) replaced the waiting with a conversation.

The proposal/agreement handshake

When a new link comes up between two switches, they don't wait for timers. The designated port sends a proposal: "I'd like to forward — sync yourself." The downstream switch blocks its other non-edge designated ports, then replies with an agreement: "Done, go ahead." The link goes forwarding almost immediately, and the sync ripples down the tree link by link.

That's the whole trick: explicit handshakes instead of conservative timers.

Port roles did the heavy lifting

Rapid PVST+ pre-computes its escape routes:

• Root port — best path to the root bridge.
• Designated port — best path for a segment.
• Alternate port — a backup root port, already known, ready to take over.
• Backup port — a backup designated port (rare, needs a hub or self-loop).

When a root port fails, the alternate port doesn't re-run a 50-second election. It just becomes the new root port — typically in under a second.

Verify it like you mean it

SW2# show spanning-tree vlan 10

VLAN0010
  Spanning tree enabled protocol rstp
  Root ID    Priority    24586
             Address     0011.2233.4455
             Cost        4
             Port        25 (GigabitEthernet1/0/1)

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

Three things worth noticing: the protocol says rstp, the alternate port is already elected and blocking, and Gi1/0/24 is an edge port — the RSTP name for what PortFast makes.

The gotchas that show up in exams

• Rapid convergence only works on point-to-point links. A half-duplex port falls back to timer-based behavior — a classic troubleshooting ticket.
• A Rapid PVST+ switch talking to an old 802.1D switch reverts to classic STP on that port. One legacy switch can slow a whole segment.
• Edge ports that receive a BPDU instantly lose edge status. That's a feature.

Spanning tree isn't legacy trivia — it's still deciding which of your links actually carry traffic. Befriend it before the lab makes you.