HPE Storage Users Group

The ATS bug affects pretty much every vendor that supports VAAI.

So they said they would upgrade us to 3.2.2 MU3, however they won't tell me why it's not advisable..

Anyone having any major issues with 3.2.2?

AFAIK 3.2.2 eMU2 P33 and MU3 are supported for 7K, 10K, 8K and 20K although the default for the 7K and 10K remains 3.2.1 MU5 i.e. what it would ship with from the factory.

Maybe it was just a timing issue around when the question was asked, the status only changed recently for the previous generation systems.

The alternative is to remain on the current recommendations and follow the VMware workaround for ATS :-
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2113956

Namlehse wrote:So they said they would upgrade us to 3.2.2 MU3, however they won't tell me why it's not advisable..

Anyone having any major issues with 3.2.2?.

I was upgraded to 3.2.2MU3 on a 7200 after HPE strongly pushed us in that direction.

The ATS bug was crippling, and resulted in major downtime. The VMware fix at the host level has addressed that however.

Josh26 wrote:

Namlehse wrote:So they said they would upgrade us to 3.2.2 MU3, however they won't tell me why it's not advisable..

Anyone having any major issues with 3.2.2?.

I was upgraded to 3.2.2MU3 on a 7200 after HPE strongly pushed us in that direction.

The ATS bug was crippling, and resulted in major downtime. The VMware fix at the host level has addressed that however.

I have a single host running 6.0U1b as we speak, everything else is still 5.5U1.

We're scheduled for update on the 7th and the 8th.

"The ATS bug was crippling, and resulted in major downtime."

Hi, could you elaborate? We just a a major outage and the cannot find root cause

If you are running 3.2.2 (any version besides MU3) then it is most likely your cause. You will see a lot of path changes in esxi logs, VM's get disconnected and/or corrupt. ESPECIALLY in a VVOL environment.

bajorgensen wrote:"The ATS bug was crippling, and resulted in major downtime."

Hi, could you elaborate? We just a a major outage and the cannot find root cause

Pretty much what he just said.. if you are running 3.2.2 on ESXi 6 and haven't applied MU3 (which only just came out) then the ATS bug will cause storage to continually drop off line.

We've been putting off upgrading until I figured out all of our potential bugs. We ran into a fairly crippling one yesterday that caused cascading host failures lol. It was finally stopped by running out of resources. Someone created a 2012 R2 VM with an E1000 card, which proceeded to kill host after host with HA. It's a "Known Issue" in our system, however people get forgetful..

We're scheduled to be updated on the 7th. I was told during a meeting last week with HP that it's "Not recommended" due to an issue with some obscure application that no one can really remember.. (Great right?). They did confirm that it plays nicely with VMware.. so we'll see how it goes. If things are par for the course lately, I may be job hunting soon enough! Rofl

turbogizzmo wrote:

Josh26 wrote:

MammaGutt wrote:If you have a 7k or 8k system, you could do the upgrade yourself.

This is wildly contradictory to a long series of consultations I have had with HPE over multiple 7k installations.

Well to be fair after 3.1.2 I thought they introduced the ability to allow customer side upgrades.

That being said even after having plenty of experience with 3par I still have a case opened for a upgrade even if I am doing it myself.

I just did an 3.2.2 upgrade on a 7k took 20 mins. I'm on 6.0u2 with 2 servers currently attached. will monitor and let you guys know if if see any issues and report back.