Methods for preserving flow state during virtual machine migration and devices thereof

• US 9,141,625 B1
• Filed: 06/22/2011
• Issued: 09/22/2015
• Est. Priority Date: 06/22/2010
• Status: Active Grant

• Current Assignee: F5 Networks, Inc. (F5 Incorporated)
• Original Assignee: F5 Networks, Inc. (F5 Incorporated)
• Inventors: Thornewell, Peter M., Moshiri, Nojan, Kushi, David, Zheng, Songbo, Cano, Charles
• Primary Examiner(s): Chacko, Joe
• Application Number:
  US13/166,624
• Time in Patent Office: 1,553 Days
• Field of Search: 709/223, 709/226
• US Class Current: 1/1
• CPC Class Codes: G06F 16/119 Details of migration of file systems migration mechanisms in storage systems G06F3/0647
• CPC Class Codes: G06F 9/4856 resumption being on a different machine, e.g. task migration, virtual machine migration G06F9/5088 takes precedence
• 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/148 Migration or transfer of sessions

Abstract

Methods, computer-readable media, and apparatuses for network flow state preservation include migration of at least one application hosted on a first server device to a second server device coupled to a second traffic management device is detected at a first traffic management device. At least a portion of connection state information associated with a network connection between at least one client device and the application is communicated by the first traffic management device to the second traffic management device via a communication channel between the first and second traffic management devices. The application is provided by the first traffic management device to the at least one client device during the migration based upon the connection state information.

Claims

1. A method for preserving network flow state, the method comprising:

detecting by a first traffic management computing device a migration of at least one application hosted on a first server device coupled to the first traffic management computing device to a second server device coupled to a second traffic management computing device, wherein the detecting further comprises detecting any latency of network traffic between the first server device and the second server device during the migration;

communicating by the first traffic management computing device connection state information associated with a network connection between at least one client device and the at least one application to the second traffic management computing device via a communication channel between the first and the second traffic management computing devices;

receiving by the first traffic management computing device at least one address resolution protocol packet from the second traffic management computing device and one or more network packets destined for the at least one client device, associated with the network connection, and originating from the at least one application from the second traffic management computing device after the migration, wherein the receiving comprises terminating at least a portion of the network traffic between the first server device and the second server device when the detected latency of network traffic is greater than a first threshold latency; and

sending subsequent inbound requests from the at least one client device and associated with the network connection using network address information included in the at least one address resolution protocol packet.

2. The method as set forth in claim 1, wherein the at least one application is a virtual machine application, and wherein the communication channel is an at least partly secure communication channel.

3. The method as set forth in claim 1, wherein the connection state information is communicated using one or more non-invasive connection state packets comprising transmission control protocol (TCP) keep-alive packets or non-invasive user datagram protocol (UDP) packets including empty UDP packets.

4. The method as set forth in claim 1, wherein the first traffic management computing device is a part of a first physical network and the second traffic management computing device is a part of a second physical network separate from the first physical network.

5. The method as set forth in claim 1 further comprising redirecting by the first traffic management computing device a new connection request from the at least one client device after the migration of the at least one application to the second traffic management computing device.

6. The method as set forth in claim 1 further comprising notifying by the first traffic management computing device a global traffic management computing device of the migration.

7. The method as set forth in claim 1, wherein the communication channel is an Ethernet communication channel.

8. The method as set forth in claim 1, wherein the detecting, the communicating, the providing, and the receiving are carried out for subsequent one or more migrations of the at least one application to at least one additional traffic management computing device.

9. The method as set forth in claim 1 further comprising monitoring by the first traffic management computing device network traffic to the second server device during the migration for allocating resources at the second server device for the at least one application.

10. A non-transitory computer readable medium having stored thereon instructions for preserving network flow state comprising machine executable code which when executed by at least one processor, causes the processor to perform steps comprising:

detecting a migration of at least one application hosted on a first server device coupled to a first traffic management computing device to a second server device coupled to a second traffic management computing device, wherein the detecting comprises detecting any latency of network traffic between the first server device and the second server device during the migration;

communicating at least a portion of connection state information associated with a network connection between at least one client device and the at least one application to the second traffic management computing device via a communication channel between the first and the second traffic management computing devices; and

receiving at least one address resolution protocol packet from the second traffic management computing device and one or more network packets destined for the at least one client device, associated with the network connection, and originating from the at least one application from the second traffic management computing device after the migration, wherein the receiving comprises terminating at least a portion of the network traffic between the first server device and the second server device when the detected latency of network traffic is greater than a first threshold latency; and

