Migrate virtual machine:
The vMotion failed because the destination host did not receive data from the source host on the vMotion network. Please check your vMotion network settings and physical network configuration and ensure they are correct
This scenario is kind of V-Motion issue stopping your patching activity as this is only way to perform live migration of running virtual machines and keep the ESXi maintenance mode. You started checking the V-Motion related settings like VMKernel, IP address and port group settings but all of them looks good. You tried to perform vmkping command from source to destination host but it failed. It seems there is communication issue for the V-Motion network and VLAN associated with it. When you engaged Network team to validate the connectivity, they confirm no firewall rule changes and other IP’s are able to communicate in the same subnet. This scenario forced you to check other settings. Upon more investigation you found that these are HP Blade servers and V-Motion network is configured as Internal network which doesn’t have an uplink associated. HP confirmed it’s known issue with the current Openview/c7000/Flex backend network settings. After contacting HP support they suggested to move the V-Motion network to another port group where communication is not broken. This helped you to migrate all the VM’s to other ESXi servers in the cluster to complete the patching activity.
The vMotion failed because the destination host did not receive data from the source host on the vMotion network. Please check your vMotion network settings and physical network configuration and ensure they are correct
This scenario is kind of V-Motion issue stopping your patching activity as this is only way to perform live migration of running virtual machines and keep the ESXi maintenance mode. You started checking the V-Motion related settings like VMKernel, IP address and port group settings but all of them looks good. You tried to perform vmkping command from source to destination host but it failed. It seems there is communication issue for the V-Motion network and VLAN associated with it. When you engaged Network team to validate the connectivity, they confirm no firewall rule changes and other IP’s are able to communicate in the same subnet. This scenario forced you to check other settings. Upon more investigation you found that these are HP Blade servers and V-Motion network is configured as Internal network which doesn’t have an uplink associated. HP confirmed it’s known issue with the current Openview/c7000/Flex backend network settings. After contacting HP support they suggested to move the V-Motion network to another port group where communication is not broken. This helped you to migrate all the VM’s to other ESXi servers in the cluster to complete the patching activity.
No comments:
Post a Comment