Host-level policies for global server load balancing

• US 7,584,301 B1
• Filed: 05/06/2004
• Issued: 09/01/2009
• Est. Priority Date: 05/06/2004
• Status: Expired due to Fees

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Foundry Networks Incorporated (Broadcom, Inc.)
• Inventors: Joshi, Prajakta S.
• Primary Examiner(s): WON, MICHAEL YOUNG
• Application Number:
  US10/839,919
• Time in Patent Office: 1,944 Days
• Field of Search: 709/203, 709/217, 709/221, 709/224, 709/226, 709/235, 709/241, 709/244, 709/238, 709/239, 709/243, 718/105
• US Class Current: 709/244
• CPC Class Codes: H04L 61/10 of different types
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/50 Address allocation
• CPC Class Codes: H04L 63/0236 Filtering by address, protocol, port number or service, e.g. IP-address or URL
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1012 based on compliance of requirements or conditions with available server resources
• CPC Class Codes: H04L 67/1023 based on a hash applied to IP addresses or costs
• CPC Class Codes: H04L 67/1025 Dynamic adaptation of the criteria on which the server selection is based
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

In a network, a user can configure host-level policies usable for load balancing traffic to servers of a domain. A global server load balancing (GSLB) switch provides load balancing to the servers, and is configured with the GSLB host-level policies. Users can define a host-level policy (alternatively or additionally to a globally applied GSLB policy) and apply the host-level policy to hosts in domains configured on the GSLB switch. Thus, the user can enable different policies for different hosts. This allows the user to have the flexibility to control metrics used for selection of a best address for querying clients, as well as the metric order and additional parameters used in the GSLB process, at the host level.

Claims

1. A method, comprising:

storing, in a load balance switch, a first load balancing policy associated with a first domain and a second load balancing policy associated with a second domain different from the first domain, wherein said first load balancing policy specifies an order in which a first plurality of metrics of said first load balancing policy are to be applied; and

load balancing traffic, by said load balance switch, to network addresses associated with the first and second domains, using corresponding said first and second load balancing policies that are respectively associated to the first and second domains,

wherein said metrics of said first load balancing policy each include at least one parameter, wherein said at least one parameter includes at least one of a tolerance, limit, threshold, DNS parameter, preference, and alternative tie-breaker metric use.

2. The method of claim 1, further comprising using, by said load balance switch, a global load balancing policy to load balance traffic to at least a third domain for which said load balance switch is configured to perform load balancing.

3. The method of claim 2 wherein if a particular metric of the first load balancing policy does not have said at least one parameter specified, a parameter related to said global load balancing policy is associated with that particular metric by said load balance switch.

4. The method of claim 2 wherein said global load balancing policy is a same load balancing policy that is associated with a plurality of different domains, other than said first and second domains, for which said load balance switch is configured to perform load balancing.

5. The method of claim 1 wherein said second load balancing policy specifies an order in which a second plurality of metrics of said second load balancing policy are to be applied.

6. The method of claim 1 wherein said load balancing traffic to the network addresses associated with the first and second domains includes re-ordering, by said load balance switch, a list of addresses that are specified in a response to a query for the addresses.

7. The method of claim 1, further comprising updating, in said load balance switch, one or more metrics and associated parameters for each of the first and second load balancing policies.

8. The method of claim 1, further comprising:

determining, by said load balance switch, whether the first load balancing policy has been defined;

if the first load balancing policy is determined to have been defined, disassociating by said load balance switch a previous load balancing policy from the first domain; and

associating, by said load balance switch, the defined first load balancing policy to the first domain.

9. The method of claim 1 wherein said load balancing traffic to network addresses associated with the first domain includes:

receiving, by said load balance switch, a reply having a list of said network addresses associated with said first domain;

determining, by said load balance switch, whether said first load balance policy has been associated with the first domain; and

obtaining, by said load balance switch, metric information pertaining said first load balancing policy, and using by said load balance switch this obtained metric information to select a preferred network address from said list to receive traffic directed to the first domain,

wherein the method further comprises if said first load balancing policy associated with the first domain cannot be determined by said load balance switch;

obtaining, by said load balance switch, metric information pertaining to a global load balancing policy, and using by said load balance switch this obtained metric information pertaining to said global load balancing policy to select the preferred network address from said list.

10. The method of claim 1 wherein said first domain is identified by at least one of a www, ftp, and other host designation associated with one or more zones.

11. A method, comprising:

associating, by a load balance switch, a first load balancing policy to a first domain associated with a first site switch, wherein said first load balancing policy specifies an order in which a first plurality of metrics of said first load balancing policy are to be applied;

associating, by said load balance switch, a second load balancing policy to a second domain associated with a second site switch and different from said first domain; and

using said first and second load balancing policies at said load balance switch to respectively rank addresses associated with said first and second domains,

