FelipeMachado
Enthusiast
Enthusiast

vMotion failed at 10%. Insufficient network bandwidth

I'm having trouble performing a vMotion migration of a virtual machine between two ESXi hosts in my cluster. The migration fails with an error message stating 'vMotion failed at 10%. Insufficient network bandwidth.' However, my network seems to be running fine, and I've successfully performed vMotion in the past. What could be causing this issue, and how can I troubleshoot and resolve it?

flube
Enthusiast
Enthusiast

The 'vMotion failed at 10%. Insufficient network bandwidth' error indicates limited network resources during vMotion. Troubleshoot by checking for network congestion, MTU settings, and connectivity between hosts. Verify proper host configuration, port group settings, and resource contention. Restart management agents if needed.

Or take a look on one of this:

  1. Network Congestion: Even if your network appears fine, temporary spikes in network traffic or congestion during the vMotion process could cause the error. Check for any other heavy network activity or bandwidth-intensive tasks on the involved hosts or network segments.

  2. MTU Settings: The Maximum Transmission Unit (MTU) size must be consistent across all networking components involved in the vMotion process. Ensure that the MTU size is large enough to accommodate vMotion packets without fragmentation.

  3. Connectivity Issues: Verify that there are no connectivity problems between the source and destination hosts. Ensure you can successfully ping each host from the other, and validate DNS resolution for both hosts.

  4. Network Configuration: Double-check the network settings on both ESXi hosts participating in the vMotion. Confirm that they are on the same subnet, and they can communicate with each other.

  5. Port Group Settings: Ensure that the VMkernel port for vMotion is correctly associated with the appropriate distributed or standard port group, and it has the necessary permissions.

  6. Resource Contention: Inspect the resource utilization on both the source and destination hosts, including CPU, memory, and storage. If either host is experiencing high contention, it could lead to vMotion failure.

  7. Restart Management Agents: If all else seems normal and the issue persists, consider restarting the management agents on both ESXi hosts using the vSphere client or SSH.

  8. vMotion Network: If you have a dedicated vMotion network, verify that it is functioning correctly and that it is not shared with other traffic to avoid contention.

By carefully reviewing these aspects and addressing any issues found, you can troubleshoot and resolve the 'Insufficient network bandwidth' error during vMotion migration in your VMware environment. Remember to document any changes made during troubleshooting for future reference.

 

Tell me if you need any help... :grinning_face_with_big_eyes:

View solution in original post

FelipeMachado
Enthusiast
Enthusiast

Thanks for sharing

Reply
0 Kudos
Mortuza1
Contributor
Contributor

MUT check for both logical and physical end.