Systems and methods for GSLB based on SSL VPN users

• US 9,781,196 B2
• Filed: 12/23/2013
• Issued: 10/03/2017
• Est. Priority Date: 11/25/2008
• Status: Active Grant

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Inventors: Suganthi, Josephine, Raja, Murali, Kamath, Sandeep
• Primary Examiner(s): Salad, Abdullahi E
• Application Number:
  US14/139,359
• Publication Number:
  US 20140189132A1
• Time in Patent Office: 1,380 Days
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 63/0227 Filtering policies mail message filtering H04L51/212
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/1433 Vulnerability analysis
• CPC Class Codes: H04L 63/166 at the transport layer
• 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

Abstract

The present invention provides a system and a method for global server load balancing of a plurality of sites based on a number of Secure Socket Layer Virtual Private Network (SSL VPN) users. The SSL VPN users may access servers at each of the plurality of sites. A global server load balancing virtual server (GSLB) may receive a request to access a server. The GSLB virtual server may load balance a plurality of sites wherein each of the plurality of sites may further comprising a load balancing virtual server load balancing users accessing the server accessing servers via an SSL VPN session. GSLB may receive from a first load balancing virtual server at a first site, a first number of current SSL VPN users accessing servers from the first site via SSL VPN sessions. The GSLB may also receive from a second load balancing virtual server at a second site, a second number of current SSL VPN users of the users accessing servers from the second site via SSL VPN sessions. GSLB may determine to forward the request to one of the first load balancing virtual server of the first site or the second load balancing virtual server of the second site by load balancing SSL VPN users across the plurality of sites based on the first number of current SSL VPN users and the second number of current SSL VPN users.

Claims

1. A method of load balancing based on a number of Secure Socket Layer Virtual Private Network (SSL VPN) users, the method comprising:

(a) receiving, by a device, a first number of Secure Socket Layer Virtual Private Network (SSL VPN) users of a first site of a plurality of sites distinguished from users of the first site that are not SSL VPN users and accessing one or more servers of the first site;

(b) receiving, by the device, a second number of SSL VPN users of a second site distinguished from users of the second site of the plurality of sites that are not SSL VPN users and accessing one or more servers of the second site, wherein the second number of SSL VPN users is different from the first number of SSL VPN users; and

(c) load balancing, by the device based at least on number of SSL VPN users across the plurality of sites, requests of clients among the first site and the second site using at least the first number of SSL VPN users and the second number of SSL VPN users.

2. The method of claim 1, wherein step (a) further comprises receiving, by the device, the first number of SSL VPN users from a second device load balancing a plurality of servers at the first site.

3. The method of claim 1, wherein step (b) further comprises receiving, by the device, the second number of SSL VPN users from a second device load balancing a plurality of servers at the second site.

4. The method of claim 1, wherein step (a) further comprises receiving, by the device, the first number of SSL VPN users accessing servers at the first site via a SSL VPN session.

5. The method of claim 1, wherein step (b) further comprises receiving, by the device, the second number of SSL VPN users accessing servers at the second site via a SSL VPN session.

6. The method of claim 1, wherein each of the first number of current SSL VPN users and the second number of current SSL VPN users comprises an average number of SSL VPN users over a predetermined time period.

7. The method of claim 1, wherein each of the first number of current SSL VPN users and the second number of current SSL VPN users comprises a peak number of SSL VPN users.

8. The method of claim 1, wherein step (c) further comprises load balancing requests of clients for accessing via an SSL VPN session a server at one of the plurality of sites.

9. The method of claim 1, wherein load balancing further comprises global server load balancing by resolving domain names to internet protocol addresses of servers at the plurality of sites.

10. The method of claim 1, wherein step (c) further comprises determining, by the device, that a threshold of a maximum number of SSL VPN users for the first site has been reached and responsive to the determination, forwarding requests to the second site.

11. A system for load balancing based on a number of Secure Socket Layer Virtual Private Network (SSL VPN) users, the system comprising:

a device configured to receive;

a first number of Secure Socket Layer Virtual Private Network (SSL VPN) users of a first site of a plurality of sites distinguished from users of the first site that are not SSL VPN users and accessing one or more servers of the first site, and a second number of SSL VPN users of a second site distinguished from users of the second site of the plurality of sites that are not SSL VPN users and accessing one or more servers of the second site, wherein the second number of SSL VPN users is different from the first number of SSL VPN users; and

a virtual server of the device configured to load balance, based at least on number of SSL VPN users across the plurality of sites, requests of clients among the first site and the second site using at least the first number of SSL VPN users and the second number of SSL VPN users.

12. The system of claim 11, wherein the device is further configured to receive the first number of SSL VPN users from a second device load balancing a plurality of servers at the first site.

13. The system of claim 11, wherein the device is further configured to receive the second number of SSL VPN users from a second device load balancing a plurality of servers at the second site.

14. The system of claim 11, wherein the device is further configured to receive the first number of SSL VPN users accessing servers at the first site via a SSL VPN session.

15. The system of claim 11, wherein the device is further configured to receive second number of SSL VPN users accessing servers at the second site via a SSL VPN session.

16. The system of claim 11, wherein each of the first number of current SSL VPN users and the second number of current SSL VPN users comprises an average number of SSL VPN users over a predetermined time period.

17. The system of claim 11, wherein each of the first number of current SSL VPN users and the second number of current SSL VPN users comprises a peak number of SSL VPN users.

18. The system of claim 11, wherein the virtual server is further configured to load balance requests of clients for accessing via an SSL VPN session a server at one of the plurality of sites.

19. The system of claim 11, wherein the virtual server is further configured to provide load balancing comprising global server load balancing by resolving domain names to internet protocol addresses of servers at the plurality of sites.

20. The system of claim 11, wherein the virtual server is further configured to determine that a threshold of a maximum number of SSL VPN users for the first site has been reached and responsive to the determination, forward requests to the second site.