For NGINX and High Availability, Avaya Oceana® clusters require the following configuration changes:
Avaya Oceana® Cluster 1
On the Cluster Editor page of Avaya Oceana® Cluster 1:
Set the HTTP Load Balancer backend server max failure response timeout period (seconds) field to 60.
Set the Max number of failure responses from HTTP Load Balancer backend server field to 2.
Set the Network connection timeout to HTTP Load Balancer backend server (seconds) field to 3.
Avaya Oceana® Cluster 2
On the Cluster Editor page of Avaya Oceana® Cluster 2:
Set the HTTP or HTTPS traffic rate limit in bytes/sec per client field to 5000000.
Set the HTTP Load Balancer backend server max failure response timeout period (seconds) field to 60.
Set the Max number of failure responses from HTTP Load Balancer backend server field to 2.
Set the Network connection timeout to HTTP Load Balancer backend server (seconds) field to 3.
Avaya Oceana® Cluster 3
On the Cluster Editor page of Avaya Oceana® Cluster 3:
Set the HTTP Load Balancer backend server max failure response timeout period (seconds) field to 60.
Set the Max number of failure responses from HTTP Load Balancer backend server field to 2.
Set the HTTP or HTTPS limit on connections per client field to 8000.
For a 100-agent deployment, set the HTTP or HTTPS limit on connections per client field to 6000.
Set the Network connection timeout to HTTP Load Balancer backend server (seconds) field to 3.
Other Avaya Oceana® clusters
On the Cluster Editor page of the other Avaya Oceana® clusters:
Set the Max number of failure responses from HTTP Load Balancer backend server field to 2.
Set the Network connection timeout to HTTP Load Balancer backend server (seconds) field to 3.
The upgrade script automatically applies these changes. However, the new customers who perform a manual installation must manually apply these changes.
Note:
These changes also apply to the 100-agent deployments where you deploy Avaya Oceana® Cluster 2 on Avaya Oceana® Cluster 1.
However, for 100-agent deployments, you must set the HTTP or HTTPS limit on connections per client field to 6000.
