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

US9806943B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9806943-B2
Application numberUS-201414261310-A
CountryUS
Kind codeB2
Filing dateApr 24, 2014
Priority dateApr 24, 2014
Publication dateOct 31, 2017
Grant dateOct 31, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Exemplary embodiments for enabling planned network changes such as an upgrade or downgrade of a network device are disclosed. The systems and methods provide for planned upgrades and downgrades for network devices without impacting existing network sessions, by utilizing two network devices simultaneously, and creating a redirect network session for a predetermined period of time. In so doing, all network traffic may be gradually transferred to the second network device, until the sessions processed by the first network device time out. The first network device can then be taken offline for upgrade or downgrade, without any disruption to the network service or loss of network traffic.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for enabling a planned upgrade or a planned downgrade of a first network device, the method comprising: establishing, at the first network device, a TCP session with a client device; receiving, at the first network device, a request for a virtual service over a network by the client device; creating a redirect network session for the TCP session at a second network device based on information associated with the TCP session, the second network device being a standby device for the first network device, wherein the information associated with the TCP session is sent by the first network device to the second network device upon establishing the TCP session with the client device; delivering, by the first network device, the request for the virtual service over a network to a server; receiving a change from a network administrator designating the second network device as an active device for the virtual service; receiving a server response at the second network device; recognizing, at the second network device, that the server response is associated with the redirect network session; 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, wherein the first network device delivers further requests associated with the TCP session from the client device directly to the server until the virtual service is completed, and wherein the second network device redirects further server responses associated with the redirect network session to the first network device until the virtual service is completed. 2. The method of claim 1 , wherein the redirect network session comprises at least one of a source IP address, a destination IP address, a source port, destination port, and protocol. 3. The method of claim 1 , wherein the virtual service is a virtual IP address. 4. The method of claim 1 , wherein the request for the virtual service is a GET request. 5. The method of claim 1 , wherein the delivering the request for the virtual service over a network to the server by the first network device further comprises load balancing of a plurality of servers. 6. The method of claim 1 , wherein the recognizing, at the second network device, that the server response is associated with the redirect network session further comprises conducting a session lookup at the second network device to determine the TCP session that corresponds with the server response received. 7. The method of claim 1 , wherein the first network device is an application delivery controller. 8. The method of claim 1 , wherein the first network device is a global server load balancer. 9. The method of claim 1 , wherein the second network device is an application delivery controller. 10. The method of claim 1 , wherein the second network device is a global server load balancer. 11. The method of claim 1 , further comprising upgrading the first network device after the redirect network session times out. 12. A system for enabling a planned upgrade or a planned downgrade of a first network device during a TCP session, the first network device configured to: establish a TCP session with a client device; receive a request for a virtual service over a network by the client device; deliver the request for the virtual service over a network to a server; receive a change from a network administrator designating a second network device as an active device for the virtual service, the second network device being a standby device for the first network device, the second device creating a redirect network session for the TCP session based on information associated with the TCP session, wherein the information associated with the TCP session is sent by the first network device to the second network device upon establishing the TCP session with the client device; receive a redirected server response from the second network device; and send the redirected server response to the client device, wherein the first network device delivers further requests associated with the TCP session from the client device directly to the server until the virtual service is completed, and wherein the second network device redirects further server responses associated with the redirect network session to the first network device until the virtual service is completed. 13. The system of claim 12 , wherein the virtual service is a virtual IP address. 14. The system of claim 12 , wherein the request for the virtual service is a GET request. 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 over a network to the server. 16. The system of claim 12 , wherein the first network device is an application delivery controller. 17. The system of claim 12 , wherein the first network device is a global server load balancer. 18. The system of claim 12 further comprising the second network device configured to: receive a server response; recognize that the server response is associated with the redirect network session; and redirect the server response to the first network device. 19. The system of claim 18 , wherein the redirect network session comprises at least one of a source IP address, a destination IP address, a source port, destination port, and protocol. 20. A non-transitory processor-readable medium having instructions stored thereon, which when executed by one or more processors, cause the one or more processors to perform the following operations: establishing, at the first network device, a TCP session with a client device; receiving, at the first network device, a request for a virtual service over a network by the client device; creating a redirect network session for the TCP session at a second network device based on information associated with the TCP session, the second network device being a standby device for the first network device, wherein the information associated with the TCP session is sent by the first network device to the second network device upon establishing the TCP session with the client device; delivering, by the first network device, the request for the virtual service over a network to a server; receiving a change from a network administrator designating the second network device as an active device for the virtual service; receiving a server response at the second network device; recognizing, at the second network device, that the server response is associated with the redirect network session; 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, wherein the first network device delivers further requests associated with the TCP session from the client device directly to the server until the virtual service is completed, and wherein the second network device redirects further server responses associated with the redirect network session to the first network device until the virtual service is completed.

Assignees

Inventors

Classifications

  • Migration or transfer of sessions · CPC title

  • avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session · CPC title

  • based on a hash applied to IP addresses or costs · CPC title

  • Persistence of sessions during load balancing · CPC title

  • Configuration setting · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9806943B2 cover?
Exemplary embodiments for enabling planned network changes such as an upgrade or downgrade of a network device are disclosed. The systems and methods provide for planned upgrades and downgrades for network devices without impacting existing network sessions, by utilizing two network devices simultaneously, and creating a redirect network session for a predetermined period of time. In so doing, …
Who is the assignee on this patent?
A10 Networks Inc
What technology area does this patent fall under?
Primary CPC classification H04L41/0803. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Oct 31 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 12 related publications on this page (citations in our corpus or others sharing the same primary CPC).