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

Troubleshooting vmkernel ports used for vMotion (59590)

Last Updated: 12/7/2018Categories: TroubleshootingTotal Views: 15822Language:
English

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

Cross vCenter vMotion allows a running VM to be moved from one vCenter instance to another. Long Distance vMotion (LDVM) is a feature of vSphere 6.x optimizes the move of a running VM between two hosts with latency below 150ms. This is often desired at greater than campus distances. At a mechanical level, this means "moving" the running VM instance from a sending ESXi instance to a receiving ESXi instance, for more information see Understand vMotion networking requirements.

When such migrations fail, which typically happens due to intermediate routers or firewalls, it may be necessary to troubleshoot specific vmkernel ports used by LDVM.

Cause

LDVM transfer failures require specific syntax to troubleshoot using directed egress of packets.

Resolution

The LDVM is effected by the transfer of two distinct kinds of data. These flows may use two different communications paths. For more information see Understand vMotion networking requirements.

When LDVM does not succeed, troubleshoot that the required ports communicate properly.

From a command line on a given ESXi host, diagnose that basic routing is correctly configured on the network between ESXi hosts. Exploit network diag (the successor to vmkping) between ESXi-Seattle and ESXi-Dallas, for example:

esxcli network diag ping -I vmk0 --netstack=defaultTcpipStack -H 10.81.20.x

In this case, the default TCP/IP stack at vmk0 is used for Management of the ESXi host, which we will use for packet egress of "pings." These packets are aimed towards the Management vmkernel port of a remote ESXi Server at 10.81.20.x, in this example. Use the real IP address of your target ESXi host. Perform this test in both directions. Note: the Management vmkernel is NOT required directly between ESXi servers for LDVM - but the success/failure of this "ping" is still a useful data point.

esxcli network diag ping -I vmk1 --netstack=vmotion -H 10.81.30.x

In this case, the vmotion stack at vmk1 is used for vMotion, which we will use for packet egress of "pings." These packets are aimed towards the vMotion vmkernel port of a remote ESXi Server at 10.81.30.x, in this example. Use the real IP address of your target ESXi host. Perform this test in both directions.This netstack is used to transfer the memory state of the running VM, plus certain other "hot" items.
Note: The real IP address of your target ESXi host is the vMotion vmkernel IP of the target ESXi host.

esxcli network diag ping -I vmk2 --netstack=vSphereProvisioning -H 10.81.40.x

In this case, the vSphereProvisioning stack at vmk2 is used for so-called provisioning of VMs, which we will use for packet egress of "pings." These packets are aimed towards the vSphereProvisioning vmkernel port of a remote ESXi Server at 10.81.40.x, in this example. Use the real IP address of your target ESXi host. Perform this test in both directions.

This netstack is used to transfer the bulk of disk blocks of the running VM, plus certain other "cold" items.
Note: vmkernel diagnostic "pings" are really kernel-directed TCP/IP packets, not ICMP.

"VMs located on datastores other than internal storage (including Fibre Channel, iSCSI, NFS, or a vMSC stretched cluster) will fail to copy their VM disks over a non-default vSphereProvisioning vmkernel port using NFC, regardless of hypervisor configuration. As such, in any hardened architectures with VLANs that are air-gapped by purpose, a long-distance vMotion (LDVM) may fail over non-default vmkernel ports. This is a known bug."

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
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vCenter Server

Related Versions:

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

VMware vCenter Server 6.5.x

VMware vCenter Server 6.0.x

Take Our Survey

Support Assistant