STP Configurations
ExtremeWare XOS 10.1 Concepts Guide
145
Multiple STPDs on a Port
Traditional 802.1d STP has some inherent limitations when addressing networks that have multiple
VLANs and multiple STPDs. For example, consider the sample depicted in Figure 11.
Figure 11: Limitations of traditional STPD
The two switches are connected by a pair of parallel links. Both switches run two VLANs, A and B. To
achieve load-balancing between the two links using the traditional approach, you would have to
associate A and B with two different STPDs, called S1 and S2, respectively, and make the left link carry
VLAN A traffic while the right link carry VLAN B traffic (or vice versa). If the right link fails, S2 is
broken and VLAN B traffic is disrupted.
To optimize the solution, you can use the Extreme Multiple Instance Spanning (EMISTP) mode, which
allows a port to belong to multiple STPDs. EMISTP adds significant flexibility to STP network design.
Referring to Figure 11, using EMISTP, you can configure all four ports to belong to both VLANs.
Assuming that S1 and S2 still correspond to VLANs A and B, respectively, you can fine-tune STP
parameters to make the left link active in S1 and blocking in S2, while the right link is active in S2 and
blocking in S1. Once again, if the right link fails, the left link is elected active by the STP algorithm for
S2, without affecting normal switching of data traffic.
Using EMISTP, an STPD becomes more of an abstract concept. It does not necessarily correspond to a
physical domain. It is better regarded as a vehicle to carry VLANs that have STP instances. Because
VLANs can overlap, so do STPDs. However, even if the different STPDs share the entire topology or
part of the redundant topology, the STPDs react to topology change events in an independent fashion.
VLAN Spanning Multiple STPDs
Traditionally, the mapping from VLANs to STP instances have been one-to-one, or many-to-one. In both
cases, a VLAN is wholly contained in a single instance. In practical deployment there are cases in which
a one-to-many mapping is desirable. In a typical large enterprise network, for example, VLANs span
multiple sites and/or buildings. Each site represents a redundant looped area. However, between any
two sites the topology is usually very simple.
EX_050
S1
S2
A
A
B
B
A
A
B
B
S1
S2
Содержание ExtremeWare XOS 10.1
Страница 12: ...12 ExtremeWare XOS 10 1 Concepts Guide Contents...
Страница 15: ...Part 1 Using ExtremeWare XOS...
Страница 16: ......
Страница 20: ...20 ExtremeWare XOS 10 1 Concepts Guide ExtremeWare XOS Overview...
Страница 32: ...32 ExtremeWare XOS 10 1 Concepts Guide Accessing the Switch...
Страница 74: ...74 ExtremeWare XOS 10 1 Concepts Guide Virtual LANs VLANs...
Страница 80: ...80 ExtremeWare XOS 10 1 Concepts Guide Forwarding Database FDB...
Страница 112: ...112 ExtremeWare XOS 10 1 Concepts Guide Status Monitoring and Statistics...
Страница 133: ...Part 2 Using Switching and Routing Protocols...
Страница 134: ......
Страница 174: ...174 ExtremeWare XOS 10 1 Concepts Guide Virtual Router Redundancy Protocol...
Страница 184: ...184 ExtremeWare XOS 10 1 Concepts Guide IP Unicast Routing...
Страница 202: ...202 ExtremeWare XOS 10 1 Concepts Guide Interior Gateway Protocols...
Страница 216: ...216 ExtremeWare XOS 10 1 Concepts Guide Exterior Gateway Routing Protocols...
Страница 224: ...224 ExtremeWare XOS 10 1 Concepts Guide IP Multicast Routing...
Страница 225: ...Part 3 Appendixes...
Страница 226: ......
Страница 234: ...234 ExtremeWare XOS 10 1 Concepts Guide Software Upgrade and Boot Options...
Страница 242: ...242 ExtremeWare XOS 10 1 Concepts Guide Troubleshooting...
Страница 256: ...4 ExtremeWare XOS 10 1 Concepts Guide Index of Commands...