Automated MSTP Configuration via Master Reconfiguration Network Device

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Configuring and maintaining Multi-instance Spanning Tree Protocol (MSTP) in networks is difficult due to the need for manual configuration, which is prone to errors and can cause network disruptions, especially when users are locked out of devices or lack local access.

Innovation Solution

A system where a master reconfiguration network device (MRD) collects network data to build an MSTP configuration, verifies its application across network devices, and enables automatic reconfiguration, including disabling and re-enabling links, to ensure stability and resilience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual configuration of MSTP is performed on each network device, then configuration flexibility is improved, but configuration complexity and error rate increase

Engineering Contradiction:
Improveconfiguration flexibilityVSAvoidconfiguration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

An application server acts as an intermediary between network administrators and network devices. The application server collects MSTP configuration data, processes it according to network topology, and automatically distributes configurations to all relevant devices. This mediator eliminates the need for manual configuration on each device while maintaining configuration flexibility through centralized control.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables self-service automatic configuration where the network infrastructure automatically obtains and applies MSTP configurations without requiring manual intervention on each device. The application server autonomously collects data, determines topology, and pushes configurations, allowing the system to configure itself while maintaining adaptability.

Inventive Principle:
Principle #25Self-service

2Stability of the object's composition

If manual configuration is performed from farthest device to nearest device, then network stability is improved during configuration, but configuration time and productivity decrease

Engineering Contradiction:
Improvenetwork stability during configurationVSAvoidconfiguration speed
Core Design Contradiction:
Stability of the object's compositionVSProductivity

Solution Approach 1:

The application server performs preliminary actions by collecting all necessary MSTP configuration data and analyzing network topology before actual configuration deployment. This preliminary data collection and topology determination phase allows the system to prepare complete configuration sets for all devices, enabling parallel deployment that maintains stability while improving productivity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically adapts the configuration deployment process based on network topology analysis. Rather than following a fixed sequential order, the application server determines the optimal configuration sequence and parallel execution strategy based on real-time network conditions and device relationships, maintaining stability while maximizing configuration speed.

Inventive Principle:
Principle #15Dynamics

3Productivity

If MSTP configuration is pushed to all network devices simultaneously, then configuration time is reduced, but network disruption and reliability risks increase

Engineering Contradiction:
Improveconfiguration speedVSAvoidnetwork reliability during configuration
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The application server segments the configuration deployment process into distinct phases: data collection, topology analysis, configuration generation, and staged deployment. This segmentation allows simultaneous configuration preparation for multiple devices while controlling actual deployment to prevent network disruption, balancing speed with reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements feedback mechanisms where the application server monitors configuration acceptance and network status in real-time. Based on this feedback, the server can adjust deployment timing, rollback failed configurations, or notify administrators of potential issues, maintaining reliability while enabling fast configuration updates.

Inventive Principle:
Principle #23Feedback

4Reliability

If physical access is required for device configuration when user is locked out, then security is improved, but ease of operation and maintenance decrease

Engineering Contradiction:
ImprovesecurityVSAvoidease of maintenance
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The application server serves as a secure intermediary that manages device access and configuration deployment. When a user is locked out, the application server can still push configurations to devices through existing authenticated sessions or scheduled maintenance windows, eliminating the need for physical access while maintaining security through centralized authentication and authorization controls.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10050841B2Applying a multi-instance spanning tree protocol (MSTP) configuration
Publication Date: 2018.08.14 HEWLETT PACKARD ENTERPRISE DEV LP
  • US10050841B2 patent drawing
  • US10050841B2 patent drawing
  • US10050841B2 patent drawing

AI summary

Applying an MSTP configuration can include instructing a plurality of network devices to disable non-MSTP links in response to a verification of receipt of the MSTP configuration and instructing the plurality of network devices to apply the MSTP configuration in response to a verification that each of the plurality of network devices disabled the non-MSTP links.