Multiple Spanning Tree Instance Root Bridge Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional communication network protocols like STP and MSTP do not optimize the use of all LANs in a network, leading to suboptimal paths for data transmission, and struggle with asymmetrical spanning tree instances which hinder efficient data routing.

Innovation Solution

Each bridge in the network is configured as a root of its own Multiple Spanning Tree Instance (MSTI), with the use of MAC-in-MAC frames and VLAN tags to enable optimal routing and load sharing, and the implementation of Reflection Vectors to resolve asymmetrical MSTIs by ensuring symmetrical port path costs and path selection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single spanning tree is used in the network, then loop prevention is achieved, but path optimization and load sharing are limited

Engineering Contradiction:
Improveloop preventionVSAvoidpath optimization
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The network is segmented into multiple spanning tree instances (MSTIs), each with its own root bridge and topology. This allows different VLANs or traffic types to use different trees, enabling path optimization and load sharing while each individual tree maintains loop-free properties.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically selects which spanning tree instance to use based on traffic characteristics, source and destination VLANs, and current network conditions. This dynamic selection enables optimal path routing while maintaining the stability and loop-free guarantee of individual spanning trees.

Inventive Principle:
Principle #15Dynamics

2Productivity

If conventional MSTP is used with VLAN-based tree selection, then some load sharing is achieved, but asymmetrical paths and optimal routing are hindered

Engineering Contradiction:
Improveload sharingVSAvoidpath symmetry
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

Each bridge is configured as the root of its own MSTI, creating locally optimized paths from each bridge's perspective. This local quality approach ensures that traffic from any bridge follows the optimal path through the network, resolving asymmetrical path issues while maintaining load sharing capabilities.

Inventive Principle:
Principle #3Local quality

3Productivity

If multiple spanning tree instances are created, then path diversity and load sharing improve, but computational load and protocol complexity increase

Engineering Contradiction:
Improvepath diversityVSAvoidprotocol complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The spanning tree protocol is made universal by enabling each bridge to serve as a root bridge for its own MSTI. This multi-functionality allows a single protocol mechanism to achieve both traditional STP loop prevention and advanced features like optimal path selection and load sharing across multiple instances, reducing the need for separate complex protocols.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS7889681B2Methods and devices for improving the multiple spanning tree protocol
Publication Date: 2011.02.15 CISCO TECHNOLOGY INC
  • US7889681B2 patent drawing
  • US7889681B2 patent drawing
  • US7889681B2 patent drawing

AI summary

The present invention provides improved unicast routing, multicast routing and unicast load sharing as compared with conventional methods. Preferred implementations of the invention provide improvements to IEEE 802.1Q. According to preferred aspects of the invention, each bridge is the root of its own multiple spanning tree instance (“MSTI”). Preferred implementations of the invention require no learning of media access control (“MAC”) addresses on the backbone of a network. Some methods of the invention can resolve spanning tree asymmetries. Preferred implementations of the invention require a very low computational load for control protocols.