Power on and vmotion operations blocked in an NSX-T environment
search cancel

Power on and vmotion operations blocked in an NSX-T environment

book

Article ID: 317176

calendar_today

Updated On:

Products

VMware NSX Networking

Issue/Introduction

Symptoms:

The following symptoms are observed:
  •  ESXi hosts were previously added and then removed from an Overlay Transport Zone
  •  vmotion is blocked in the Web Client wizard at network compatibility checks with an error vdl2 down
   "Currently connected network interface" 'Network adapter 1' uses network 'VM_NETWORK:vdl2 down)'. which is not accessible.
  •  The vdl2 component is present on the ESXi host even though it is not part of Overlay TZ
   #net-dvs | grep component_list
  com.vmware.common.opaqueDvs.status.component_list = nsxa,vdl2,vswitch,lcp.ccpSession,lcp.liveness,lcp.vdl2SyncStatus,lcp.kcpSyncStatus
  •  vdl2 status is down. vCenter reads this information and blocks the vmotion
  #net-dvs | grep "component.vdl2"
   com.vmware.common.opaqueDvs.status.component.vdl2 = down , propType = RUNTIME


Environment

VMware NSX-T Data Center
VMware NSX-T Data Center 2.x

Cause

When an ESXi host is added to an Overlay Transport Zone, the vdl2 component is added to the host.
This component should be removed automatically when the ESXi host is removed from the Transport Zone.
Due to an issue present in NSX-T 2.4.0 the vdl2 component may not be correctly removed from the host.

Resolution

This issue is resolved in NSX-T Data Center 2.5.0 and above.

Workaround:
To workaround this issue unconfigure NSX on the ESXi host, this will remove the vdl2 component.
The ESXi host can then be reconfigured for NSX.

Powered by Wolken Software