HCX - Network disconnected on VM after Cold migration into VMware Cloud Director environment
Article ID: 328960
Updated On:
Products
VMware HCX
Issue/Introduction
Identify a known issue with HCX Cold migration services when deployed in a cloud environment running VCD 10.2.x version.
Symptoms:
VMs will have their network interfaces disconnected after Cold migration into a cloud environment with VMware Cloud Director 10.2.x.
Symptoms:
VMs will have their network interfaces disconnected after Cold migration into a cloud environment with VMware Cloud Director 10.2.x.
Cause
As per VCD workflow, when a powered off VM is imported into VCD, it re-configures the startConnected flag for the NICs to 'false' and also sets the network to 'none'.
However, when the VM is powered on, it resets the network and startConnected flag to be the same as before the import.
In VCD 10.2.x, the VM after power on is connected to the correct network but startConnected flag remains 'false', leading to the NIC being in disconnected state.
However, when the VM is powered on, it resets the network and startConnected flag to be the same as before the import.
In VCD 10.2.x, the VM after power on is connected to the correct network but startConnected flag remains 'false', leading to the NIC being in disconnected state.
Resolution
Final resolution is pending VCD code changes.
Workaround:
The user must reconnect all network interfaces manually prior to powering up VMs migrated to the cloud using Cold migration.
Workaround:
The user must reconnect all network interfaces manually prior to powering up VMs migrated to the cloud using Cold migration.
Additional Information
Impact/Risks:
VMs Cold migrated into the VMware Cloud Director environment running with 10.2.x will lose all network connectivity upon powered on.
VMs Cold migrated into the VMware Cloud Director environment running with 10.2.x will lose all network connectivity upon powered on.
Feedback
Yes
No
Powered by
