HCX VM's vNIC in disconnected state after vMotion or RAV switchover
search cancel

HCX VM's vNIC in disconnected state after vMotion or RAV switchover

book

Article ID: 328984

calendar_today

Updated On:

Products

VMware HCX

Issue/Introduction

Identify known issue.

Symptoms:
vNIC is in disconnected state after vMotion relocation or RAV switchover.

Cause

If the VM relocation process takes more than one hour, the NSX port sync-up process will remove the inactive port from the vDS, which was created at the beginning of the workflow and it is not connected until relocation has completed.
When the VM becomes active on target, the port will not be available and the vNIC will end up in disconnected state.

Resolution

The issue is resolved in HCX service update R143. Upgrade to that version is required.

Workaround:
Reconnect vNIC after relocation.

Additional Information

Impact/Risks:
All network connectivity will be unavailable therefore service impact is expected for a "hot" migration.
This issue only impacts HCX deployments running service update R142.