Identifying and marking failed egress links in data plane

Patent metadata

Field	Value
Publication number	US-10063407-B1
Application number	US-201615150015-A
Country	US
Kind code	B1
Filing date	May 9, 2016
Priority date	Feb 8, 2016
Publication date	Aug 28, 2018
Grant date	Aug 28, 2018

Abstract

A method of identifying a failed egress path of a hardware forwarding element. The method detects an egress link failure in a data plane of the forwarding element. The method generates a link failure signal in the data plane identifying the failed egress link. The method generates a packet that includes the identification of the egress link based on the link failure signal. The method sets the status of the egress link to failed in the data plane based on the identification of the egress link in the generated packet.

First claim

What is claimed is:

1. A method of identifying a failed egress path of a hardware forwarding element, the method comprising:
detecting an egress link failure in a data plane of the forwarding element;
generating a link failure signal in the data plane identifying the failed egress link;
generating a packet comprising an identification of the failed egress link based on the link failure signal;
matching the identification of the failed egress link with a match field at one of a plurality of match-action stages of a packet pipeline within the data plane of the forwarding element, the match field comprising a corresponding action field;
determining a location of a status flag associated with the egress link based on the corresponding action field; and
setting the status flag associated with the failed egress link to failed in the data plane based on the identification of the failed egress link in the generated packet.

2. The method of claim 1 , wherein the failed egress link is one of an egress port of the forwarding element and an egress path of the forwarding element.

3. The method of claim 1 , wherein the flag is stored in a storage location, wherein setting the status flag associated with the failed egress link to failed comprises writing to the storage location using a set of hardware components.

4. The method of claim 1 , wherein each match-action stage comprises a set of match tables against which at least a subset of the packet header field values stored in the first set of registers is matched.

5. The method of claim 1 , wherein detecting the egress link failure in the data plane comprises:
monitoring the egress link by a hardware unit;
detecting the egress link failure by the hardware unit; and
sending a link down signal to a traffic manager in the forwarding unit.

6. The method of claim 5 , wherein generating the link failure signal comprises:
receiving the link down signal at the traffic manager; and
sending said link failure signal from the traffic manager to a packet generator unit in the forwarding element.

7. The method of claim 1 , wherein the data plane of the forwarding element is utilized to carry data packets traffic through the forwarding element.

8. The method of claim 1 , wherein said detecting the egress link failure, generating the link failure signal, generating the packet, and setting the status are performed by a set of hardware components of the forwarding element.

9. The method of claim 1 , wherein the forwarding element is one of a switch and a router.

10. The method of claim 1 , wherein the failed egress link is an egress port, the method further comprising:
receiving a data packet at the forwarding element, the data packet specifying the failed egress port as a destination port of the packet;
determining that the egress port has failed based on the status of the egress port; and
sending the packet to a backup egress port associated with the failed egress port.

11. A method of identifying a failed egress path of a hardware forwarding element, the method comprising:
detecting an egress link failure in a data plane of the forwarding element by monitoring the egress link with a hardware unit, detecting the egress link failure by the hardware unit, and sending a link down signal to a traffic manager in the forwarding unit;
generating a link failure signal in the data plane identifying the failed egress link, by receiving the link down signal at the traffic manager, and sending said link failure signal from the traffic manager to a packet generator unit in the forwarding element;
based on the link failure signal, generating a packet comprising an identification of the failed egress link by (1) generating the packet with the packet generator in the data plane, a header of the packet comprising the identification of the failed egress link, and (2) placing the packet in an ingress pipeline of the forwarding element; and
setting a status of the failed egress link to failed in the data plane based on the identification of the egress link in the generated packet.

12. A hardware forwarding element comprising:
a set of media access control (MAC) units detecting a failure of an egress link in a data plane of the forwarding element and generating a link down signal;
a traffic manager generating, in response to receiving each link down signal, a link failure signal in the data plane identifying a failed egress link;
a packet generator receiving a link failure signal and generating a packet in the data plane based on the received link failure signal, a header of each packet comprising an identification of the failed egress link; and
a set of match-action units (i) matching the identification of the failed egress link with a match field at one of a plurality of match-action stages of a packet pipeline within the data plane of the forwarding element, the match field comprising a corresponding action field, (ii) determining a location of an status flag associated with the failed egress link based on the corresponding action field, and (iii) setting the status flag associated with the failed egress link to failed in the data plane based on the identification of the egress link included in the header of a packet generated by the packet generator.

13. The hardware forwarding element of claim 12 , wherein the failed egress link is one of an egress port of the forwarding element and an egress path of the forwarding element.

14. The hardware forwarding element of claim 12 further comprising a set of storage locations, wherein the flag is stored in one of said storage locations, wherein the set of match-action units set the status flag associated with the failed egress link to failed by writing to the storage location using a set of hardware components.

15. The hardware forwarding element of claim 12 , wherein each match-action stage comprises a set of match tables against which at least a subset of the packet header field values stored in the first set of registers is matched.

16. The hardware forwarding element of claim 12 , wherein the set of MAC units detects the egress link failure in the data plane by monitoring the egress link by a MAC unit, detecting the egress link failure by the MAC unit, and sending a link down signal to the traffic manager.

17. The hardware forwarding element of claim 16 , wherein the traffic manager generates the link failure signal by receiving the link down signal at the traffic manager and sending said link failure signal from the traffic manager to a packet generator in the set of packet generators.

18. The hardware forwarding element of claim 12 , wherein the data plane of the forwarding element is utilized to carry data packets traffic through the forwarding element.

19. The hardware forwarding element of claim 12 , wherein the forwarding element is one of a switch and a router.

20. The hardware forwarding element of claim 12 , wherein the egress link is an egress port, wherein the set of match-action units further determines that a port specified as an egress port of a particular data packet received at the forwarding element has failed based on the status of the egress port, and sends the particular packet to a backup egress port associated with the failed egress port.

21. A hardware forwarding element comprising:
a set media access control (MAC) units, a traffic manager, a packet generator and a set of match-action units;
the set of media access control (MAC) units detecting an egress link failure in a data plane of the forwarding

Assignees

• Barefoot Networks Inc

Inventors

• Kodeboyina Chaitanya
• Cruz John
• Licking Steven
• Attig Michael E

Classifications

• H04L41/0654 Primary

  using network fault recovery (ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437) · CPC title

• H04L45/745

  Address table lookup; Address filtering · CPC title

• H04L69/22

  Parsing or analysis of headers · CPC title

• Y02D30/50

  in wire-line communication networks, e.g. low power modes or reduced link rate · CPC title

• H04L41/0677 Primary

  Localisation of faults · CPC title