A three-node Controller cluster deployment is a requirement for optimum operation of the NSX Advanced Load Balancer.
NSX Advanced Load Balancer Controller Sizing Guidelines for CPU and Memory
The amount of CPU/memory capacity to allocate to the Controller is calculated based on the following parameters:
The number of virtual services to support
The number of Service Engines to support
Analytics thresholds
CPU/ Memory Allocation |
8 CPUs / 24 GB |
16 CPUs / 32 GB |
24 CPUs / 48 GB |
|---|---|---|---|
Maximum Virtual Service Scale |
200 |
1000 |
5000 |
Maximum NSX Advanced Load Balancer Service Engine Scale |
100 |
200 |
400 |
NSX Advanced Load Balancer Controller Sizing Guidelines for Disk
The amount of disk capacity to allocate to the Controller is calculated based on the following parameters:
The amount of disk capacity required by analytics components
The number of virtual services to support
Disk allocation based on VS count |
Log analytics without full logs |
Log analytics with full logs |
Metrics |
Base processes |
Total (without full logs) |
|---|---|---|---|---|---|
100 VS |
16 GB |
128 GB |
16 GB |
48 GB |
80 GB |
1,000 VS (100k transactions / year) |
128 GB |
1 TB |
32 GB |
56 GB |
216 GB |
5,000 VS |
512 GB |
Not supported |
160 GB |
64 GB |
736 GB |
Decision ID |
Design Decision |
Design Justification |
Design Implication |
|---|---|---|---|
AVI-CTLR-022 |
Deploy one Controller cluster for each NSX Manager cluster for configuring and managing load balancing services. |
Required to form a highly available Controller cluster. |
None |
AVI-CTLR-023 |
Deploy each node in the Controller cluster with a minimum of 8 vCPUs, 24GB memory and 216 GB of disk space. |
Support up to 200 virtual services. Support up to 100 NSX Advanced Load Balancer Service Engines. Can scale-up with expansion of the Controller sizes anytime.
Note:
Under sizing, the Controllers can lead to unstable control plane functionality. |
None |
