Avoiding loops by preventing further fast reroute (FRR) after an earlier FRR

Patent metadata

Field	Value
Publication number	US-12425331-B2
Application number	US-202318505070-A
Country	US
Kind code	B2
Filing date	Nov 8, 2023
Priority date	Dec 31, 2019
Publication date	Sep 23, 2025
Grant date	Sep 23, 2025

Abstract

In some cases, once Fast Reroute (FRR) has taken place (e.g., for MPLS protection), a further FRR is undesirable, and even detrimental. A mechanism to prevent a further FRR, once such a further FRR is determined to be potentially harmful, is described.

First claim

What is claimed is:

1. A system, the system comprising a data forwarding device including:
a) at least one communications interface;
b) at least one processor; and
c) at least one storage device storing processor-executable instructions which, when executed by the at least one processor, cause the at least one processor to perform a method for avoiding loops in a communications network, the method including:
1) receiving, by the data forwarding device, a data packet to be forwarded over a label-switched path (LSP);
2) determining, by the data forwarding device, a next hop of the data packet received;
3) determining, by the data forwarding device, whether or not the next hop is reachable; and
4) responsive to determining that the next hop is not reachable,
A) determining, by the data forwarding device (i) a backup next hop associated with the next hop that is not reachable and (ii) a forwarding label associated with the backup next hop, and
B) adding to the data packet, (1) the forwarding label and (2) a loop prevention label indicating that a backup detour is being made, to generate an updated data packet, wherein the loop prevention label is one of (A) a special purpose label, or (B) an extended special purpose label, and
C) forwarding, by the data forwarding device, the updated data packet to the backup next hop, and

otherwise, responsive to determining that the next hop is reachable, forwarding the data packet using a forwarding label associated with the next hop.

2. The system of claim 1 , wherein the data forwarding device is a provider edge device of a transport network to which a customer edge device is multihomed,
the system further comprising:
a second provider edge device of the transport network to which the customer edge device is multihomed,
wherein the backup next hop at the provider edge device associated with a next hop set to the customer edge device is set to the second provider edge device such that a backup is provisioned between the provider edge device and the second provider edge device,
wherein the second provider edge device has a backup next hop set to the provider edge device associated with a next hop set to the customer edge device, and
wherein the loop prevention label prevents the second provider edge device from sending the data packet back to the provider edge device.

3. The system of claim 1 wherein the backup next hop is part of a Segment Routing (SR) backup tunnel or a Source Packet Routing in NetworkinG (SPRING) backup tunnel, and
wherein the loop prevention label is a special purpose label, but not an extended special purpose label.

4. The system of claim 1 , wherein the data forwarding device is a node on a protection ring.

5. The system of claim 4 , wherein the next hop at the data forwarding device is an adjacent node that is either (A) clockwise of the data forwarding device on the protection ring or (B) counterclockwise of the data forwarding device on the protection ring.

6. The system of claim 5 , further comprising:
a second data forwarding device which is a node on the protection ring,
wherein the second data forwarding device has a backup next hop which is either (A) counterclockwise of the second data forwarding device on the protection ring or (B) clockwise of the second data forwarding device on the protection ring.

7. The system of claim 6 , wherein the loop prevention label:
prevents the second data forwarding device from sending the data packet clockwise on the protection ring if the data forwarding device has sent it on the backup next hop that is counterclockwise of the data forwarding device on the protection ring, or
prevents the second data forwarding device from sending the data packet counterclockwise on the protection ring if the data forwarding device has sent it on the backup path that is clockwise of the data forwarding device on the protection ring.

8. The system of claim 1 , wherein, responsive to determining that the next hop is reachable, the data packet is forwarded using the forwarding label associated with the next hop but without using a further label indicating that a backup detour is not being made.

9. The system of claim 1 , further comprising a second data forwarding device on the LSP and having (a) at least one communications interface, (b) at least one processor, and (c) at least one storage device storing processor-executable instructions which, when executed by the at least one processor of the second data forwarding device, cause the at least one processor of the second data forwarding device to perform a method including:
e) receiving, by the second data forwarding device, an instance of the data packet;
f) determining a further next hop of the instance of the data packet received;
g) determining whether or not the further next hop is reachable;
h) responsive to determining that the further next hop is not reachable,
1) determining whether or not the instance of the data packet received includes the further label indicating that a backup detour was made, and
2) responsive to the determination that the instance of the data packet received includes the further label indicating that a backup detour was made, dropping the instance of the data packet, and
otherwise, responsive to determining that the further next hop is available, forwarding the instance of the data packet using a forwarding label associated with the further next hop.

10. The system of claim 1 , further comprising a second data forwarding device on the LSP and having (a) at least one communications interface, (b) at least one processor, and (c) at least one storage device storing processor-executable instructions which, when executed by the at least one processor of the second data forwarding device, cause the at least one processor of the second data forwarding device to perform a method including:
e) receiving, by the second data forwarding device, an instance of the data packet, wherein the instance of the data packet includes an incoming label;
f) determining a further next hop of the instance of the data packet received using the incoming label;
g) determining whether or not the further next hop is reachable;
h) responsive to determining that the further next hop is not reachable,
1) determining whether or not the instance of the data packet received includes the further label indicating that a backup detour was made, and
2) responsive to the determination that the instance of the data packet received includes the further label indicating that a backup detour was made, dropping the instance of the data packet, and
otherwise, responsive to determining that the further next hop is reachable,
1) popping the incoming label of the instance of the data packet,
2) removing the further label indicating that a backup detour was made if the further label indicating that a backup detour was made is at the top a label stack associated with the instance of the data packet,
3) adding an outgoing label if the next hop includes an outgoing label, and
4) forwarding the instance of the data packet using the further next hop.

11. A non-transitory computer-readable medium storing processor-executable instructions which, when executed by a least one processor of a data forwarding device, cause the data forwarding device to perform a method for avoiding loops in a communications network, the method including:
a) receiving, by the data forwarding device, a data packet to be forwarded over a label-switched path (LSP);
b) determining, by the data forwarding device, a next hop of the data packet received;
c) determining, by the data forwarding device, whether or not the next hop is reachable; and
d) respons

Assignees

• Juniper Networks Inc

Inventors

• Kompella Kireeti
• Lin Wen
• Wang Kevin

Classifications

• H04L69/22

  Parsing or analysis of headers · CPC title

• H04L45/507

  Label distribution · CPC title

• H04L45/22

  Alternate routing · CPC title

• H04L45/20

  Hop count for routing purposes, e.g. TTL · CPC title

• H04L12/4633

  Interconnection of networks using encapsulation techniques, e.g. tunneling · CPC title