Spanning Tree

ExtremeXOS™ Operation and

Configuration, Version 12.1

© 2008 Extreme Networks, Inc. All rights reserved. ExtremeXOS Operation and Configuration, Version 12.1. Part number DOC-00919.
 Student Objectives

Upon completion of this module, you will be able to:

Define the spanning tree protocol.
Explain how spanning tree works.
Identify the building blocks of STP.
Describe the relationship between ports, VLANs, and the Spanning
Tree Domain.
Configure STP on Extreme Networks switches.
Describe Extreme Networks STP enhancements.

Depending on the needs of the students, the instructor may choose to reduce or eliminate the protocol
overview portion of this module.
Slide 2
 Spanning Tree

802.1D - Bridging, Switching and

Spanning Tree specification
Developed by DEC
Adopted by the IEEE and is defined
in the IEEE 802.1D specification

Detects and
Allows for
reroutes any
redundant
broken
bridging paths
network paths
Prevents
network
loops from
occurring

Slide 3
 Network Redundancy

Often redundancy is required in a network.

In this design, Layer 2 redundancy is achieved:
• If any one of the links fail, the two PCs are still able to communicate.
So, what is the problem?

Slide 4
 Looped Topologies Cause Broadcast Storms

Broadcast Storm

Broadcast

Slide 5
 Identifying the Solution

Solution - Disable one of the links

• Also enable link again if required
A redundant design with no loops
Bridged networks must allow for redundancy
Only one path should be enabled to any destination on the network

Slide 6
 Spanning Tree Algorithm

Ports in the forwarding state are allowed to forward packets.

Ports in blocking state participate in spanning tree but do not
forward data packets.
Redundant paths are pruned from the tree.

Slide 7
 Reconfiguration After a Link Failure

Occurs when there is a change in the active topology:

• Link failure
• Bridge failure
• Administrative configuration change

Link
Lost

Link
Restored

Slide 8
 Spanning Tree Port States

Ports participating in STP can be in any one of the following states:

Blocking
• Initial state or determined by STP
• No forwarding, no MAC address learning
Listening
• Temporary state preparing for forwarding
Learning
• MAC addresses are learned and entered in FDB
Forwarding
• Active port for frame transmission

Slide 9
 How Spanning Tree Works

A stable active topology is maintained by the root bridge.

The root bridge transmits Configuration BPDUs out of all of its
active ports to determine the least cost path.
When a designated bridge detects a topology change, it sends out
a Topology Change BPDU through it's root port to the root bridge.

Root Bridge
Root Port Root Port

Root Port

Slide 10
 Spanning Tree Protocol Building Block

Spanning Tree uses the following building blocks:

Bridge ID
Bridge Protocol Data Unit
Root bridge
Root port
Designated bridge
Designated port

Slide 11
 Selecting the Root Bridge

The root bridge controls the STP topology.

Root bridge = lowest bridge ID.
Bridge ID = bridge priority and MAC address:
• Priority = 0 – 65,535, Default = 32,768 (80:00 Hex)
• e.g. Bridge ID = 80:00:00:01:30:12:34:56
Every bridge transmits CBPDUs claiming to be the root bridge.
Each bridge saves and transmits the CBPDU information of the
bridge with the lowest bridge ID.
If the bridge IDs are equal, save the information with the lower MAC
address.

Slide 12
 Selecting the Root Bridge (Continued…)

In this example, Switch 1 becomes the root bridge.

79:00:00:01:30:00:00:01 80:00:00:01:30:00:00:02

1 1000 2
Root

100 1000

100 100

3 100 4

80:00:00:01:30:00:00:03 80:00:00:01:30:00:00:04

Slide 13
 Selecting the Root Port

Each switch except the root bridge selects the root port as follows:
• The port that provides the lowest total cost to the root bridge.
• If the cost is the same, whichever has the lowest port number.
Root ports are allowed to forward traffic.
Only one root port per spanning tree, per bridge.

Slide 14
 Selecting the Root Port (Continued…)

In 802.1D, port costs are:

• 10 MB = 100, 100 MB = 19, 1000 MB = 4, 10 GB = 2
In this example, the following root ports are selected:
• Switch 1 = root bridge Switch 2 root port = 1
• Switch 3 root port = 1 Switch 4 root port = 3

79:00:00:01:30:00:00:01 80:00:00:01:30:00:00:02
3 1
1 4 R 2
Root 1 2 2 3
19 4
R 2 19 19 2 R
1 3
3 1
3 19 4
80:00:00:01:30:00:00:03 80:00:00:01:30:00:00:04

