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