cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
741
Views
0
Helpful
5
Replies

RSTP confusion

Hi everyone.

I have some questions about RSTP. Cisco says that UplinkFast and BAckboneFast are natively included into RSTP thus ARE NOT SUPPORTED IN IT. But what a hell does this mean? What will RSTP switch do if it lose root port??? Recalculate STP with proposal-agreement sync? Or will launch something similar to UplinkFast? It is a little bit confusing. Please help, because I dont get it.

1 Accepted Solution

Accepted Solutions

Hello Volodymyr,

Yes, you are correct. RSTP internally contains mechanisms that make up the core of UplinkFast and BackboneFast extensions. It may not do things in exactly the same way but it achieves the same goals.

You are also correct in stating that with RSTP, it is pointless to turn on the UplinkFast and BackboneFast. In fact, you can't even do that: if you have RSTP activated then the commands spanning-tree uplinkfast and spanning-tree backbonefast may be present in the configuration but will be ignored and will have no effect.

Best regards,

Peter

View solution in original post

5 Replies 5

sukanyachavan
Level 1
Level 1

Hi,

If RSTP running switch loses its root port , spanning tree will converge . There won't be any recalculation.

RSTP has backbonefast and uplinkfast inbuilt in it. As compared to STP, RSTP doesnt have listening state so it will directly transition from blocking to learning . Hence speeding up the convergence by 20 seconds

HTH,

Sukanya

PS: Please rate helpful posts...

Peter Paluch
Cisco Employee
Cisco Employee

Hi Volodymyr,

The Cisco UplinkFast and BackboneFast are optimizations to the basic STP algorithm. When RSTP was developed and standardized, the main algorithms on which UplinkFast and BackboneFast were based were adapted and incorporated into RSTP design. In other words, RSTP natively contains algorithms that were inspired and partially retaken from UplinkFast and BackboneFast extensions and that provide the same function as Uplink/BackboneFast without actually needing to activate them explicitly.

So with RSTP, you have UplinkFast-alike and BackboneFast-alike functionality immediately as soon as you activate RSTP, and it makes no sense to activate these mechanisms explicitly. These commands would have no effect on RSTP operation, anyway.

Does this make it more clear? Please welcome to ask further!

Best regards,

Peter

Yeap))) I have read Cisco materials more carefully. The answer is out there. There is no Uplink and Backbone FAst features in RSTP, but there are a little bit similar features. So as I can conclude Uplink and Backbone features are included in Rapid-PVST but it is pointless to turn them on since RSTP algorithm is naturally better by its calculation. Right?

Hello Volodymyr,

Yes, you are correct. RSTP internally contains mechanisms that make up the core of UplinkFast and BackboneFast extensions. It may not do things in exactly the same way but it achieves the same goals.

You are also correct in stating that with RSTP, it is pointless to turn on the UplinkFast and BackboneFast. In fact, you can't even do that: if you have RSTP activated then the commands spanning-tree uplinkfast and spanning-tree backbonefast may be present in the configuration but will be ignored and will have no effect.

Best regards,

Peter

Thanks)))

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: