# US 2026/0089093 A1 · BGP Backup Path Selection Excluding Fate Shared Paths

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

- Number: US 2026/0089093 A1
- Document ID: US20260089093A1
- Status: Published application
- Kind: A1
- Application number: 18/897,570
- Filed: 2024-09-26
- Published: 2026-03-26
- Earliest claimed: 2024-09-26
- Assignees: Arista Networks, Inc.
- Applicants: Arista Networks, Inc.
- Inventors: Megha SINHA; Qing YANG
- Web page: https://patentgrep.com/patent/US20260089093A1

## CPC

- H04L 45/28: using route fault recovery
- H04L 45/04: {Interdomain routing, e.g. hierarchical routing}
- H04L 45/22: {Alternate routing}
- H04L 45/24: Multipath
- H04L 45/748: using longest matching prefix
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Techniques for performing Border Gateway Protocol (BGP) backup path selection are provided. In one set of embodiments, a BGP speaker can select a best path for an Internet Protocol (IP) prefix and can determine that the best path is in a first fate shared group comprising a group of paths that are vulnerable to a common failure. The BGP speaker can then determine one or more candidate backup paths that are in a second fate shared group different from the first fate shared group (or are not in any fate shared group) and can select at least one of the one or more candidate backup paths as a backup path for the IP prefix.

## Claims

### Claim 1

A method performed by a network device that implements Border Gateway Protocol (BGP), the method comprising:
selecting a best path for an Internet Protocol (IP) prefix, the best path being a preferred network route for reaching a destination device or network identified by the IP prefix;
determining whether the best path is in a fate shared group comprising a group of paths that are vulnerable to a common failure;
upon determining that the best path is in a fate shared group, determining whether any candidate backup paths in a list of candidate backup paths for the IP prefix are not in the fate shared group; and
upon determining that at least one candidate backup path in the list of candidate backup paths is not in the fate shared group:
identifying a subset of candidate backup paths in the list that are not in the fate shared group; and
selecting one or more candidate backup paths from the subset as backup paths for the IP prefix.

### Claim 2 (depends on 1)

The method of claim 1 further comprising, upon determining that the best path is not in a fate shared group:
selecting one or more candidate backup paths in the list as backup paths for the IP prefix.

### Claim 3 (depends on 1)

The method of claim 1 further comprising, upon determining that all candidate backup paths in the list of candidate backup paths are in the fate shared group:
selecting one or more candidate backup paths in the list as backup paths for the IP prefix.

### Claim 4 (depends on 1)

The method of claim 1 wherein determining whether the best path is in a fate shared group comprises:
determining whether the best path is associated with a fate shared group identifier in a fate shared group configuration maintained on the network device.

### Claim 5 (depends on 1)

The method of claim 1 wherein determining whether any candidate backup paths in a list of candidate backup paths for the IP prefix are not in the fate shared group comprises:
determining whether any candidate backup paths in the list are associated with a same fate shared group identifier as the best path in a fate shared group configuration maintained on the network device.

### Claim 6 (depends on 1)

The method of claim 1 wherein the fate shared group is locally configured on the network device.

### Claim 7 (depends on 1)

The method of claim 1 wherein the fate shared group is defined based on information received via one or more route advertisement packets sent by one or more BGP peers of the network device.

### Claim 8 (depends on 7)

The method of claim 7 wherein each of the one or more route advertisement packets includes a path and a routing attribute for the path that identifies the fate shared group.

### Claim 9 (depends on 8)

The method of claim 8 wherein the routing attribute is a BGP community attribute.

### Claim 10

A network device that implements Border Gateway Protocol (BGP), the network device comprising:
a central processing unit (CPU);
a non-volatile storage; and
a main memory having stored thereon program code that, when executed by the CPU, causes the CPU to:
select a best path for an Internet Protocol (IP) prefix, the best path being a preferred network route for reaching a destination device or network identified by the IP prefix;
determine whether the best path is in a fate shared group comprising a group of paths that are vulnerable to a common failure;
upon determining that the best path is in a fate shared group, determine whether any candidate backup paths in a list of candidate backup paths for the IP prefix are not in the fate shared group; and
upon determining that at least one candidate backup path in the list of candidate backup paths is not in the fate shared group:
identify a subset of candidate backup paths in the list that are not in the fate shared group; and
select one or more candidate backup paths from the subset as backup paths for the IP prefix.

### Claim 11 (depends on 10)

The network device of claim 10 wherein the program code further causes the CPU to, upon determining that the best path is not in a fate shared group:
select one or more candidate backup paths in the list as backup paths for the IP prefix.

### Claim 12 (depends on 10)

The network device of claim 10 wherein the program code further causes the CPU to, upon determining that all candidate backup paths in the list of candidate backup paths are in the fate shared group:
select one or more candidate backup paths in the list as backup paths for the IP prefix.

### Claim 13 (depends on 10)

The network device of claim 10 wherein the program code that causes the CPU to determine whether the best path is in a fate shared group comprises program code that causes the CPU to:
determine whether the best path is associated with a fate shared group identifier in a fate shared group configuration maintained on the network device.

### Claim 14 (depends on 10)

The network device of claim 10 wherein the program code that causes the CPU to determine whether any candidate backup paths in a list of candidate backup paths for the IP prefix are not in the fate shared group comprises program code that causes the CPU to:
determine whether any candidate backup paths in the list are associated with a same fate shared group identifier as the best path in a fate shared group configuration maintained on the network device.

### Claim 15 (depends on 10)

The network device of claim 10 wherein the fate shared group is locally configured on the network device.

### Claim 16 (depends on 10)

The network device of claim 10 wherein the fate shared group is defined based on information received via one or more route advertisement packets sent by one or more BGP peers of the network device.

### Claim 17 (depends on 16)

The network device of claim 16 wherein each of the one or more route advertisement packets includes a path and a routing attribute for the path that identifies the fate shared group.

### Claim 18 (depends on 17)

The network device of claim 17 wherein the routing attribute is a BGP community attribute.

### Claim 19

A method performed by a network device that implements Border Gateway Protocol (BGP), the method comprising:
selecting a best path for an Internet Protocol (IP) prefix, the best path being a preferred network route for reaching a destination device or network identified by the IP prefix;
determining that the best path is in a first fate shared group comprising a group of paths that are vulnerable to a common failure;
determining one or more candidate backup paths that are in a second fate shared group different from the first fate shared group, or are not in any fate shared group; and
selecting at least one of the one or more candidate backup paths as a backup path for the IP prefix.

### Claim 20 (depends on 19)

The method of claim 19 wherein the first and second fate shared groups are locally configured on the network device or are defined based on information received via one or more route advertisement packets.
