Method and apparatus for coping with link failures in central control plane architectures

• US 8,619,546 B2
• Filed: 08/17/2010
• Issued: 12/31/2013
• Est. Priority Date: 08/17/2010
• Status: Active Grant

• Current Assignee: RPX Corporation
• Original Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Inventors: Desai, Maulik, Nandagopal, Thyaga
• Primary Examiner(s): Pham, Chi
• Assistant Examiner(s): HYUN, SOON D
• Application Number:
  US12/858,050
• Publication Number:
  US 20120044813A1
• Time in Patent Office: 1,232 Days
• Field of Search: None
• US Class Current: 370/216
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 45/28 using route fault recovery

Abstract

A capability for coping with link failures in central control plane architectures is provided. The capability for coping with link failures enables targeted reporting of link failures within the network in a manner that prevents flooding of link failure messages (LFMs) within the network. A method for reporting a failure of a link associated with a node includes detecting a failure of a link associated with the node, identifying an interface of the node associated with the failed link, identifying, from a flow table of the node, an ingress interface of the node via which a flow intended for the failed link is received, generating an LFM for the identified ingress interface, and sending the LFM via the identified ingress interface. A method for use at a local node having a flow table includes receiving an LFM indicative of a link failure detected at a remote node where the LFM includes a flow definition of a flow received at the remote node from the local node, identifying an interface of the local node via which the LFM is received, identifying from the flow table of the local node an ingress interface of the local node via which a flow intended for the failed link is received, generating a new LFM for the identified ingress interface of the node, and sending the new LFM via the identified ingress interface of the local node.

Claims

1. A method for reporting a failure of a link associated with a node, the method comprising:

detecting a failure of a link associated with the node;

identifying an interface of the node associated with the failed link;

identifying, from a flow table of the node, an ingress interface of the node via which a flow intended for the failed link is received;

generating a link failure message for the identified ingress interface; and

sending the link failure message via the identified ingress interface.

2. The method of claim 1, wherein identifying an ingress interface of the node via which a flow intended for the failed link may be received comprises:

searching the flow table of the node for identifying a flow table entry comprising an Action field indicative that packets of the flow are to be forwarded to the interface of the node associated with the failed link; and

determining the ingress interface from the identified flow table entry.

3. The method of claim 2, wherein the ingress interface is determined from an ingress interface field of the identified flow table entry.

4. The method of claim 1, wherein the link failure message comprises a Source Address field, a Message Identifier field, a Flow Definition field, a Flow Count field, and at least one Flow Def. # field.

5. The method of claim 1, wherein:

for each flow that is (1) received via the ingress interface via which the link failure message is sent and (2) transmitted via the interface of the node associated with the failed link, the link failure message comprises a definition of the flow.

6. The method of claim 1, further comprising:

for each flow that is (1) received via the ingress interface via which the link failure message is sent and (2) transmitted via the interface of the node associated with the failed link, modifying an Action field of a flow table entry of the flow.

7. The method of claim 6, wherein modifying the Action field of the flow table entry of the flow comprises one of:

modifying the Action field to indicate that packets for the flow should be dropped by the node; and

modifying the Action field to indicate that packets for the flow should be forwarded, by the node, toward a controller configured for controlling the node.

8. An apparatus for reporting a failure of a link associated with a node, the apparatus comprising:

a processor configured for;

detecting a failure of a link associated with the node;

identifying an interface of the node associated with the failed link;

identifying, from a flow table of the node, an ingress interface of the node via which a flow intended for the failed link may be received;

generating a link failure message for the identified ingress interface; and

sending the link failure message via the identified ingress interface.

9. A method for use at a local node comprising a flow table, the method comprising:

receiving a link failure message indicative of a link failure detected at a remote node, wherein the link failure message comprises a flow definition of a flow received at the remote node from the local node;

identifying an interface of the local node via which the link failure message is received;

identifying, from the flow table of the local node, an ingress interface of the local node via which a flow intended for the failed link is received;

generating a new link failure message for the identified ingress interface of the node; and

sending the new link failure message via the identified ingress interface of the local node.

10. The method of claim 9, wherein identifying the ingress interface of the local node comprises:

searching the flow table of the node for identifying a flow table entry (1) having an Action field indicative that the flow is forwarded via the identified interface of the local node via which the link failure message is received and (2) having a flow definition matching the flow definition of the flow indicated in the received link failure message; and

determining the ingress interface from the identified flow table entry of the local node.

11. The method of claim 10, wherein the ingress interface is determined from an ingress interface field of the identified flow table entry.

12. The method of claim 11, wherein the flow definition of the flow of the received link failure message represents a subset of flows defined in the flow table entry of the local node, the method further comprising:

splitting the flow table entry into two flow table entries;

modifying an Action field of one of the two flow table entries.

13. The method of claim 9, wherein the received and new link failure messages each comprise a Source Address field, a Message Identifier field, a Flow Definition field, a Flow Count field, and at least one Flow Def. # field.

14. The method of claim 9, wherein the received link failure message includes a Message Identifier field having a Message Identifier value.

15. The method of claim 14, wherein the new link failure message includes a Message Identifier field including the Message Identifier value from the Message Identifier field of the received link failure message.

16. The method of claim 9, wherein:

for each flow that is (1) received via the ingress interface via which the new link failure message is sent and (2) transmitted via the interface of the local node via which the link failure message is received, the new link failure message comprises a definition of the flow.

17. The method of claim 16, wherein, for each flow, the definition of the flow that is included within the new link failure message is the flow definition from the associated flow table entry of the flow.

18. The method of claim 9, further comprising:

for each flow (1) received via the ingress interface via which the new link failure message is sent and (2) transmitted via the interface of the local node via which the link failure message is received, modifying an Action field of a flow table entry of the flow.

19. The method of claim 18, wherein modifying the Action field of the flow table entry of the flow comprises one of:

modifying the Action field to indicate that packets for the flow should be dropped by the local node; and

modifying the action field to indicate that packets for the flow should be forwarded, by the local node, toward a controller configured for controlling the local node.

20. An apparatus for use at a local node comprising a flow table, the apparatus comprising:

a processor configured for;

receiving a link failure message indicative of a link failure detected at a remote node, wherein the link failure message comprises a flow definition of a flow received at the remote node from the local node;

identifying an interface of the local node via which the link failure message is received;

identifying, from the flow table of the local node, an ingress interface of the local node via which a flow intended for the failed link is received;

generating a new link failure message for the identified ingress interface of the node; and

sending the new link failure message via the identified ingress interface of the local node.