Imagine that I have ApplicationCritical devices on SwitchA, Vlan 300. SwitchA is connected to Layer3Switch via trunk.
Then NonCriticalApplication devices are connected to SwitchB, Vlan 300. SwitchB is connected to Layer3Switch via trunk.
Devices on SwitchA and SwitchB have no dependency other than sharing same VLAN.
Imagine I need to reboot SwtichB for maintenance.
Do you see how normal STP recalculations generated by the fact I am power cycling SwitchB could affect ApplicationCritical devices functionality on SwitchA? I do not think that is expected, but I am just checking.
Do you have a diagram?
If you have just a ONE Layer3Switch then it shouldn't cause any problem at all as there are no blocking ports. The only thing it will create is a TCN situation where all L2 tables will be put to fast aging. It won't cause an outage tho.
If you have dual Layer3Switches then hopefully you have one of these as the root bridge and then again - nothing will affect SwtichA (critical)
I guess that Layer3Switch is connecting via switchports to A and B, else A and B are in different bridged domains...
Are you running Rapid-PVST or MST ? If so, you could experience a sync if B is the root.
Sorry, forgot to mention it is rapid-pvst.
Yes, SwitchA-trunk vlan300-->Layer3Switch.
I checked and in this case SwitchA (Critical Applications) is the root for vlan 300.
So if I reboot SwitchA, SwitchB will remain as the root.
If you reboot switch B, switch A will remain the root;-) This should not introduce any change on the link between switch A and the layer3switch, so you are safe. Sure, you'll get a topology change (which will result in a short flooding phase), but this will have no impact on the applications.