Difference between revisions of "VMotion failed with "Failed waiting for data" error"
From Notes_Wiki
(Created page with "<yambe:breadcrumb>VMWare_vCenter|VMWare vCenter</yambe:breadcrumb> =vMotion failed with "Failed waiting for data" error"= If vMotion fails with "Failed waiting for data" then...") |
m |
||
| Line 1: | Line 1: | ||
[[Main_Page|Home]] > [[VMWare platform]] > [[VMWare vCenter]] > [[VMotion failed with "Failed waiting for data" error|vMotion failed with "Failed waiting for data" error]] | |||
If vMotion fails with "Failed waiting for data" then issue could be wrong MTU on various places (vmkernel, vSwitch or physical switch). To resolve try: | If vMotion fails with "Failed waiting for data" then issue could be wrong MTU on various places (vmkernel, vSwitch or physical switch). To resolve try: | ||
| Line 13: | Line 12: | ||
Refer: | Refer: | ||
* https://communities.vmware.com/thread/546954 | * https://communities.vmware.com/thread/546954 | ||
[[Main_Page|Home]] > [[VMWare platform]] > [[VMWare vCenter]] > [[VMotion failed with "Failed waiting for data" error|vMotion failed with "Failed waiting for data" error]] | |||
Latest revision as of 08:55, 7 April 2022
Home > VMWare platform > VMWare vCenter > vMotion failed with "Failed waiting for data" error
If vMotion fails with "Failed waiting for data" then issue could be wrong MTU on various places (vmkernel, vSwitch or physical switch). To resolve try:
- Set MTU 9216 on switch
- Then set MTU 9000 on distributed switch or standard switch
- Then set MTU 8900 on vmkernel ports which use the port-groups on corresponding vswitches
- Then try below ping command with -s 8800 and see if it works
- vmkping -d -s <size> -I <vmk1> <IP>
Refer:
Home > VMWare platform > VMWare vCenter > vMotion failed with "Failed waiting for data" error
