Unable to migrate virtual machine in NSX-T prepared hosts - vdl2: down
search cancel

Unable to migrate virtual machine in NSX-T prepared hosts - vdl2: down

book

Article ID: 322430

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

Issue 1:

  • The hosts are prepared for NSX-T Overlay traffic.
  • The TEP (Tunnel End Point) interface have been configured to get their IP addresses from DHCP
  • The vDL2 module is down, which will cause vMotion to fail for any VM on an Overlay or VLAN-backed NSX segment
  • The error seen on screen when trying to connect to a logical network looks like this:
  • Run the following command on the host:
net-dvs | grep "component.vdl2"
  • In the result you will see the vdl2 component status is down:
com.vmware.common.opaqueDvs.status.component.vdl2 = down , propType = RUNTIME
  • To check on the ESXi host if it obtained the correct IP address or a link local address, run the following command:
esxcli network ip interface ipv4 get
  • The below image shows the TEP interface of an EXi host, vmk10 using a link local address and it is configured for DHCP:



Issue 2:

  • Post patching of ESXi host transport node and rollback caused issue with the vDL2 module down, which will cause vMotion to fail for any VM on an Overlay or VLAN-backed NSX segment.
  • vdl2 NSX-T data plane component responsible for logical switching.
  • This issue can be validated using the /var/log/proton/nsxapi.log from NSX manager, Confirms the NSX configuration realization error for a particular transport node.
    • Log reference: 
      • 2025-07-21T02:47:24.688Z  INFO com.vmware.nsx.management.policy.policyframework.realization.StatusTracker RealizationStateServiceImpl 76694 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Returning current realization status 'Status = 'UNKNOWN', Message = 'Unable to collect status for '1' transport node.', TNs = TN = '<Problematic Host TN UUID>', Status = 'UNKNOWN', Message = 'This CCP is not the master of this TN.[ NSX-Controller <NSX Controller UUID>:

 

Environment

VMware NSX-T

Cause

This issue can occur when a host is prepared for NSX-T and the TEP interfaces used for overlay traffic are configured to obtain IP addresses from DHCP.

Under /var/run/log/vobd.log, we could see log entries 'Could not get a lease on interface vmk10'.



Therefore if the ESXi host is unable to get an IP address from the DHCP server, the TEP interface will use an address from the Link Local address range.

Resolution

Issue1:
  • This is a configuration issue, please make sure the interface configured for overlay traffic on the ESXi host are able to connect to the DHCP server and obtain an IP address.
  • If this is the case, also make sure there are sufficient IP address available in the DHCP range.
 
issue 2:
  • Since the controller configuration did not realized on the problematic host transport node, Perform a rolling reboot of NSX managers one at a time by maintaining the cluster stability.
  • Keep the problematic host transport node into maintenance mode from vCenter, Move the problematic host transport node to a datacenter from cluster to remove NSX configuration and add it back to the cluster. NSX configuration will be readded to the problematic host transport node. Test the vMotion.

Additional Information

Powered by Wolken Software