Network appliance for balancing load and platform services

• US 8,572,249 B2
• Filed: 12/10/2003
• Issued: 10/29/2013
• Est. Priority Date: 12/10/2003
• Status: Expired due to Fees

• Current Assignee: Aventail LLC
• Original Assignee: Aventail LLC
• Inventors: Hopen, Chris A., Tomlinson, Gary B., Brooke, John, Brown, Derek W., Burdge, Jonathan, Erickson, Rodger D.
• Primary Examiner(s): Joo, Joshua
• Application Number:
  US10/733,808
• Publication Number:
  US 20050132030A1
• Time in Patent Office: 3,611 Days
• Field of Search: 709220-226, 709/201, 709/203
• US Class Current: 709/226
• CPC Class Codes: G06F 11/2007 using redundant communication media
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 45/121 by minimising delays
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/101 based on network conditions
• CPC Class Codes: H04L 67/1017 based on a round robin mechanism
• CPC Class Codes: H04L 67/1029 using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• CPC Class Codes: H04L 67/1038 Load balancing arrangements to avoid a single path through a load balancer

Abstract

A network appliance is described that can provide a variety of software services, including both platform services, such as access method services, and a load balancing service. A network may include a network appliance that both provides one or more platform services and acts as a load balancer. When two or more such appliances are used together, they can replace a substantial portion of a conventional network. For example, when a network appliance receives a client communication, its load balancer service can determine whether one of its own platform services will process the communication or forward the communication to another network appliance for processing. Moreover, if the load balancing service of a network appliance fails, another network appliance can provide load balancing. Similarly, if another service of a network appliance fails, then the network appliance may continue to provide load balancing but forward communications requiring the failed service to another network appliance for processing.

Claims

1. A network appliance, comprising:

at least one platform service stored in memory, the at least one platform service executable by a processing device;

a service monitor stored in memory and executable by a processor to;

monitor a working status of the at least one platform service when executed from memory, the service monitor using interprocess communications, the working status indicating that the at least one platform service is starting,

place the at least one platform service in hold mode based on the working status indicating that the at least one platform service is starting, and

remove the at least one platform service from hold mode when a predetermined number of successful replies are received from the at least one platform service in response to a plurality of requests; and

a load balancer stored in memory and executable by a processor to suspend received communications to the at least one platform service while the at least one platform service is in hold mode and to resume communications when the at least one platform service is no longer in hold mode.

2. The network appliance of claim 1, further comprising a backplane interface through which the network appliance exchanges data with another device.

3. The network appliance of claim 2, wherein the another device hosts at least one second platform service stored in memory, and the service monitor is executable to monitor a working status of the at least one second platform service using communications transmitted over the backplane.

4. The network appliance of claim 1, further comprising an interface monitor stored in memory and executable to monitor a working status of interfaces and connections employed by the network appliance.

5. The network appliance of claim 1, wherein the at least one platform service is an access method service.

6. The network appliance of claim 5, wherein the access method service is a virtual private network service.

7. The network appliance of claim 5, wherein the access method service is an extranet Web service.

8. The network appliance of claim 1, further comprising a node manager stored in memory and executable to determine the working status of the at least one platform service and provide the determined working status of the at least one platform service to the service monitor.

9. The network appliance of claim 1, further comprising a distributed cache service that caches information relating to at least one platform service on another network appliance.

10. The network appliance of claim 9, wherein the at least one platform service of the other network appliance is an access method service, and the information cached includes authentication information and encryption key information for encryption sessions hosted by the access method service.

11. A system for balancing loads in a network, the system comprising:

a first network appliance having;

at least one first platform service stored in memory,

a service monitor stored in memory and executable to;

monitor a working status of the at least one first platform service when executed from memory, the service monitor using interprocess communications, the working status indicating that the at least platform service is starting,

place the at least one first platform service in hold mode based on the working status indicating that the at least one platform service is starting, and

remove the at least one first platform service from hold mode when a predetermined number of successful replies are received from the at least one first platform service in response to a plurality of requests; and

a first load balancer stored in memory and executable to suspend communications to the at least one first platform service while the at least one first platform service is in hold mode and to resume communications when the at least one first platform service is no longer in hold mode, the working status indicating that the at least one first platform service is starting; and

a second network appliance having;

at least one second platform service stored in memory, and

a second load balancer stored in memory and executable to perform load balancing on communications received by the second network appliance, wherein the first network appliance is configured to receive all client communications to the network unless the first load balancer fails, and the second network appliance is configured to receive all client communications to the network if the first load balancer fails.

12. The system of claim 11, wherein the second network appliance further includes a second service monitor stored in memory and executable to monitor a working status of the at least one second platform service using interprocess communications.

13. The system of claim 11, wherein the at least one first platform service is an access method service.

14. The system of claim 13, wherein the access method service is a virtual private network service.

15. The system of claim 13, wherein the access method service is an extranet Web service.

16. The system of claim 11, wherein the at least one second platform service is an access method service.

17. The system of claim 16, wherein the access method service is a virtual private network service.

18. The system of claim 16, wherein the access method service is an extranet Web service.

19. A method of processing client communications to a network comprising:

receiving a first client communication at a first network appliance hosting at least one first platform service;

monitor a working status of the at least one first platform service when executed from memory, the monitoring using interprocess communications, the working status indicating that the at least one first platform service is starting;

placing the at least one platform service in hold mode based on the working status indicating that the at least one platform service is starting;

removing the at least one platform service from hold mode when a predetermined number of successful replies are received from the at least one platform service in response to a plurality of requests;

employing a load balancer hosted by the first network appliance to suspend communication to the at least one first platform service hosted by the first network appliance while the at least one first platform service is in hold mode and to resume communications when the at least one first platform service is no longer in hold mode;

receiving a second client communication at the first network appliance; and

employing the load balancer to direct the second client communication to a second platform service hosted by a second network appliance based on at least the working status indicating that the at least one first platform service is starting and a working status of the second platform service.

20. The method of claim 19, further comprising:

analyzing the first client communication to determine if the first client communication includes association data indicating that the first client communication is associated with the at least one first platform service; and

determining that the first client communication includes association data indicating that the first communication is associated with the at least one first platform service.

21. The method of claim 20, wherein the association data is a session identifier identifying an encryption session maintained by the at least one first platform service.

22. The method of claim 19, further comprising:

executing a load balancing algorithm to determine whether the second client communication should be directed to the second platform service; and

determining that the second client communication should be directed to the second platform service based upon results of the executed load balancing algorithm.