Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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 vMotion network connectivity issues (65184)

Last Updated: 3/30/2021Categories: Best PracticesTotal Views: 111882Language:
Chinese (Simplified)JapaneseEnglish

18 like this article

Subscribe to get an email
newsletter with new updates

18 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Purpose

This article provides information about the tools that can be used to troubleshoot vMotion network connectivity issues.

Resolution

To troubleshoot network connectivity issues for vMotion:

Identify which vmknics are used for vMotion on both hosts.

Option 1 Using the vCenter Server User Interface (UI)

Notes: All VMkernel adapters with vMotion Enabled will be used for vMotion. For more information on how to enable vMotion on VMkernel adapters, see Creating a VMkernel port and enabling vMotion on an ESXi/ESX host (2054994). For best practices on which VMkernel adapters to enable for vMotion, see the Networking Best Practices for vSphere vMotion section of the vCenter Server and Host Management Guide.

Option 2 Using the ESXi command line

esxcli network ip interface list

Sample output:

vmk0
Name: vmk0
MAC Address: 02:00:45:02:26:65
Enabled: true
Portset: vSwitch0
Portgroup: Management Network
Netstack Instance: defaultTcpipStack
VDS Name: N/A
VDS UUID: N/A
VDS Port: N/A
VDS Connection: -1
Opaque Network ID: N/A
Opaque Network Type: N/A
External ID: N/A
MTU: 1500
TSO MSS: 65535
RXDispQueue Size: 1
Port ID: 33554436

For each VMkernel adapter entry, run this command:

esxcli network ip interface tag -i [VMkernel adapter name]

Example command:

esxcli network ip interface tag -i vmk0

Any adapters with tag value vMotion will be used for vMotion.

Sample vMotion VMKernel adapter value:

Tags: VMotion

Run diagnostic tools between source and destination vMotion VMkernel adapters

vmkping

vmkping uses a VMkernel’s TCP/IP stack to send ICMP traffic to a destination host.

Suppose you have source vMotion VMkernel adapter vmk0 with IP 192.168.0.1, and destination vMotion VMkernel adapter vmk0 with IP 192.168.0.2.

From source ESXi host, run this command:

vmkping -I vmk0 192.168.0.2

Similarly, from destination ESXi host, run this command:

vmkping -I vmk0 192.168.0.1

For more information on vmkping, see Testing VMkernel network connectivity with the vmkping command (1003728).

OR

Run this command: vmkping --help

With long distance vMotion, the maximum supported RTT is 150 miliseconds.

nc

nc is the netcat utility and can be used to verify connectivity on a specific remote port.

Suppose you have source vMotion VMkernel adapter vmk0 with IP 192.168.0.1, and destination vMotion VMkernel adapter vmk0 with IP 192.168.0.2. Since vMotion listens on port 8000 of the vMotion VMkernel adapter, you need to verify if you can establish a connection to port 8000.

From source ESXi host, run this command:

nc -z 192.168.0.2 8000

From destination ESXi host, run this command:

nc -z 192.168.0.1 8000

Sample successful output:

Connection to 192.168.0.2 8000 port [tcp/*] succeeded!

For more information on nc and troubleshooting specific tcp/ip port connectivity issues, see:

Troubleshooting network and TCP/UDP port connectivity issues on ESX/ESXi (2020669)

Troubleshooting vMotion fails with network errors (1030264)

Workaround

VMware Skyline Health Diagnostics for vSphere - FAQ (81931)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

Take Our Survey

Support Assistant