VM's lost connectivity after vMotion triggered by DRS. VM's ports are deleted from NSX and are in blocked state on host.
search cancel

VM's lost connectivity after vMotion triggered by DRS. VM's ports are deleted from NSX and are in blocked state on host.

book

Article ID: 375527

calendar_today

Updated On:

Products

VMware NSX Networking VMware NSX VMware NSX-T Data Center

Issue/Introduction

  • DRS migrated VM's loose network connectivity
  • When viewing the vDS port state for the problem VM, you see that the VM's ports are in blocked state.

Environment

VMware NSX
VMware NSX-T Data Center

Cause

This issue occurs because:

  • While vmotion is triggered, one of the manager restarts.
  • Opsagent, times out with ATTACH_VIF request.
  • DETACH_VIF request is received and port gets deleted on MP side.
  • Port gets blocked on host.

Relevant logs :

ESXi support bundle : /var/run/log/nsx-syslog.log :

<Date> nsx-opsagent[2110371]: NSX 2110371 - [nsx@6876 comp="nsx-esx" subcomp="opsagent" s2comp="nsxa" tid="2111144" level="ERROR" errorCode="MPA42003"] [DoMpVifAttachRpc] MP_AddVnicAttachment() failed: RPC call to NSX management plane timeout
<Date> nsx-opsagent[2110371]: NSX 2110371 - [nsx@6876 comp="nsx-esx" subcomp="opsagent" s2comp="nsxa" tid="2111144" level="INFO"] [DoVifPortOperation] request=[opId:[########-##-##-##-##-####-##] op:[HOSTD_ATTACH_PORT(1)] vif:[########-####-####-####-############] ls:[########-####-####-####-############] vmx:[/vmfs/volumes/vsan:################-################/########-####-####-####-############/VM_name.vmx] lp:[]]

Port deletion logs in NSX manager support bundle : /var/log/proton/nsxapi.log :

<Date> INFO L2TaskExecutor4 LogicalPortServiceImpl 6607 SWITCHING [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Schedule a delayed deletion task for logical port LogicalPort [id=<logical_port_uuid>, logicalPortState=UP, ephemeral=true, logicalSwitchId=LogicalSwitch/########-####-####-####-############, transportZoneId=TransportZone/########-####-####-####-############, transportZoneType=OVERLAY, vif=########-####-####-####-############, vifType=vif, switchingProfileIds=null, switchMode=STANDARD, extraConfigs=null, internalId=<logical_port_uuid>, initState=null, tags=null, pendingConfigFromHostd=true], expected starting time = 1722472307104.

<Date> INFO L2TaskExecutor4 LogicalPortServiceImpl 6607 SWITCHING [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] dvport [logical_port_uuid] to be detached on host: [host-uuid]

Resolution

This is known issue affecting NSX 3.2.*, 4.0.*, 4.1.*

This issue is resolved in VMware NSX 4.2.0, available at
Broadcom downloads.
If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.

Resync task will re-trigger the ATTACH_VIF request with same port Id as that of the deleted port and port will get unblocked. When this issue occurs, re-sync will be triggered after 5 minutes and the issue will get resolved.

Workaround:

Perform a manual vMotion on problematic VM's to a different host.