sending subsequent inbound requests from the at least one client device and associated with the network connection using network address information included in the at least one address resolution protocol packet.

11. The medium as set forth in claim 10, wherein the at least one application is a virtual machine application, and wherein the communication channel is an at least partly secure communication channel.

12. The medium as set forth in claim 10, wherein the connection state information is communicated using one or more non-invasive connection state packets comprising transmission control protocol (TCP) keep-alive packets or non-invasive user datagram protocol (UDP) packets including empty UDP packets.

13. The medium as set forth in claim 10, wherein after the migration, the at least one application is configured to transmit at least one network packet frame, associated with a virtual image of network sites where the first and the second traffic management computing devices are located, to the second traffic management computing device that forwards at least one address resolution protocol packet to the first traffic management computing device for handling subsequent inbound requests from the at least one client device, wherein the at least one network packet frame comprises one or more of an Ethernet frame including an address resolution protocol packet and an IP frame.

14. The medium as set forth in claim 10, wherein the first traffic management computing device is a part of a first physical network and the second traffic management computing device is a part of a second physical network separate from the first physical network.

15. The medium as set forth in claim 10 further comprising redirecting a new connection request from the at least one client device after the migration of the at least one application to the second traffic management computing device.

16. The medium as set forth in claim 10 further comprising notifying a global traffic management computing device of the migration.

17. The medium as set forth in claim 10, wherein the communication channel is an Ethernet communication channel.

18. The medium as set forth in claim 10, wherein the detecting, the communicating, the providing, and the receiving are carried out for subsequent one or more migrations of the at least one application to at least one additional traffic management computing device.

19. The medium as set forth in claim 10 further comprising monitoring network traffic to the second server device during the migration for allocating resources at the second server device for the at least one application.

20. A traffic management computing device comprising:

one or more processors;

a memory coupled to the one or more processors;

a network interface unit coupled to the one or more processors and the memory via at least one bus, at least one of the network interface unit configured to implement or the one or more processors configured to execute programmed instructions stored in the memory comprising;

detecting a migration of at least one application hosted on a first server device coupled to the traffic management computing device to a second server device coupled to a second traffic management computing device, wherein the detecting comprises detecting any latency of network traffic between the first server device and the second server device during the migration;

communicating at least a portion of connection state information associated with a network connection between at least one client device and the at least one application to the second traffic management computing device via a communication channel between the traffic management computing device and the second traffic management computing device; and

receiving at least one address resolution protocol packet from the second traffic management computing device and one or more network packets destined for the at least one client device, associated with the network connection, and originating from the at least one application from the second traffic management computing device after the migration, wherein the receiving comprises terminating at least a portion of the network traffic between the first server device and the second server device when the detected latency of network traffic is greater than a first threshold latency; and

sending subsequent inbound requests from the at least one client device and associated with the network connection using network address information included in the at least one address resolution protocol packet.

21. The traffic management computing device as set forth in claim 20, wherein the at least one application is a virtual machine application, and wherein the communication channel is an at least partly secure communication channel.

22. The traffic management computing device as set forth in claim 20, wherein the connection state information is communicated using one or more non-invasive connection state packets comprising transmission control protocol (TCP) keep-alive packets or non-invasive user datagram protocol (UDP) packets including empty UDP packets.

23. The traffic management computing device as set forth in claim 20, wherein after the migration, the at least one application is configured to transmit at least one network packet frame, associated with a virtual image of network sites where the first and the second traffic management computing devices are located, to the second traffic management computing device that forwards at least one address resolution protocol packet to the first traffic management computing device for handling subsequent inbound requests from the at least one client device, wherein the at least one network packet frame comprises one or more of an Ethernet frame including an address resolution protocol packet and an IP frame.

24. The traffic management computing device as set forth in claim 20, wherein the first traffic management computing device is a part of a first physical network and the second traffic management computing device is a part of a second physical network separate from the first physical network.

25. The traffic management computing device as set forth in claim 20 further comprising redirecting a new connection request from the at least one client device after the migration of the at least one application to the second traffic management computing device.

26. The traffic management computing device as set forth in claim 20 further comprising notifying a global traffic management computing device of the migration.

27. The traffic management computing device as set forth in claim 20, wherein the communication channel is an Ethernet communication channel.

28. The traffic management computing device as set forth in claim 20, wherein the detecting, the communicating, the providing, and the receiving are carried out for subsequent one or more migrations of the at least one application to at least one additional traffic management computing device.

29. The traffic management computing device as set forth in claim 20 further comprising monitoring network traffic to the second server device during the migration for allocating resources at the second server device for the at least one application.