HPE 3PAR OS 3.3.1 MU2 Release

[ailean]

Release Notes are out at least.

https://support.hpe.com/hpsc/doc/public/display?sp4ts.oid=1008793289&docLocale=en_US&docId=emr_na-a00046462en_us

Hopefully stable as will probably be migrating to it before end of year.

[cbuxton]

I'm looking forward to this one, we would like to have some more all-flash systems, but without the data efficiency of 3.3.1, they are too expensive. One a side note, how did you find these release notes so quickly?

[ailean]

I'm looking forward to this one, we would like to have some more all-flash systems, but without the data efficiency of 3.3.1, they are too expensive. One a side note, how did you find these release notes so quickly?

Out of habit I check the 3PAR OS documentation list on a regular basis as there's little else in the way of (useful) customer notifications.

[cbuxton]

YES! I do too, but where do you find it? I am looking at the storage information library:
http://h17007.www1.hpe.com/us/en/storag ... index.aspx

[ailean]

YES! I do too, but where do you find it? I am looking at the storage information library:
http://h17007.www1.hpe.com/us/en/storag ... index.aspx

Currently (changes every few months ) I'm using the following link and selecting sort by date.

https://support.hpe.com/hpesc/public/home/productHome?sp4ts.oid=1008793289


But yeah, that plus the product pages for the quickspec, SPOCK, Software Depot and licensed downloads pages are all part of the browsing adventure that is 3PAR support.

[oby]

Does anyone have experience with MU2 in production?

[mujzeptu]

I just got told my node reboots are caused by 3.3.1 MU1 with latest patches and I need to update to MU2. Anyone aware of said issue or know what the specific issue is? I feel like 3PAR support has been telling me for the past several years, "a fix is coming!"

[ailean]

I just got told my node reboots are caused by 3.3.1 MU1 with latest patches and I need to update to MU2. Anyone aware of said issue or know what the specific issue is? I feel like 3PAR support has been telling me for the past several years, "a fix is coming!"

Check out the release notes, there are several node reboot fixes listed, hopefully some are applicable to what you're seeing.

We went through similar issues with 3.2.2, it was at MU2 by time I started running it but wasn't till MU4 that I was happy to roll it out across all our arrays. HPE did promise to do better next time (i.e. 3.3.1) so I am hoping MU2 will be stable (previous to 3.2.2 I'd been happy with 3PAR code by time it reached MU2).

[SergioQC]

Any news on experience with MU2 in production?

Thanks!

[Patrick]

Anyone try rolling the dice on this release with older 7k/10k series arrays?