HTTP load balancing in an Avaya Breeze® platform cluster

Last Updated : Oct 09, 2017 |
Prolog information
Metadata
Keywords:
Enable load balancing for a cluster if you want to scale the HTTP services without targeting a particular Avaya Breeze® platform server. All the requests are sent to the cluster IP address. When you enable load balancing, two Avaya Breeze® platform servers are chosen as the active and standby load balancing servers. The active load balancer distributes the HTTP requests to all the other servers in the cluster in a round robin fashion.
The following cluster attributes must be configured for HTTP load balancing:
Name
Description
HTTP Load Balancer backend server max failure response timeout period (seconds)
The maximum timeout period of the failure response of the HTTP Load Balancer backend server. The default value is 15.
Max number of failure responses from HTTP Load Balancer backend server
The maximum number of failure responses from the HTTP Load Balancer backend server. The default value is 2.
Network connection timeout to HTTP Load Balancer backend server (seconds)
The network connection timeout period from the HTTP Load Balancer backend server. The default value is 10.

Load balancing validations

The following are the validations when you enable load balancing in a cluster:
  • Load balancing is not supported in a single server cluster.
  • By default the load balancing check box is not selected.
  • For load balancing to function, the cluster must have two Avaya Breeze® platform servers that have the SIP Entity IP addresses in the same subnet as the cluster IP address. The active server starts a network alias using the cluster IP address. If the active server is down, the standby starts a network alias with the cluster IP address. The standby server takes over as the active load balancer.
  • With load balancing, you cannot remove the active or the standby Avaya Breeze® platform server from the cluster unless another server in the cluster meets the subnet validation.

Session affinity

Session affinity ensures that all the requests from the same client are directed to the same back end Avaya Breeze® platform server in a cluster. Session affinity is mandatory for snap-ins like the WebRTC Connect.
To enable session affinity, select the Is session affinity cluster attribute.
Use the Trusted addresses for converting to use X-Real-IP for session affinity cluster attribute to enter trusted addresses that are known to send correct replacement addresses so thatAvaya Breeze® platform load balancer can use the real client IP when an HTTP request traverses through reverse proxies like Avaya Session Border Controller. The header which is used to identify the real client IP address is X-Real-IP
Related links
Cluster administration