Loading

×Sorry to interrupt
CSS Error

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 fails with network errors (1030264)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 44180Language:
Chinese (Simplified)JapaneseEnglish

10 like this article

Subscribe to get an email
newsletter with new updates

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

Symptoms

You see errors similar to:

Example 1:

The VMotion failed because the ESX hosts were not able to connect over the VMotion network. Please check your VMotion network settings and physical network configuration.
VMotion [184329483:1276605211167987] failed to create connection with remote host <10.252.164.14>: The ESX hosts failed to connect over the VMotion network
Migration [184329483:1276605211167987] failed to connect to remote host <10.252.164.14>: Timeout

Example 2:

The VMotion failed because the ESX hosts were not able to connect over the VMotion network. Please check your VMotion network settings and physical network configuration.
VMotion [-1408237366:1279683851917265] failed to create connection with remote host <172.16.1.204>: The ESX hosts failed to connect over the VMotion network
Migration [-1408237366:1279683851917265] failed to connect to remote host <172.16.1.204>: Connection refused

In the /var/log/hostd.log file, you see entries similar to:

[27703B90 verbose 'Vmsvc.vm:/vmfs/volumes/5538de90-249141cc-a57c-40f2e9638530/TEMP-TEMP/TEMP-TEMP.vmx'] Handling message _vmx1: Migration [a991333:1451374787315531] failed to connect to remote host from host : Timeout

Impact / Risks

Network misconfiguration can cause random vMotion failures. Retrying the vMotion operation may be successful, but VMware recommends that you follow this article to isolate and correct the problem.

Resolution

To resolve this issue:

Check for IP address conflicts on the vMotion network.

Note: Each host in the cluster should have a vMotion vmkernel, assigned a unique IP address.

Check for packet loss over the vMotion network. Try having the source host ping (vmkping) the destination host's vMotion vmknic IP address for the duration of the vMotion.

For example:

vmkping -I vmkX <IP of destination host vMotion vmk>

Where vmkX is the vmkernel number of the vMotion vmkernel on the source host.

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

Check the driver/firmware of the physical adapter used for vMotion.

Note: If the driver or firmware is not up to date, the vMotions can fail with a "timeout" or "waiting for data" error. For more information, see Determining Network/Storage firmware and driver version in ESXi (1027206).

Ensure the ESXi firewall ruleset for vMotion is enabled and that there are no other conflicting rules blocking the traffic.

Note: For information on configuring the ESXi firewall, see the VMware documentation page ESXi Firewall Configuration

Check for potential interaction with firewall hardware or software that prevents connectivity between the source and the destination TCP port 8000.

Related Information

For more information on vMotions and troubleshooting vMotion issues, see Understanding and troubleshooting vMotion (1003734).

Other examples:

Migration [184329483:1276605211167987] failed to connect to remote host <10.252.164.14>: Timeout.

This error indicates that remote host did not accept the connection within the allowed time limit.

Migration [-1408237366:1279683851917265] failed to connect to remote host <172.16.1.204>: Connection refused.

This error indicates that the remote host is explicitly not listening on the vMotion port.

Additional Articles

Troubleshooting vMotion network connectivity issues (65184)

ネットワーク エラーで vMotion が失敗する (1030264)

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

VMware ESX Server

Related Versions:

Take Our Survey

Support Assistant