# US 2020/0403923 A1 · System and method for multi-path load balancing in network fabrics

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

- Number: US 2020/0403923 A1
- Document ID: US20200403923A1
- Status: Published application
- Kind: A1
- Application number: 17/007,526
- Filed: 2020-08-31
- Published: 2020-12-24
- Earliest claimed: 2013-11-05
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Mohammadreza Alizadeh Attar; Thomas J. Edsall; Sarang M. Dharmapurikar; Janakiramanan Vaidyanathan
- Web page: https://patentgrep.com/patent/US20200403923A1

## CPC

- H04L 47/125: by balancing the load, e.g. traffic engineering
- H04L 45/38: {Flow based routing}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In accordance with one embodiment, a source leaf device receives a packet. The source leaf device identifies a flowlet associated with the packet and a destination leaf device to which the packet is to be transmitted. The source leaf device may determine whether the flowlet is a new flowlet. The source leaf device may select an uplink of the source leaf device via which to transmit the flowlet to the destination leaf device according to whether the flowlet is a new flowlet. The source leaf device may then transmit the packet to the destination leaf device via the uplink.

## Claims

### Claim 1

A method comprising:
ascertaining available bandwidth associated with a plurality of uplinks of a first device;
selecting a path of a plurality of paths from the plurality of uplinks to transmit a flowlet to a second device based at least in part on the available bandwidth;
encapsulating one or more packets of the flowlet with a header, the header including a plurality of fields including a load-balancing tag field, the load-balancing tag field including an identifier representing the plurality of paths; and
transmitting the one or more packets via the path.

### Claim 2 (depends on 1)

The method as recited in claim 1, wherein the selecting of the one of the path is based, at least in part, upon a level of congestion of the plurality of paths between the first device and the second device.

### Claim 3 (depends on 1)

The method as recited in claim 1, wherein each path of the plurality of paths is associated with an uplink of the plurality of uplinks.

### Claim 4 (depends on 1)

The method as recited in claim 1, further comprising:
maintaining a remote congestion metrics indicating a level of congestion associated the plurality of uplinks.

### Claim 5 (depends on 1)

The method as recited in claim 1, wherein the selecting of the path includes comparing the remote congestion metrics for each of the plurality of uplinks with remote congestion metrics associated with a previously selected path from one of the plurality of uplinks.

### Claim 6 (depends on 5)

The method as recited in claim 5, wherein the previously selected path from one of the plurality of uplinks is selected when the remote congestion metrics for each of the plurality of uplinks does not provide at least a minimum amount of improvement over the previously selected path from one of the plurality of uplinks.

### Claim 7 (depends on 1)

The method as recited in claim 1, wherein the header does not contain congestion information for every path between a source and destination devices.

### Claim 8

A system comprising:
at least one processor; and
at least one memory storing instructions which when executed by the at least one processor causes the at least one processor to:
ascertain available bandwidth associated with a plurality of uplinks of a first device;
select a path of a plurality of paths from the plurality of uplinks to transmit a flowlet to a second device based at least in part on the available bandwidth;
encapsulate one or more packets of the flowlet with a header, the header including a plurality of fields including a load-balancing tag field, the load-balancing tag field including an identifier representing the plurality of paths; and
transmit the one or more packets via the path.

### Claim 9 (depends on 8)

The system as recited in claim 8, wherein the selection of the one of the path is based, at least in part, upon a level of congestion of the plurality of paths between the first device and the second device.

### Claim 10 (depends on 8)

The system as recited in claim 8, wherein each path of the plurality of paths is associated with an uplink of the plurality of uplinks.

### Claim 11 (depends on 8)

The system as recited in claim 8, further comprising instructions which when executed causes the at least one processor to:
maintain a remote congestion metrics indicating a level of congestion associated the plurality of uplinks.

### Claim 12 (depends on 8)

The system as recited in claim 8, wherein the selection of the path includes a comparison of the remote congestion metrics for each of the plurality of uplinks with remote congestion metrics associated with a previously selected path from one of the plurality of uplinks.

### Claim 13 (depends on 12)

The system as recited in claim 12, wherein the previously selected path from one of the plurality of uplinks is selected when the remote congestion metrics for each of the plurality of uplinks does not provide at least a minimum amount of improvement over the previously selected path from one of the plurality of uplinks.

### Claim 14 (depends on 9)

The system as recited in claim 9, wherein the header does not contain congestion information for every path between a source and destination devices.

### Claim 15

At least one non-transitory computer readable medium storing instructions which when executed by at least one processor causes the at least one processor to:
ascertain available bandwidth associated with a plurality of uplinks of a first device;
select a path of a plurality of paths from the plurality of uplinks to transmit a flowlet to a second device based at least in part on the available bandwidth;
encapsulate one or more packets of the flowlet with a header, the header including a plurality of fields including a load-balancing tag field, the load-balancing tag field including an identifier representing the plurality of paths; and
transmit the one or more packets via the path.

### Claim 16 (depends on 15)

The at least one non-transitory computer readable medium as recited in claim 15, wherein the selection of the one of the path is based, at least in part, upon a level of congestion of the plurality of paths between the first device and the second device.

### Claim 17 (depends on 15)

The at least one non-transitory computer readable medium as recited in claim 15, wherein each path of the plurality of paths is associated with an uplink of the plurality of uplinks.

### Claim 18 (depends on 15)

The at least one non-transitory computer readable medium as recited in claim 15, further comprising instructions which when executed causes the at least one processor to:
maintain a remote congestion metrics indicating a level of congestion associated the plurality of uplinks.

### Claim 19 (depends on 15)

The at least one non-transitory computer readable medium as recited in claim 15, wherein the selection of the path includes a comparison of the remote congestion metrics for each of the plurality of uplinks with remote congestion metrics associated with a previously selected path from one of the plurality of uplinks.

### Claim 20 (depends on 15)

The at least one non-transitory computer readable medium as recited in claim 15, wherein the header does not contain congestion information for every path between a source and destination devices.
