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.

Nick

Adding a section from the VMware KB artice for future use.

vStorage APIs for Array Integration FAQ

Are there any caveats that I should be aware of in ESX/ESXi 4.x? 

There are a few reasons why a hardware-accelerated operation may fail.

For any primitive that the array does not implement, the array returns an error, which triggers the ESX data mover to attempt the operation using software data movement. In the case of ATS, it reverts to using SCSI Reservations.

VAAI hardware offload cannot be used when:

• The source and destination VMFS volumes have different block sizes 
• The source file type is RDM and the destination file type is non-RDM (regular file)  
• The source VMDK type is eagerzeroedthick and the destination VMDK type is thin
• The source or destination VMDK is any sort of sparse or hosted format 
• Cloning a Virtual Machine that has snapshots, since this process involves consolidating the snapshots into the virtual disks of the target Virtual Machine.  
• The logical address and/or transfer length in the requested operation are not aligned to the minimum alignment required by the storage device (all datastores created with the vSphere Client are aligned automatically) 
• The VMFS datastore has multiple LUNs/extents spread across different arrays
• Hardware cloning between arrays (even if within the same VMFS datastore) does not work.

Read the full KB Article:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1021976

Carles, Here is a article talking about vSphere 5 VAAI features, http://blogs.vmware.com/vsphere/2011/07/new-enhanced-vsphere-50-storage-features-part-3-vaai.html you might look at “

What about NAS?”

section elaborating related parameter setting. Thanks, Eddy

Eddy,

What NAS platforms support VAAI ?

Thanks

Thanks, is Isilon on the roadmap anytime soon ?

Dynamox,

As I know, VNX with File OE above v7.0.12.0 does Support VAAI for NFS, the available feature is listed as follow,

1. Fast Clone

2. Full Clone

3. Reserve Space

4. Extended Stats

5. Offload Status/Abort

Thanks,

Eddy

I am not sure when VAAI would be GA on Isilon, but according to Chad’s blog, it is coming.

Here is the article for your reference. http://virtualgeek.typepad.com/virtual_geek/2011/08/emc-and-vsphere-5-whats-supported-when.html

Thanks,

Eddy

Sure. Newest VNX OE (7.0.35) and newest VSI plug-in...

There is nothing enabled

Hi,

is there anything to do on the VNX (5500 in my case) to enable VAAI? In my environment (vSphere 5) the NFS datastores are displayed with "Not Supported" in the hardware acceleration tab...

best regards

Christian Johannsen