3PAR OS 3.3.1 MU1 is released

[storsnapper]

"We are sorry to inform the OS Upgrade for 3.3.1 MU1 is on hold by our engineering team, however another latest released OS version 3.2.2MU6 is also available for your Inserv."


Nope no luck, we were scheduled for upgrade already and it has been pulled yet again. Kinda tired of this 3.3.1 code fiasco.

[mujzeptu]

Yeah, this is a real mess they are just trying to outrun....

Anyone heard of a fix for RMC support? Since upgrading to 3.3.1 in August RMC hasnt worked since on either array (7450 and V400). Support is of course still working on it... enterprise class baby!

[storsnapper]

Yeah, this is a real mess they are just trying to outrun....

Anyone heard of a fix for RMC support? Since upgrading to 3.3.1 in August RMC hasnt worked since on either array (7450 and V400). Support is of course still working on it... enterprise class baby!

Wow, thats a little worrying. I've waited on deploying RMC due to the issues between code versions. I had planned to deploy it once I had everything on same code 3.3.1 mu1, but now I'm stuck watching 2 different versions again since they pulled it.

3.3.1 dedupe/compression has been an absolute shit show, they rushed it out the door to compete and it has fallen flat. I have a follow up with our HPE and VAR next week as the promised 4:1 compression/dedupe is only getting us 1.7x and they still recommend not using it.

[Patrick]

Patrick, do you have TDVV version 1?

We hit a bug after upgrade causing controller reboots, but it hits only in very specific circumstances.
(sorry, under NDA here)
The workaround is to migrate to TDVV3 which you want anyway,
but it is time consuming on a 7000 and require coordination between customer and support.
HPE is doing the right thing holding the upgrade if you are candidate for this issue.

If I were you, I'd reschedule upgrade for early/mid February,
or just go for 3.2.2 until the dust settles on 3.3.1.
It is still going through a rough stability phase, wait for MU2 or MU3.
DECO volumes be damned, I expect 100% stability on a storage system this size.

- Anders

Not using TDVV anywhere, was just looking at the Infosight telemetry. There was no explanation for why exactly it was cancelled other than "there is currently an issue with the code". At this point I'm waiting until prod gets moved off of the current arrays before requesting another firmware upgrade.

The lovely support paired with the current pricing models have gotten us to look elsewhere going forward, such a shame.

[david godfrey]

Just wondering if anyone has experienced the upgrade to 3.3.1 (any update version) on an 8450, and if so any issues?
Thanks
DG

[storsnapper]

Just wondering if anyone has experienced the upgrade to 3.3.1 (any update version) on an 8450, and if so any issues?
Thanks
DG

I just performed an upgrade on one of our 8450's this past saturday (1/27/18). It went as smooth as can be expected, took approx 8 hours in total though.

We had the following steps to get fully up to date:

Pre-check
Upgrade SP to 4.5
Pre-upgrade workarounds for 3.3.1 applied
Upgrade to 3.3.1 started (total time approx 2 hours)
Update credentials to new standard
Post-upgrade workarounds removed
Disk firmware updated
Disk Cage firmware updated
Upgrade SP to 5.0
Apply latest OS patches

No major issues or outages occured, I had them do manual reboots on each node so I could verify esxi paths etc came back properly.

[david godfrey]

Just wondering if anyone has experienced the upgrade to 3.3.1 (any update version) on an 8450, and if so any issues?
Thanks
DG

I just performed an upgrade on one of our 8450's this past saturday (1/27/18). It went as smooth as can be expected, took approx 8 hours in total though.

We had the following steps to get fully up to date:

Pre-check
Upgrade SP to 4.5
Pre-upgrade workarounds for 3.3.1 applied
Upgrade to 3.3.1 started (total time approx 2 hours)
Update credentials to new standard
Post-upgrade workarounds removed
Disk firmware updated
Disk Cage firmware updated
Upgrade SP to 5.0
Apply latest OS patches

No major issues or outages occured, I had them do manual reboots on each node so I could verify esxi paths etc came back properly.

Thanks for the feedback thats really good to know we have been waiting to see how others found the upgrade before committing to it, we are also specing up a new array for another project and it's been speced with 3.3.1

[oby]

Today we had a curious experience one our 8440 array. The write latency went up to 500ms until we've restarted the master node. After that everything returned to a normal level sub ms service time. On that one we have opened another hpe case.

[Marc.mvh.vanhoof]

Hi members.
Some good news to share. We implemented 3.3.1 EMU1 dec 2017 on 8450's with no issues at all.
Started convering TDVV (old 3.2.2 dedupe cpg) to thin compressed VV's in another CPG.
Everything ok for now. Compression ratio is 2,3 to 1 but we use 20 to 30% extra user cpu.
One has to know that tunevv will no start when Dedupe acoounting background task is running.
Just try again, that will do.
Did have some issues during upgrade to 3.3.1 EMU1 on our 2850 .... io timeouts seen .... Waiting for HPE RCA before upgrading primary system for this 20850 3PAR pair.

[Chris212]

SSMC 3.3 released. Someone has already installed it ? Does it work well ?