nsxaVim: [2103354]: INFO Port [spfPortd##########] does not have networkId. Skip port deletion/block^@nsxaVim: [2103354]: INFO Port [6a183086-####-####-####-#########] does not have networkId. Skip port deletion/block^@nsxaVim: [2103354]: INFO Port [8f5413c0-####-####-####-#########] does not have networkId. Skip port deletion/block^@
nsxaVim: [2103354]: ERROR Dvs [d5 0b 99 ## ## ## ## ##-## ## ## ## ## ## ## ##] cannot be deleted; dvport e78d21d4-####-####-####-######### with externalId [35c5e3c5-####-####-####-#########] is link up; dvport 26cc7bd4-####-####-####-######### with externalId [12f841af-####-####-####-#########] is link upnsxaVim: [2103354]: INFO Add com.vmware.vswitch.disabled for dvs [d5 0b 99 be ## ## ## ## ##-## ## ## ## ## ## ## ##]^@
VMware NSX
The issue was caused by an incomplete migration of VMkernel adapters (vmk0 and vmk1) from the legacy N-VDS (nvds_overlay) to the new VDS.
Although the new switch was introduced, the VMkernel adapters remained bound to the old N-VDS, which was not fully decommissioned. This left the nvds_overlay switch in a disabled yet partially active state, preventing full cleanup and causing configuration inconsistencies on the host
esxcfg-vmknic -l