Introduction to Spanning-Tree

Spanning-tree is a protocol that runs on our switches that helps us to solve loops. Spanning-tree is one of the protocols that you must understand as a network engineer and you will encounter it for sure if you decide to face the Cisco CCNA R&S exam. This lesson is an introduction to spanning-tree, you will learn why we need it, how it works and how you can check the spanning-tree topology on your Cisco switches.

Spanning-tree is a protocol that runs on our switches that helps us to solve loops. Spanning-tree is one of the protocols that you must understand as a network engineer and you will encounter it for sure if you decide to face the Cisco CCNA R&S exam. This lesson is an introduction to spanning-tr

Why do we need spanning-tree?

What is a loop and how do we get one? Let me show you an example:

In the picture above we have two switches. These switches are connected to each other with a single cable so there is a single point of failure.To get rid of this single point of failure we will add another cable:

With the extra cable we now have redundancy. Unfortunately for us redundancy also brings loops. Why do we have a loop in the scenario above? Let me describe it to you:

H1 sends an ARP request because it’s looking for the MAC address of H2. An ARP request is a broadcast frame.

SW1 will forward this broadcast frame on all it interfaces, except the interface where it received the frame on.

SW2 will receive both broadcast frames.

Now what does SW2 do with those broadcast frames?

It will forward it out of every interface except the interface where it received the frame on.

This means that the frame that was received on interface Fa0/0 will be forwarded on Interface Fa1/0.

The frame that was received on Interface Fa1/0 will be forwarded on Interface Fa0/0.

Do you see where this is going? We have a loop! Both switches will keep forwarding over and over again until the following happens:

You fix the loop by disconnecting one of the cables.

One of your switches will crash because they are overburdened with traffic.

Ethernet frames don’t have a TTL (Time to Live) value so they will loop around forever. Besides ARP requests there are many frames that are broadcasted. For example whenever the switch doesn’t know about a destination MAC address it will be flooded.

How spanning-tree solves loops

Spanning-tree will help us to create a loop-free topology by blocking certain interfaces. Let’s take a look how spanning-tree works! Here’s an example:

We have three switches and as you can see we have added redundancy by connecting the switches in a triangle, this also means we have a loop here. I have added the MAC addresses but simplified them for this example:

SW1: MAC AAA

SW2: MAC BBB

SW3: MAC CCC

Since spanning tree is enabled, all our switches will send a special frame to each other called a BPDU (Bridge Protocol Data Unit). In this BPDU there are two pieces of information that spanning-tree requires:

MAC address

Priority

The MAC address and the priority together make up the bridge ID. The BPDU is sent between switches as shown in the following picture:

Spanning-tree requires the bridge ID for its calculation. Let me explain how it works:

First of all spanning tree will elect a root bridge; this root-bridge will be the one that has the best “bridge ID”.

The switch with the lowest bridge ID is the best one.

By default the priority is 32768 but we can change this value if we want.

So who will become the root bridge? In our example SW1 will become the root bridge! Priority and MAC address make up the bridge ID. Since the priority is the same on all switches it will be the MAC address that is the tiebreaker. SW1 has the lowest MAC address thus the best bridge ID and will become the root bridge.

The ports on our root bridge are always designated which means they are in a forwarding state. Take a look at the following picture:

Above you see that SW1 has been elected as the root bridge and the “D” on the interfaces stands for designated.

Now we have agreed on the root bridge our next step for all our “non-root” bridges (so that’s every switch that is not the root) will have to find the shortest path to our root bridge! The shortest path to the root bridge is called the “root port”. Take a look at my example:

I’ve put an “R” for “root port” on SW2 and SW3, their Fa0/0 interface is the shortest path to get to the root bridge. In my example I’ve kept things simple but “shortest path” in spanning tree means it will actually look at the speed of the interface. Each interface has a certain cost and the path with the lowest cost will be used. Here’s an overview of the interfaces and their cost:

10 Mbit = Cost 100

100 Mbit = Cost 19

1000 Mbit = Cost 4

Excellent!…we have designated ports on our root bridge and root ports on our non-root bridges, we still have a loop however so we need to shut down a port between SW2 and SW3 to break that loop. So which port are we going to shut down? The one on SW2 or the one on SW3? We’ll look again at the best bridge ID:

Bridge ID = Priority + MAC address.

Lower is better, both switches have the same priority but the MAC address of SW2 is lower, this means that SW2 will “win this battle”. SW3 is our loser here which means it will have to block its port, effectively breaking our loop! Take a look at my example:

Forum Replies

The cost is 19 because the line speed connecting the switches is fast ethernet (100 meg), which is assigned a cost value of 19 by STP. Port 18 (FastEthernet 0/16) is the port that connects Switch B to the root bridge. To be honest, I haven’t figured out why it is assigned a value of “18” instead of “16” (the actual physical interface port).

A port moves out of the BLOCKING state once it stops hearing BPDUs coming in on that interface for the MaxAge amount of time (20 seconds by default). In other words, BPDUs must continue to be received in order f