We have some Cisco switches running PVST. I need to convert them to use extended system-id so I can use high numbered vlans.
When you enable or disable the extended system ID, the bridge IDs of all active STP instances are updated, which might change the spanning tree topology.
If I start at the PVST root and change my primary root, then secondary root, and then all other switches, are there any risks of loops or nasty downtime?
If anything it may just need to reconverge. About 45 seconds of interruption IIRC. If you can, while you are changing it on all the switches anyway, use rapid PVST. That will allow for faster convergence.
Be aware - when you change your root, you'll cause a topology change, at which time all your STP will pause and recalculate. While 45 seconds doesn't sound like very long - it's an eternity to the systems on your network, some of which think .15 seconds (150ms) is a long time.
I caused a topology change accidentally on my "storage" vlan (NAS). SQL servers lost their connection to NAS attached hard drives - and all crashed, which caused front end systems to crash. It was a poor design, that was like that when I got there, and I stepped on a mine in the mine field - so I didn't get fired. But the server team had to spend the rest of the day bringing servers back up. Then they had to do it again, when we fixed spanning tree and it recalculated again.
Make sure to CYA - advise management, in writing, that this is highly risky to the uptime of the network, and make sure you get a change window, with an approved change control (with an OK from the Server Team management). All of course depending on your network and environment.
