VAAI Train Running Late Today

Another one of those posts today that most likely will not affect most, however there is a known issue with the vStorage APIs for Array Integration (VAAI) mixed together with EMC VMAX Storage Arrays. My best bud, Chad Sakac, wrote about this last week (over here).

Long story short, if you’re running a VMAX with Enginuity 5875.135.91 or 5875.139.93 along with ESX(i) 4.1 hosts you may see some slowness when trying to do things like Storage vMotion, Deploy from Template, etc…basically things that leverage HardwareAcceleratedMove.

So how do you fix it?  First thing is you need to disable HardwareAcceleratedMove, instructions on how to do this can be found in VMware KB1033665. Next thing is to contact EMC Support and have the ePack that engineering released for this problem installed on your VMAX. Then finally, contact VMware support for their hotfix…rumor has it that a VMware support bundle should be released sometime soon. After you have the patch for VMAX as well as vSphere you should have no problem turning HardwareAcceleratedMove back on.

So to wrap this up….VAAI issue when mixed with VMAX, but it doesn’t affect all VAAI functionality, just XCOPY (HardwareAcceleratedMove) and even then it doesn’t affect every single operation. Get the patches, get them installed and get back on schedule!

Created on June 14, 2011 by Rick Scherer

Posted under Storage, vSphere.

This blog has 1,828 views.

Tags: , , , ,

1 Star2 Stars3 Stars4 Stars5 Stars (2 votes, average: 5.00 out of 5)

1 Comment so far

  1. Duncan
    11:56 pm on June 14th, 2011

    Also to point out that when you disable the hwmove you will continue to experience the slowness until you have patched the environment and turned it on again.

Leave a Comment

Name (required)

Email (required)



More Blog Post