Backbone Fast is used to recover from an indirect link failure. What does that mean? Let me show you an example of an indirect link failure and how spanning tree deals with it:
Take a look at the picture above. SW1 is the root bridge, and the Et0/3 interface on SW3 has been blocked. Suddenly, the link between SW1 and SW2 fails. From SW3’s perspective, this is an indirect link failure.
This is what will happen:
- SW2 will immediately detect this link failure since it’s directly connected. Since it doesn’t receive any BPDUs from the root anymore, it assumes it is now the new root bridge and will send BPDUs toward SW3, claiming to be the new root.
- SW3 will receive these BPDUs from SW2, but it will realize that this new BPDU is inferior compared to the old one it has currently stored on its Et0/3 interface and will ignore this new BPDU. When a switch receives an inferior BPDU, it means that the neighbor switch has lost its connection to the root bridge.
- After 20 seconds (default timer), the max-age timer will expire for the old BPDU on the Et0/3 interface of SW3. The interface will go from blocking to the listening state and will send BPDUs towards SW2.
- SW2 will receive this BPDU from SW3 and discovers that he isn’t the root bridge. It won’t send BPDUs anymore towards SW3.
- The Et0/3 interface on SW3 will continue from the listening state (15 seconds) to the learning state (15 seconds) and end up in the forwarding state.
Connectivity is now restored, but it took 20 seconds for the max-age timer to expire, 15 seconds for the listening state, and another 15 seconds for the learning state before we go to the forwarding state. That’s a total of 50 seconds of downtime. Let’s take a look at this situation on our switches. I’m using three IOL-L2 switches (SW1, SW2 and SW3) running Cisco IOS XE 17.18.2 in PVST+ mode. SW1 has priority 4096, SW2 has priority 8192, and SW3 uses the default priority (32768). I will enable a debug:
SW2#debug spanning-tree events
Spanning Tree event debugging is on
SW3#debug spanning-tree events
Spanning Tree event debugging is on
And let’s shut down the interface to simulate an indirect link failure:
SW2(config)#interface Ethernet0/1
SW2(config-if)#shutdown
SW2 believes it is the root bridge:
SW2#show spanning-tree vlan 1
VLAN0001
Spanning tree enabled protocol ieee
Root ID Priority 8193
Address aabb.cc01.4800
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 8193 (priority 8192 sys-id-ext 1)
Address aabb.cc01.4800
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 15 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Et0/3 Desg FWD 100 128.4 P2p
And SW3 receives the BPDU from SW2, who claims to be the root bridge:
SW3#
STP: VLAN0001 heard root 8193-aabb.cc01.4800 on Et0/3
STP: VLAN0001 heard root 8193-aabb.cc01.4800 on Et0/3
STP: VLAN0001 heard root 8193-aabb.cc01.4800 on Et0/3
STP: VLAN0001 heard root 8193-aabb.cc01.4800 on Et0/3
STP: VLAN0001 heard root 8193-aabb.cc01.4800 on Et0/3
STP: VLAN0001 heard root 8193-aabb.cc01.4800 on Et0/3
STP: VLAN0001 heard root 8193-aabb.cc01.4800 on Et0/3
STP: VLAN0001 heard root 8193-aabb.cc01.4800 on Et0/3
STP: VLAN0001 heard root 8193-aabb.cc01.4800 on Et0/3
STP: VLAN0001 Et0/3 -> listening
STP: VLAN0001 heard root 8193-aabb.cc01.4800 on Et0/3
STP: VLAN0001 Topology Change rcvd on Et0/3
STP: VLAN0001 sent Topology Change Notice on Et0/2
STP: VLAN0001 Et0/3 -> learning
STP[1]: Generating TC trap for port Ethernet0/3
STP: VLAN0001 sent Topology Change Notice on Et0/2
STP: VLAN0001 Et0/3 -> forwarding
After the max age timer expires (20 seconds) for the old BPDU from SW2, the Et0/3 interface on SW3 will go to the listening and learning state and end up in the forwarding state. A bit later, we see this:
SW2#
STP: VLAN0001 heard root 4097-aabb.cc01.4700 on Et0/3
supersedes 8193-aabb.cc01.4800
STP: VLAN0001 new root is 4097, aabb.cc01.4700 on port Et0/3, cost 200
STP: VLAN0001 sent Topology Change Notice on Et0/3
The identity crisis of SW2 comes to an end. It now hears the BPDUs from the root bridge through SW3 and understands that it’s not the root bridge.
Without backbone fast, spanning tree will discard the inferior BPDUs that SW3 receives on its Et0/3 interface, and it will have to wait till the max age timer expires (20 seconds).
If we enable backbone fast, it will skip the max age timer, so we can save 20 seconds. Let’s restore that interface:
SW2(config)#interface Ethernet0/1
SW2(config-if)#no shutdown
And we’ll enable backbone fast:
SW1(config)#spanning-tree backbonefast
SW2(config)#spanning-tree backbonefast
SW3(config)#spanning-tree backbonefast
This is a global command. To see this in action, we’ll enable some more debugging:
Hi Rene,
In my understanding , ND port can only receive BPDU . With Backbone fast enabled,
How does switch C send RLQ on both the Root port and ND port ? RLQ is not a BPDU frame ?
Please explain RLQ.
Thanks,
Srini
Hi Srini,
The RLQ is not send on the ND port, only the root port. The last message is a bit cryptic, it means that SwitchC received a reply on its root port that it sent because it received an inferior BPDU on its ND port.
Rene
Hi Rene,
Thanks for explainig RLQ in RSTP.
Srini.
Uplinkfast and Backbone fast are they used together in conjunction?
In the past yes, these were used for PVST.
RPVST has similar built-in mechanisms so you don’t have to enable these nowadays.