Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

Search...

Table of Contents
CCIE Routing & Switching

 Unit 1: Preparation

 Unit 2: Switching

Static MAC Address Table Entry

Cisco Switch Virtualization

Introduction to VLANs (Virtual LAN)

How to con�gure VLANs

802.1Q Encapsulation

How to con�gure a trunk between switches

Cisco DTP (Dynamic Trunking Protocol) Negotiation

802.1Q Tunneling (Q-in-Q)

Etherchannel over 802.1Q Tunneling

How to change the Native VLAN

VTP (VLAN Trunking Protocol)

VTP Version 3

Protected Port

Private VLANs (PVLAN)

Introduction to Spanning-Tree

1 of 19 08/16/2017 03:46 AM
Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

Spanning-Tree Cost Calculation

PVST (Per VLAN Spanning Tree)

Spanning-Tree Port States

Spanning-Tree TCN (Topology Change Noti�cation)

Spanning-Tree Portfast

Spanning-Tree UplinkFast

Spanning-Tree Backbone Fast

Rapid Spanning-Tree

Rapid Spanning-Tree Con�guration

MST (Multiple Spanning-Tree)

Spanning-Tree BPDUGuard

Spanning-Tree BPDUFilter

Spanning-Tree RootGuard

Spanning-Tree LoopGuard and UDLD

FlexLinks

Introduction to Etherchannel

Layer 3 Etherchannel

Cisco IOS SPAN and RSPAN

 Unit 3: IP Routing

 Unit 4: RIP

 Unit 5: EIGRP

 Unit 6: OSPF

 Unit 7: BGP

 Unit 8: Multicast

 Unit 9: IPv6

 Unit 10: Quality of Service

 Unit 11: Security

 Unit 12: System Management

 Unit 13: Network Services

 Unit 14: MPLS

2 of 19 08/16/2017 03:46 AM
Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

You are here: Home » Cisco » CCIE Routing & Switching

Spanning-Tree UplinkFast
a d k y v

Uplinkfast is a spanning-tree feature that was created to improve the convergence time.
In this lesson we’ll take a look at how uplinkfast works. Here’s the topology that I will use
to demonstrate it:

3 of 19 08/16/2017 03:46 AM
Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

Three switches and SW1 is our root bridge. The fa0/16 interface on SW3 has been
blocked. I’m only using VLAN 1 so nothing fancy here…

If we look at SW3 we see that the fa0/16 interface has been blocked and fa0/14 is the
root port. Let’s see what happens with this topology when one of the links fails:

When the fa0/14 interface on SW3 fails we’ll have to use fa0/16 to reach the root bridge.
How long does it take for SW3 to make the transition? Let’s �nd out:

4 of 19 08/16/2017 03:46 AM
Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

SW3#debug spanning-tree events

Spanning Tree event debugging is on

SW3(config)#interface fa0/14
SW3(config-if)#shutdown

Now we’ll just wait for the magic to happen…

SW3#STP: VLAN0001 new root port Fa0/16, cost 38

SW3#STP: VLAN0001 Fa0/16 -> listening
SW3#STP: VLAN0001 Fa0/16 -> learning
SW3#STP: VLAN0001 Fa0/16 -> forwarding

BPDUs are originated from the root bridge so if we receive BPDUs on an interface the
switch knows it can reach the root bridge on this interface. We have to go through the
listening (15 seconds) and learning state (15 seconds) so it takes 30 seconds to end up in
the forwarding state.

The good thing is that spanning-tree solves the link failure automatically but it also
means that we have a downtime of 30 seconds. If you want you can tune the forward
delay timer to speed up this process down to roughly 14 seconds.

SW3(config)#interface fa0/14
SW3(config-if)#no shutdown

Let’s restore connectivity �rst.

SW3(config)#spanning-tree uplinkfast

5 of 19 08/16/2017 03:46 AM
Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

Now I’m going to enable spanning-tree uplinkfast. This is a global command, you can’t
con�gure it on the interface level.

