Below is a short overview of STP and how to navigate it in the CISCO IOS enjoy.
[youtube=http://www.youtube.com/watch?v=zapAZRP7mEk&w=560&h=315]
Below is a short overview of STP and how to navigate it in the CISCO IOS enjoy.
[youtube=http://www.youtube.com/watch?v=zapAZRP7mEk&w=560&h=315]
The Root switch is elected in the following order:
Once the root switch is elected either by lowest BID or MAC address, this switch will be responsible for sending the periodic Hello Bridge Protocol Data Unit‘s (BPDU). These Hello BPDU’s are status messages which all switches on the LAN will receive from the root switch to indicate that the connected links are still working. This sort of works like a heartbeat for the link.
The Hello BPDU contains the following pieces of information:
The hello timer defaults to 2 seconds with a MaxAge time of 10secs.
The Hello timer is the amount of time which the Root waits to send a Hello, while the MaxAge timer is used to tell the listening device how long it should wait before it converges to a new STP topology, after not receiving Hello’s for the indicated amount of time.
To finish up the first topic under LAN Switching Technologies, identifying enhanced switching technologies. I will give you an overview of Etherchannels.
What they are, what they do and how to configure one for yourself.
Firstly an Etherchannel is a configuration that allows a switch to treat two parallel links as one physical link. This also allows STP to treat the entire channel as one and either block or forward traffic over this link as per vlan.
As a result of this, the switch can now load balance traffic over the channel. Without Etherchannel one of the links would be blocked by STP, as is shown in the example below.
In the above example, SW0 and SW1 are connected via two links. Fa0/1 to Fa0/1 and Fa0/2 to Fa0/2, but due to STP it has blacked Fa0/2 on SW1 from forwarding frames. STP at this point see’s these two links as they are, separate from one another.
When we run a show spanning-tree command on SW1 we discover that, port Fa0/1 is in a forwarding state as the RP, Port Fa0/2 is blocked and Fa0/3 is the DP. Running the show spanning-tree command on SW0 would show us that it is the Root Bridge and all three ports are DP’s or Designated Ports.
To make STP use both the Fa0/1 and Fa0/2 links on SW0 and SW1 we need to configure the interfaces in the same Channel-group or Etherchannel. Doing so will change how STP see’s those two links. From two separate links to one link which can be used to load balance. We are not actually making one physical link but like a VLAN where we can make many Virtual LAN’s we are creating one Virtual Link using 2 parallel links.
For this network the configuration is virtually the same, just remember you will need to add the correct interfaces in the same channel group for an Etherchannel to become active.
The following image shows you how to correctly configure an Etherchannel, using the command channel-group 1 mode on, you can configure upto 8 parallel links on the one Etherchannel.
Below you can see the new show spanning-tree output displayed on SW1 after the Etherchannel has been configured. Notice the Po1, that indicates that all the configuration parameters checked and that is the new channel group 1, which was configured earlier.
The new diagram, with the two links now bundled in the new Etherchannel. Notice how Fa0/2 has come out of blocking mode to become a RP
The second item under the topics in the new ICND2 200-101 exam, requires that you can identify PVSTP.
PVSTP or Per VLAN Spanning Tree Protocol does just that, each VLAN will have a different STP setup or topology, as it is done on per VLAN basis.
As the engineer this provides you with a great tool to load balance traffic over the network, using some configuration options you can decide what switches will become root.
Note: All of the interfaces on the Root switch will be DP’s
The above example show you how the two VLANs have a different topology.
If you are going to setup a LAN with redundant paths, it is important that STP is running. If not you will be opening yourself up to these few problems
While the issue of broadcast storms may seem obvious, the other two may not be the things you think about at all. In the case of MAC table instability your switches will experience frequent updates to their MAC tables with wrong entires, from the looped frames which are being sent around the LAN.
The second issue of Multiple frame transmission can be somewhat, a disastrous side affect of not running STP. Duplicate copies of the looping frame can end up at the end host, in turn completely confusing it, resulting in discarded frames.
Luckily though on CISCO switches STP is on by DEFAULT
For those unfamiliar with this protocol, you will find that it is a very important part of switching. It is defined by IEEE 802.1D. The purpose of STP is to allow you to create a redundant topology utilising switches and bridges without creating loops. STP will dynamically elect a Root switch for which all traffic must pass through and set the appropriate interfaces in a blocking mode. This is how STP prevents frames from forever looping around the LAN.
The diagram below is the network in use:
Switch 3
FA0/1 – DP
FA1/1 – DP
Switch 1
FA1/1 – RP
FA0/1 DP
Switch 2
FA1/1 – RP
FA0/1 – DP
Switch 0
FA0/1 – RP
FA1/1 – ALTN
The lab for this example can be downloaded by clicking here