NVDS to CVDS migration failed in the customer environment

Products

• VMware NSX

Issue/Introduction

- During NVDS to CVDS migration, APPLY_TOPOLOGY gets FAILED.

- We can see the following error in nsxapi.log :

2024-06-27T17:36:52.113Z ERROR NvdsUpgradeTaskExecutor1 DVPortgroupOperation 4393 SWITCHING [nsx@6876 comp="nsx-manager" errorCode="MP9701" level="ERROR" subcomp="manager"] Create nsx portgroup failed for vds: dvs-##### on vc 1961ea09-####-####-#### : VC operation failed : A specified parameter was not correct: spec.shaper.averageBandwidth,
com.vmware.nsx.management.lcm.vc.soap.exceptions.CmFabricVcOperationFailedException: VC operation failed : A specified parameter was not correct: spec.shaper.averageBandwidth

- If we check the QOS profile on the LS which we give in vmk install mappings, we can see the values greater than 2047.

Environment

NSX-T 3.2

Cause

This issue happens during NVDS to CVDS migration if we have the QoS profile configured with traffic shaping values greater than 2047 Mb/sec. When the Segment used in vmk install mappings has this QoS profile attached to it, during port group creation, we see this issue.

Resolution

Workaround:

1. Update the Qos profile by changing the values greater than 2047 to 2047.

2. Run apply topology with the same payload as before:
POST https://{{server_ip}}/api/v1/nvds-urt/topology?action=apply

3. After applying the topology, please check nvds-urt status-sumary using below rest-api
GET https://<nsx_manager_ip>/api/v1/nvds-urt/status-summary/<precheck_id>
The response should have precheck_status as READY and overall_state for migration_state for each transport node as UPGRADE_READY.

4. Change the traffic shaping policies on VC on the created PortGroup to the desired value as below : 
Select Portgroup -> click on configure -> select policies from settings -> EDIT -> select Traffic Shaping -> Modify values -> Save the configuration.

5. If precheck_status is READY in step-3, then trigger NVDS to CVDS migration for individual transport node using below rest-api.
Please try to trigger NVDS to CVDS migration for only one host first. If succeeded, then trigger NVDS to CVDS migration for rest of the hosts one by one.
POST https://<nsx_manager_ip>/api/v1/transport-nodes/<tn_id>?action=migrate_to_vds