DCBX Application Network Parameter Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Data Center Bridging (DCB) specifications do not allow centralized configuration of network parameters for applications that do not use industry standard UDP or TCP socket numbers, limiting the availability of DCB features for various types of traffic.
Innovation Solution
A system and method that deploy application network parameters from a network switch to network devices using a modified DCB configuration table and DCBX protocol, enabling DCB features for any application executing on a network device by extending the TLV format to include management parameters, allowing priority and bandwidth management independent of predefined Ethertype or socket numbers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If DCB parameters are centrally configured using DCBX protocol with TLVs, then network administrators can manage priority and bandwidth for standard traffic types, but DCB features remain unavailable for applications that do not use industry standard UDP or TCP socket numbers
Solution Approach 1:
The patent extends the DCBX configuration system to handle multiple traffic identification methods beyond just Ethertype and TCP socket numbers. The modified TLV format can now carry application-specific identifiers including proprietary protocol identifiers, enabling the same configuration infrastructure to serve both standard and custom applications uniformly.
Solution Approach 2:
The patent segments the traffic identification approach by introducing application-specific TLVs that can be selectively applied to different traffic types. This allows the configuration system to divide traffic management into standard traffic (using existing Ethertype/socket methods) and custom application traffic (using new application-specific identifiers), enabling granular control without overwhelming complexity.
2Adaptability or versatility
If DCB configuration is limited to Ethertype and TCP socket number associations, then the configuration system remains simple and standardized, but a variety of applications including virtual machines, e-mail, database, and proprietary protocols cannot access DCB features
Solution Approach 1:
The patent adds a new dimension to traffic identification by introducing application-specific identifiers that operate alongside the existing Ethertype and socket number methods. This creates a multi-layered identification system where traffic can be recognized through multiple possible attributes, significantly expanding the range of applications that can be configured for DCB features.
Solution Approach 2:
The patent introduces an intermediary mechanism in the form of application-specific TLVs that act as mediators between the DCB configuration system and diverse applications. These TLVs translate various application identifiers into a unified configuration format that the DCBX protocol can process, enabling applications with proprietary protocols to integrate seamlessly with the standard DCB framework.
3Ease of operation
If centralized configuration is implemented only for standard traffic types, then network switches can maintain simple configuration management, but virtual machine operations, e-mail, database, and other specialized traffic cannot receive priority and bandwidth management
Solution Approach 1:
The patent makes the configuration system dynamic by allowing the addition of application-specific TLVs without requiring fundamental changes to the DCBX protocol structure. Network administrators can dynamically configure new application types as they emerge, and the system adapts to accommodate different identification methods based on the specific traffic being managed, maintaining ease of operation while improving productivity.
Data Source
AI summary
Information handling system network traffic is managed by populating a DCBX client framework with application network parameters associated with predetermined applications. Network devices, such as information handling system clients and servers, retrieve a TLV from a switch to obtain application network parameters for an application and apply the parameters so that the application executing on the device tags network communications with the associated parameters, such as bandwidth, loss less behavior, priority, latency, through put and CPU utilization.