Hands-On Lab: Assigning Spanning Tree Priority to Multiple VLANs Simultaneously

This hands-on lab configures Spanning Tree bridge priority across several VLANs in a single command using a VLAN range, rather than repeating the configuration individually for each VLAN, and verifies the priority was correctly applied to every VLAN in the range.

STP VLAN RangeBulk Priority ConfigurationPVST+ Per-VLAN Instances

~3 دقیقه مطالعه · آخرین به‌روزرسانی ۳۱ شهریور ۱۴۰۵

Lab Objective

Configure a single switch as the root bridge for a range of VLANs using one command that applies to all of them simultaneously, rather than issuing a separate priority command for each individual VLAN, and verify the priority applied correctly to every VLAN in the range.

Lab Purpose

Cisco's default Spanning Tree implementation, PVST+, runs a completely separate Spanning Tree instance for every VLAN, each with its own independent root bridge election. On a switch supporting dozens of VLANs, configuring priority one VLAN at a time is tedious — the VLAN range syntax solves this directly.

Lab Topology

Switch1 (intended root for VLANs 10-50)

VLANs 10, 20, 30, 40, and 50 already exist
on the switch and are carried on its trunk links

Task 1: Verify Current Priority Across the VLAN Range

Check the current default priority for VLANs 10, 20, 30, 40, and 50 individually.

Task 2: Configure Priority for All Five VLANs in One Command

Using a single command with a VLAN range, set the priority for VLANs 10 through 50 to 4096.

Task 3: Verify the Priority Applied to Every VLAN in the Range

Check each VLAN individually and confirm all five now show the new priority.

Task 4: Confirm Root Bridge Status Per VLAN

Confirm the switch is recognized as root for each of the five VLANs independently.

Solution and Verification

Switch1# show spanning-tree vlan 10 | include Priority
Bridge ID  Priority    32768

Switch1# show spanning-tree vlan 50 | include Priority
Bridge ID  Priority    32768
-- Every VLAN currently sits at the default,
-- and would each need its own individual
-- command without using a range

Switch1(config)# spanning-tree vlan 10,20,30,40,50 priority 4096

-- A hyphenated range also works identically:
-- spanning-tree vlan 10-50 priority 4096
-- (matches only VLANs that actually exist
--  within that numeric range)

Switch1# show spanning-tree vlan 10 | include Priority
Bridge ID  Priority    4096

Switch1# show spanning-tree vlan 20 | include Priority
Bridge ID  Priority    4096

Switch1# show spanning-tree vlan 50 | include Priority
Bridge ID  Priority    4096
-- All five VLANs updated from a single command

Switch1# show spanning-tree vlan 30 | include Root
Root ID    Priority    4096
           This bridge is the root

Switch1# show spanning-tree vlan 40 | include Root
Root ID    Priority    4096
           This bridge is the root
-- Confirmed root for each VLAN independently,
-- since PVST+ maintains a completely separate
-- election and topology per VLAN

Key Takeaway

Because PVST+ runs an entirely independent Spanning Tree instance per VLAN, changing priority for one VLAN never affects any other — the VLAN range syntax is purely a configuration-time convenience for applying the identical change across many instances at once, not a sign that those VLANs somehow share a single underlying tree.

نوشته و پژوهش‌شده توسط دکتر شاهین صیامی

مقالات مرتبط

Hands-On Lab: Final Comprehensive CCNP Troubleshooting Challenge (BGP, DMVPN, and QoS Integration)

This hands-on lab presents a complex multi-layer failure across an integrated BGP-over-DMVPN topology combined with QoS marking, requiring systematic diagnosis of a route reflector misconfiguration, an NHRP registration failure, and an incorrectly applied QoS policy simultaneously affecting the same network.

ادامه

Hands-On Lab: Configuring BGP over DMVPN

This hands-on lab runs iBGP as the routing protocol across the same DMVPN hub-and-spoke topology used in the two previous labs, configuring the hub as a route reflector so spokes learn each other's routes without a full iBGP mesh, combining two previously separate concepts into one integrated design.

ادامه

Hands-On Lab: Configuring OSPF over DMVPN

This hands-on lab runs OSPF as the dynamic routing protocol across the same DMVPN hub-and-spoke topology, configuring the tunnel interface as an OSPF point-to-multipoint network type to correctly handle the hub-and-spoke adjacency pattern without requiring the broadcast network type's DR/BDR election.

ادامه

Hands-On Lab: Configuring EIGRP over DMVPN

This hands-on lab runs EIGRP as the dynamic routing protocol across the DMVPN hub-and-spoke topology built in earlier labs, verifying neighbor relationships form correctly across the multipoint tunnel and routes propagate without requiring per-spoke static configuration on the hub.

ادامه

Hands-On Lab: Configuring HSRP MD5 Authentication

This hands-on lab configures MD5 authentication on an HSRP group, verifying two routers with matching authentication strings form a normal active/standby relationship while a router with a mismatched string is excluded from the group entirely.

ادامه

Hands-On Lab: Configuring Cisco Umbrella-Style DNS Security via DNS Forwarding Redirection

This hands-on lab configures a router to redirect all client DNS queries toward a security-focused DNS resolver using DNS forwarding interception, approximating cloud-delivered DNS security enforcement without requiring per-client configuration changes.

ادامه