Slide 15
 Selecting the Designated Bridge

One designated bridge per directly connected segment (collision

domain).
Provides the lowest path cost to root:
• If the cost is the same, the lowest bridge ID is selected.

79:00:00:01:30:00:00:01 80:00:00:01:30:00:00:02

1 D 4 R 2
3 1
Root 1 D D 2 2 D D 3

19 4
R
2 19 19 2
R
1 3
3 1
3 D 19 4
80:00:00:01:30:00:00:03 80:00:00:01:30:00:00:04

Slide 16
 Selecting the Designated Port

Ports on a designated bridge that attach to the segments for which

that bridge is the designated bridge:
• The designated port is allowed to forward traffic.

79:00:00:01:30:00:00:01 80:00:00:01:30:00:00:02

1 D 4 R 2
3 1
Root 1 D D 2 2 D D 3

19 4
R
2 19 19 2
R
1 3

3 D 19 4
3 1
80:00:00:01:30:00:00:03 80:00:00:01:30:00:00:04

Slide 17
 Forwarding and Blocking Ports

All root and designated ports are allowed to forward.

All other ports are blocked.

79:00:00:01:30:00:00:01 80:00:00:01:30:00:00:02

1 D 4 R 2
3 1
Root 1 D D
2 2 D 3
D

19 4
19 19
2 2
1 R R 3

3 19 D 4
3 1
80:00:00:01:30:00:00:03 80:00:00:01:30:00:00:04

Slide 18
 Active Topology

Now there is only a single active path.

What if an active link fails?

79:00:00:01:30:00:00:01 80:00:00:01:30:00:00:02

1 2
3 1
Root 1 2 2 3

2 2
1 3

3 4
3 1
80:00:00:01:30:00:00:03 80:00:00:01:30:00:00:04

Slide 19
 Detecting Topology Changes

STP detects changes to the active topology in the following ways:

• Failure of communications with root bridge:
The root bridge periodically sends out a configuration BPDU (Type 0) every 2
seconds as a keep alive. If a non-root bridge does not receive this BPDU within 20
seconds, it presumes to have lost communications with the root bridge.
• Local topology change / receive topology change BPDU:
A topology change triggers a topology change BPDU (Type 80) which is sent out
and repeated by all the root ports.
If a change in the active topology is detected, STP can recalculate
the necessary port states.

Slide 20
 A Change in Active Topology

Switch 4 is not able to exchange frames with the other switches.

Switch 2 sends out a topology change BPDU.
When the Root bridge receives this BPDU, it changes a flag in the
configuration BPDU triggering recalculation.
79:00:00:01:30:00:00:01 80:00:00:01:30:00:00:02

1 2
3 1
Root 1 2 2 3

Break

2 2
1 3

3 4
3 1
80:00:00:01:30:00:00:03 80:00:00:01:30:00:00:04

Slide 21
 Recalculating Port States

All root and designated ports are allowed to forward.

All other ports are blocked.

79:00:00:01:30:00:00:01 80:00:00:01:30:00:00:02

1 D 4 R 2
3 1
Root 1 D D
2 2 3
D

19
19 19
2 R 2
1 R 3

D
3 19 4
3 1
80:00:00:01:30:00:00:03 80:00:00:01:30:00:00:04

Slide 22
 New Active Topology

Switch 4 can now exchange frames with the other switches.

If the connection between switches 2 and 4 is restored, another
topology change BPDU is released triggering another recalculation
which restores the active topology to it original state.
79:00:00:01:30:00:00:01 80:00:00:01:30:00:00:02

1 2
3 1
Root 1 2 2 3

Break

2 2
1 3

3 4
3 1
80:00:00:01:30:00:00:03 80:00:00:01:30:00:00:04

Slide 23
 Planning a Spanning Tree Topology

Diagram the network topology and identify loops.

Determine the root bridge, designated bridges, and designated
ports using default values.
Identify if there is a more desirable topology and what needs to be
done to implement it.
Test all link and bridge failures on paper to identify resulting
topology.
Identify if there are more desirable topologies and what needs to be
done to implement it.
Document everything.

Slide 24
 Spanning Tree Enhancements

Extreme Networks switches support the following modes:

