Auto-Enabling BBSC Protocol via Training Frames
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing networking devices in fabrics require manual configuration of protocols like BBSC through CLI commands, which is tedious and burdensome, especially in large networks, leading to inefficiencies in traffic management and credit recovery.
Innovation Solution
Enabling protocols such as BBSC within networking devices using training frames, eliminating the need for CLI commands by embedding requests for protocol enablement in training frames distributed throughout the fabric, allowing peer devices to automatically sync and recover credits as needed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual configuration of protocols like BBSC is performed through CLI commands at each networking device, then protocol enablement can be achieved, but the process becomes tedious and burdensome especially in large fabrics
Solution Approach 1:
The networking devices automatically enable the BBSC protocol through self-service mechanisms. When a device detects credit loss conditions, it autonomously enables BBSC on affected ports without requiring manual CLI configuration, allowing the system to configure itself based on actual operational needs
Solution Approach 2:
The system performs preliminary detection of credit loss conditions and proactively enables BBSC protocol before traffic loss occurs. By monitoring credit states in advance and automatically enabling the protocol when needed, the system prevents harmful effects rather than reacting after problems arise
2Adaptability or versatility
If manual configuration is performed on individual switches or ports via CLI commands, then protocol control is achieved, but the process is time-consuming in large fabrics
Solution Approach 1:
The system segments the protocol enablement process by port and device, enabling BBSC selectively only on ports experiencing credit loss conditions rather than configuring the entire fabric uniformly. This targeted approach reduces configuration time while maintaining necessary control
Solution Approach 2:
The system implements feedback mechanisms where networking devices continuously monitor credit states and automatically adjust BBSC protocol enablement based on real-time conditions. This closed-loop approach eliminates manual configuration time while maintaining precise protocol control through automated detection and response
3Reliability
If BBSC protocol is enabled manually on each device, then buffer state management can be monitored, but administrative burden increases significantly
Solution Approach 1:
Networking devices automatically monitor their own buffer states and credit conditions, enabling self-service buffer management without external administrative intervention. The devices independently detect credit loss and enable BBSC protocol as needed, eliminating the burden of manual configuration while maintaining reliable buffer state management
Solution Approach 2:
The system merges the functions of credit monitoring, protocol enablement decision-making, and BBSC activation into a single automated process within each networking device. This consolidation reduces administrative burden by combining multiple manual tasks into one self-executing system
Data Source
AI summary
In one embodiment, a first networking device sends, to a second networking device, a training frame of a transmitter training signal (TTS) that includes a request for the second networking device to enable a protocol on the second networking device. In addition, the first networking device receives, from the second networking device, an indication that the second networking device has enabled the protocol on the second networking device. The first networking device may also send, using the protocol, first flow-control information indicating a number of data packets sent by the first networking device to the second networking device and a number of acknowledgments received from the second networking device, in addition to receiving second flow-control information indicating a number of data packets received at the second networking device from the first networking device and a number of acknowledgments sent by the second networking device to the first networking device.