High latency vMotion networks
Article ID: 334291
Updated On:
Products
Issue/Introduction
ESXi has detected 6ms round-trip vMotion network latency between host 192.xyz.1.1 and 192.xyz.1.2. High latency vMotion networks are only supported if both ESXi hosts have been configured for vMotion latency tolerance.
This message is received if vMotion detects a 5ms or higher network Round Trip Time(RTT) latency between the source and destination hosts, and if the two hosts are not configured with the Metro vMotion feature. Metro vMotion is automatically enabled with Enterprise Plus licensing. With other licensing types, Metro vMotion is disabled.
If you do not have Metro vMotion, you can still perform the vMotion under high latency conditions. However, high latency impacts vMotion performance, and with large enough latency causes vMotion to fail, leaving the environment as it was before the migration was attempted.
Environment
Resolution
If you see this message, check the latency between the vMotion hosts. If the RTT latency between the hosts is greater than or equal to 5ms, consider upgrading to Enterprise Plus licensing in order to leverage latency awareness or Metro vMotion optimizations. Metro vMotion supports up to 10ms RTT between vMotion hosts.
If you are unable to utilize Metro vMotion, you may have to resort to cold migration. High latency may also be a condition correctable by network performance analysis and remediation.
Additional Information
For translated versions of this article, see:Feedback
