Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

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

Last Updated: 6/12/2020Categories: TroubleshootingTotal Views: 7488Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

The hosts are prepared for NSX-T Overlay traffic.

The hosts have not been moved between transport zones, there is another issue which has same error, this is dealt with in this KB: 68088

The TEP (Tunnel End Point) interface have been configured to get their IP addresses from DHCP

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:

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.
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

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.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Android Enterprise の新しい EMM 登録が断続的に失敗する (79429)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T

Take Our Survey

Support Assistant