In an NSX-v environment, a virtual machine's NIC is unable to connect to an NSX-v logical switch
Article ID: 407351
Updated On:
Products
Issue/Introduction
- Attempting to connect the virtual machine to an NSX-v logical switch fails.
- No error is visible in the NSX-v Graphical Interface.
- On the ESXi host supporting the VM, in /var/log/vmkernel.log, lines similar to the below are seen:
2025-08-13T13:09:37.721Z cpu59:50101065)Net: 2184: connected <VirtualMachineName>.eth0 eth0 to vDS, portID 0x####8ca
2025-08-13T13:09:37.721Z cpu59:50101065)netschedHClk: NetSchedHClkCreateQueue:5266: vmnic4: Multiple vnic queue not enabled on port ######546 for pool netsched.pools.vm.######546, no multiple tx vnic world being in use
2025-08-13T13:09:37.721Z cpu59:50101065)netschedHClk: NetSchedHClkCreateQueue:5306: vmnic4: look up for vm leaf pool tag gave out ######546
2025-08-13T13:09:37.721Z cpu59:50101065)netschedHClk: NetSchedHClkCreateQueue:5266: vmnic3: Multiple vnic queue not enabled on port ######546 for pool netsched.pools.vm.######546, no multiple tx vnic world being in use
2025-08-13T13:09:37.721Z cpu59:50101065)netschedHClk: NetSchedHClkCreateQueue:5306: vmnic3: look up for vm leaf pool tag gave out ######546
2025-08-13T13:09:37.721Z cpu59:50101065)Net: 3007: associated dvPort 8922 with portID 0x####8ca
...
2025-08-13T13:09:37.750Z cpu59:50101065)Vmxnet3: 14113: indLROPktToGuest: 1, vcd->umkShared->vrrsSelected: 3 port 0x####8ca
2025-08-13T13:09:37.750Z cpu59:50101065)Vmxnet3: 14380: Using default queue delivery for vmxnet3 for port 0x####8ca
2025-08-13T13:09:37.750Z cpu59:50101065)Vmxnet3: 1727: UPT feature is disabled.
2025-08-13T13:09:37.750Z cpu59:50101065)NetPort: 3054: resuming traffic on DV port ###2
2025-08-13T13:09:37.750Z cpu59:50101065)vxlan: VDL2_CPSetCPEnabled:4394: Control plane enabled on VXLAN network[###0]
2025-08-13T13:09:37.750Z cpu59:50101065)NetIOChain: 158: Failed to insert IOChain to port 0x####8ca for iocl is not ready for new lock model
2025-08-13T13:09:37.750Z cpu59:50101065)nsx-traceflow: TF_InsLeafOutputIOChain:844: Fail to insert traceflow leaf output iochain for port: 0x[####8ca] : Not supported
2025-08-13T13:09:37.750Z cpu59:50101065)vxlan: VDL2_DestroyNetwork:1999: Control plane not ready, defer freeing VNI[###0]
2025-08-13T13:09:37.750Z cpu59:50101065)vxlan: VDL2SetPortVNI:2608: Block port[0x####8ca] on VDS[DvsPortset-#]
2025-08-13T13:09:37.750Z cpu59:50101065)WARNING: vxlan: VDL2PortPropSet:727: Failed to create VXLAN port[0x####8ca] on VDS[DvsPortset-#] : Not supported
2025-08-13T13:09:37.750Z cpu59:50101065)WARNING: NetDVS: 2786: Failed to write critical property com.vmware.net.vxlan.id on port 8922, return :Not supported.
2025-08-13T13:09:37.750Z cpu59:50101065)DVFilter: 1117: Ignoring property clear during migration: port ######546 (name = com.vmware.common.port.dvfilteraltvmx)
2025-08-13T13:09:37.750Z cpu59:50101065)WARNING: NetPort: 1568: failed to enable port, portID: 0x####8ca, status: Not supported
2025-08-13T13:09:37.750Z cpu59:50101065)netschedHClk: NetSchedHClkPortQuiesce:7153: vmnic4: received a force quiesce for port 0x####8ca
2025-08-13T13:09:37.750Z cpu59:50101065)netschedHClk: NetSchedHClkPortQuiesce:7153: vmnic3: received a force quiesce for port 0x####8ca
2025-08-13T13:09:37.750Z cpu59:50101065)NetPort: 1810: disabled port 0x####8ca
2025-08-13T13:09:37.750Z cpu59:50101065)Vmxnet3: 17070: Port_Enable failed for port 0x####8ca
2025-08-13T13:09:37.751Z cpu25:2098251)DVFilter: 4164: During creation, got endPointType of 0
- From the ESXi host cli, the following properties are found on the vDS
#esxhost-cli> net-dvs -l | grep -E "com.vmware.common.opaqueDvs.status.component.lcp.vdl2SyncStatus|com.vmware.common.opaqueDvs.status.component.nsxa|com.vmware.common.opaqueDvs.status.component.lcp.kcpSyncStatus|com.vmware.common.opaqueDvs.status.component.lcp.ccpSession"com.vmware.common.opaqueDvs.status.component.lcp.ccpSession = up , propType = RUNTIMEcom.vmware.common.opaqueDvs.status.component.nsxa = up , propType = CONFIGcom.vmware.common.opaqueDvs.status.component.lcp.kcpSyncStatus = up , propType = RUNTIMEcom.vmware.common.opaqueDvs.status.component.lcp.vdl2SyncStatus = up , propType = RUNTIME - The host is prepared for NSX-v.
Environment
VMware NSX Data Center for vSphere
Cause
The failure to write the NSX-v required property com.vmware.net.vxlan.id to the vDS is caused by the ESXi host having once been an NSX prepared host. Moving from VMware NSX or VMware NSX-T to NSX-v is not a supported procedure.
The settings component.lcp.ccpSession, component.nsxa, component.lcp.kcpSyncStatus, and component.lcp.vdl2SyncStatus are VMware NSX-T 3.x, VMware NSX 4.x, and newer settings that are incompatible with NSX-v. These settings being present on the vDS mean NSX-T 3.x or VMware NSX 4.x/newer VIBs have been installed on the ESXi host and have been removed, to be replaced with NSX-v VIBs. Uninstalling the NSX-T 3.x or VMware NSX 4.x/newer VIBs from a host does not remove these settings from the vDS.
Resolution
Perform a complete host re-image, using an ESXi image that does not have any NSX (NSX-v, NSX-T 3.x, or VMware NSX 4.x/newer) VIBs installed. This will ensure the vDS is free of incompatible settings for NSX-v virtual machines and logical switches.
Moving an ESXi host from a VMware NSX-T 3.x or VMware NSX 4.x/newer installation to any version of NSX-v without a reimage is an unsupported operation.
Additional Information
Please note that NSX-v has been out of support and technical guidance since January 16, 2023.
Instructions on how to migrate from NSX-v to VMware NSX are in the Migration Guide.
Feedback
