Set Bridge Priority for ALL switches in network?

[Mark-SPS]

Hi All,

I was wondering what everyone does regarding Bridge priority. We have our core switch set to "0", but then I saw this document that I've linked below.

https://documentation.meraki.com/MS/Port_and_VLAN_Configuration/Configuring_Spanning_Tree_on_Meraki_...

There is a section that states:

It is best practices to set a layered approach to the STP priorities in a network. For instance, if there is a clear Core <> Distribution <> Access Layer, priorities should be Core (4096), Distribution (16384), and Access (61440). At no point in a production network should you leave the any switch at its default configurations. 

It's the last line that caught mt attention. Does everyone set a bridge priority for all their switches?

Thanks Mark

[alemabrahao · Accepted solution]

For Core, you can set it to 0, but it's not a problem.

It's definitely recommended to change it in the distribution as well, but I don't see any problem in leaving it as default in the access layer.

I see these numbers more as a reference than something mandatory.

[Mark-SPS]

Thanks for the response and confirmation. The core has been set to 0 since install.

[cmr]

Coming from a 24/7 background, I always follow those guidelines as any switch that has the same priority as another can get upset when either switch is rebooted.  Although by having the core set to the highest priority, you are protecting that, you can still have disruption downstream.

I use 4k as the core, 12k down to 28k as the distribution and 36k down as the edge.  I try to separate it out as much as possible to keep things reliable.

[cmr]

When I'm replacing a core, I change it to the 'spare' 8k setting and then the new core can go back in at 4k without any other disruption.