Host-level policies for global server load balancing
DC CAFCFirst Claim
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 first load balancing policy is used by the load balancing switch to rank addresses associated with said first domain and said second load balancing policy is used by the load balancing switch to rank addresses associated with said second domain.
4 Assignments
Litigations
0 Petitions
Reexaminations
Accused Products
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.
-
Citations
19 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 first load balancing policy is used by the load balancing switch to rank addresses associated with said first domain and said second load balancing policy is used by the load balancing switch to rank addresses associated with said second domain. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. 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, 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 and different from said first domain; and using said first load balancing policy by the load balancing switch to rank addresses associated with said first domain, and using said second load balancing policy by the load balancing switch to rank addresses associated with said second domain. - View Dependent Claims (12, 13, 14)
-
-
15. 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. - View Dependent Claims (16, 17, 18, 19)
Specification