Host vMotion to a host that has access to the same datastore fails

[Dziva]

I have 3 hosts in one hostset, that has access to VLUN "Test_clone" and another host that is not part of the hostset but has access to the same VLUN "Test_clone" exported directly. All the 4 hosts can see "Test_clone" volume in the vCenter. I have tried host vmotion (CPU and memory only) for a VM in one of the hosts in the hostset to the host that is not in the hostset. After the VM vmotion operation I am unable to ping the migrated VM. But if i vmotion the same VM to either of the hosts in the same hostset, it's working perfectly. Can someone explain to me why this is so? My second question is that is it safe for me to add the host to the hostset without first unexporting the "Test_clone" volume from the direct export

[Sanika]

Hi @Dziva 

The issue you are facing with vMotion might be because of network-related performance issues between the hosts.

Migration with vMotion requires correctly configured network interfaces on source and target hosts.

According to my understanding, in your scenario, the standalone host might be configured with a separate network for VM traffic compared to hostset.
Ensure all hosts involved use the same VLANs for VM traffic.
Check that vMotion is enabled on a VMkernel port on both the source & target hosts.
Also, configure hosts for vMotion with shared storage to ensure that virtual machines are accessible to both source and target hosts.

Here are some resources related to the similar scenario which could be helpful:
https://kb.vmware.com/s/article/59232
https://kb.vmware.com/s/article/1003734
https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-30FAA00F-D5F3-475D-820E-5D45517AC18E.html
https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-7DAD15D4-7F41-4913-9F16-567289E22977.html

And in my opinion, I think it is safe to add the host to the hostset without first unexporting to the volume from the direct export. Adding a host to a hostset associates the host with the set of volumes defined for the hostset. It may not modify the exisiting direct export.

However, I would still recommend to contact HPE support team as they can provide specific guidance and assistance in troubleshooting and addressing this problem.

Hope this helps.

Regards,
Sanika.

If you feel this was helpful, please click the KUDOS thumb below. Also consider marking this as an "Accepted Solution", if the post has helped to solve your issue.

[Sanika]

Hi Dziva,

Let us know if your concern has been addressed.

If you have no further query and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.

Regards,
Sanika.