802.1D
• Using IEEE 802.1D (revised version, 1998).
802.1w Rapid Spanning Tree
• Easy to enable.
• Faster convergence.
• Compatible with 802.1D.
Extreme Multiple Instance Spanning Tree Protocol (EMISTP)
• Default mode for user-created STPD.
Per VLAN Spanning Tree (PVST+)
• For compatibility with third party switches that run this version of STP.

Slide 25
 Spanning Tree Enhancements (Continued…)

Extreme Networks switches support:

Multiple Spanning Tree Protocol (MSTP)
• Logically divides a Layer 2 network into regions.
• Each region can contain multiple instances of spanning trees.
• Uses rapid spanning tree as a converging algorithm and is fully interoperable
with earlier versions of STP.
• IEEE standard 802.1Q-2004 (previously 802.1s).

Slide 26
 Configuring a Single Spanning Tree in dot1w Mode

Enable the STP protocol for the STPD, by using the following syntax. The
default spanning tree domain is s0.
• enable stpd {<stpd_name>}
Configure the default STP domain for 802.1w mode:
• configure stpd s0 mode dot1w
Add VLANs to the spanning tree domain:
• configure stpd <stpd_name> add vlan <vlan name> port <portlist>
Optionally, configure bridge priority to control election of the root bridge:
• configure stpd <stpd_name> priority <priority>
For RSTP and MSTP priorities are in increments of 4096
Optionally, configure port cost to control election of designated bridge and
designated port:
• configure stpd <stpd_name> ports cost <auto | cost> <portlist>

Slide 27
 Configuring a Single STPD in dot1w Mode (Continued...)

Configure the port priority to select the designated port in case of a

tie:
• configure stpd {<stpd_name>} ports priority <priority>
<portlist>
Enable the STP protocol for the STPD:
• enable stpd {<stpd_name>}

Note: The default STP domain (STPD) is named s0.

Slide 28
 Configuring STP Parameters

Typically default values are sufficient.

Parameter changes require advanced STP knowledge.
Parameters include:
• Hello time
• Forward delay
• Max age

Slide 29
 Verifying STP Configuration

If the local BridgeID and the Designated root ID match, then this switch is a root bridge.

Slide 30
 Verifying STP Ports

Slide 31
 Notes on Spanning Tree Configuration

The 802.1D ports must be untagged.

A VLAN and port can belong to only one 802.1D STPD.
A VLAN can only be a member of one 802.1D STPD.
A physical port can belong to only one 802.1D STPD.
If a port is a member of multiple VLANs, then those VLANs must
belong to the same 802.1D STPD.

Slide 32
 Notes on Spanning Tree Operation

You should remove all VLANs associated with the STP before
deleting the STPD. If you delete an STPD, member VLANs are
automatically deleted.
STP, load-sharing, and redundant physical ports/links work
together.
Blocked ports only process BPDU packets.

Slide 33
 Summary

You should now be able to:

Define the spanning tree protocol.
Explain how spanning tree works.
Identify the building blocks of STP.
Describe the relationship between ports, VLANs, and the Spanning
Tree Domain.
Configure STP on Extreme Networks switches.
Describe Extreme Networks STP enhancements.

Slide 34
 Lab

Turn to the Spanning Tree Configuration Lab

in your XOS Operations and Configuration - Lab Guide, Rev. 12.1
and complete the hands-on portion of this module.

Slide 35
Review Questions

© 2008 Extreme Networks, Inc. All rights reserved. ExtremeXOS Operation and Configuration, Version 12.1. Part number DOC-00919.
This presentation contains forward-looking statements that involve
risks and uncertainties, including statements regarding our
expectations as to products, trends and our performance. There can be
no assurances that any forward-looking statements will be achieved,
and actual results could differ materially from forecasts and estimates.
For factors that may affect our business and financial results please
refer to our filings with the Securities and Exchange Commission,
including, without limitation, under the captions: “Management’s
Discussion and Analysis of Financial Condition and Results of
Operations,” and “Risk Factors,” which is on file with the Securities
and Exchange Commission (http://www.sec.gov). We undertake no
obligation to update the forward-looking information in this release.

© 2008 Extreme Networks, Inc. All rights reserved. ExtremeXOS Operation and Configuration, Version 12.1. Part number DOC-00919.
©
© 2008
2008 Extreme
Extreme Networks,
Networks, Inc.
Inc. All
All rights
rights reserved.
reserved. ExtremeXOS
ExtremeXOS Operation
Operation and
and Configuration,
Configuration, Version
Version 12.1.
12.1. Part
Part number
number DOC-00919.
DOC-00919.