System Limits
Overview
The NSX Advanced Load Balancer Controller includes a framework for tracking and enforcing various system-wide limits, based on the size of the Controller instances and other parameters.
Controller Classification Sizing
Avi Controller deployments are classified into the following sizing categories which determine the system limits such as the maximum number of Virtual Services that can be configured.
| Classification | Minimum vCPUs | Minimum Memory (GB) |
|---|---|---|
| Essentials* | 4 | 16 |
| Small | 6 | 24 |
| Medium | 10 | 32 |
| Large | 16 | 48 |
The Controller classification is based on meeting the minimum requirements for both vCPU and memory. For instance, a Controller with 12 vCPUs and 28GB RAM will be classified as Small because the minimum memory requirement for Medium classification is not met.
For more details on CPU memory usage, refer to Avi Controller Sizing guide.
Note: Starting with NSX Advanced Load Balancer release 20.1.5, the Essentials Controller size is supported. But, it can only be used for a Controller deployed in the Essentials license tier in conjunction with VMware Tanzu solutions and running on-premises in a VMware environment.
This applies only to on-premises VMware vCenter Cloud deployments with Tanzu, on a single-node Avi Controller.
System Limits
This section provides the recommended configuration limits for VMware products. While configuring, ensure that the mentioned limits are maintained.
For more details on configuration limits, refer to VMware Configuration Limits guide. Ensure that you select the correct software version in VMware Configuration Maximum window. If the specific release being deployed is not listed, select the closest release below the version being deployed.
Behavior on Upgrade from a pre-20.1.1 Release
An upgrade from a pre-20.1.1 release, with the object count exceeding the defined limits, is allowed. However, additional creation/updates for the object will fail with an error.
Example Scenarios
-
The Controller cluster with 8 vCPU/24 GB RAM, and having 200 virtual services, is upgraded from 18.2.9 to 20.1.1. In this case, the upgrade will succeed. However, the creation of an additional (201st) virtual service or updates to the virtual services will fail.
-
The Controller cluster with 8 vCPU/24 GB RAM, and having one Virtual Service and one Pool having 2050 servers, is upgraded from 18.2.9 to 20.1.1. In this case, the upgrade will succeed. However, editing of the pool will not be allowed.
Document Revision History
| Date | Change Summary |
|---|---|
| April 06, 2022 | Revamped the content |