NAT Interface Group Load Balancing for Data Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing link aggregation methods, such as LACP, are cumbersome to configure, do not deliver full bandwidth, and are limited to single IP addresses, making them inefficient for load balancing and failover in networked data backup systems, especially across NAT networks.

Innovation Solution

The ifgroup method, which uses link aggregation to distribute backup-application client connections across multiple network interfaces while maintaining VLAN isolation, allowing for dynamic load balancing and failover without additional overhead, and supports multiple IP addresses for efficient operation across NAT networks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If LACP link aggregation is used to combine multiple network connections, then redundancy and load sharing are provided, but configuration becomes cumbersome and complex

Engineering Contradiction:
Improveconnection reliabilityVSAvoidconfiguration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent combines multiple IP addresses into a single logical interface group that can be treated as one unit. This interface group acts as a unified network interface while internally distributing traffic across multiple physical connections, eliminating the need for complex LACP configuration at each network hop.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces an intermediary interface group layer between the application layer and physical network interfaces. This intermediary handles the complexity of multi-connection management, providing a simple single-interface view to applications while managing multiple underlying connections through NAT and connection tracking.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If LACP link aggregation is used to increase throughput, then bandwidth is improved, but full bandwidth of all interfaces is not delivered

Engineering Contradiction:
ImprovethroughputVSAvoidbandwidth utilization efficiency
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent implements dynamic connection distribution where the system actively monitors and adjusts traffic distribution across multiple network interfaces in real-time. This dynamic approach ensures optimal utilization of available bandwidth by adapting to current network conditions and interface availability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the operational parameters by using multiple IP addresses associated with a single interface group, allowing traffic to be distributed across different network paths. This parameter change enables full utilization of aggregate bandwidth by bypassing LACP's bandwidth limitations.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If LACP link aggregation is used for load sharing, then data traffic distribution is provided, but changes require taking interfaces offline for configuration

Engineering Contradiction:
Improveload sharing capabilityVSAvoidconfiguration downtime
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent performs preliminary configuration by pre-establishing the interface group with multiple associated IP addresses before traffic needs to be distributed. This allows the system to be ready for load sharing without requiring interface take-down during configuration changes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements self-service configuration where the system automatically manages the interface group and its associated connections. The system can dynamically add or remove IP addresses from the interface group without manual intervention or interface downtime, as the NAT and connection tracking infrastructure handles the transitions automatically.

Inventive Principle:
Principle #25Self-service

4Reliability

If LACP link aggregation is used to provide redundancy, then failover capability is improved, but the system is very sensitive to network errors

Engineering Contradiction:
Improvefailover capabilityVSAvoidnetwork error sensitivity
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent creates multiple IP address copies associated with a single interface group, providing redundancy at the logical level rather than requiring physical link aggregation. This copying approach distributes traffic across multiple network paths without the sensitivity to network errors that plagues LACP, as each IP address can be independently managed and failed over.

Inventive Principle:
Principle #26Copying

5Adaptability or versatility

If LACP link aggregation is used to bundle physical ports, then a single logical channel is formed, but it is limited to only one IP address

Engineering Contradiction:
Improvelogical channel formationVSAvoidconfiguration operations at each network hop
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent makes the interface group universal by associating it with multiple IP addresses, allowing a single logical interface to serve multiple network functions and address spaces. This multi-functional interface group can represent entire networks or subnets while maintaining a single point of configuration, eliminating the need for configuration at each network hop.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS10225331B1Network address translation load balancing over multiple internet protocol addresses
Publication Date: 2019.03.05 EMC IP HLDG CO LLC
  • US10225331B1 patent drawing
  • US10225331B1 patent drawing
  • US10225331B1 patent drawing

AI summary

Embodiments for a method of providing load balancing over multiple network addresses across an network address translation (NAT) network including a data storage system, that defines an interface group identifying a private network for one or more clients to communicate with a host for read/write operations, configuring, in the server, pre-NAT IP (Internet Protocol) addresses for the one or more clients and adding them to the interface group, upon receiving a client hostname, returning an interface group an IP address to the client that it can use it for a data transfer operation to the data storage system, and incrementing the pre-NAT addresses after the client starts the data transfer operation such that the least used address in the interface group is always selected for the client so as to maintain load-balance across the plurality of clients.