Enabling planned upgrade/downgrade of network devices without impacting network sessions

• US 10,411,956 B2
• Filed: 09/07/2018
• Issued: 09/10/2019
• Est. Priority Date: 04/24/2014
• Status: Active Grant

• Current Assignee: A10 Networks Incorporated
• Original Assignee: A10 Networks Incorporated
• Inventors: Golshan, Ali, Sankar, Swaminathan, Natham, Venky
• Primary Examiner(s): Nano, Sargon N
• Application Number:
  US16/125,078
• Publication Number:
  US 20190020536A1
• Time in Patent Office: 368 Days
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 67/1023 based on a hash applied to IP addresses or costs
• CPC Class Codes: H04L 67/1027 Persistence of sessions during load balancing
• CPC Class Codes: H04L 67/145 avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

Provided are methods and systems for enabling a planned upgrade or a planned downgrade of a first network device. A method may commence with receiving a request for a virtual service via a Transmission Control Protocol (TCP) session between the first network device and the client device. The method may further include creating, by a second network device being a standby device for the first network device, a redirect network session for the TCP session. The method may continue with delivering, by the first network device, the request for the virtual service to a server. Upon a change designating the second network device as an active device for the virtual service, the second network device may receive, from the server, a server response associated with the virtual service and redirect the server response to the first network device for further sending of the server response to the client device.

Claims

1. A method for enabling a planned upgrade or a planned downgrade of a first network device, the method comprising:

the first network device;

establishing a TCP session with a client device;

receiving via the TCP session, a request for a virtual service over a network;

delivering the request for the virtual service to a server;

sending a server response associated with the virtual service to the client device;

receiving further requests associated with the TCP session from the client device; and

creating, by the second network device, a redirect network session for the TCP session, the second network device being a standby device for the first network device;

delivering, by the first network device, the request for the virtual service to a server;

receiving, from a network administrator, a change designating the second network device as an active device for the virtual service;

receiving, by the second network device, from the server, a server response associated with the virtual service;

redirecting, by the second network device, the server response to the first network device in accordance with the redirect network session; and

sending, by the first network device, the server response to the client device.

2. The method of claim 1, further comprising:

receiving, by the first network device, further requests associated with the TCP session from the client device; and

delivering, by the first network device, the further requests associated with the TCP session to the server until the virtual service is completed.

3. The method of claim 2, further comprising:

receiving, by the second network device, further server responses associated with the virtual service from the server; and

redirecting, by the second network device, the further server responses to the first network device until the virtual service is completed.

4. The method of claim 1, wherein the redirect network session comprises at least one of the following:

a source IP address, a destination IP address, a source port, a destination port, and a protocol.

5. The method of claim 1, further comprising establishing, by the first network device, the TCP session with the client device.

6. The method of claim 1, wherein the delivering of the request for the virtual service to the server by the first network device further comprises load balancing of a plurality of servers.

7. The method of claim 1, further comprising upon receipt of the server response, recognizing, by the second network device, that the server response is associated with the redirect network session.

8. The method of claim 7, wherein the recognizing, by the second network device, that the server response is associated with the redirect network session comprises conducting a session lookup by the second network device to determine the TCP session that corresponds to the server response received from the server.

9. The method of claim 1, wherein the first network device includes one of the following:

an application delivery controller and a global server load balancer.

10. The method of claim 1, wherein the second network device includes one of the following:

an application delivery controller and a global server load balancer.

11. The method of claim 1, further comprising upgrading the first network device after the virtual service is completed.

12. A system for enabling a planned upgrade or a planned downgrade of a first network device, the system comprising:

a first network device to;

establish a TCP session with a client device;

receive, via the TCP session between the first network device and the client device, a request for a virtual service over a network;

deliver the request for the virtual service to a server;

receive, from a network administrator, a change designating a second network device as an active device for the virtual service; and

send a server response associated with the virtual service to the client device;

receive further requests associated with the TCP session from the client device; and

deliver the further requests associated with the TCP session to the server until the virtual service is completed; and

the second network device, the second network device being a standby device for the first network device, the second network device;

creating a redirect network session for the TCP session;

receiving, from the server, the server response associated with the virtual service;

redirecting the server response to the first network device in accordance with the redirect network session;

receiving further server responses associated with the virtual service from the server; and

redirecting the further server responses to the first network device until the virtual service is completed.

13. The system of claim 12, wherein the first network device is further configured to:

receive further requests associated with the TCP session from the client device; and

deliver the further requests associated with the TCP session to the server until the virtual service is completed.

14. The system of claim 13, wherein the second network device is further configured to:

receive further server responses associated with the virtual service from the server;

redirect the further server responses to the first network device until the virtual service is completed.

15. The system of claim 12, wherein the first network device is further configured to load balance a plurality of servers before delivering the request for the virtual service to the server.

16. The system of claim 12, wherein each of the first network device and the second network device includes one of the following:

an application delivery controller and a global server load balancer.

17. The system of claim 12, wherein the first network device is further configured to establish the TCP session with the client device.

18. The system of claim 12, wherein the first network device is further configured to, upon receipt of the server response, recognize that the server response is associated with the redirect network session.

19. The system of claim 12, wherein the redirect network session comprises at least one of a source Internet Protocol (IP) address, a destination IP address, a source port, a destination port, and a protocol.