Rapid Spanning Tree Protocol (RSTP) & Rapid PVST+
STP Version Comparison
Understanding the evolution of Spanning Tree Protocol is critical for the CCNA. RSTP is an evolution, not a revolution, of Classic STP.
| Protocol | IEEE Standard / Cisco Proprietary | STP Instances | Load Balancing Capability | Notes |
|---|---|---|---|---|
| Classic STP | IEEE 802.1D | 1 (Shared by all VLANs) | No | Original standard; slow convergence (up to 50s). |
| PVST+ | Cisco Proprietary | 1 per VLAN | Yes | Cisco’s upgrade to 802.1D. Requires dot1q trunking. |
| RSTP | IEEE 802.1w | 1 (Shared by all VLANs) | No | Fast convergence via handshake, but no per-VLAN load balancing. |
| Rapid PVST+ | Cisco Proprietary | 1 per VLAN | Yes | Default on modern Cisco switches. Combines RSTP speed with per-VLAN instances. |
| MSTP | IEEE 802.1s | Multiple VLANs per instance | Yes | Groups VLANs into instances (e.g., VLANs 1-100 in Instance 1). Cisco runs the standard 802.1s. Best for large networks. |
Things to note: Rapid PVST+ is the version referenced in the CCNA exam topics and is the default on modern Cisco switches.
RSTP vs. Classic STP: Core Differences
- Convergence Mechanism: Classic STP relies on long, rigid timers. RSTP uses a bridge-to-bridge handshake mechanism to negotiate and move ports directly to the Forwarding state immediately if safe.
- BPDU Origination: In Classic STP, only the Root Bridge originates BPDUs. In RSTP, ALL switches originate and send their own BPDUs from their Designated Ports.
- BPDU Aging: Classic STP waits 10 Hello intervals (20 seconds) to declare a neighbor lost. RSTP considers a neighbor lost after 3 missed BPDUs (6 seconds) and immediately flushes MAC addresses learned on that interface.
- Port Costs: Expanded in RSTP to accommodate speeds beyond 10 Gbps.
RSTP Port Costs
| Link Speed | RSTP Cost |
|---|---|
| 10 Mbps | 2,000,000 |
| 100 Mbps | 200,000 |
| 1 Gbps | 20,000 |
| 10 Gbps | 2,000 |
| 100 Gbps | 200 |
| 1 Tbps | 20 |
| 10 Tbps | 2 |
RSTP Port States
RSTP simplifies the 5 Classic STP states into just 3 states by combining Blocking, Listening, and Disabled into a single state.
| RSTP State | Description | Traffic Forwarding? | MAC Learning? |
|---|---|---|---|
| Discarding | Combines Classic STP’s Blocking, Listening, and Disabled states. No user data is forwarded or learned. | No | No |
| Learning | Port prepares to forward traffic; learns MAC addresses but does not forward user data. | No | Yes |
| Forwarding | Port actively forwards user traffic and learns MAC addresses. | Yes | Yes |
Things to note: The show spanning-tree CLI output may still display “BLK” (Blocking) for discarding ports, but conceptually in RSTP, this is the Discarding state.
RSTP Port Roles
RSTP retains Root and Designated roles but splits the Classic STP “Non-Designated” role into two distinct roles for faster convergence.
| Port Role | Description | Fails Over To |
|---|---|---|
| Root Port (RP) | Unchanged. The port with the lowest root cost to the Root Bridge. | N/A |
| Designated Port (DP) | Unchanged. The port on a segment sending the best BPDU. | N/A |
| Alternate Port | A discarding port that receives a superior BPDU from another switch. Acts as a backup to the Root Port. | Root Port |
| Backup Port | A discarding port that receives a superior BPDU from another interface on the same switch (only occurs when connected via a hub). Acts as a backup to a Designated Port. | Designated Port |
graph TD
Root[Root Bridge SW1] -->|DP| SW2
Root -->|DP| SW3
SW2 -->|DP| SW4[SW4: Root Port via SW2 due to lower Bridge ID]
SW3 -->|DP| Hub
Hub -->|Shared Link| SW4
SW2 -->|DP| Hub
Hub -->|Backup Port| SW2
SW4 -->|Alternate Port| Hub
Figure: Visualizing Alternate vs. Backup ports. SW2’s connection to the Hub creates a Backup Port scenario.
Built-in Classic STP Features in RSTP
Three optional Classic STP features are built into RSTP by default and do not require manual configuration:
- PortFast $\rightarrow$ Edge Port: Moves directly to Forwarding without negotiation.
- UplinkFast $\rightarrow$ Alternate Port: Allows immediate transition to Forwarding if the Root Port fails.
- BackboneFast $\rightarrow$ Built into BPDU handling: Allows rapid expiration of the Max Age timer if inferior BPDUs are received, speeding up convergence after an indirect link failure.
Things to note: You do not need to know how to configure UplinkFast or BackboneFast for the CCNA, but you must know they are inherently active in RSTP.
RSTP BPDU Differences
You do not need to memorize the entire BPDU structure, but you must know these key differences for the exam:
- Protocol Version:
2(Classic STP is0). - BPDU Type:
2. - Flags Field: Uses all 8 bits for the negotiation handshake (Classic STP only used the 1st and 8th bits).
- Transmission: Generated by all switches, not just the Root Bridge.
RSTP Link Types
RSTP distinguishes between three link types to determine how to handle port state transitions.
| Link Type | Connected Device | Duplex Mode | Configuration Command |
|---|---|---|---|
| Edge | End Host (PC, Server, Printer) | N/A | spanning-tree portfast |
| Point-to-Point | Another Switch | Full-Duplex | spanning-tree link-type point-to-point (Auto-detected) |
| Shared | Hub | Half-Duplex | spanning-tree link-type shared (Auto-detected) |
Common Misconception: To configure an RSTP Edge port, you use the spanning-tree portfast command. There is no spanning-tree link-type edge command.
CLI Commands & Configuration
! Set the spanning tree mode to Rapid PVST+ (Default on modern switches)
Switch(config)# spanning-tree mode rapid-pvst
! Verify STP mode, port roles, and states
Switch# show spanning-tree
! Configure an interface as an Edge port (PortFast)
Switch(config)# interface GigabitEthernet0/1
Switch(config-if)# spanning-tree portfast
! Explicitly configure link type (usually auto-detected, but good to know)
Switch(config-if)# spanning-tree link-type point-to-point
Switch(config-if)# spanning-tree link-type shared
Things to note: RSTP is backward compatible with Classic STP (802.1D). If an RSTP-enabled switch connects to a Classic STP switch, the specific interface connecting to the older switch will automatically fall back to Classic STP mode (using 802.1D timers and state transitions), while the rest of the network remains in RSTP.
Exam Insights & Common Pitfalls
- Root Bridge Election: Unchanged from Classic STP (Lowest Priority, then Lowest MAC Address).
- Hub Scenarios: Hubs do not participate in STP and add no cost to BPDUs. They create a single collision domain, which is the only scenario where a Backup Port or Shared link type exists. Hubs are obsolete, but this concept is tested.
- Boson ExSim Tip: If a question asks which feature “reduces convergence time by immediately placing edge ports into a forwarding state,” the answer is PortFast. Root Guard, BPDU Guard, and Loop Guard are security/stability features, not convergence accelerators.
Command Summary
spanning-tree mode rapid-pvst ! Enable Rapid PVST+ (Default)
show spanning-tree ! View STP status, roles, and states
spanning-tree portfast ! Enable PortFast (configures Edge port)
spanning-tree link-type point-to-point ! Manually set link type to P2P
spanning-tree link-type shared ! Manually set link type to Shared