FIGURE-1: UplinkFast usage scenario
Warning: When uplink fast is enabled, it is enabled for switch as a whole, therefore, for all VLANs. Since it keeps tracks of possible path to root bridge, it is not allowed on Root Bridge. UplinkFast also ensures that the switch never becomes a Root Bridge (RB). UplinkFast ensures by making the priority to be raised to 49,152 and port cost is incremented by 3000, making the switch un-desirable to be the root bridge.
Configuration
Step-1: configure terminal
Step-2: spanning-tree uplinkfast
Step-3: end
BackboneFast
BackboneFast is used to speed convergence when indirect link failure occurs in the STP topology. When BackboneFast is enabled, the switch actively monitors alternative path to Root Bridge. BackboneFast detects indirect link failures when it receives an inferior BPDU from a Designated Bridge on Root Port (RP) or blocked port. A Designated Bridge generates an inferior BPDU when it has lost connectivity to Root Bridge and it announces itself as the New Root. This inferior BPDU is a sign of indirect link failure.
In normal STP behavior, switch receiving the (inferior) BPDU must wait the STP Max Age Timer to expire before responding. In case of BackboneFast, the switch proactively determines other alternative paths to Root Bridge. This proactive behavior is due to Root Link Query (RLQ) protocol.
Configuration
BackboneFast must be enabled on entire STP domain on every switch.
Step-1: configure terminal
Step-2: spanning-tree backbonefast
This brings us to the end of this article in which we learned two very essential STP optimization techniques that are used to speed up convergence due to direct and indirect link failure. The configuration of both uplinkfast and backbone is very simple but you must understand the indepth workings of boths of them.