Week 5 · Lesson 19

Rapid PVST+

Classic STP takes up to fifty seconds to converge — an eternity for modern voice. Rapid PVST+ is Cisco’s delivery of the improved RSTP algorithm (802.1w): same loop-prevention goal, dramatically shorter convergence, and one spanning tree per VLAN. This lesson covers the RSTP port states, the two new roles it dared to invent, and the safety switches — PortFast, BPDU guard, root guard — that protect it.

CCNA 200-301 Domain 2.0 Network Access Verified 2026-10-11
Learning objectives
Part 1

Why fifty seconds is too long

Classic 802.1D convergence — max age 20 s + listening 15 s + learning 15 s — can hold traffic off a newly available link for about 50 seconds. Fifty seconds is fine for file transfers and a nightmare for IP telephony and modern collaboration: call setup fails, TCP sessions time out, and the network manager gets a phone call. The fundamental problem with 802.1D is that it assumes all ports need the slow, cautious transition when only a few truly do. The Rapid Spanning Tree Protocol, IEEE 802.1w, keeps the tree logic but replaces the timers with handshakes and role knowledge, cutting convergence to a handful of seconds.

Definition — RSTP RSTP (IEEE 802.1w) is a redesigned spanning tree algorithm that converges much faster than 802.1D by negotiating transitions between designated and root ports instead of waiting out timers. It is backwards-compatible, speaks to legacy bridges through BPDUs, and is the engine inside Cisco’s Rapid PVST+.
In this lesson · select a part to jump

Key ideas & exam traps · select one

Part 2

RSTP: the 802.1w redesign

RSTP keeps the essential machinery — root election by lowest bridge ID, BPDUs, path costs — and speeds up the parts that made 802.1D slow. The key change is a proposal/agreement handshake: a designated port proposes itself, the downstream switch agrees, and the port goes straight to forwarding without waiting for forward delays. Because the negotiation happens hop by hop toward the leaves as soon as the root is known, the topology settles almost immediately. RSTP also sends BPDUs every hello time on every port (not just the root), so a lost neighbour is detected in two missed hellos rather than after the max-age wait.

For the exam, the cleanest statement is comparative: RSTP converges in seconds; 802.1D can take 50. The handshake replaces the timers. Everything else you memorised in Lesson 18 about root election and path cost still applies.

Part 3

Three states, not five

RSTP compresses the five port states into three. Blocking, listening, and disabled merge:

RSTP stateReplaces in 802.1DLearns MACs?Forwards?
DiscardingBlocking + Listening + DisabledNoNo
LearningLearningYesNo
ForwardingForwardingYesYes

The exam trap is symmetrical to the 802.1D one: in RSTP a blocked port is described as discarding, not blocking. Read the protocol in the question before you pick the word. If it says “RSTP port state” and offers blocking as an option, that is the distractor.

Part 4

Alternate and backup ports

802.1D had one passive role — non-designated. RSTP splits it into two, because the two kinds of redundancy are different:

Both alternate and backup are in the discarding state while active; both become Altn BLK or Back BLK in show spanning-tree output. The mnemonic the syllabus recognises: alternate = alternate root path; backup = backup of my own designated port.

ROOT SW1 SW2 SW3 root port FWD root port FWD alternate — discarding ready to replace the root port in seconds
RSTP keeps a warm spare: the alternate port is discarding but ready. If SW2’s root port fails, the alternate takes over through a handshake, not a 50-second wait.
Part 5

Rapid PVST+: one tree per VLAN

PVST+ (Per VLAN Spanning Tree) runs an independent spanning tree per VLAN so that different VLANs can load-balance over different links — VLAN 10’s tree can block here while VLAN 20’s blocks there. Rapid PVST+ is simply PVST+ running the RSTP algorithm inside each per-VLAN tree, and it is the default spanning-tree mode on modern Catalyst switches. One BPDU per VLAN, tagged accordingly, gives per-VLAN convergence and per-VLAN safety settings.

Because each VLAN elects its own root bridge, a network should deliberately place the elected root differently per VLAN to spread the load — an advanced design point that the exam recognises as a benefit of any per-VLAN STP. The commands that set the mode and the root:

S1(config)# spanning-tree mode rapid-pvst
S1(config)# spanning-tree vlan 10,20 priority 0   ! force this switch as root for those VLANs
S1(config)# interface gigabitethernet 0/24
S1(config-if)# spanning-tree portfast
S1(config-if)# spanning-tree bpduguard enable
S1(config-if)# end
Exam tip The command spanning-tree mode rapid-pvst is IOS’s answer to “which command enables Rapid PVST+?” and the default replacement for classic spanning-tree mode pvst. Pair it with the fact that Rapid PVST+ uses RSTP and you have the two facts the blueprint asks for.
Part 6

