VMWare vMotion Failing for VM On Nimble VVOL with Snaphot/Replication - Error 195887167

[IanVickery]

We are in the process of setting up a new HPE VMWare solution (2 DCs, Hosts and Nimble AF in each) and I have run into a problem with compute only vMotion migrations of VMs within the same cluster. this came to light when trying to put one of the hosts into Maintenance mode which failed as the VM could not be migrated.

We are using VVOLs and policies to snapshot and replicate the VMs between the Nimbles. When I try to vMotion a VM between hosts within the same cluster (storage staying the same), i get an error as follows - 'Failed waiting for data. Error 195887167. Connection closed by remote host, possibly due to timeout'.

It only does this for VMs stored on VVOLs (VMs on standard LUN migrate without issues) and I think this may have started after setting up the snapshot/replication policy but am trying to verify this currently.

Has anyone else experienced similar issues?

Thanks

Ian

[AAlexanian]

We setup a new vSphere Cluster with no snapshot or replication and we are having the same thing.  Glad We are not the only ones having this issue. Looks like we need to call HP support

[SprinkleJames]

If you're on vSphere 7.0 U1, there's a known issue affecting vMotion with vVols on Nimble. Call Nimble support. They'll have a hotfix for it, depending on your Nimble OS version.

[IanVickery]

Many thanks for that. I will raise a ticket and let you know how it goes.

[Peter_Auyeung]

Any news on this? I think I am hitting the same issue.

Thanks!

Peter

[mamatadesaiNim]

Peter,

Sorry to hear you're having trouble.  There can be different root causes behind similar-looking failures.  I'd encourage you to contact Nimble Support, so your case can be properly triaged & root-caused.

--m

[IanVickery]

Peter,

I am happy to report that this has now been resolved by Nimble Support after application of a patch to our arrays. As always, they were extremely helpful in getting this resolved.

Regards

Ian 

[arik01071]

can you share what patch exactly solved this issue with compute vmotion?