> ## Content Index
> Fetch the complete content index at: https://www.pinglabz.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Configuring Rapid PVST+ on Cisco Catalyst Switches
- URL: https://www.pinglabz.com/configure-rapid-pvst-cisco/
- Published: 2026-03-27T05:16:12.000Z
- Updated: 2026-07-04T23:02:00.000Z
- Description: Rapid PVST+ (RSTP) replaces STP with a faster mechanism that converges in seconds instead of minutes. This article covers configuration, proposal/agreement handshakes, edge port usage, and migration from legacy PVST+.
- Author: Jaime
- Tags: STP, #Import 2026-08-01 19:54

## Why Rapid PVST+?

Standard STP converges in 30-50 seconds after a topology change (listening phase 15 sec + learning phase 15 sec + transition). Modern networks cannot tolerate 50-second outages. Rapid PVST+ (based on IEEE 802.1w) converges in **under 5 seconds** for most topology changes, and under 1 second for edge port transitions (PortFast).

(This article is part of the PingLabz STP series - the [full spanning-tree guide](https://www.pinglabz.com/spanning-tree-protocol/) maps the whole cluster in reading order.)

Rapid PVST+ is the de facto standard for campus networks and should be enabled on all Catalyst switches running IOS XE 17.x.

## Core Improvements: Proposal/Agreement Mechanism

The key to RSTP's speed is the **proposal/agreement handshake**. Unlike STP, which uses passive listening, RSTP switches actively negotiate port roles:

1. **Proposal:** Designated port proposes to accept the neighboring root information
2. **Agreement:** The neighbor accepts and immediately transitions the port to forwarding (no listening/learning delay)

This handshake happens on point-to-point links without timers, enabling sub-second convergence.

**How It Works:**

```
Switch A (Root)              Switch B (non-root)
    │                              │
    │ BPDU with Proposal bit=1    │
    ├─────────────────────────────>
    │                    Process & agree
    │ BPDU with Agreement bit=1   │
    │<─────────────────────────────┤
    │
   (Port B transitions to Forwarding immediately)

```

This replaces the old listening → learning → forwarding sequence.

## Enabling Rapid PVST+

The configuration is simple - one global command changes the STP mode:

```
SW1(config)# spanning-tree mode rapid-pvst
SW1(config)# end

```

Verify immediately:

```
SW1# show spanning-tree summary

Switch is in rapid-pvst+ mode
Root bridge for VLAN0010

Rapid PVST Instances
VLAN IDs of instances running Rapid PVST
 1, 10, 20, 30, 99

```

The status line **"Switch is in rapid-pvst+ mode"** confirms the change.

Apply the command to all switches in the network:

```
SW1(config)# spanning-tree mode rapid-pvst
SW2(config)# spanning-tree mode rapid-pvst
SW3(config)# spanning-tree mode rapid-pvst
SW4(config)# spanning-tree mode rapid-pvst

```

No downtime occurs during the mode change - existing topology continues, and RSTP mechanics take effect immediately.

## Link Type Configuration

Rapid PVST+ automatically detects link types, but explicit configuration ensures predictable behavior:

**Point-to-Point Links (Uplinks, Trunk Links)**

```
SW1(config)# interface GigabitEthernet 1/0/1
SW1(config-if)# spanning-tree link-type point-to-point
SW1(config-if)# exit

```

Point-to-point links support proposal/agreement, enabling rapid transitions. Uplinks between switches should always be point-to-point.

**Shared Links (Hub, Switch with Hosts)**

```
SW1(config)# interface GigabitEthernet 1/0/48
SW1(config-if)# spanning-tree link-type shared
SW1(config-if)# exit

```

Shared links (rare in modern networks) do not support proposal/agreement and fall back to STP timers.

**Auto-Detect (Default)**

```
SW1(config)# interface GigabitEthernet 1/0/1
SW1(config-if)# spanning-tree link-type auto
SW1(config-if)# exit

```

Catalyst switches automatically detect duplex and enable point-to-point for full duplex, shared for half duplex. **This is sufficient for most deployments** and is the default.

## Edge Ports in Rapid PVST+

Edge ports are access ports connected to end devices (hosts, printers, IP phones). They have **no loop risk** because they cannot form links with other switches.

```
SW1(config)# interface range GigabitEthernet 1/0/1-24
SW1(config-if-range)# spanning-tree portfast
SW1(config-if-range)# exit

```

Edge ports configured with `spanning-tree portfast`:

- Transition to forwarding immediately without listening/learning
- Skip proposal/agreement handshake (not needed - no loop risk)
- Converge in **milliseconds** instead of seconds

**Verify Edge Port (Called "Edge" in Output)**

```
SW1# show spanning-tree detail interface GigabitEthernet 1/0/1

Role: Designated
State: Forwarding
Priority:   128
Cost:       4
Portfast:   Enabled
Edge Port:  Yes
Link type:  Point-to-point

```

The **"Edge Port: Yes"** line confirms PortFast is active on this interface.

## Rapid PVST+ Configuration on Lab Topology

Lab setup: Catalyst 9300, VLANs 10 (Users), 20 (Servers), 30 (Management), 99 (Native).

**All Switches: Enable Rapid PVST+**

```
SW1(config)# spanning-tree mode rapid-pvst
SW1(config)# spanning-tree vlan 10 root primary
SW1(config)# spanning-tree vlan 20 root primary
SW1(config)# spanning-tree vlan 30 root primary
SW1(config)# end

```

```
SW2(config)# spanning-tree mode rapid-pvst
SW2(config)# spanning-tree vlan 10 root secondary
SW2(config)# spanning-tree vlan 20 root secondary
SW2(config)# spanning-tree vlan 30 root secondary
SW2(config)# end

```

**Distribution Switches (SW1, SW2): Configure Uplinks as Point-to-Point**

```
SW1(config)# interface GigabitEthernet 1/0/1
SW1(config-if)# description Link to SW3
SW1(config-if)# spanning-tree link-type point-to-point
SW1(config-if)# exit

SW1(config)# interface GigabitEthernet 1/0/2
SW1(config-if)# description Link to SW4
SW1(config-if)# spanning-tree link-type point-to-point
SW1(config-if)# exit

```

**Access Switches (SW3, SW4): Configure All Access Ports as Edge**

```
SW3(config)# interface range GigabitEthernet 1/0/1-24
SW3(config-if-range)# spanning-tree portfast
SW3(config-if-range)# exit

SW3(config)# interface range GigabitEthernet 1/0/25-28
SW3(config-if-range)# description Uplinks to Distribution
SW3(config-if-range)# spanning-tree link-type point-to-point
SW3(config-if-range)# no spanning-tree portfast
SW3(config-if-range)# exit

```

Access port uplinks (Gi1/0/25-28) should NOT have PortFast - they need proposal/agreement for rapid convergence in the event of root bridge failure.

## Verification Commands

**Verify RSTP Mode and Summary**

```
SW1# show spanning-tree summary

Switch is in rapid-pvst+ mode
Root bridge for VLAN0010, VLAN0020, VLAN0030

Rapid PVST Instances
VLAN IDs of instances running Rapid PVST
 1, 10, 20, 30, 99

```

**Check Specific VLAN Details**

```
SW1# show spanning-tree vlan 10

VLAN0010
  Spanning tree enabled protocol rstp
  Root ID    Priority    4096
             MAC-address  0022.55a6.5801
  Bridge ID  Priority    4096 (priority 4096 sys-id-ext 0)
             MAC-address  0022.55a6.5801

Interface        Role Sts Cost      Prio.Nbr Type
---------------- ---- --- --------- -------- --------------------
Gi1/0/1          Desg FWD 4         128.1    P2p
Gi1/0/2          Desg FWD 4         128.2    P2p

```

The **"Type: P2p"** (point-to-point) confirms link-type configuration.

**Verify PortFast on Access Ports**

```
SW3# show spanning-tree interface GigabitEthernet 1/0/1 detail

Role:       Designated
State:      Forwarding
Priority:   128
Cost:       19
Portfast:   Enabled
Edge Port:  Yes
Link type:  Point-to-point
Portfast incurred cost: 0

```

**Verify on Non-Root Switch**

```
SW3# show spanning-tree vlan 10

VLAN0010
  Spanning tree enabled protocol rstp
  Root ID    Priority    4096
             MAC-address  0022.55a6.5801
  Bridge ID  Priority   32768 (priority 32768 sys-id-ext 0)
             MAC-address  0055.8844.2203

Interface        Role Sts Cost      Prio.Nbr Type
---------------- ---- --- --------- -------- --------------------
Gi1/0/25         Root FWD 4         128.25   P2p
Gi1/0/26         Altn BLK 4         128.26   P2p
Gi1/0/1          Desg FWD 19        128.1    Edge

```

Note:

- **Gi1/0/25:** Root port (forwards toward root)
- **Gi1/0/26:** Alternate port (blocked, backup to root)
- **Gi1/0/1:** Designated edge port (PortFast, immediate forwarding)

**View Rapid PVST+ Timer Information**

```
SW1# show spanning-tree summary hello max-age forward-delay

Switch is in rapid-pvst+ mode

Hello Time Forward Delay Max Age
---- ----
2 sec  15 sec  20 sec

```

Rapid PVST+ uses the same timers as PVST+ but applies them differently - timers govern BPDU generation, not state transitions.

## Migration from PVST+ to Rapid PVST+

If your network currently runs PVST+ (the non-rapid variant), migration is straightforward and non-disruptive:

**Step 1: Verify Current Mode**

```
SW1# show spanning-tree summary

Switch is in pvst+ mode  ! Old mode

```

**Step 2: Enable Rapid PVST+ on All Switches**

Perform this on one switch at a time, waiting 30 seconds between switches:

```
SW1(config)# spanning-tree mode rapid-pvst
SW1(config)# end
! Wait 30 seconds for convergence
show spanning-tree summary

SW2(config)# spanning-tree mode rapid-pvst
SW2(config)# end
! Wait 30 seconds

SW3(config)# spanning-tree mode rapid-pvst
SW3(config)# end
! Wait 30 seconds

SW4(config)# spanning-tree mode rapid-pvst
SW4(config)# end

```

**Step 3: Verify Convergence**

```
SW1# show spanning-tree summary

Switch is in rapid-pvst+ mode

Rapid PVST Instances
VLAN IDs of instances running Rapid PVST
 1, 10, 20, 30, 99

```

All VLANs now run RSTP. No reboot required, and spanning tree topology does not change.

**Step 4: Add PortFast and Link-Type Configuration**

After RSTP is enabled globally, add edge port and link-type configuration to access and uplink ports:

```
config t
interface range Gi1/0/1-24
spanning-tree portfast
exit

interface range Gi1/0/25-28
spanning-tree link-type point-to-point
no spanning-tree portfast
exit
end

```

This provides optimal convergence on edge ports (milliseconds) and point-to-point uplinks (sub-second).

## Rapid PVST+ vs. MSTP

Both RSTP and MSTP (Multiple Spanning Tree) run the same proposal/agreement mechanism. The difference:

- **Rapid PVST+:** One STP instance per VLAN (100 instances for 100 VLANs)
- **MSTP:** Multiple VLANs mapped to fewer instances (e.g., 100 VLANs → 4 instances)

For most campus networks, Rapid PVST+ is simpler and adequate. MSTP (Article 14) is used when you have 50+ VLANs and want to reduce CPU overhead.

## Convergence Behavior: Before and After

**Standard PVST+ Topology Change:**

```
Link Fails (t=0s)
    ↓
Detection (t=1s)
    ↓
Listening Phase (t=1-16s)
    ↓
Learning Phase (t=16-31s)
    ↓
Port Forwarding (t=31s)
Total: 30 seconds

```

**Rapid PVST+ Topology Change:**

```
Link Fails (t=0s)
    ↓
Detection (t=1s)
    ↓
Proposal/Agreement (t=1-2s)
    ↓
Port Forwarding (t=2s)
Total: 2 seconds

```

**Edge Port (PortFast):**

```
Host Connects (t=0s)
    ↓
Detection (t=<100ms)
    ↓
Forwarding (t=<100ms)
Total: <1 second

```

This dramatic improvement is the primary reason to deploy RSTP.

## Troubleshooting Rapid PVST+

### Symptom: Ports Not Transitioning to Forwarding

**Cause:** Proposal/agreement mechanism blocked due to unidirectional link or misconfigured link-type.

**Fix:** Check link-type and duplex:

```
SW1# show spanning-tree interface Gi1/0/1 detail

Link type: Point-to-point
Full duplex: Yes

```

If link-type is "Shared," change to point-to-point manually or check duplex status.

### Symptom: Edge Ports Still Have 30-Second Delay

**Cause:** PortFast not enabled on access ports.

**Fix:**

```
config t
interface range Gi1/0/1-24
spanning-tree portfast
end

```

Verify:

```
SW1# show spanning-tree interface Gi1/0/1 detail

Portfast: Enabled
Edge Port: Yes

```

### Symptom: Can't Determine If Switch Is Running RSTP or Legacy STP

**Cause:** Viewing generic spanning-tree output that doesn't show protocol name clearly.

**Fix:** Always use `show spanning-tree summary`:

```
SW1# show spanning-tree summary

Switch is in rapid-pvst+ mode  ! CLEAR indication

```

## What's Next

Rapid PVST+ provides fast convergence, but PortFast configuration on access ports is critical to realize sub-second edge port transitions. Article 10 covers "PortFast Configuration on Cisco Switches: When and How to Use It," including PortFast on trunks, interaction with DHCP and 802.1X, and PortFast risks if misconfigured.

## Related STP Articles

- [802.1D vs PVST+ vs Rapid PVST+ vs MST: Comparing STP Variants](https://www.pinglabz.com/stp-variants-compared-pvst-rstp-mst/)
- [STP Port States: Blocking, Listening, Learning, Forwarding, and Disabled](https://www.pinglabz.com/stp-port-states-explained/)
- [PortFast Configuration on Cisco Switches: When and How to Use It](https://www.pinglabz.com/portfast-configuration-cisco-switches/)
- [BPDU Guard Configuration: Protecting Your STP Topology](https://www.pinglabz.com/bpdu-guard-configuration-cisco/)