Does it make sense to open a SR to get more acceleration? What certification is meant, maybe I can get further informations internal?
I've been banging my head against the exact same issue cjohannsen for weeks. Its frustratingly difficult to find any documentation on the subject and I've been getting less than useful information from the EMC and VMware tickets I have open on it. In the mean time cloning VMs continues to be agonizingly slow. I should have stayed on block.....
Indeed. No official statement, no solution, no knowledge. Seems like there isn´t a solution for NFS My customer has implemented 2x 10GB NICs per Server and there is no additional value with VAAI...
There are 2 parts to the VAAI for NFS on VNX. One is the support within the OE code within the VNX. Second is the vStorage plug-in that gets installed in the ESX server.
This second piece is currently in certification testing with eLabs for inclusion on both the EMC and VMware compatibility matrices......I will provide more details as they become available.
The VSI plug-ins that are currently on Powerlink which is 184.108.40.206 for Unified Storage Management and 220.127.116.11 for Storage Viewer don't quite pull it off. I also have gone so far as to install the SMI-S provider and Solution Enabler v18.104.22.168-1305 in an attempt to get Storage Profiles working. Frankly I'm disappointed in this round of EMC "solutions". This stuff used to be built into the FLARE code when I was using block. I only went after NFS because thats what EMC/VMware were preaching as best practice and how to get deduplication. I frankly dont mind if the plugin is certified if its close. Taking an hour to deploy a new VM from template is beyond frustrating.
@kendcollins Is there any official statement when this will happen? It is really annoying to tell the customer that there is something in progress... over weeks!
The VSI plug-ins are not related to VAAI support or the vStorage Plug-in.
Here's the difference:
VSI plugs into vSphere client to interact with vCenter for out-of-band (outside of the data path) management.
vStorage plug-in installs into the ESX server and issues in-band (within the data path) commands to detect/etc VAAI support on the array.
Xanlith - please send me any/all details including what you are trying to accomplish. I cannot tell if you are having an issue trying to execute a VSI feature/function vs getting VAAI working??? or something else??
Working on getting official word for you.....understood on the frustration part, hopefully we get this resolved very quickly.
Not sure this will help but, it is a start.
If an unsupported operation is attempted, the array returns an error to ESX and the ESX server will use its native method to perform the operation. VNX OE for File v7.0.35.X and Block R31.5.5xx supports VAAI with FC, iSCSI, and NFS protocols.
Please note that the ESX server must also support these features.
One can verify that VAAI functionality is enabled on the ESX server using vSphere. Navigating to the ESX server, Configuration tab, and choosing the Advanced Settings under Software brings up the Advanced Settings window. The HardwareAcceleratedparameters found in the DataMoversection and the HardwareAcceleratedparameter found in the VMFS3 section indicate whether VAAI is enabled on the ESX server. If the parameter is set to "1," the VAAI feature is enabled. If the parameter is set to "0," the VAAI feature is disabled. The features are enabled by default.
The esxcfg-advcfg command can also be used to set and get the HardwareAccelerated parameters.
The –s option is used to set the parameter, and the –g option is used to get the current setting.
Thanks for jumping into the fray. I've also escalated my SR on this and my account representative has gotten me in touch with her vSpecialist as well.
Unfortunately the ESXi servers and the VNX both are at the code level necessary to enable VAAI and the feature parameters are set to 1 but regardless Hardware Acceleration remains at "Not Supported". I've seen a few articles that suggest VMFS5 is at fault and that if you build your stores with VMFS3 and then upgrade to VMFS5 they remain supported but I dont have the environment necessary to test that since my stores are all in production already.