VMware vMotion error at 14%
Issue
While performing vMotion, the operation fails at 14% with the below error :
A general system error occurred: Migrtion to host <Destination ESXi IP> failed with erro Connection closed by remote host, possibly due to timeout (0xbad003f).
Migrate virtual machine:A general system error occurred: Migration to host <Destination ESXi IP> failed with error Connection closed by remote host, possibly due to timeout (0xbad003f).
vMotion migration [-1062729272:1406020861428172] (19-71629048648008) failed to receive...
Scenarios
Scenario 1: Your management network and vmotion network are in the same subnet using the same physical NIC.
Consider the case, where the management network and vmotion network are in the same subnet and you have assigned a VLAN id to the vMotion network, the operation fails at 14%.
My first point will be to avoid using same IP subnet for both management and vmotion networks. Because if you use the same subnet, all the vmotion traffic will be forwarded to the physical NIC connected to the management network. Because, by default all traffic from vmkernel portgroups from the same subnet will be forwarded to the first NIC configured in the ESXi for that IP subnet. Obviously this will be the management network.
And if you still stick to the plan of using same subnet, please make sure that you have not assigned any VLAN id to the vMotion portgroup.
What happens when we assign a VLAN to the vMotion portgroup ? vMotion vmknic will try to communicate with the default gateway and since the default gateway is not tagged with the VLAN id you choose for vMotion, the operation fails.
Scenario 2: Your management network and vmotion network are in the same subnet using different physical NIC (may be using different vswitches as well).
The comments in the above scenario applies to this scenario also. It doesn't matter if you have created a new vSwitch or a new portgroup or a dedicated physical NIC for the vmotion network, if your management network is in the same subnet, do not assign a VLAN id to the portgroup.
Scenario 3: Your management network and vmotion network are in different subnet.
In this case you need to check the physical switch configuration.
While performing vMotion, the operation fails at 14% with the below error :
A general system error occurred: Migrtion to host <Destination ESXi IP> failed with erro Connection closed by remote host, possibly due to timeout (0xbad003f).
Migrate virtual machine:A general system error occurred: Migration to host <Destination ESXi IP> failed with error Connection closed by remote host, possibly due to timeout (0xbad003f).
vMotion migration [-1062729272:1406020861428172] (19-71629048648008) failed to receive...
Scenarios
Scenario 1: Your management network and vmotion network are in the same subnet using the same physical NIC.
Consider the case, where the management network and vmotion network are in the same subnet and you have assigned a VLAN id to the vMotion network, the operation fails at 14%.
My first point will be to avoid using same IP subnet for both management and vmotion networks. Because if you use the same subnet, all the vmotion traffic will be forwarded to the physical NIC connected to the management network. Because, by default all traffic from vmkernel portgroups from the same subnet will be forwarded to the first NIC configured in the ESXi for that IP subnet. Obviously this will be the management network.
And if you still stick to the plan of using same subnet, please make sure that you have not assigned any VLAN id to the vMotion portgroup.
What happens when we assign a VLAN to the vMotion portgroup ? vMotion vmknic will try to communicate with the default gateway and since the default gateway is not tagged with the VLAN id you choose for vMotion, the operation fails.
Scenario 2: Your management network and vmotion network are in the same subnet using different physical NIC (may be using different vswitches as well).
The comments in the above scenario applies to this scenario also. It doesn't matter if you have created a new vSwitch or a new portgroup or a dedicated physical NIC for the vmotion network, if your management network is in the same subnet, do not assign a VLAN id to the portgroup.
Scenario 3: Your management network and vmotion network are in different subnet.
In this case you need to check the physical switch configuration.
Thanks for the good in site of vmotion failures..
ReplyDeleteIts really helped me to understand ESXi
ReplyDeletenetwork connectivity.
Good information. Also, I have seen scenarios like vMotion fails because of the RAM of virtual machine is higher like 200 or 300GB.
ReplyDelete