Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
You are performing an NVDS to VDS migration with version 7.0.0 VDS in VCenter with LACP FastMode enabled.In the VMware NSX UI when you attempt to create the VDS to be used for the migration, you get the following error displayed: Error Message: Failed to create VDS The creation of the VDS fails with the following errors in the NSX-T manager appliance in /var/log/proton/nsxapi.log. ERROR NvdsUpgradeTaskExecutor1 VcDvsOperation 7210 SWITCHING [nsx@6876 comp="nsx-manager" errorCode="MP8347" level="ERROR" subcomp="manager"] Failed to create or configure vds CVDS-nvds-overlayERROR NvdsUpgradeTaskExecutor1 DistributedVirtualSwitchOperationImpl 7210 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP8347" level="ERROR" subcomp="manager"] Failed to create DVS com.vmware.nsx.management.lcm.vc.soap.exceptions.CmFabricVcOperationFailedException: VC operation failed : The operation is not supported on the object.ERROR NvdsUpgradeTaskExecutor1 NvdsUpgradeReadinessCheckServiceImpl 7210 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP250008" level="ERROR" subcomp="manager"] Failed to create VDS CVDS-nvds-overlay on ComputeManager 62c1cc83-58bc-4788-bf0f-1ba741d0f3b4: com.vmware.nsx.management.switching.sync.host.DvsExecutionException: FAILED_TO_CREATE_VDS_ON_VC Also in the same file we see /var/log/proton/nsxapi.log we see it as VDS 7.0.0: INFO NvdsUpgradeTaskExecutor1 VcDvsOperation 7210 SWITCHING [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Creating DVS using spec (vim.CreateSpec) {... productInfo = (vim.dvs.ProductSpec) { dynamicType = null, dynamicProperty = null, name = DVS, vendor = VMware, Inc., version = 7.0.0, build = 00000, forwardingClass = cswitch, bundleId = null, bundleUrl = null... In the NSX-T manager log /var/log/syslog you can see the VDS is set to 7.0.0: INFO NvdsUpgradeTaskExecutor1 VcNsxDvsUtils 7210 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] DVS version is set to 7.0.0 In vCenter logs /var/log/vmware/vpxd/vpxd.log we see it is set as 7.0.0 and LACP Fast Mode: info vpxd[21742] [Originator@6876 sub=Default opID=36fa4] [VpxLRO] -- ERROR task-1079 -- dvs-xxxx -- vim.dvs.VmwareDistributedVirtualSwitch.updateLacpGroupConfig: vmodl.fault.NotSupported:...key = "LacpFastMode", value = "7.0.0"
The LacpFastMode feature is not supported in vSphere VDS 7.0.0, which causes the VDS creation, triggered by NVDS migration, to fail in vCenter.
Make sure the version of vSphere VDS is 7.0.2 or higher.
To workaround this issue, upgrade the vSphere VDS to 7.0.2 or higher.For details on upgrading a VDS version please review the vSphere Networking Document.Reapply the topology in NSX-T and manually configure LACP in vCenter and: Get the URT topology using below rest API: GET https://<nsx-manager-ip>/api/v1/nvds-urt/topology/<precheck-id> Apply the URT topology using below rest API with the response received from above step as input payload. POST https://<nsx-manager-ip>/api/v1/nvds-urt/topology?action=apply Verify that the apply topology is successful and URT status summary shows precheck_status as "READY" using below rest API: GET https://<nsx-manager-ip>/api/v1/nvds-urt/status-summary/<precheck-id> Locate the new VDS in vCenter, navigate to Configure tab -> LACP, and Click on New.Manually configure LACP settings on the VDS in vCenter by adding a new link aggregation group.Verify the configuration matches the LACP settings in the NSX-T UI (System>Uplink Profiles>Select and edit the related Uplink profile) for the Uplink profile used in the NVDS.The default MTU set on CVDS (Converged VDS) is 1700 please verify this MTU value and change it if required.NVDS to CVDS migration can be triggered for the hosts after this, please review the Migrate Host Switch to vSphere Distributed Switch guide for further details.