Single VIP Cluster Load Balancer for Flat and Routed Client Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network solutions require each controller in a cluster to maintain two sets of IP addresses for flat and routed clients, leading to inefficiencies and increased administrative burden.

Innovation Solution

Implement a system where a dedicated client load balancer monitors ARP requests and assigns controllers using a single virtual IP, distinguishing between flat and routed clients based on target VIPs, and applies load balancing logic to manage connections efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If each controller maintains two sets of IP addresses for flat and routed clients, then both client types can be supported, but device complexity increases

Engineering Contradiction:
Improvesupport for both flat and routed clientsVSAvoidIP address management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges the management of flat and routed client IP addresses into a single unified VIP (Virtual IP) address space. Instead of maintaining separate IP address sets for flat and routed clients, the system uses a single VIP that can be reached through multiple paths (direct network connection or via router), thereby reducing device complexity while maintaining support for both client types.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The VIP address is designed to serve multiple functions simultaneously - it can be accessed by both flat clients (through direct network connection) and routed clients (through router gateway). This universal address eliminates the need for separate IP address management for different client types, reducing administrative burden while maintaining versatility.

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

2Ease of operation

If separate IP addresses are used for flat and routed clients, then client identification is simplified, but administrative burden increases

Engineering Contradiction:
Improveclient identificationVSAvoidadministrative burden
Core Design Contradiction:
Ease of operationVSEase of manufacture

Solution Approach 1:

The system combines the identification of flat and routed clients under a single VIP address framework. The load balancer monitors ARP requests and determines client type (flat or routed) based on the request characteristics, eliminating the need for separate IP address management and reducing administrative burden while maintaining clear client identification.

Inventive Principle:
Principle #5Merging (Combining)

3Device complexity

If a single VIP is used for both flat and routed clients, then IP management is simplified, but client differentiation becomes more difficult

Engineering Contradiction:
ImproveIP address managementVSAvoidclient type identification
Core Design Contradiction:
Device complexityVSDifficulty of detecting and measuring

Solution Approach 1:

The load balancer acts as an intermediary that monitors ARP requests and determines client type (flat or routed) based on the request characteristics. This intermediary component enables clear client differentiation and appropriate load balancing decisions while the system maintains a simplified single VIP address structure, resolving the contradiction between simplified IP management and client differentiation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10243915B2Method and system for managing flat and routed clients in a cluster using single type of VIPs
Publication Date: 2019.03.26 DELL PROD LP
  • US10243915B2 patent drawing
  • US10243915B2 patent drawing

AI summary

A method and a system for managing flat and routed clients in a cluster using single virtual IP (VIP) are provided herein. The method includes broadcasting an ARP request from a client to a cluster of nodes; monitoring the broadcasted ARP request at one of the nodes and ignoring the ARP request at all other nodes; in a case that the monitored ARP requests is associated with a different target VIP for same client IP, determining the client associated with the ARP request as a routed client, otherwise the client is determined as a flat client; applying at least one load balancing logic for assigning one of the nodes to the client associated with the ARP request, wherein both flat clients and routed clients are treated as independent clients counted separately; and notifying the client associated with the ARP of a MAC address of the assigned node.