While performing VMware vMotion, the operation fails at 14%. What could be the possible reasons? One reason could be If your management network and vMotion network are in the same subnet using the same physical NIC, and you have assigned a VLAN id to the vMotion network, then this operation will fail. 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.
By default all traffic from VMkernel port-groups 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. So, 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.
Subscribe to:
Post Comments (Atom)
What option on VMware vSphere will help you avoid morning boot storm VMs, storage related issues?
(Choose one) Comment Your Suggested Answer! A. Configure vCenter HR ad DRS B. Cluster/ESXi Storage DRS C. Enable Storage I/O Control D. VMFS...
-
Explain the difference between vpxd and vpxa. HOSTD- This is the agent of ESX server, where VPXA pass the information to the HOSTD and hostd...
-
You tried to remove a host from a VMware vSphere Distributed Switch (vDS) and got the following error message: "The resource ’9’ is in ...
-
When the ESXi and VMs in a vCenter server appears to be disconnected what should you try to fix the issue? - (vpxa) a service which runs in ...
No comments:
Post a Comment