Unable to migrate from NVDS to VDS, APPLY_TOPOLOGY gets FAILED

Products

• VMware NSX Networking

Issue/Introduction

Unable to migrate From NVDS to VDS due to high QOS profiles configuration 

Environment

all versions before and including 3.2.5 could potentially hit this issue.

Cause

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

 

Symptoms: 

- During NVDS to CVDS migration we are getting error on API APPLY_TOPOLOGY gets FAILED.

API call: 

GET https://<nsx-mgr>/api/v1/nvds-urt/status-summary/<precheck-id>

- On the nsxapi.log  (NSX-t manager) we are going to get the following error: 

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-331122 on vc 111.1111.1111.111 : 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

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