# US 2022/0030060 A1 · Policy-based forwarding to a load balancer of a load balancing cluster

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0030060 A1
- Document ID: US20220030060A1
- Status: Published application
- Kind: A1
- Application number: 16/938,733
- Filed: 2020-07-24
- Published: 2022-01-27
- Earliest claimed: 2020-07-24
- Assignees: VMware, Inc.
- Applicants: VMware, Inc.
- Inventors: Jayant Jain; Anand Parthasarathy; Mani Kancherla; Anirban Sengupta
- Web page: https://patentgrep.com/patent/US20220030060A1

## CPC

- H04L 67/1023: based on a hash applied to IP addresses or costs
- H04L 12/4633: {Interconnection of networks using encapsulation techniques, e.g. tunneling}
- H04L 12/66: Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
- H04L 47/125: by balancing the load, e.g. traffic engineering
- H04L 47/20: Traffic policing
- H04L 67/1027: Persistence of sessions during load balancing
- H04L 61/2596: Translation of addresses of the same type other than IP, e.g. translation from MAC to MAC addresses
- H04L 2101/622: Layer-2 addresses, e.g. medium access control [MAC] addresses
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Some embodiments of the invention provide a method for forwarding data messages between a client and a server (e.g., between client and server machines and/or applications). In some embodiments, the method receives a data message that a load balancer has directed from a particular client to a particular server after selecting the particular server from a set of several candidate servers for the received data message's flow. The method stores an association between an identifier associated with the load balancer and a flow identifier associated with the message flow, and then forwards the received data message to the particular server. The method subsequently uses the load balancer identifier in the stored association to forward to the particular load balancer a data message that is sent by the particular server. The method of some embodiments is implemented by an intervening forwarding element (e.g., a router) between the load balancer set and the server set.

## Claims

### Claim 1

A method for forwarding data messages between a client and a server, the method comprising:
receiving a first data message that a load balancer has directed from a particular client to a particular server after selecting the particular server from the plurality of candidate servers for a message flow of the received first data message, wherein the load balancer is a particular load balancer selected from a plurality of load balancers by a front-end load balancer;
storing a record associating an identifier associated with the particular load balancer and a flow identifier associated with the message flow, said record for subsequent use in identifying the particular load balancer from the plurality of load balancers as the destination of a responsive second data message from the particular server;
forwarding the data message to the particular server; and
using the load balancer identifier in the stored association to forward to the particular load balancer the responsive second data message that is sent by the particular server.

### Claim 2 (depends on 1)

The method of claim 1, wherein the data message that is sent by the particular server is sent back to the particular client.

### Claim 3 (depends on 1)

The method of claim 1, wherein the plurality of load balancers select servers for message flows received by the load balancers from clients of the servers.

### Claim 4 (depends on 3)

The method of claim 3, wherein the received data message is a first data message of the message flow, and the particular load balancer receives the first data message from a network element that selects, for the message flow, the particular load balancer from the plurality of load balancers.

### Claim 5 (depends on 1)

The method of claim 1, wherein the record specifies a layer 2 redirection of data messages sent from the particular server to the particular client.

### Claim 6 (depends on 5)

The method of claim 5, wherein the record is a policy-based routing record.

### Claim 7 (depends on 5)

The method of claim 5, wherein the record stores a MAC address of the load balancer as the load balancer identifier, and using the load balancer identifier comprises replacing the destination MAC address of the data message sent by the particular server with the MAC address of the particular load balancer.

### Claim 8 (depends on 1)

The method of claim 1, wherein the record is a policy-based routing record that specifies a layer 3 redirection of data messages sent from the particular server to the particular client.

### Claim 9 (depends on 8)

The method of claim 8, wherein the record stores the load balancer identifier, which comprises a tunnel identifier that identifies a tunnel to a device implementing the load balancer, and using the load balancer identifier comprises using the tunnel identifier to identify the tunnel to use to forward the data message sent by the particular server to the load balancer.

### Claim 10 (depends on 1)

The method of claim 1, wherein
the received data message is a first data message and the data message sent by the particular server is the second data message,
the particular server forwards the second data message to a gateway as the particular server,
the receiving, storing, forwarding, and use performed by a forwarding element that receives the second data message and redirects the second data message to the particular load balancer.

### Claim 11 (depends on 10)

The method of claim 10, wherein the forwarding element is a router executing on a host computer along with the particular server.

### Claim 12 (depends on 10)

The method of claim 10, wherein the forwarding element is a router outside of a host computer on which the particular server executes.

### Claim 13 (depends on 10)

The method of claim 10, wherein the forwarding element is the gateway, and the gateway is at a north/south boundary of a network that comprises the particular load balancer and the plurality of candidate servers.

### Claim 14 (depends on 10)

The method of claim 10, wherein the gateway is a default gateway.

### Claim 15 (depends on 1)

The method of claim 1, wherein
the received data message is a first data message and the data message sent by the particular server is the second data message,
the load balancer processes the second data message and forwards the processed second data message back to the particular client.

### Claim 16 (depends on 1)

The method of claim 1, wherein
the message flow is a first message flow,
storing the association comprises creating a record that associates the identifier of the load balancer with a flow identifier of a second message flow that is a reverse flow of the first message flow.

### Claim 17 (depends on 1)

The method of claim 1, wherein the record associates the identifier of the load balancer with a flow identifier of the message flow.

### Claim 18

A non-transitory machine readable medium storing a router program for execution by at least one processing unit of a host computer to forward data messages between a client and a server, the router program comprising sets of instructions for:
receiving a data message that a load balancer has directed from a particular client to a particular server after selecting the particular server from the plurality of candidate servers for a message flow of the received data message, wherein the load balancer is a particular load balancer selected from a plurality of load balancers by a front-end load balancer;
creating and storing a policy-based routing (PBR) record to associate an identifier associated with the particular load balancer and a flow identifier associated with the message flow;
forwarding the received data message to the particular server;
using the PBR record to map a flow identifier of a data message that is sent by the particular server to the load balancer identifier in order to identify the particular load balancer; and
forwarding the sent data message to the identified particular load balancer.

### Claim 19 (depends on 18)

The non-transitory machine readable medium of claim 18, wherein the data message that is sent by the particular server is sent back to the particular client.

### Claim 20 (depends on 18)

The non-transitory machine readable medium of claim 18, wherein
the plurality of load balancers that select servers for message flows received by the load balancers from clients of the servers,
the received data message is a first data message of the message flow, and
the particular load balancer receives the first data message from a network element that selects, for the message flow, the particular load balancer from the plurality of load balancers.

### Claim 21

(canceled)

### Claim 22 (depends on 18)

The non-transitory machine readable medium of claim 18, wherein the policy-based routing record specifies a layer 3 redirection of data messages sent from the particular server to the particular client.
