High Rate of STP Topology Changes

[Eclipse]

I get "High Rate of STP Topology Changes" on all of my Meraki Core switchports that are connected to other non-Meraki switches. Should I be concerned and what would be my next steps in troubleshooting this? 

[MilesMeraki]

I'd, first of all, understand your STP topology and then work backwards from there. Do you have the Layer 2/STP topology diagramed/documented at all?

[MerakiDave]

Agreed, I'd confirm all of the physical connectivity and do some quick packet captures or work with Support to find the source(s) of the TCN BPDUs and start from there, possibly even temporarily admin-downing certain redundant/blocking links to isolate the issue.

[Misfits1138]

I'm having the same issue on my Meraki. It only has one uplink to the Cisco core switch. None of my other Meraki switches are having the same issue. I'm fairly new to Meraki, so any help is much appreciated.

[PhilipDAth]

Have you configured the root priority for the switch that should be the core of your network?

https://documentation.meraki.com/MS/Other_Topics/Switch_Settings#Setting_the_STP_Root_Bridge

Next the other switches, what are they?  If they are Cisco Enterprise switches I would configure them to use mst "spanning-tree mode mst".

If they are dumb layer 2 switches it is possible they don't even run spanning tree.

Look for links between edge/leaf switches that should be there.  You ideally want a loop free design where the downstream switches only connect to the core switch and no other switches.

[Bossnine]

Also, in addition to the above....I found in a couple of my networks I had that error on my Meraki Core switch another tech had ports configured incorrectly, mismatches, and in fixing that removed my errors.

[GIdenJoe]

Also make sure every single access port (connecting end devices) on your switches in your entire network is running in portfast/edge mode.
If you don't every time a device turns off or on you will get a TCN flood in your network causing shortened MAC address lifetimes.