Table Of Contents
Configuring Spanning Tree Protocol
This chapter descibes how to configure Spanning Tree Protocol (STP) on your access point/bridge. This chapter contains these sections:
Note For complete syntax and usage information for the commands used in this chapter, refer to the Cisco IOS Command Reference for Access Points and Bridges for this release.
Understanding Spanning Tree Protocol
This section describes how spanning-tree features work. It includes this information:
STP is a Layer 2 link management protocol that provides path redundancy while preventing loops in the network. For a Layer 2 Ethernet network to function properly, only one active path can exist between any two stations. Spanning-tree operation is transparent to end stations, which cannot detect whether they are connected to a single LAN segment or to a LAN of multiple segments.
When you create fault-tolerant internetworks, you must have a loop-free path between all nodes in a network. The spanning-tree algorithm calculates the best loop-free path throughout a Layer 2 network. Infrastructure devices such as wireless access point/bridges and switches send and receive spanning-tree frames, called bridge protocol data units (BPDUs), at regular intervals. The devices do not forward these frames but use them to construct a loop-free path.
Multiple active paths among end stations cause loops in the network. If a loop exists in the network, end stations might receive duplicate messages. Infrastructure devices might also learn end-station MAC addresses on multiple Layer 2 interfaces. These conditions result in an unstable network.
STP defines a tree with a root bridge and a loop-free path from the root to all infrastructure devices in the Layer 2 network.
Note STP discussions use the term root to describe two concepts: the bridge on the network that serves as a central point in the spanning tree is called the root bridge, and the port on each bridge that provides the most efficient path to the root bridge is called the root port. These meanings are separate from the Role in radio network setting that includes root and non-root options. A bridge whose Role in radio network setting is Root Bridge does not necessarily become the root bridge in the spanning tree. In this chapter, the root bridge in the spanning tree is called the spanning-tree root.
STP forces redundant data paths into a standby (blocked) state. If a network segment in the spanning tree fails and a redundant path exists, the spanning-tree algorithm recalculates the spanning-tree topology and activates the standby path.
When two interfaces on a bridge are part of a loop, the spanning-tree port priority and path cost settings determine which interface is put in the forwarding state and which is put in the blocking state. The port priority value represents the location of an interface in the network topology and how well it is located to pass traffic. The path cost value represents media speed.
The access point/bridge supports both per-VLAN spanning tree (PVST) and a single 802.1q spanning tree without VLANs. The access point/bridge cannot run 802.1s MST or 802.1d Common Spanning Tree, which maps multiple VLANs into a one-instance spanning tree.
The access point/bridge maintains a separate spanning-tree instance for each active VLAN configured on it. A bridge ID, consisting of the bridge priority and the access point/bridge MAC address, is associated with each instance. For each VLAN, the access point/bridge with the lowest access point/bridge ID becomes the spanning-tree root for that VLAN.
350 Series Bridge Interoperability
Cisco Aironet 1300 and 350 Series Bridges are interoperable when STP is enabled and no VLANs are configured. This configuration is the only one available for the following reasons:
•When STP is disabled, the 350 series bridge acts as a 350 series access point and disallows association of non-root bridges, including non-root 350 and 1300 series bridges.
•The 350 series bridge supports only a single instance of STP in both non-VLAN and VLAN configurations, while the 1300 series bridge has a single instance of STP in non-VLAN configurations and multiple instances of STP in VLAN configurations.
•Incompatibilities between single and multiple instances of STP can cause inconsistent blocking of traffic when VLANs are configured. When the native VLAN is blocked, you can experience bridge flapping.
Therefore, the best configuration for STP interoperability is when the 350 and 1300 series access point/bridges STP feature is enabled and VLANs are not configured.
Note When the 350 and 1300 series access point/bridges are configured as workgroup bridges, they can operate with STP disabled and allow for associations with access points. However, this configuration is not technically a bridge-to-bridge scenario.
Access Point/Bridge Protocol Data Units
The stable, active spanning-tree topology of your network is determined by these elements:
•The unique access point/bridge ID (wireless access point/bridge priority and MAC address) associated with each VLAN on each wireless access point/bridge
•The spanning-tree path cost to the spanning-tree root
•The port identifier (port priority and MAC address) associated with each Layer 2 interface
When the access point/bridges in a network are powered up, each access point/bridge functions as the STP root. The access point/bridges send configuration BPDUs through the Ethernet and radio ports. The BPDUs communicate and compute the spanning-tree topology. Each configuration BPDU contains this information:
•The unique access point/bridge ID of the wireless access point/bridge that the sending access point/bridge identifies as the spanning-tree root
•The spanning-tree path cost to the root
•The access point/bridge ID of the sending access point/bridge
•The identifier of the sending interface
•Values for the hello, forward delay, and max-age protocol timers
When a access point/bridge receives a configuration BPDU that contains superior information (lower access point/bridge ID, lower path cost, and so forth), it stores the information for that port. If this BPDU is received on the root port of the access point/bridge, the access point/bridge also forwards it with an updated message to all attached LANs for which it is the designated access point/bridge.
If a access point/bridge receives a configuration BPDU that contains inferior information to that currently stored for that port, it discards the BPDU. If the access point/bridge is a designated access point/bridge for the LAN from which the inferior BPDU was received, it sends that LAN a BPDU containing the up-to-date information stored for that port. In this way, inferior information is discarded, and superior information is propagated on the network.
A BPDU exchange results in these actions:
•One access point/bridge is elected as the spanning-tree root.
•A root port is selected for each access point/bridge (except the spanning-tree root). This port provides the best path (lowest cost) when the access point/bridge forwards packets to the spanning-tree root.
•The shortest distance to the spanning-tree root is calculated for each access point/bridge based on the path cost.
•A designated access point/bridge for each LAN segment is selected. The designated access point/bridge incurs the lowest path cost when forwarding packets from that LAN to the spanning-tree root. The port through which the designated access point/bridge is attached to the LAN is called the designated port.
•Interfaces included in the spanning-tree instance are selected. Root ports and designated ports are put in the forwarding state.
•All interfaces not included in the spanning tree are blocked.
Election of the Spanning-Tree Root
All access point/bridges in the Layer 2 network participating in STP gather information about other access point/bridges in the network through an exchange of BPDU data messages. This exchange of messages results in these actions:
•The election of a unique spanning-tree root for each spanning-tree instance
•The election of a designated access point/bridge for every LAN segment
•The removal of loops in the network by blocking Layer 2 interfaces connected to redundant links
For each VLAN, the access point/bridge with the highest access point/bridge priority (the lowest numerical priority value) is elected as the spanning-tree root. If all access point/bridges are configured with the default priority (32768), the access point/bridge with the lowest MAC address in the VLAN becomes the spanning-tree root. The access point/bridge priority value occupies the most significant bits of the access point/bridge ID.
When you change the access point/bridge priority value, you change the probability that the access point/bridge will be elected as the root access point/bridge. Configuring a higher value decreases the probability; a lower value increases the probability.
The spanning-tree root is the logical center of the spanning-tree topology. All paths that are not needed to reach the spanning-tree root from anywhere in the network are placed in the spanning-tree blocking mode.
BPDUs contain information about the sending access point/bridge and its ports, including access point/bridge and MAC addresses, access point/bridge priority, port priority, and path cost. STP uses this information to elect the spanning-tree root and root port for the network and the root port and designated port for each LAN segment.
Table 8-1 describes the timers that affect the entire spanning-tree performance.
Creating the Spanning-Tree Topology
In Figure 8-1, bridge 4 is elected as the spanning-tree root because the priority of all the access point/bridges is set to the default (32768) and bridge 4 has the lowest MAC address. However, because of traffic patterns, number of forwarding interfaces, or link types, bridge 4 might not be the ideal spanning-tree root. By increasing the priority (lowering the numerical value) of the ideal bridge so that it becomes the spanning-tree root, you force a spanning-tree recalculation to form a new topology with the ideal bridge as the spanning-tree root.
Figure 8-1 Spanning-Tree Topology
Spanning-Tree Interface States
Propagation delays can occur when protocol information passes through a wireless LAN. As a result, topology changes can take place at different times and at different places in the network. When an interface transitions directly from nonparticipation in the spanning-tree topology to the forwarding state, it can create temporary data loops. Interfaces must wait for new topology information to propagate through the LAN before starting to forward frames. They must allow the frame lifetime to expire for forwarded frames that have used the old topology.
Each interface on a access point/bridge using spanning tree exists in one of these states:
•Blocking—The interface does not participate in frame forwarding.
•Listening—The first transitional state after the blocking state when the spanning tree determines that the interface should participate in frame forwarding.
•Learning—The interface prepares to participate in frame forwarding.
•Forwarding—The interface forwards frames.
•Disabled—The interface is not participating in spanning tree because of a shutdown port, no link on the port, or no spanning-tree instance running on the port.
An interface moves through these states:
•From initialization to blocking
•From blocking to listening or to disabled
•From listening to learning or to disabled
•From learning to forwarding or to disabled
•From forwarding to disabled
Figure 8-2 illustrates how an interface moves through the states.
Figure 8-2 Spanning-Tree Interface States
When you enable STP on the access point/bridge, the Ethernet and radio interfaces go through the blocking state and the transitory states of listening and learning. Spanning tree stabilizes each interface at the forwarding or blocking state.
When the spanning-tree algorithm places a Layer 2 interface in the forwarding state, this process occurs:
1. The interface is in the listening state while spanning tree waits for protocol information to transition the interface to the blocking state.
2. While spanning tree waits the forward-delay timer to expire, it moves the interface to the learning state and resets the forward-delay timer.
3. In the learning state, the interface continues to block frame forwarding as the access point/bridge learns end-station location information for the forwarding database.
4. When the forward-delay timer expires, spanning tree moves the interface to the forwarding state, where both learning and frame forwarding are enabled.
An interface in the blocking state does not participate in frame forwarding. After initialization, a BPDU is sent to the access point/bridge's Ethernet and radio ports. A access point/bridge initially functions as the spanning-tree root until it exchanges BPDUs with other access point/bridges. This exchange establishes which access point/bridge in the network is the spanning-tree root. If there is only one access point/bridge in the network, no exchange occurs, the forward-delay timer expires, and the interfaces move to the listening state. An interface always enters the blocking state when you enable STP.
An interface in the blocking state performs as follows:
•Discards frames received on the port
•Does not learn addresses
Note If a access point/bridge port is blocked, some broadcast or multicast packets can reach a forwarding port on the access point/bridge and cause the bridging logic to switch the blocked port into listening state momentarily before the packets are dropped at the blocked port.
The listening state is the first state an interface enters after the blocking state. The interface enters this state when STP determines that the interface should participate in frame forwarding.
An interface in the listening state performs as follows:
•Discards frames received on the port
•Does not learn addresses
An interface in the learning state prepares to participate in frame forwarding. The interface enters the learning state from the listening state.
An interface in the learning state performs as follows:
•Discards frames received on the port
An interface in the forwarding state forwards frames. The interface enters the forwarding state from the learning state.
An interface in the forwarding state performs as follows:
•Receives and forwards frames received on the port
An interface in the disabled state does not participate in frame forwarding or in the spanning tree. An interface in the disabled state is nonoperational.
A disabled interface performs as follows:
•Discards frames received on the port
•Does not learn addresses
•Does not receive BPDUs
Configuring STP Features
You complete three major steps to configure STP on the access point/bridge:
1. If necessary, assign interfaces and sub-interfaces to bridge groups
2. Enable STP for each bridge group
3. Set the STP priority for each bridge group
These sections include spanning-tree configuration information:
Default STP Configuration
STP is disabled by default. Table 8-2 lists the default STP settings when you enable STP.
The radio and Ethernet interfaces and the native VLAN on the access point/bridge are assigned to bridge group 1 by default. When you enable STP and assign a priority on bridge group 1, STP is enabled on the radio and Ethernet interfaces and on the primary VLAN, and those interfaces adopt the priority assigned to bridge group 1. You can create bridge groups for sub-interfaces and assign different STP settings to those bridge groups.
Configuring STP Settings
Beginning in privileged EXEC mode, follow these steps to configure STP on the access point/bridge:
STP Configuration Examples
These configuration examples show how to enable STP on root and non-root access point/bridges with and without VLANs:
Root Bridge Without VLANs
This example shows the configuration of a root bridge with no VLANs configured and with STP enabled:hostname master-bridge-southip subnet-zero!bridge irb!interface Dot11Radio0no ip addressno ip route-cache!ssid tsunamiauthentication openguest-mode!speed basic-6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0rts threshold 2312station-role rootno cdp enableinfrastructure-clientbridge-group 1!interface FastEthernet0no ip addressno ip route-cacheduplex autospeed autobridge-group 1!interface BVI1ip address 184.108.40.206 255.255.0.0no ip route-cache!ip default-gateway 220.127.116.11bridge 1 protocol ieeebridge 1 route ipbridge 1 priority 9000!line con 0exec-timeout 0 0line vty 0 4loginline vty 5 15login!end
Non-Root Bridge Without VLANs
This example shows the configuration of a non-root bridge with no VLANs configured with STP enabled:hostname client-bridge-northip subnet-zero!bridge irb!interface Dot11Radio0no ip addressno ip route-cache!ssid tsunamiauthentication openguest-mode!speed basic-6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0rts threshold 2312station-role non-rootno cdp enablebridge-group 1!interface FastEthernet0no ip addressno ip route-cacheduplex autospeed autobridge-group 1 path-cost 40!interface BVI1ip address 18.104.22.168 255.255.0.0no ip route-cache!bridge 1 protocol ieeebridge 1 route ipbridge 1 priority 10000!line con 0line vty 0 4loginline vty 5 15login!end
Root Bridge with VLANs
This example shows the configuration of a root bridge with VLANs configured with STP enabled:hostname master-bridge-hq!ip subnet-zero!ip ssh time-out 120ip ssh authentication-retries 3!bridge irb!interface Dot11Radio0no ip addressno ip route-cache!ssid vlan1vlan 1infrastructure-ssidauthentication open!speed basic-6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0rts threshold 2312station-role rootno cdp enableinfrastructure-client!interface Dot11Radio0.1encapsulation dot1Q 1 nativeno ip route-cacheno cdp enablebridge-group 1!interface Dot11Radio0.2encapsulation dot1Q 2no ip route-cacheno cdp enablebridge-group 2!interface Dot11Radio0.3encapsulation dot1Q 3no ip route-cachebridge-group 3bridge-group 3 path-cost 500!interface FastEthernet0no ip addressno ip route-cacheduplex autospeed auto!interface FastEthernet0.1encapsulation dot1Q 1 nativeno ip route-cachebridge-group 1!interface FastEthernet0.2encapsulation dot1Q 2no ip route-cachebridge-group 2!interface FastEthernet0.3encapsulation dot1Q 3no ip route-cachebridge-group 3!interface BVI1ip address 22.214.171.124 255.255.0.0no ip route-cache!ip default-gateway 126.96.36.199bridge 1 protocol ieeebridge 1 route ipbridge 1 priority 9000bridge 2 protocol ieeebridge 2 priority 10000bridge 3 protocol ieeebridge 3 priority 3100!line con 0exec-timeout 0 0line vty 5 15!end
Non-Root Bridge with VLANs
This example shows the configuration of a non-root bridge with VLANs configured with STP enabled:hostname client-bridge-remote!ip subnet-zero!ip ssh time-out 120ip ssh authentication-retries 3!bridge irb!interface Dot11Radio0no ip addressno ip route-cache!ssid vlan1vlan 1authentication openinfrastructure-ssid!speed basic-6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0rts threshold 2312station-role non-rootno cdp enable!interface Dot11Radio0.1encapsulation dot1Q 1 nativeno ip route-cacheno cdp enablebridge-group 1!interface Dot11Radio0.2encapsulation dot1Q 2no ip route-cacheno cdp enablebridge-group 2!interface Dot11Radio0.3encapsulation dot1Q 3no ip route-cacheno cdp enablebridge-group 3!interface FastEthernet0no ip addressno ip route-cacheduplex autospeed auto!interface FastEthernet0.1encapsulation dot1Q 1 nativeno ip route-cachebridge-group 1!interface FastEthernet0.2encapsulation dot1Q 2no ip route-cachebridge-group 2!interface FastEthernet0.3encapsulation dot1Q 3no ip route-cachebridge-group 3bridge-group 3 path-cost 400!interface BVI1ip address 188.8.131.52 255.255.0.0no ip route-cache!bridge 1 protocol ieeebridge 1 route ipbridge 1 priority 10000bridge 2 protocol ieeebridge 2 priority 12000bridge 3 protocol ieeebridge 3 priority 2900!line con 0line vty 5 15!end
Displaying Spanning-Tree Status
To display the spanning-tree status, use one or more of the privileged EXEC commands in Table 8-3:
For information about other keywords for the show spanning-tree privileged EXEC command, refer to the Cisco Aironet IOS Command Reference for Cisco Aironet Access Points and Bridges for this release.