Considerations for vCenter Cloud while upgrading from releases prior to 22.1.1

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

• vCenter Read Access mode is not supported starting with NSX Advanced Load Balancer22.1.1. The deprecation was announced in 21.1.3 Release Notes. Any upgrade to 22.1.1 with vCenter Read Access mode cloud configuration will fail and get rolled back.

• 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:

    Avi Internal Port group is not used starting with NSX Advanced Load Balancer 22.1.1. The upgraded Service Engines from the prior release will retain the vNICs attached to Avi Internal Port-group, but any vNIC updated later will start using the Service Engine management network/ port-group.

• Starting with NSX Advanced 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 NSX Advanced Load Balancer 22.1.1, the existing vCenter APIs and CLIs are modified. Refer to vCenter Cloud API CLI guide.