SW3(config)#interface fa0/14
SW3(config-if)#shutdown

SW3# STP: VLAN0001 new root port Fa0/16, cost 3038

SW3# %SPANTREE_FAST-7-PORT_FWD_UPLINK: VLAN0001 FastEthernet0/16
moved to Forwarding (UplinkFast).

Here’s the big di�erence. When uplinkfast is enabled a non-designated port will go to
forwarding state immediately if the root port fails. Instead of 30 seconds downtime
connectivity is restored immediately.

UplinkFast is useful but it will cause a problem with our MAC address tables. In the
picture above I added two computers to our topology. Interface fa0/16 on SW3 is the
non-designated port and fa0/14 is the root port. Take a look at the following topology:

6 of 19 08/16/2017 03:46 AM
Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

Let me show you the MAC address tables for all switches:

SW1#show mac address-table dynamic

Mac Address Table
-------------------------------------------

Vlan Mac Address Type Ports

---- ----------- -------- -----
1 000c.2928.5c6c DYNAMIC Fa0/14
1 000c.29e2.03ba DYNAMIC Fa0/17

SW2#show mac address-table dynamic

Mac Address Table
-------------------------------------------

Vlan Mac Address Type Ports

---- ----------- -------- -----
1 000c.2928.5c6c DYNAMIC Fa0/2
1 000c.29e2.03ba DYNAMIC Fa0/14

SW3#show mac address-table dynamic

Mac Address Table
-------------------------------------------

Vlan Mac Address Type Ports

---- ----------- -------- -----
1 000c.2928.5c6c DYNAMIC Fa0/14
1 000c.29e2.03ba DYNAMIC Fa0/3

Here are the MAC addresses of the computers:

7 of 19 08/16/2017 03:46 AM
Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

H1: 000c.2928.5c6c
H2: 000c.29e2.03ba

When the link between SW1 and SW3 fails, SW3 will use the fa0/16 interface immediately.
However it will take 15 seconds for the topology change mechanism to age out the MAC
address table!

SW2#show mac address-table dynamic

Mac Address Table
-------------------------------------------

Vlan Mac Address Type Ports

---- ----------- -------- -----
1 000c.2928.5c6c DYNAMIC Fa0/2
1 000c.29e2.03ba DYNAMIC Fa0/14

Take a look again at the MAC address table for SW2. The MAC address (000c.29e2.03ba)

8 of 19 08/16/2017 03:46 AM
Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

that I highlighted belongs to H2. When SW2 receives an Ethernet Frame for H2 it will be
forwarded to SW1 and it will be dropped! (Well at least for 15 seconds until the topology
change mechanism kicks in…).

Of course we have a solution to speed this up, here’s what we will do:

Once SW3 switches over to use its non-designated port it will create a dummy multicast
frame. The source MAC address of this Ethernet Frame will be all the MAC addresses
that it has in its MAC address table. In my example above this is only the MAC address
of H2. The destination multicast address is a proprietary Cisco MAC address.

This multicast frame will be �ooded to all other switches so they can update their MAC
address tables right away.

Spanning-tree has saved the day again…anything else you need to know? What do you
think will happen if I re-enable the fa0/14 interface on SW3 again (the original root port)?

9 of 19 08/16/2017 03:46 AM
Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

SW3(config)#interface fa0/14
SW3(config-if)#no shutdown

Let’s bring the interface back up. In my lab it’s not as exciting as in the picture…

SW3# STP: VLAN0001 Fa0/14 -> listening

SW3# STP: VLAN0001 Fa0/14: root port delay timer active
SW3# STP: VLAN0001 Fa0/14 -> blocking
SW3# STP: VLAN0001 new root port Fa0/14, cost 3019
SW3# STP: VLAN0001 Fa0/16 -> blocking (uplinkfast)

You can see we don’t immediately switch back to interface fa0/14. There’s no reason to
switch back to this interface ASAP because we have a working root port. Even if we would
switch back to interface fa0/14 right away we’d still have to wait because the fa0/17
interface on SW1 will have to go through the listening and learning state (which takes 30
seconds).

