some time ago i installed the 9.7.1 VSC in my vSphere 7.0.1 environment and created a VVOL datastore. I migrated VM's from NFS 4.1 datastores to the VVOL datastore without problems.
But when doing a "compute" vMotion the process stuck at 85% for 30 to 40 sec. In this time the VM freezes.
I had a NetApp case open, they found nothing in the logs but told me that they currently don't support the 7.0.1 but they adon't know that there are issues in that kind, i should open a case at VMware. VMware made some research but don't found something too in the the logs.
To send this case in the next level i should bring my environment to a from VMware supported version, but in the VMware HCL the newest versions are:
ESXi 6.5 U3
VASA Provider 7.1P1 (end of support since jan 2019)
ONTAP 9.4 (end of support since jun 2019)
So VMware closes the case...
Today i updated my VSC to 9.7.1P1, but the vMotion issue is still present.
So i have an issue and can't get help!
Now the environment is supported by NetApp IMT, but this don't help when NetApp told me to open a case at VMware, and they don't help me because NetApp has missed to update the HCL at VMware.
It took some effort especially with some previous NetApp versions, but we finally got vVols running stably with our NetApps. The latest versions of ONTAP and NetApp's VASA seem to work pretty well. I haven't run into the same problem jcolonfzenpr is having; that's an interesting one.
I doubt it's involved here, but never place the VSC/VASA/SRM VM on a vVol (and probably not the VCSA either). Leave those on "regular" storage.
Engineering is working on certifying our VASA Provider, but ran into a minor failure with 9.7.1 that blocked certification. I believe they are working to certify 9.7 now, and will address the issue so 9.8 can be certified. I am sorry for the limited certification in the VCG.
Regarding your original issue (slow vMotion), we have been working with VMware on this and recently learned that there is a problem with NFS file locking that slows migration of VMs on vVols datastores. The bug is 2668244 and is targeted to vSphere 7.0U2. There are also several other vVols optimizations in7.0U1 and U2 that should improve migration times.
By the way, we are still working with VMware on NFSv4.1 datastores. We don't currently list support for v4.1 datastores in the NetApp IMT due to VMs being occasionally powered off during a storage failover. We continue working with them on this and hope to resolve this soon.
thank you very much for that informations! And a happy new year!
But i'm wondering, when i look into the IMT and search for VSC 9.7.1 or for the VASA provider then the combination of VASA/VSC 9.7.1 / ONAP 9.8 / vSphere 7.0.1 is shown as supported with no additional note.
This is very confusing...
The problems with NFS 4.1 i'm aware, but i have only a single node system here, so i can ignore that problem.
The bug id you wrote, that insn't a NetApp id, correct? Because i can't find that id...
So i just tryed to install the 7.0.2 (december beta) on my hosts, to look if the vMotion problem in that version is alredy resolved, but when booting that iso, the H410C giving me a PSOD:
Failed at bora/modules/vmkernel/rdma/driver/rdma-driver.c:545 -- VMK_ASSERT(deviceAttr.nodeGuid != 0)
I will do some research or open a vmware beta case...
Yes, we worked with VMware through much of 2020 to resolve that one, after they identified and fixed the 'datastore inaccessible' problem in earlier releases. Yet, we identified one more infrequent problem in recent testing that we are working on right now.
O.k. in my testing environment i see currently no issues with NFS 4.1 datstores (non VVOL), it's running very well.
I dicovered only a little problem in the VSC 9.7.1 and 9.7.1p1 with the NFS host settings in a vSphere 7.0.1 environment, but i think this has Andreas yesterday already reported in your direction, because he was able to see the same issue in his new version. 🙂