System and method for providing recovery and resynchronization for a tunneling protocol

• US 8,018,956 B1
• Filed: 10/15/2008
• Issued: 09/13/2011
• Est. Priority Date: 10/15/2008
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Shankarkumar, Vinaychandra, Deng, Mingqi, Henderson, Samuel G.
• Primary Examiner(s): Ngo; Ricky
• Assistant Examiner(s): Patel; Chandrahas
• Application Number:
  US12/251,625
• Time in Patent Office: 1,063 Days
• Field of Search: 370/352, 370/401
• US Class Current: 370/401
• CPC Class Codes: H04L 1/187 Details of sliding window management
• CPC Class Codes: H04L 41/0659 by isolating or reconfiguring faulty entities
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 69/324 in the data link layer [OSI layer 2], e.g. HDLC
• CPC Class Codes: H04L 69/327 in the session layer [OSI layer 5]
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

An apparatus is provided in one example embodiment and it includes a first node coupled to an active endpoint and a standby endpoint. The first node communicates with a second node. When the active endpoint experiences a failure, the standby endpoint is activated such that a communication involving the second node continues. The standby endpoint communicates a complete window'"'"'s worth of packets to the second node after the failure, the window'"'"'s worth of packets including a last known sequence number acknowledged by the second node. In more specific embodiments, the first node is an L2TP network server (LNS) and the second node is an L2TP access concentrator (LAC). The last known sequence number was check pointed by the active endpoint to the standby endpoint.

Claims

1. A method, comprising:

communicating, via a first node, with a second node, wherein the first node is coupled to an active endpoint and a standby endpoint;

activating the standby endpoint when the active endpoint experiences a failure such that a communication involving the second node continues; and

communicating a complete window'"'"'s worth of packets to the second node after the failure, the window'"'"'s worth of packets including a last known sequence number acknowledged by the second node, wherein the first node is an L2TP network server (LNS) and the second node is an L2TP access concentrator (LAC), wherein the standby endpoint is configured to communicate a control packet prior to propagation of HELLO packets, wherein the standby endpoint creates a particular control packet associated with an Incoming Call Request/Outgoing Call Request (ICRQ)/(OCRQ) format to be sent to the second node, the particular control packet having an unused session ID that is reserved.

2. The method of claim 1, wherein the last known sequence number was check pointed to the standby endpoint.

3. The method of claim 1, wherein the standby endpoint creates a new packet to be sent to the second node and the new packet is electronically acknowledged by the second node.

4. The method of claim 1, wherein if the first node receives an acknowledgement for the control packet, a sequence number is advanced for a communication involving the first and second nodes.

5. Logic encoded in one or more tangible non-transitory media for execution and when executed by a processor operable to:

communicate, via a first node, with a second node, wherein the first node is coupled to an active endpoint and a standby endpoint;

activate the standby endpoint when the active endpoint experiences a failure such that a communication involving the second node continues; and

communicate a complete window'"'"'s worth of packets to the second node after the failure, the window'"'"'s worth of packets including a last known sequence number acknowledged by the second node, wherein the first node is an L2TP network server (LNS) and the second node is an L2TP access concentrator (LAC), wherein the standby endpoint is configured to communicate a control packet prior to propagation of HELLO packets, wherein the standby endpoint creates a particular control packet associated with an Incoming Call Request/Outgoing Call Request (ICRQ)/(OCRQ) format to be sent to the second node, the particular control packet having an unused session ID that is reserved.

6. The logic of claim 5, wherein if the first node receives an acknowledgement for the control packet, a sequence number is advanced for a communication involving the first and second nodes.

7. The logic of claim 5, wherein the last known sequence number was check pointed to the standby endpoint.

8. The logic of claim 5, wherein the standby endpoint creates a new packet to be sent to the second node and the new packet is electronically acknowledged by the second node.

9. A system, comprising:

means for communicating, via a first node, with a second node, wherein the first node is coupled to an active endpoint and a standby endpoint;

means for activating the standby endpoint when the active endpoint experiences a failure such that a communication involving the second node continues; and

means for communicating a complete window'"'"'s worth of packets to the second node after the failure, the window'"'"'s worth of packets including a last known sequence number acknowledged by the second node, wherein the first node is an L2TP network server (LNS) and the second node is an L2TP access concentrator (LAC), wherein the standby endpoint is configured to communicate a control packet prior to propagation of HELLO packets, wherein the standby endpoint creates a particular control packet associated with an Incoming Call Request/Outgoing Call Request (ICRQ)/(OCRQ) format to be sent to the second node, the particular control packet having an unused session ID that is reserved.

10. The system of claim 9, wherein the standby endpoint creates a new packet to be sent to the second node and the new packet is electronically acknowledged by the second node.

11. The system of claim 9, wherein if the first node receives an acknowledgement for the control packet, a sequence number is advanced for a communication involving the first and second nodes.

12. The system of claim 9, wherein the last known sequence number was check pointed to the standby endpoint.

13. An apparatus, comprising:

a first node coupled to an active endpoint and a standby endpoint, wherein the first node communicates with a second node, and wherein when the active endpoint experiences a failure, the standby endpoint is activated such that a communication involving the second node continues, and wherein the standby endpoint communicates a complete window'"'"'s worth of packets to the second node after the failure, the window'"'"'s worth of packets including a last known sequence number acknowledged by the second node, wherein the first node is an L2TP network server (LNS) and the second node is an L2TP access concentrator (LAC), wherein the standby endpoint is configured to communicate a control packet prior to propagation of HELLO packets, wherein the standby endpoint creates a particular control packet associated with an Incoming Call Request/Outgoing Call Request (ICRQ)/(OCRQ) format to be sent to the second node, the particular control packet having an unused session ID that is reserved.

14. The apparatus of claim 13, wherein the last known sequence number was check pointed to the standby endpoint.

15. The apparatus of claim 13, wherein the standby endpoint creates a new packet to be sent to the second node and the new packet is electronically acknowledged by the second node.

16. The apparatus of claim 13, wherein if the first node receives an acknowledgement for the control packet, a sequence number is advanced for a communication involving the first and second nodes.