STATEFUL FAILOVER MANAGEMENT IN A NETWORK TRAFFIC MANAGER

• US 20140068103A1
• Filed: 08/19/2013
• Published: 03/06/2014
• Est. Priority Date: 08/17/2012
• Status: Abandoned Application

• Current Assignee: F5 Networks, Inc. (F5 Incorporated)
• Original Assignee: F5 Networks, Inc. (F5 Incorporated)
• Inventors: Vachharajani, Manish, Giacomoni, John, Terrel, Mark, Gyambavantha, Raghu Menzo
• Application Number:
  US13/970,478
• Publication Number:
  US 20140068103A1
• Time in Patent Office: Days
• US Class Current: 709/238
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/19 at layers above the network layer network arrangements for networked applications for scheduling or organising the servicing of application requests H04L67/60
• CPC Class Codes: H04L 47/20 Traffic policing
• CPC Class Codes: H04L 47/2475 for supporting traffic characterised by the type of applications
• CPC Class Codes: H04L 47/27 Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
• CPC Class Codes: H04L 47/28 in relation to timing considerations
• CPC Class Codes: H04L 47/34 ensuring sequence integrity, e.g. using sequence numbers
• CPC Class Codes: H04W 8/04 Registration at HLR or HSS [Home Subscriber Server]

Abstract

Methods, systems, and devices are described for stateful failover in traffic manager module functioning as a proxy between at least one first network device and at least one server. In a first set of embodiments, an amount of synchronized state information may be reduced through a controlled use of acknowledgment messages. In a second set of embodiments, state information may be synchronized to a standby traffic manager module in response to changes in a sequence number delta between two logically paired connections. In a third set of embodiments, connections may be restored at a standby traffic manager module based on stored connection information, a synchronized sequence number delta stack, and rediscovered sequence numbers.

Claims

1. A method of managing network communications, comprising:

receiving a packet from a first network device at a traffic manager module serving as a proxy to a second network device for the first network device;

forwarding data from the packet to the second network device; and

delaying transmitting an acknowledgment of the packet from the traffic manager module to the first network device until after the traffic manager module has received an acknowledgment of the data by the second network device.

2. The method of claim 1, wherein the traffic manager module comprises a first traffic manager module, the method further comprising:

tracking a sequence number delta at the first traffic manager module between a first connection with the first network device and a second connection with the second network device;

detecting a change in the sequence number delta; and

synchronizing a state of the first traffic manager module with a second traffic manager module in response to the detected change in the sequence number delta.

3. The method of claim 2, further comprising:

synchronizing the state of the first traffic manager module with the second traffic manager module in response to one or more of;

a rollover of a sequence number of one of the connections to an initial value or a change in a connection state of one of the connections.

4. The method of claim 2, further comprising:

storing a stack of sequence number deltas between the first connection and the second connection at the first traffic manager module.

5. The method of claim 4, wherein synchronizing the state of the first traffic manager module with the second traffic manager module comprises:

synchronizing the stack of sequence number deltas with the second traffic manager module.

6. The method of claim 2, further comprising:

refraining, in response to the change in the sequence number delta, from forwarding data between the first network device and the second network device until the state of the first traffic manager module has been synchronized with the state of the second traffic manager module.

7. The method of claim 2, further comprising:

storing a logical coupling between the first connection and the second connection at the first traffic manager module.

8. The method of claim 7, wherein synchronizing the state of the first traffic manager module with the second traffic manager module comprises:

synchronizing the logical coupling between the first connection and the second connection with the second traffic manager module.

9. The method of claim 2, further comprising:

storing Quality of Service (QoS) information related to the first connection and the second connection at the first traffic manager module.

10. The method of claim 9, wherein synchronizing the state of the first traffic manager module with the second traffic manager module comprises:

synchronizing the QoS information related to the first connection and the second connection with the second traffic manager module.

11. A traffic manager module, comprising:

at least one processor; and

a memory communicably coupled with the at least one processor, the memory configured to store code that, when executed by the at least one processor, causes the at least one processor to;

receive a packet from a first network device, the traffic manager module serving as a proxy to a second network device for the first network device;

forward data from the packet to the second network device; and

delay transmitting an acknowledgment of the packet from the traffic manager module to the first network device until after the traffic manager module has received an acknowledgment of the data by the second network device.

12. The traffic manager module of claim 11, wherein:

the traffic manager module comprises a first traffic manager module; and

the code causes the at least one processor to;

track a sequence number delta at the first traffic manager module between a first connection with the first network device and a second connection with the second network device;

detect a change in the sequence number delta; and

synchronize a state of the first traffic manager module with a second traffic manager module in response to the detected change in the sequence number delta.

13. The traffic manager module of claim 12, wherein the code causes the at least one processor to:

synchronize the state of the first traffic manager module with the second traffic manager module in response to one or more of;

a rollover of a sequence number of one of the connections to an initial value or a change in a connection state of one of the connections.

14. The traffic manager module of claim 12, wherein the code causes the at least one processor to:

store a stack of sequence number deltas between the first connection and the second connection at the first traffic manager module.

15. The traffic manager module of claim 14, wherein the code causes the at least one processor to synchronizing the state of the first traffic manager module with the second traffic manager module by:

synchronizing the stack of sequence number deltas with the second traffic manager module.

16. The traffic manager module of claim 12, wherein the code causes the at least one processor to:

refrain, in response to the change in the sequence number delta, from forwarding data between the first network device and the second network device until the state of the first traffic manager module has been synchronized with the state of the second traffic manager module.

17. The traffic manager module of claim 12, wherein the code causes the at least one processor to:

store a logical coupling between the first connection and the second connection at the first traffic manager module.

18. The traffic manager module of claim 17, wherein the code causes the at least one processor to synchronize the state of the first traffic manager module with the second traffic manager module by:

synchronizing the logical coupling between the first connection and the second connection with the second traffic manager module.

19. The traffic manager module of claim 12, wherein the code causes the at least one processor to:

store Quality of Service (QoS) information related to the first connection and the second connection at the first traffic manager module.

20. The traffic manager module of claim 19, wherein the code causes the at least one processor to synchronize the state of the first traffic manager module with the second traffic manager module by:

synchronizing the QoS information related to the first connection and the second connection with the second traffic manager module.

21. A tangible computer-readable medium comprising computer-readable program code stored thereon, which is configured to cause at least one processor to:

receive a packet from a first network device at a traffic manager module serving as a proxy to a second network device for the first network device;

forward data from the packet to the second network device; and

delay transmitting an acknowledgment of the packet from the traffic manager module to the first network device until after the traffic manager module has received an acknowledgment of the data by the second network device.

22. The computer program product of claim 21, wherein:

the traffic manager module comprises a first traffic manager module; and

the computer-readable program code is further configured to cause at least one processor to;

track a sequence number delta at the first traffic manager module between a first connection with the first network device and a second connection with the second network device;

detect a change in the sequence number delta; and

synchronize a state of the first traffic manager module with a second traffic manager module in response to the detected change in the sequence number delta.