10 of 19 08/16/2017 03:46 AM
Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

That’s all there is about spanning-tree uplinkfast. I hope this lesson has been useful!

« Previous Lesson
Spanning-Tree Portfast
Next Lesson
Spanning-Tree Backbone Fast »
Forum Replies

humbertoacostachida
February 16, 2015

Hi Rene, excelent post.

However, I have some doubts about this topic. I read that using RSTP we have some
improvements similar to Uplink and Backbone Fast. So, we don´t have to use this features on
RSTP. Is that correct?

This output was taken from a Cat3750: "UplinkFast is enabled but inactive in rapid-pvst mode"
Can you help me with this??

Whatever, your example is fantastic.

Zaman.rubd
May 26, 2016

Hlw Rene,

Nice explanation in right WAY, GREAT !

So , if we use Uplinkfast then no downtime occure ?? So how SWITCHC will update its MAC table as
SWITCHB updated its MAC table using Multiicast Frame sending by SWITCHC ? I think there is 15
sec downtime needed due MAC table �ush in SWITCHC.

Another Questions ..After STP convergence , Only Root Bridge will send BPDU(Hello time interval)

11 of 19 08/16/2017 03:46 AM
Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

and other SWITCH will receive BPDU [if no Topology Chage].

br//
zaman

lagapides
December 7, 2016

Hello �orian.

To answer your �rst question:

But this is only the case if uplink-fast is con�gured, right?

If it is not con�gured the port would stay in block state for 20 sec and then move through
the other states!?

Yes, my description in the above post is for situations where uplinkfast is not implemented. In
case uplinkfast is con�gured, this is reduced from 30 seconds to almost 0 seconds. Cisco explains
it like so:

The UplinkFast feature is based on the de�nition of an uplink group. On a given switch, the uplink
group consists of the root port and all the ports that provide an alternate connection to the root
bridge. If the root port fails, which means if the primary uplink fails, a port with next lowest cost
from the uplink group is selected to immediately replace it.
This is found at http://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol
/10575-51.html#uplink_fast_theory

Concerning your second question:

When does a port actually stay in blocking state before it moves to listening and so on?
If the root port is down the blocking interface goes directly to listening?
And Uplink-fast just helps to move the port directly to forwarding, right?

A port remains in blocking state as long as there is another active path to the root bridge. To say it
another way, a port remains in blocking state when STP has converged. If there is a topology
change, ports do not remain in a blocked state for any period of time before moving to listening
and learning. So yes, "if the root port is down, the blocking interface goes directly to listening" in
normal STP operation. If you use uplinkfast, the listening and learning states are skipped.

12 of 19 08/16/2017 03:46 AM
Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

It is only during root bridge elections that a port remains in a blocking state for 20 seconds. If a
topology change occurs but the root bridge does not change, then this extra blocking state for 20
seconds is skipped.

A very clear step by step explanation can be found here:

Uplink failure without uplinkfast enabled: http://www.cisco.com/c/en/us/support/docs/lan-

switching/spanning-tree-protocol/10575-51.html#uplink_fail

Uplink failure with uplinkfast enabled: http://www.cisco.com/c/en/us/support/docs/lan-switching

/spanning-tree-protocol/10575-51.html#uplink_fast_fail

I hope this has been helpful!

Laz

wilder7bc
April 21, 2017

So I have a question on this. it is stated that dummy multicast are �ooded out all ports that
contain the switch with the broken links Mac address table. in addition this mechanism will cause
the 20 second timer enacted by the topology table to stop and the other switches can go to
receiving the new mac address information immediately. quote from web lesson:

Take a look again at the MAC address table for SW2. The MAC address (000c.29e2.03ba) that I
highlighted belongs to H2. When SW2 receives an Ethernet Frame for H2 it will be forwarded to
SW1 and it will be dropped! (Well at least for 15 seconds until the topology change mechanism
kicks in…).

