FCoE Device Direct Communication via Name Server MAC Registration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current FCoE standards lack a method for direct communication between FCoE devices without requiring an intermediary like an FCoE Forwarder, and proposed solutions are either technically difficult or costly, such as modifying name servers.
Innovation Solution
Registering FCoE devices with a name server to store their MAC addresses, allowing direct communication by generating and sending fabric login request and reply frames to create a VN_Port and associate MAC addresses for direct frame routing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If FCoE devices use standard FCoE protocols with FCF intermediaries, then communication reliability is maintained, but direct communication capability between FCoE devices is lost
Solution Approach 1:
The patent uses the Name Server as an intermediary to enable direct communication. The Name Server stores MAC address information of FCoE devices and provides this information to initiators, allowing them to communicate directly without FCF intermediaries while maintaining protocol compatibility and reliability
Solution Approach 2:
The patent copies MAC address information from the FCoE target's identity into the Name Server, creating a readable copy that initiators can access. This allows direct address resolution without requiring the target's direct participation in the address resolution process
2Ease of operation
If a new object for storing Ethernet address is added to the Name Server, then direct communication is enabled, but implementation cost and complexity increase significantly
Solution Approach 1:
The patent makes the existing Port_Name object multi-functional by storing both the FC identifier and the Ethernet MAC address in the same object. This eliminates the need for a separate object structure while enabling direct communication, reducing implementation complexity
Solution Approach 2:
The patent changes the content parameter of the existing Port_Name object to include MAC address information alongside the FC identifier. This parameter expansion allows the object to serve dual purposes without requiring structural modifications to the Name Server
3Adaptability or versatility
If all vendors update name servers to support a new object, then direct communication is achieved, but implementation cost increases
Solution Approach 1:
By making the existing Port_Name object multi-functional to store both FC identifiers and MAC addresses, the patent ensures compatibility with existing Name Server implementations across all vendors, eliminating the need for costly updates while enabling direct communication
4Productivity
If FCoE devices require FCF intermediaries for communication, then network service reliability is maintained, but communication efficiency decreases
Solution Approach 1:
The patent extracts the address resolution function from the FCF intermediary and places it in the Name Server. This allows initiators to resolve target addresses independently and communicate directly, improving efficiency while the Name Server maintains reliability through standardized protocols
Data Source
AI summary
Disclosed is an improved mechanism for direct communications and frame routing between FCoE devices within an Ethernet network supporting FCoE protocols. In particular, the methods and systems disclosed herein enable direct communications from one FCoE device to another without going through any intermediary such as an FCF (FCoE Forwarder) that is designed to route traffic between FCoE devices according to the current FCoE standards. This is accomplished by registering the Ethernet MAC address of an FCoE device in a name server via certain objects presently used in an FIP fabric login request, e.g., Port_Name or Node_Name, and other standard-specified objects and functionalities without requiring any changes to the existing FCoE and FC standards.