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
The Avi Controllers are classified into the following categories:
| Classification | vCPUs | Memory (GB) |
|---|---|---|
| Essentials | 4-8 | 12-24 |
| Small | 8-15 | 24-32 |
| Medium | 16-23 | 32-48 |
| Large | >24 | >48 |
For more details on CPU memory usage, refer to Avi Controller Sizing guide.
Note: Starting with Avi Vantage release 20.1.5, a new classification of Avi Controller has been introduced which is available as Essentials.
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.
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 |