STP high rate of topology changes when updating MS switches in the network

Head in the Cloud

STP high rate of topology changes when updating MS switches in the network

Hello, I always get "high rate of STP topology change" errors while updating MS switches in our networks. Most switches are uplinked with a aggregat to the distri switch. I there any idea to prevent this issue to avoid network errors on network parts which are not getting updated (staggered upgrade)?

Maybe the aggregat is not established while the switch is booting and going online?


Any good ideas?


Kind of a big deal

@redsector : Did you set root priority for the switch, I mean spanning tree priority on your root to be lower than the rest of your switches and BPDU Guard ? 

Inderdeep Singh ( Awarded by Cisco IT Blogs award 2020)

Yes, shure. The core is the boss. I mean best priority. It´s an Cisco Cat 6800, (root bridge around 8196) , all Meraki switches are Meraki standard (32768).

Kind of a big deal

Hi @redsector , is your Cisco core running MSTP?

Take a read through the below which will help you tweak your config:

Darren O'Connor |

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.
Kind of a big deal
Kind of a big deal

@redsector is it actually causing a problem?  I see this often when updating switches but there is no user issue and the error soon clears.

Kind of a big deal

Unless it is causing some other issue I wouldn't worry about this.


The error is probably correct and being caused by lots of Meraki switches rebooting due to the upgrade.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.