Flow to Port Affinity Management for Fabric Switch Link Aggregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
High performance network fabric switches with Ethernet Gateway functionality face challenges in managing large numbers of traffic streams and link aggregation policies, leading to hardware component and processing inefficiencies due to the need for extensive traffic flow listing and rebalancing when port states change.
Innovation Solution
A hardware-efficient method utilizing a traffic flow table with index values for link aggregation policies and hash values from packet headers to determine output ports, reducing the need for maintaining state per traffic flow list and allowing for efficient adjustments based on port state changes and policy decisions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the switch maintains detailed state information for each traffic flow list to ensure accurate link aggregation policy enforcement, then traffic isolation and policy compliance are improved, but hardware component usage and processing intensity increase significantly
Solution Approach 1:
The patent extracts only the essential elements needed for policy enforcement (port lists and hash values) from the complete traffic flow state, storing them in a compact flow to port affinity table. This selective extraction maintains policy compliance while dramatically reducing the hardware resources required to track traffic flows through the Ethernet gateway.
Solution Approach 2:
Instead of maintaining complete traffic flow state and deriving port assignments, the patent inverts the approach by pre-configuring port lists for each link aggregation policy and using hash values to directly index into these pre-defined port assignments. This inversion eliminates the need for complex real-time state tracking while preserving policy enforcement.
2Reliability
If the switch tracks every traffic stream through the Ethernet gateway to maintain flow affinity, then traffic isolation is improved, but processing time and rebalancing overhead increase
Solution Approach 1:
The patent uses hash values derived from packet headers as compact representations (copies) of the actual traffic flow identifiers. These hash values serve as efficient keys to lookup port assignments in the flow to port affinity table, eliminating the need to process and track complete traffic flow information while maintaining accurate flow-to-port mapping for isolation purposes.
Solution Approach 2:
The patent performs preliminary configuration of port lists for each link aggregation policy before traffic flows arrive. When packets arrive, the hash-based lookup directly retrieves pre-computed port assignments, eliminating real-time computation and rebalancing overhead while maintaining traffic isolation through consistent flow-to-port affinity.
3Productivity
If the switch uses extensive hardware resources to manage link aggregation for numerous traffic streams, then throughput capacity is improved, but hardware efficiency deteriorates
Solution Approach 1:
The flow to port affinity table serves multiple functions simultaneously: it enforces link aggregation policies, maintains flow affinity for traffic isolation, and provides port selection for load balancing. This multi-functionality eliminates the need for separate hardware components for each function, improving hardware efficiency while maintaining full throughput capacity for managing numerous traffic streams.
Data Source
AI summary
Implementations of the present disclosure involve an apparatus, device, component, and/or method for a hardware efficient flow to port affinity management table for link aggregation for a network fabric switch with Ethernet Gateway functionality. Rather than maintaining a state per traffic flow list, the present disclosure utilizes a handle or hash value derived from the traffic flow and associates an output port state to the hash value. The output port state for the hash value is further associated with a portlist that is based on at least a traffic flow policy of the server or group of servers associated with the traffic flow. In addition, the management table may be adjusted based on state changes to one or more of the output ports such that, if a port becomes unavailable, the management table may be adjusted to account for the unavailability of the port.