Abstract: Example methods and systems for service-aware global server load balancing are described. One example may involve a first load balancer receiving, from a client device, a request to access a service associated with an application deployed in at least a first cluster and a second cluster. In response to determination that a first pool in the first cluster is associated with an unhealthy status, the first load balancer may identify a second pool implementing the service in the second cluster, the second pool being associated with a healthy status and includes one or more second backend servers selectable by a second load balancer to process the request. Failure handling may be performed by interacting with the client device, or the second load balancer, to allow the client device to access the service implemented by the second pool in the second cluster.

Abstract: Example methods and systems for capability-aware service request distribution are described. In one example, a network element may obtain a set of capability information associated with multiple load balancers capable of service request handling and identify varying capability levels among the multiple load balancers. The network element may assign unequal path cost information to the multiple load balancers to indicate the varying capability levels. The unequal path cost information may include (a) a first path cost that is assigned to the first load balancer; and (b) a second path cost that is assigned to the second load balancer and different to the first path cost to indicate the lower capability level of the second load balancer compared to the first load balancer. In response to detecting a service request, the service request may be steered towards one of the multiple load balancers based on the unequal path cost information.

Abstract: Example methods and systems for capability-aware service request distribution are described. In one example, a network element may obtain a set of capability information associated with multiple load balancers capable of service request handling and identify varying capability levels among the multiple load balancers. The network element may assign unequal path cost information to the multiple load balancers to indicate the varying capability levels. The unequal path cost information may include (a) a first path cost that is assigned to the first load balancer; and (b) a second path cost that is assigned to the second load balancer and different to the first path cost to indicate the lower capability level of the second load balancer compared to the first load balancer. In response to detecting a service request, the service request may be steered towards one of the multiple load balancers based on the unequal path cost information.