wherein said metrics of said first load balancing policy each include at least one parameter, wherein said at least one parameter includes at least one of a tolerance, limit, threshold, DNS parameter, preference, and alternative tie-breaker metric use.

12. The method of claim 11, wherein said second load balancing policy specifies an order in which a second plurality of metrics of said second load balancing policy are to be applied.

13. The method of claim 11, further comprising if a particular load balancing policy is not associated to a particular domain, using by said load balance switch a global load balancing policy to rank addresses associated with said particular domain.

14. The method of claim 11, further comprising if some parameters to be used by the metrics of said first load balancing policy are not specified, using by said load balance switch, parameters from a global load balancing policy for these metrics.

15. An article of manufacture, comprising:

a storage medium having instructions stored thereon that are executable by a processor of a load balance switch to enable load balancing, by;

associating, by said load balance switch, a first load balancing policy to a first domain associated with a first site switch, wherein said first load balancing policy specifies an order in which a first plurality of metrics of said first load balancing policy are to be applied;

associating, by said load balance switch, a second load balancing policy to a second domain associated with a second site switch and different from said first domain; and

using said first and second load balancing policies by the load balance switch to respectively rank addresses associated with said first and second domains,

wherein said metrics of said first load balancing policy each include at least one parameter, wherein said at least one parameter includes at least one of a tolerance, limit, threshold, DNS parameter, preference, and alternative tie-breaker metric use.

16. The article of manufacture of claim 15 wherein the storage medium further includes instructions stored thereon that are executable by said processor to:

use, by said load balance switch, a global load balancing policy, associated with a plurality of domains different from said first and second domains, to rank addresses associated with at least a third domain.

17. The article of manufacture of claim 15 wherein if some parameters of said metrics of said first load balancing policy are not specified, the storage medium further includes instructions stored thereon that are executable by said processor to:

use, by said load balance switch, parameters from a global load balancing policy for these metrics of said first load balancing policy.

18. The article of manufacture of claim 15 wherein the second load balancing policy specifies an order in which a second plurality of metrics of the second load balancing policy are to be applied.

19. A system, comprising:

a means in a load balance switch for storing a plurality of load balancing polices that are respectively associated to a plurality of domains, wherein each of said load balancing policies specify an order of application of a plurality of metrics of each respective load balancing policy; and

a means in said load balance switch for load balancing traffic to network addresses associated with each domain based on at least one of said metrics of a respective one of said load balancing policies respectively associated to each domain,

wherein said metrics, of each respective load balancing policy, each include at least one parameter, wherein said at least one parameter includes at least one of a tolerance, limit, threshold, DNS parameter, preference, and alternative tie-breaker metric use.

20. The system of claim 19 wherein said means for load balancing uses a global load balancing policy to load balance traffic to another domain that does not have one of said stored load balancing policies associated thereto.

21. The system of claim 19 wherein said plurality of metrics are usable by said means for load balancing for determining a preferred address, among a plurality of said network address associated with each domain, to route traffic, said preferred address being placed on top of a list of addresses.

22. The system of claim 19, further comprising:

a means in said load balance switch for sending a query to remote site switches for metric information to be used for each of said load balancing policies.

23. The system of claim 19 wherein said means for load balancing updates said at least one parameter of each metric said stored load balancing policies.

24. An apparatus, comprising:

a load balance switch that includes;

a first storage unit to store a plurality of load balancing policies, which are to be applied by said load balance switch to rank addresses of different domains,

wherein each of said load balancing policies specify an order of application of a plurality of metrics of each respective load balancing policy; and

a controller coupled to the first storage unit to use a respective one of said stored load balancing policies to rank addresses of each one of said domains,

wherein said metrics, of each respective load balancing policy, each include at least one parameter, wherein said at least one parameter includes at least one of a tolerance, limit, threshold, DNS parameter, preference, and alternative tie-breaker metric use.

25. The apparatus of claim 24 wherein the first storage unit includes a database.

26. The apparatus of claim 24 wherein said load balance switch further includes a second storage unit to store a global load balancing policy, and wherein said controller is adapted to use the global load balancing policy to rank addresses of at least one domain that has not been associated with any of the load balancing policies stored in the first storage unit.

27. The apparatus of claim 26 wherein said controller is adapted to use some parameters from the global load balancing policy for any other load balancing policy that does not have corresponding said at least one parameter specified.

28. The apparatus of claim 24 wherein said controller is adapted to update at least one of said load balancing policies.

29. The apparatus of claim 24 wherein said controller is adapted to provide notification if at least one of:

(a) a domain for which a load balancing policy is to be associated is undefined and (b) a load balancing policy for a particular domain is undefined.

30. The apparatus of claim 24 wherein the controller of said load balance switch is adapted to communicate with remote site switches to obtain metric data to be used in said load balancing policies.

31. The apparatus of claim 24 wherein said controller is adapted to use a global load balancing policy for all said domains if said controller is unable to determine which of the stored said load balancing policies to associate to respective said domains.