Switch Fabric Load Balancing for Data Center Traffic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current load-balancing technologies do not effectively scale for East-West traffic in data center switch fabrics, requiring external, costly load-balancers and lacking resilience for non-responsive servers.
Innovation Solution
A programmable network fabric with pervasive load balancing (PLB) that distributes servers, virtual machines, and containers across the fabric, using switches to load balance traffic by matching IP address and Layer 3/4 fields, and automatically rerouting traffic to standby nodes upon server failure, with each switch acting as a load balancer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If external load-balancers are used for East-West traffic, then load balancing capability is provided, but system cost and complexity increase
Solution Approach 1:
The patent makes the switch fabric itself perform load balancing functions that were previously required from external dedicated load balancer devices. Each switch in the fabric is configured to independently perform load balancing decisions for traffic flows, eliminating the need for separate external load-balancing infrastructure and reducing overall system complexity while maintaining load balancing capability.
Solution Approach 2:
The switch fabric serves itself by implementing load balancing natively within the switching infrastructure. The switches monitor traffic patterns and automatically distribute East-West traffic across available paths and destinations without requiring external control devices, enabling the system to self-manage load balancing operations.
2Productivity
If traditional load-balancing technologies are used, then basic load distribution is achieved, but scalability for data center East-West traffic is limited
Solution Approach 1:
The patent divides the load balancing function into distributed segments across multiple switches in the fabric. Each switch independently performs load balancing for its local traffic flows rather than relying on a centralized load balancer, enabling the system to scale with the fabric size and handle increasing East-West traffic volumes efficiently.
Solution Approach 2:
The patent extends load balancing from traditional North-South traffic patterns to multi-dimensional East-West traffic flows within the data center fabric. By implementing load balancing at the fabric level rather than at perimeter points, the system gains the ability to dynamically route traffic across multiple spatial dimensions and paths within the switching fabric.
3Productivity
If servers are distributed across the fabric, then resource utilization improves, but traffic routing complexity increases
Solution Approach 1:
The patent pre-configures load balancing policies and routing rules in the switch fabric before traffic flows are established. The switches are programmed with load balancing algorithms and destination mappings that enable automatic traffic distribution to distributed servers without requiring complex real-time routing decisions, simplifying the routing process while maintaining efficient resource utilization.
Data Source
AI summary
A switch/switching fabric is configured to load balance traffic. The switch fabric includes a plurality of switches. A packet is received at a first switch of the plurality of switches. The first switch load balances the packet to a particular entity among a plurality of entities. Each of the entities is connected to one of the plurality of switches. The first switch determines a particular switch of the plurality of switches to which the packet should be directed, the particular entity being connected to the particular switch of the plurality of switches. The particular switch receives the packet, and determines which interface of the particular switch to direct the packet to the particular entity. The plurality of entities include servers and network appliances as physical devices or virtual machines.


