Automated Peer Load Balancing via Multicast Teaming
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network architectures face bottlenecks in reliability and throughput due to the limitations of traditional network interface resources, particularly for servers handling high demand, where the cost of implementing high-throughput interfaces is not always cost-effective, and existing load-balancing methods require specialized switches or complex configurations.
Innovation Solution
The method automatically configures peer network devices to load-balance data on a point-by-point basis using teams of network resources, where each device multicasts data frames with peer attributes, updating them as necessary, to achieve load-balancing without the need for specialized switches, enabling efficient data transmission and fault tolerance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional network interface resources are used, then device complexity is reduced, but network throughput and reliability deteriorate
Solution Approach 1:
The system enables automated configuration where network devices autonomously establish load-balancing relationships through multicast message exchange. Each device automatically discovers peers, negotiates parameters, and configures teaming relationships without manual intervention, eliminating complex configuration while achieving high reliability through multiple active network paths
Solution Approach 2:
The system pre-establishes load-balancing relationships and peer associations before actual data transmission begins. Through preliminary multicast exchanges and automated configuration, the network topology is prepared in advance, allowing immediate high-reliability operation without complex runtime configuration
2Productivity
If high-throughput network interfaces are implemented, then network throughput is improved, but cost increases
Solution Approach 1:
The system segments network traffic across multiple standard-speed network interfaces, distributing data flows through teaming relationships. By dividing throughput requirements across multiple affordable interfaces rather than using single high-cost high-throughput interfaces, the system achieves equivalent aggregate bandwidth at lower cost
Solution Approach 2:
The system combines multiple standard network interfaces into teamed configurations that function as unified high-throughput channels. Through load-balancing and traffic aggregation across teamed interfaces, the system achieves high throughput equivalent to expensive single interfaces while using multiple affordable standard interfaces
3Productivity
If specialized switches are used for load-balancing, then network throughput is improved, but device complexity and cost increase
Solution Approach 1:
The system extracts the load-balancing functionality from specialized switches and implements it directly at the endpoint devices through software-based automated configuration. This eliminates the need for expensive specialized switching hardware while maintaining load-balancing throughput through peer-to-peer teaming relationships
Solution Approach 2:
The system uses standardized multicast messages as intermediaries to enable automated load-balancing configuration between peers. These message exchanges serve as mediators that facilitate peer discovery, parameter negotiation, and relationship establishment without requiring specialized switching hardware or complex manual configuration
Data Source
AI summary
A plurality of peer network devices are configured to load-balance data transmitted between them on a point-by-point basis. Each peer device has a team of network resources coupling it to a local area network. A peer device transmitting data to one of the other peer devices load-balances the data over the team of resources of the receiving one of the peer devices. Each peer device multicasts to the other peer devices a data frame from that includes peer data defining attributes of the team of the multicasting peer device. The multicast data frame is updated with new peer data whenever one or more of the attributes of the team of the multicasting peer device are changed.