Switch from pvst to rapid-pvst

[marcinwojcik]

Hi

There are 26 switches running pvst in our network. I'd like to switch them to rapid-pvst. Is there a 'proper' way of doing that? I assume I start from the stack which acts as the root and then just switch one ofter another to rapid-pvst?

I have noticed that there is a spanning-tree portfast trunk set on some trunk connections between switches - according to that what I know it is a 'bad' practice. Do you agree that I shall remove it before I start changing the config from pvst to rapid-pvst?

Please advise.

Thanks.

Marcin.

[Dennis Mink · Accepted solution]

I recently change spanning tree from pvst to rapid-pvst for a customer. And I started with the core first and worked my way to the access switches. (might be a good idea to hard set the bridge priority is that isn't already done)

RSTP natively supports most of the PVST features, so you can have a combination of both within your spanning tree domain.

Portfast on a TRUNK is a no no, trunks are generally connected between switches, or at least should take part in spanning tree. i.e. a trunk should go through the different port states (listening, learning, forwarding) contrary to an access port. By all means remove it if you find it on a trunk. ONe of the few cases where you could get away with using it is, is possibly when the trunk port connects to a VMWARE server that tags multiple vlans

here is a docco on migrating from PVST to Rapid PVST

http://www.cisco.com/en/US/products/hw/switches/ps708/products_configuration_example09186a00807b0670.shtml

[marcinwojcik]

Thanks for your help.