Hi,   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.   This very very bad!!!!   NetApp PLEASE!!! Update the HCL at VMware!!!! ... View more

Latest  Virtual Storage Console for VMware vSphere only supports up to vSphere 6.7 For a while now VMWare went to vSphere version 7. What is the ETA for a new version of  Virtual Storage Console for VMware vSphere and a NetApp NFS Plug-in for VMware VAAI  that supports vSphere 7 ? In a demo pool I implemented a virtual storage console on a vSphere 7. The VASA ( NetApp NFS Plug-in for VMware VAAI 1.1.2)  provider is installed on the ESXi hosts but showing as not being capable of hardware acceleration in the vSphere 7 client. The option to Rapid clone is not available. The virtual storage console is available and shows information inside the vSphere 7 client but there isn't much to do. It lost alot of functionality compared to vSphere 6.7 environment. ... View more

We had an unusual event last week that I wanted to share.  I had seven VMs on a NetApp NFS-based vVol.  Our Cohesity backups kicked off at 3:01pm and by 3:04pm, the VMDK files for six of those VMs went missing (the .vmdk descriptor files were still there, but the .vmdk file containing the actual data were somehow inaccessible).  All versions of software were supported per NetApp's IMT: VMware versions were 7.0U1, VSC was 9.7.1P1, ONTAP was  9.7P6, VAAI plugin was 2.0.  The one remaining VM on the same vVol was undamaged, and two other VMs on a separate vVol also remained intact.  We've never had trouble with Cohesity backing up hundreds of other VMs on "regular NFS" datastores and this was the first time we'd seen trouble on a vVol datastore.   We were able to restore the VMs from backups taken the previous day and with little/no data loss.  I currently have ticket 2008782637 in with NetApp on how to delete the suspect vVol because vCenter won't allow it.  (vCenter thinks that VMs still reside on the vVol and it's probably right - even though the old, broken VMs have been deleted, their VMDKs likely exist *somewhere* in the vVol.)  The only recent change I made was that I moved one VM to the impacted vVol and two VMs off of it in the hours before the backup.  (vVols had been working so well for us that I wanted to put another production VM on vVols and remove two non-production ones.)   I'll continue to use vVols, but only for test VMs for the near future. ... View more

Hi, I have allocated couple of NetApp LUNs from different filer to a Vmware host ? Now how do I identify NetApp LUN IDs along with their Filer name or serial number ? Thanks Raj ... View more