Congestion Notification Across Layer-2 Domains
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Congestion notification mechanisms, as defined by IEEE 802.1Qau, are ineffective in networks with multiple layer-2 domains, as they terminate at devices operating above layer 2, such as IP routers or Fibre Channel Forwarders, preventing congestion notifications from reaching end stations across different layer-2 domains.
Innovation Solution
The system modifies and routes congestion notification messages by generating a new layer-2 header based on the source address information, allowing CNMs to be forwarded across routers and Fibre Channel Forwarders, enabling them to reach the correct source end station by looking up the source IP or FC address and maintaining consistent VLAN IDs across FCoE fabrics.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If congestion notification messages are sent across multiple layer-2 domains using standard IEEE 802.1Qau mechanism, then congestion detection capability is improved, but the messages terminate at layer-3 devices (routers/FCFs) and cannot reach end stations, causing delivery failure
Solution Approach 1:
The patent introduces an intermediary mechanism where layer-3 devices (routers/FCFs) act as mediators that receive CNM messages, extract source address information, and forward them to the correct end stations. This intermediary approach allows CNM messages to traverse layer-3 boundaries while maintaining end-to-end delivery capability across multiple layer-2 domains.
Solution Approach 2:
The patent extends the traditional layer-2 confined CNM mechanism into the layer-3 dimension by allowing routers/FCFs to process and forward CNM messages. This dimensional transition enables congestion notification to operate across both layer-2 and layer-3 boundaries, solving the domain isolation problem.
2Ease of operation
If congestion notification messages are modified to include source address information for routing across domains, then message routing capability is improved, but message format complexity increases
Solution Approach 1:
The patent makes CNM messages multi-functional by enabling them to carry both traditional layer-2 addressing information and layer-3 source address information. This universality allows the same message format to serve both layer-2 local delivery and layer-3 cross-domain routing purposes without requiring separate message types.
Solution Approach 2:
The patent segments the addressing information into distinct fields within the CNM message structure, separating layer-2 MAC addresses from layer-3 IP or FC addresses. This segmentation allows receiving devices to selectively process only the addressing layer they operate at, reducing the effective complexity each device must handle.
3Ease of manufacture
If standard CNM mechanism is used within single layer-2 domain, then implementation simplicity is maintained, but congestion management effectiveness deteriorates in multi-domain networks
Solution Approach 1:
The patent applies preliminary action by pre-configuring routers/FCFs with source address to layer-2 address mapping information before CNM messages arrive. This pre-preparation enables these devices to quickly and efficiently forward CNM messages without complex real-time lookups, maintaining implementation simplicity while extending effectiveness to multi-domain networks.
Data Source
AI summary
One embodiment of the present invention provides a congestion notification. During operation, the system receives a congestion notification message with a destination layer-2 address set as the receiving mechanism's layer-2 address. The system modifies a destination layer-2 address, a source layer-2 address, and optionally a VLAN identifier of the congestion notification message, and forwards the modified congestion notification message.