/var/log/vpxa.log displays the following error:(vim.fault.InvalidDeviceSpec) {
faultCause = (vmodl.MethodFault) null,
property = "virtualDeviceSpec.device.backing",
deviceIndex = 13
msg = "Invalid configuration for device '13'."
}
deviceIndex = 13 corresponds to a network adapter requesting a connection to a Distributed Virtual Switch (DVS) with a specific port key and connection cookie:(vim.vm.device.VirtualDeviceSpec) {
operation = "add",
fileOperation = <unset>,
device = (vim.vm.device.VirtualVmxnet3) {
dynamicProperty = <unset>,
key = 4000,
deviceInfo = (vim.Description) {
label = "Network adapter 1",
summary = "DVSwitch: <MAC_ADDRESSES>"
},
backing = (vim.vm.device.VirtualEthernetCard.DistributedVirtualPortBackingInfo) {
port = (vim.dvs.PortConnection) {
switchUuid = "<REDACTED_MAC_ADDRESSES>",
portgroupKey = "dvportgroup-######",
portKey = "##",
connectionCookie = ##############
}
}
}
}ESXi: 8.x
VC: 8.x
VCF: 5.x
TCP: 5.x
A stale Distributed Virtual Port allocation state within the vCenter Server Database (VCDB) causes a mismatch with the ESXi host's local DVS proxy switch, resulting in an invalid configuration fault during migration.
Right-click the affected virtual machine in the vSphere Client and select Edit Settings.
Locate the Network Adapter corresponding to the device index from the error (e.g., Network Adapter 1 for device 13). Note the current Distributed Port Group.
Temporarily change the Network Adapter connection to any different, valid Port Group and click OK.
Right-click the virtual machine and select Edit Settings again.
Revert the Network Adapter connection back to the original Distributed Port Group and click OK.
Retry the Storage vMotion operation.