Automated DCB Configuration State Machine for Access Switches

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Data Center Bridging (DCB) configuration of access switches relies heavily on manual provisioning, which is time-consuming and costly, especially when switches are replaced or rebooted, leading to potential disruptions and incomplete propagation of DCB configurations.

Innovation Solution

An automated state machine-based system for access switches that manages DCB configuration by transitioning between DCB disabled, downstream, and upstream states based on received network packets, enabling automatic determination and propagation of DCB configurations without manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If manual provisioning is used for DCB configuration, then configuration accuracy can be ensured, but time consumption and cost increase significantly

Engineering Contradiction:
ImproveDCB configuration accuracyVSAvoidDCB configuration time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The access switch automatically performs DCB configuration by receiving DCB configuration packets from peer devices, extracting configuration information, and applying it without human intervention. This self-service mechanism eliminates manual provisioning while maintaining configuration accuracy through automated validation and application processes.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

DCB configuration information is pre-packaged in standardized DCB configuration packets that contain all necessary parameters. When the access switch receives these packets, the configuration is already prepared and validated, enabling rapid automated application without requiring manual analysis or preparation steps.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If manual provisioning is used for DCB configuration, then configuration completeness can be ensured, but operational complexity increases

Engineering Contradiction:
ImproveDCB configuration completenessVSAvoidDCB configuration ease
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The automated system receives DCB configuration packets from peer devices, automatically extracts configuration parameters, validates completeness, and applies the configuration. This self-service process ensures configuration completeness through automated validation while eliminating the operational complexity of manual provisioning steps.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The access switch monitors the DCB configuration process by receiving configuration packets, validating the received parameters, and confirming successful application. This feedback mechanism ensures configuration completeness by verifying that all necessary parameters are present and correctly applied, while maintaining ease of operation through automated monitoring.

Inventive Principle:
Principle #23Feedback

3Productivity

If automated DCB configuration is implemented, then productivity increases, but system complexity increases

Engineering Contradiction:
ImproveDCB configuration speedVSAvoidDCB configuration system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The access switch autonomously performs the entire DCB configuration process by receiving standardized configuration packets, automatically extracting parameters, validating completeness, and applying configurations without human intervention. This self-service approach dramatically increases productivity while managing system complexity through standardized protocols and automated validation logic.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

DCB configuration information is pre-structured in standardized packets containing all necessary parameters before transmission. This preliminary organization of configuration data enables the access switch to rapidly process and apply configurations automatically, increasing productivity while reducing the complexity of configuration management through consistent data formats.

Inventive Principle:
Principle #10Preliminary action

4Stability of the object's composition

If manual provisioning is used for DCB configuration, then configuration consistency can be maintained, but downtime increases during switch replacement or reboot

Engineering Contradiction:
ImproveDCB configuration consistencyVSAvoidNetwork downtime
Core Design Contradiction:
Stability of the object's compositionVSLoss of time

Solution Approach 1:

DCB configuration information is pre-packaged in standardized DCB configuration packets that contain all necessary parameters for consistent configuration. When switches are replaced or rebooted, these pre-prepared configuration packets enable rapid reconfiguration, maintaining consistency while minimizing downtime through automated application processes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The access switch automatically receives and applies DCB configuration packets from peer devices after replacement or reboot, ensuring configuration consistency without requiring manual re-provisioning. This self-service mechanism maintains stable DCB configuration composition while eliminating the downtime associated with manual configuration processes.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9553763B2System and method for automated DCB configuration of access switches
Publication Date: 2017.01.24 DELL PROD LP
  • US9553763B2 patent drawing
  • US9553763B2 patent drawing
  • US9553763B2 patent drawing

AI summary

A system and method of automated Data Center Bridging (DCB) configuration of an access switch includes a control unit, a memory, and a port configured to couple the access switch to a peer device. The control unit is configured to operate the port according to a state machine including a DCB disabled state, a DCB downstream state, and a DCB upstream state. When the port is in the DCB disabled state, the control unit exchanges network traffic on the port without any DCB extensions. When the port is in the DCB upstream state, the control unit exchanges network traffic on the port using DCB extensions based on the DCB configuration and receives the DCB configuration from the peer device. When the port is in the DCB downstream state, the control unit exchanges network traffic on the port using the DCB extensions and transmits the DCB configuration to the peer device.