I tend to really learn when I have to explain this back to myself or another person as if I was
teaching. When I did so the I saw an inquisitive explorative question that might arise if we just did
not take something as fact because it was said.

==========

why does the dummy multicast cause the switches to stop holding those MAC addresses
contained within the dummy multicast??? why does it not drop the dummy multicast like it does in
the quote above from the web lesson??

13 of 19 08/16/2017 03:46 AM
Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

Now if asked this I would simply say because the dummy multicast are a special address that the
switches recognize so they simply drop those from its aging table and then they are able to
receive.

however, I am just making the most logical guess that I can make as I did not see that posted
anywhere. the true answer would be I don't know for certain.

Anyway diving deep into questions like this helps me to remember the content better as its all
embedded behind the reasoning and must be known to get to this point so I �gured why not ask
=)

I actually am being naughty, I have not read my book or tried to watch the videos to see if they
state this detail. so I am being lazy. What I will do is this; I will go back read my book and try to go
through and �nd the answer they give in my video and post here. I think its worth having the
question on the forums as others can bene�t as well. If someone provides an answer here before
I can get back and post that's great to as I a:) may not be able to �nd my answer or b:) will con�rm
what I �nd when I come back to post my �ndings!

Ok �rst information non related to my question but I will post as its useful:

Con�guring Uplink Fast Uplink Fast is enabled on Access layer switches and keeps track of
possible paths to the Root Bridge. Once the Uplink Fast feature is enabled globally, it is enabled
for the entire switch and all VLANs. By default, when Uplink Fast is enabled, Cisco IOS software
performs the following actions on the local switch:

The Bridge Priority of the switch is raised to 49,152

The Port Cost of all VLANs is increased by 3,000

These two actions ensure that the switch will never be elected Root Bridge, and it makes the path
through this switch as undesirable as possible for any downstream switches. For this reason,
Uplink Fast should never be enabled on the Root Bridge because it will lose its Root status or lose
switches that have other downstream switches connected to them.

Tafa, Farai. Cisco CCNP SWITCH Simpli�ed (Kindle Locations 2588-2596). Reality Press Ltd. Kindle
Edition.

===========================
Next is the answer to my question. was not in the book basically the same as the web lesson it did
have a extra piece of information or two:

14 of 19 08/16/2017 03:46 AM
Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

By transitioning the port to a Forwarding state almost immediately, the Uplink Fast feature
presents the potential problem of incorrect entries in the CAM tables of the other switches
because they have not had an opportunity to re-learn the new path for the MAC addresses of the
devices connected to the Access switch.

To prevent this, the Access layer switch on which the Uplink Fast feature is enabled oods dummy
frames with the di�erent MAC addresses that it has in its CAM as a source. The frames are sent to
the Multicast address 01-00.0C-CD-CD-CD and appear to originate from the hosts connected to
the switch so all the upstream switches can learn of these addresses through the new port.

By default, the switch sends out these Multicast frames at a rate of 150 packets per second (pps).
However, this value can be adjusted by using the spanning-tree uplinkfast max-update-rate [rate]
global conguration command.

Tafa, Farai. Cisco CCNP SWITCH Simpli�ed (Kindle Locations 2618-2620). Reality Press Ltd. Kindle
Edition.

===============================
so next I will try to scan through my INE CCNP video and see if they mention the answer to my
question!

===================

They did not give an answer on INE as well they just said it sent dummy multicast and that �xed it.
so I am only left to guess that it �xes it and is not dropped because the address is special and the
software code says hey when you see this address drop the MAC addresses and add these Mac
addresses from this location or maybe it does not drop but just changes but the e�ect is the
same.

if someone is able to �nd this answer feel free to post at least I now did my due diligence in trying
to �nd the answer!

note: I did �nd the following it does not spell out the answer of how either, it does once again
logically suggest that the "how" is because its a special address and strengthens it with terms such
as "ensures" ect...

cisco.com

15 of 19 08/16/2017 03:46 AM
Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

