Considerations for vCenter Cloud while upgrading from releases prior to 22.1.1

Consider the recommendations and restrictions below while upgrading the Avi Load Balancer Controller from releases prior to 22.1.1.

• The Service Engine management network (Port-group) needs to be provisioned with required free ports as per the planned number of Service Engines multiplied by 10.

  • For instance, if the administrator plans to deploy 50 Service Engines, then the management network/ port-group allocated from Avi Service Engine should have at least 500 unused ports (50 Service Engines * vNICs per Service Engine).

    Note:

    To better support vMotion and DRS, the Avi Load Balancer Controller Internal Port group is no longer used starting with Avi Load Balancer Controller version 22.1.1. Instead, unused vNICs are attached to the configured Management Port Group in a disconnected state. Service Engines upgraded from an earlier release will retain any vNICs attached to the Avi Load Balancer Controller Internal Port Group until a new virtual service placement occurs, at which point unused vNICs will be re-attached to the Management Port Group. The Avi Load Balancer Controller Internal Port Group can be deleted once there are no Service Engines connected to it.

• Starting with Avi Load Balancer 22.1.1, the vCenter cloud configuration has a new option use_content_lib to utilize the content library for storing the Service Engine ova instead of storing on respective ESXi host. Post upgrade to the 22.1.1 version, for new Service Engine deployment, you can configure the content library as part of vCenter cloud configuration. Once this option is configured, it cannot be disabled.

• Starting with Avi Load Balancer 22.1.1, the existing vCenter APIs and CLIs are modified. Refer to vCenter Cloud API CLI guide.