Edge ports and PortFast

Access ports connect to end devices — PCs, servers, printers — none of which speak STP. Making an access port wait through listening and learning is pure waste, so PortFast tells the switch the port is an edge port: no BPDUs are expected, no loop can form, and the port jumps straight to forwarding when the link comes up. A PC gets connectivity in seconds instead of thirty.

The danger is honest: the port is edge because you say so. If someone plugs a switch into a PortFast port, you have just created a potential loop with no STP protection at that port. That risk is exactly what BPDU guard exists to neutralise (next section). PortFast is configured per interface with spanning-tree portfast (optionally spanning-tree portfast default globally on all access ports at the interface level).

Part 7

BPDU guard

BPDU guard turns the PortFast assumption into a police action: if a BPDU ever arrives on a BPDU-guarded port, the switch immediately puts that port into the error-disabled state (effectively shut down) rather than allow the frame to disturb the tree. The configuration pairs naturally with PortFast on access ports (as in the block above): legitimately attached hosts never send BPDUs, so the only way the guard fires is if an attacker or a careless colleague connects a switch to the port — at which point you want that port dead on the spot. Recovery is manual (shutdown/no shutdown) or automatic via errdisable recovery cause bpduguard.

Watch out PortFast alone skips the loop-prevention dance; BPDU guard enforces that no BPDU arrives. They are typically deployed together on access ports, and the exam likes to ask which one stops a rogue switch: BPDU guard — because PortFast does not inspect BPDUs, it just ignores the STP transition.
Part 8

Root guard

The tree’s shape depends on who wins the root election. A legitimate-but-misconfigured switch with a very low priority — or an attacker who can inject superior BPDUs — can steal the root and reroute the whole network through itself. Root guard protects an interface by forbidding it from becoming a root port: if a superior BPDU arrives there, the port is moved to the root-inconsistent state (blocked) until the offending BPDUs stop. It is used on ports that should never lead toward the true root, such as downstream access-facing uplinks. The command is spanning-tree guard root.

Contrast the two guards with one sentence each: BPDU guard protects the edge ports from receiving BPDUs (error-disables on sight); root guard protects the tree topology from a port that claims to be the better root (blocks, then recovers automatically).

Part 9

Configuration and convergence comparison

S1(config)# spanning-tree mode rapid-pvst
S1(config)# spanning-tree vlan 10 root primary       ! or set priority
S1(config)# interface range gigabitethernet 0/1-24
S1(config-if-range)# spanning-tree portfast
S1(config-if-range)# spanning-tree bpduguard enable
S1(config-if-range)# end

S1# show spanning-tree
VLAN0010
  Spanning tree enabled protocol rstp
  Root ID    Priority    32778
             Address     aaaa.aaaa.bbbb
  Bridge ID  Priority    32778
             Address     aaaa.aaaa.bbbb
  Interface  Role Sts Cost      Prio.Nbr Type
  Gi0/1      Root FWD 4         128.1    P2p
  Gi0/23     Altn BLK 4         128.23   P2p
  Gi0/24     Desg FWD 4         128.24   Edge

Read the output the RSTP way. The protocol line says rstp. The root port is Root FWD; the spare is Altn BLK; the access port configured with PortFast shows Edge and skips the forwarding delay. This one screen is the whole Rapid PVST+ lesson in compressed form.

CharacteristicClassic STP (802.1D)Rapid PVST+ (RSTP)
StandardIEEE 802.1DIEEE 802.1w (RSTP), per VLAN
Port statesBlocking, Listening, Learning, Forwarding, DisabledDiscarding, Learning, Forwarding
Transition methodForward-delay timersProposal/agreement handshake
Typical convergenceUp to ~50 sA few seconds
Extra rolesNon-designatedAlternate, Backup, Edge
Key protection—PortFast, BPDU guard, root guard, loop guard
Reference table · select a row

Key terms

The vocabulary you need

Every term below appears in the lesson text above. Select one to read its definition, then use the quiz at the end to check what stuck.

Key terms · select a term

Part 10 · Your turn

Review

Check what you have learned with these review questions.

Review · 5 questions

Sources

Sources & references

  1. Cisco. CCNA (200-301) Exam Topics. cisco.com.
  2. IETF. Request for Comments (RFCs). rfc-editor.org.
  3. IANA. Internet Assigned Numbers Authority registries. iana.org.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.