Understanding and Configuring the Cisco UplinkFast Feature

UplinkFast is a Cisco speci�c feature that improves the convergence time of the Spanning-Tree
Protocol (STP) in the event of the failure of an uplink. The UplinkFast feature is supported on Cisco
Catalyst 4500/4000, 5500/5000, and 6500/6000 series...

In order to solve this problem, switch A begins to �ood dummy packets with the di�erent MAC
addresses that it has in its CAM table as a source. In this case, a packet with C as a source address
is generated by A. Its destination is a Cisco proprietary multicast MAC address that ensures
that the packet is �ooded on the whole network and updates the necessary CAM tables on the
other switches.

lagapides
July 4, 2017

Hello Maodo

kayoutoure:
In one of the previous lessons (TCN), it was said about 50s delay for moving from Blocking to
Forwarding state. This lesson does only talk about 30s delay. Something important that this lesson
has to say is : SW3 does not need to wait for the 20s of "Max Age" (parameter setting on the
switch) ; because it detects immediately that a port (belonging to the switch) is not working.

In the TCN lesson, it mentions that there will be a maximum of 50 seconds delay when there is a
change in topology. When a TCN is received, a port will go into the blocking state for the Max Age
interval which is an interval of 20 seconds by default before beginning the STP recalculation. The
maximum of 50 seconds is ONLY for topology changes.

In this lesson, it is mentioned that it takes a maximum of 30 seconds for STP to converge when
STP function occurs from scratch, that is, after the switches are rebooted or turned on. This

16 of 19 08/16/2017 03:46 AM
Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

includes ONLY the Listening (15s) and Learning (15s) states. In this case, 30 seconds is only
needed.

kayoutoure:
The lesson is saying that the Listening and Learning delay could be as lower as 14s. It would
be important to recall that this delay is always twice (2 x 7s) the "Forward Delay" parameter
(setting on the switch).

How the result of approximately 14 seconds has been achieved depends on several factors
including network diameter. For further information, you can check this Cisco documentation that
further explains STP timers in detail.

kayoutoure:
The end of the lesson is very confusing. Once the link between SW3 and SW1 is back ;
nothing explains by which process and how long it takes for the ports of those two switches to get
back to their former states.

As is stated in the lesson, essentially nothing happens. The root port remains the same and
Fa0/14 remains blocked. Since the network is currently working, no changes have been made,
BPDUs are successfully exchanged, the network remains in this state until there is a topology
change.

I hope this has been helpful!

Laz

 35 more replies! Ask a question or join the discussion by visiting our Community
Forum

About NetworkLessons.com
Hello There! I'm René Molenaar (CCIE #41726), Your main Instructor of
NetworkLessons.com. I'd like to teach you everything about Cisco, Wireless and Security.

17 of 19 08/16/2017 03:46 AM
Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

I am here to Help You Master Networking!

Read my story

Social Fans

 
14,368 9,659
FANS FOLLOWERS

 
101 3,129
FOLLOWERS SUBSCRIBERS

New Lessons
OSPF Graceful Shutdown
OSPF Stub Router
OSPF Pre�x Suppression
OSPF Incremental SPF
OSPF LSA Throttling

Tag Cloud
802.1Q 802.1X ACL ARP Authentication Certi�cate Default Route DHCP DMVPN Filtering
Firewall GRE IGMP IKE IOS IP Routing IPSec LDP Linux
Load Balancing LSA NAT Network Management Network Services Network Type

OER OSPFv3 PAT PFR PIM PPP Redistribution RIP Security Shaping
SNMP SSH Stub Summarization Trunk Tuning VLAN VPN VRF Wireless

Disclaimer
Privacy Policy

18 of 19 08/16/2017 03:46 AM
Spanning-Tree UplinkFast | NetworkLessons.com https://networklessons.com/cisco/ccie-routing-swi...

Support

© 2013 - 2017 NetworkLessons.com 11681

19 of 19 08/16/2017 03:46 AM