I attempted the workaround mentioned here, and it seemed successful... However, upon a reboot of the ESXi 5.0 host, the VMFS 5 datastores created with the work around, once again showed "Unknown" in the Hardware acceleration column. We're using a VNX 5700 on Flare 05.31.000.5.008. I'm checking with our EMC folks to determine if the newer Flare code has any enhancements that will help resolve this problem.
In the new Flare code (05.31.000.5.502) release notes it mentions changes to support all of the VAAI specification requirements for ESXi 5...
Please post back if VMware Support comes back with a response.
Hmm i am on 5.31.000.5.011 on my VNX and 4.30.000.5.517 my CX4 and doesnt have that problem. Did you check your ESX's Storage Connectivity Status? It should be set to Failover Mode 4 AULA and not the default mode 1. You can check by clicking on Storage System Connectivity Status, and edit the esx host. You also should be using round robin or powerpath too. If it is on mode1, you will need to do the Failover Wizard to reset the mode, pick CLARiion Open as type. I did it while the hosts are still running.. but i would suggest doing it in maintenance mode just to be safe. Then prob want to rescan or reboot the host also to check
We are using failover mode 4 ALUA; though we are using Fixed, rather than Round Robin for our path selection. l'll make the change to Round Robin and post the results.
Oh sorry, round robin just helps with mulitpathing, but it won't help with fixing the VAAI status =(. I should have mentioned that round robin comment was for best practice policy and not related to VAAI.
I am at version 4.30.000.5.507 and seeing the issue. I will be upgrading to version 4.30.000.5.522 shortly, and will inform you of our findings after the upgrade
Med venlig hilsen/ Best regards
Dan Have Larsen
Senior IT Konsulent
Berendsen Textil Service A/S
Dir. tlf.: +45 39538562
Mobil: +45 23738562
From: Hpang <email@example.com>
To: Dan Have Larsen <firstname.lastname@example.org>
Date: 07-10-2011 21:17
Please do. Our upgrade has just been scheduled for next Wed. I'll be looking forward to your results!
We have reports that there are a number of fixes for VAAI in 4.30.000.5.522.
You'll definitly want to upgrade from .507 due to other bug fixes (I don't have access to the articles myself)....
Primus solutions: emc255741, emc255604, emc254763
We just finished updating our VNX 5700 with the latest Flare code (05.31.000.5.502). This seems to have resolved our issues with VMFS5 partitions in excess of 2TB showing an "Unknown" Status. Upon recreation of the datastore in VMFS5 format, the datastore now shows "Supported" and the status remains in a supported state after a reboot.
It's nice to know that EMC has fixed the issue - at least with VNX.
Unfortunately the CX4 FLARE is only at 04.30.000.5.522, and there is no mention of VAAI fixes in the release notes.
I just finished upgrading to all my hosts to 5 and I'm also showing "unknown". We have two cx4-480's both at flare 30.511. I went ahead and scheduled the flare update to 30.522. Has that actualy resolved it for anybody? Somewhere i saw a post mentioning a fix that was in 30.512, but for the live of me i can't find it again.
EMC have confirmed that they haven't certified VAAI for use with Flare 30 with Clariion arrays on ESX 5.0 (it is supported in ESX 4.1).
The Clariion is supported for use with ESX 5.0 without VAAI enabled.
The VNX is certified for use with VAAI with Flare 31.
I don't have any timelines on when it may be supported.
EMC needs to get with the program!
Please run the "failover wizard" from your CX4 system, and set the vmware host nodes to Clariion open and MODE 4
All went to "supported" when i did this
What was your failover mode set to before?
Can you confirm your version of FLARE and ESXi 5?
Date: Fri, 11 Nov 2011 05:47:22 -0600
VAAI - ESXi 5 - status "unknown"
reply from lydian666<http://communities.vmware.com/people/lydian666> in VMware ESXi 5 - View the full discussion<http://communities.vmware.com/message/1861800#1861800