Requires Membership to View
To gain access to this and all member only content, please provide the following information:
By submitting your registration information to SearchTelecom.com you agree to receive email communications from the TechTarget network of sites, and/or third party content providers that have relationships with TechTarget, based on your topic interests and activity, including updates on new content, event notifications, new site launches and market research surveys. Please verify all information and selections above. You may unsubscribe at any time from one or more of the services you have selected by editing your profile, unsubscribing via email or by contacting us here
- Your use of SearchTelecom.com is governed by our Terms of Use
- We designed our Privacy Policy to provide you with important disclosures about how we collect and use your registration and other information. We encourage you to read the Privacy Policy, and to use it to help make informed decisions.
- If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States.
There are several approaches to this problem, and none of them are perfect.
You can design your network in a hierarchical tree structure using multi-chassis link aggregation to make redundant links appear as part of the same link aggregation group. In this solution, you would still run spanning tree, but as the network would look like a perfect tree, the spanning tree would have no impact on the network.
Alternatively, you can try to use Provider Backbone Bridging Traffic Engineering (PBB-TE, 802.1Qay), where the paths across the network are configured statically from the network management station.
The ideal solution to this problem is shortest-path bridging (turning bridging into an almost-routing technology), implemented with 802.1aq or TRILL.
This was first published in January 2011