Dynamic Port Type Detection for Multi-Protocol Network Switches
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Contemporary network switches struggle with auto-detecting link data rates when multiple protocols are involved, leading to configuration errors due to protocol-specific data rate auto-detection and incorrect port attachments.
Innovation Solution
A method and system for dynamic port type detection, where a server initializes a default mode of operation and transmits a link initialization frame with a protocol identifier to a switch port, repeatedly changing the protocol identifier and resetting the wait pulse repetition time until a handshake response is received, allowing for protocol detection and configuration across multiple supported modes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If data rate auto-detection is used with predefined protocol capabilities per port, then Ethernet link data rate can be automatically determined, but it breaks down when multiple protocols are involved leading to configuration errors
Solution Approach 1:
The patent changes the parameter being detected from data rate to protocol type. Instead of assuming predefined protocol capabilities and detecting data rates, the system transmits initialization frames with protocol identifiers and detects the actual protocol type in use, thereby resolving the breakdown that occurs when multiple protocols are involved
Solution Approach 2:
The patent introduces an intermediary mechanism - a link initialization frame containing a protocol identifier - that mediates between the server and switch to enable accurate protocol detection. This intermediary structure allows the system to overcome the limitations of direct protocol-specific auto-detection methods
2Measurement precision
If protocol-specific data rate auto-detection is implemented, then each protocol can be detected accurately, but port attachments are incorrectly configured when multiple protocols are involved
Solution Approach 1:
The system enables self-service configuration by automatically detecting the protocol type through initialization frames and configuring the port accordingly. This eliminates the need for manual configuration and reduces complexity in isolating configuration errors, as the system self-adjusts based on detected protocol identifiers
3Productivity
If a single default protocol mode is set at server initialization, then the system can start operation quickly, but it cannot adapt to different protocol types without manual reconfiguration
Solution Approach 1:
The patent implements dynamic protocol detection by transmitting initialization frames with different protocol identifiers and detecting which protocol type is actually supported. This dynamic approach allows the system to adapt to different protocol types (Ethernet, FCoE, iWARP, RoCE) while maintaining quick initialization, resolving the contradiction between speed and adaptability
Data Source
AI summary
A default mode of operation for a link is set at a server upon initialization. A wait pulse repetition time and number of supported modes of operation are set at the server. A protocol identifier is set to the default mode. A link initialization frame including the protocol identifier is transmitted to a port of a switch. Based on failing to receive a handshake response to acknowledge successful decoding of the protocol identifier from the switch prior to expiration of the wait pulse repetition time: the protocol identifier is changed to a next mode of operation, the wait pulse repetition time is reset, and the link initialization frame is transmitted to the port of the switch. Changing the protocol identifier, resetting the wait pulse repetition time, and transmitting the link initialization frame are repeated until the handshake response is received or all supported modes of operation are checked.