Hot Downloads

Welcome, Guest
Username: Password: Remember me

TOPIC: Spanning Tree Question

Spanning Tree Question 7 years 9 months ago #34937

  • JamieP
  • JamieP's Avatar
  • Offline
  • Frequent Member
  • Posts: 60
  • Karma: 0
Hi, this is probably a really simple question, but im not quite sure of the answer...

we have an old old switch hanging off our cores, and it is the spanning-tree root for one of our vlan's as the priority has never been set for this vlan on the core switches.

Obviously i need to rectify this, but what will be the impact of lowering the priority on the cores, will the vlan be unavaliable for 30seconds whilst spanning tree reconverges? (as when you connect a new device it does the 15 seconds listening, 15 seconds learning) or will it move over seemlessly?
Jamie Parks
Network Engineer, UK
The administrator has disabled public write access.

Re: Spanning Tree Question 7 years 9 months ago #34941

  • skepticals
  • skepticals's Avatar
  • Offline
  • Expert Member
  • Posts: 783
  • Karma: 0
Yes, there will be a convergence time while the tree is chopped down and rebuilt. Are you using 802.1D? Should be about 20 seconds.
The administrator has disabled public write access.

Re: Spanning Tree Question 7 years 9 months ago #34960

If it's 802,1D then down time can be up to 50 secs as Spanning Tree reconverges. But instead of lowering the cores and taking them down, why not raise the priority of the switch that you want to "remove"?

switch(config)#spanning-tree vlan x priority 61440

The priority values you can use start at 0 (zero) and go up to 61440 in increments of 4096, so 0, 4096, 8192, 12238, etc, with the default 32768 being the mid point.). Low numbers are the winners in Spanning-Tree elections / convergence situations so setting a switch to prioroty 61440 means it will never win the Spanning-Tree Root Bridge election, but the election / reconvergence will still happen. Altering priorities gives you a predictable, if slow, result.

BUT, whilst you are scheduling down time, why not convert ALL your switches to Rapid Spanning Tree (RSTP, IEEE 802.1W), and add in some extra redundant links and configure an Etherchannel.
To "switch on" Rapid Spaning-Tree, the command is:

switch(config)#spanning-tree mode rapid-pvst

This command affects all VLAN's and it's *MUCH* better. With RSTP running on all switches, convergence at layer two on a small-ish segment is almost instantaneous. BUT, if a single switch is left to run ordinary Spanning-Tree, full convergence takes up to 50 seconds, so make sure you change them ALL to RSTP.

It's *extremely* rare for me to come across a network running ordinary 802.1D Spanning-Tree because of the slow convergence time, and at the Core Layer, none of my networks rely on Layer 2 convergence as there are routers at the core, they are mostly Layer 3 switches (as well as the aforementioned routers) so we use EIGRP and / or OSPF for faster convergence across all devices at the core.
The administrator has disabled public write access.
Time to create page: 0.101 seconds


Cisco Routers

  • SSL WebVPN
  • Securing Routers
  • Policy Based Routing
  • Router on-a-Stick

VPN Security

  • Understand DMVPN
  • GRE/IPSec Configuration
  • Site-to-Site IPSec VPN
  • IPSec Modes

Cisco Help

  • VPN Client Windows 8
  • VPN Client Windows 7
  • CCP Display Problem
  • Cisco Support App.

Windows 2012

  • New Features
  • Licensing
  • Hyper-V / VDI
  • Install Hyper-V


  • File Permissions
  • Webmin
  • Groups - Users
  • Samba Setup