Page 2 of 5

Re: 3PAR OS 3.2.1

Posted: Mon Sep 29, 2014 11:11 am
by Cleanur
I think what they meant is updates to 3.2.1 GA are not supported with configurations using a combination of CLX and RC today, other remote copy configurations are fine, this is likely to be a CLX qualification issue (identifying corner cases is what the controlled release is all about). But yes you are correct the two are used together otherwise there's no point running CLX. Peer Persistence is now supported on Windows clusters / HyperV as well as VMware as part of the Remote Copy suite so the use case for CLX is likely to be reduced moving forward.

I think they were maybe a little too precise in the wording which led to the confusion.

Express writes are part of the Inform Base O/S in 3.2.1 it's an optimal method of posting writes on the array HBA to reduce latency per write, very important for flash systems where low latency is king. There's a great video that Ivan Iannacone did which discusses express writes among other things.

http://h30507.www3.hp.com/t5/Around-the ... CmIR_ldXg0

Re: 3PAR OS 3.2.1

Posted: Tue Sep 30, 2014 5:16 am
by demiurg
I did upgrade 3PAR 7400 4-node to 3.2.1, Flash cache started.

Re: 3PAR OS 3.2.1

Posted: Tue Sep 30, 2014 10:42 am
by trentwtaylor
(I work at HP)

What kinds of issues did you experience with the controlled release of 3.1.3?

Re: 3PAR OS 3.2.1

Posted: Tue Sep 30, 2014 2:11 pm
by Darking
Our admithw -ni task failed under the upgrade with the following error:

2014-04-04 123330 CEST Error t2cpg NL_r6 is already associated with an AO configuration.
2014-04-04 123330 CEST Error Task exited with status 1
2014-04-04 123330 CEST Failed Could not complete task.


I contacted support, and was told i could disregard the error message. I just find it annoying that it even occurs with a totally default array.

This was with the 3.13 GA

Re: 3PAR OS 3.2.1

Posted: Tue Sep 30, 2014 4:02 pm
by trentwtaylor
Thanks ... I suspect most people will wait for 321MU1 but I was curious to see if anyone had production affecting issues with either CR/GA of 313 or 321.

Thanks again ~

Re: 3PAR OS 3.2.1

Posted: Wed Oct 01, 2014 4:39 am
by demiurg
Me too

admithw -ni
Checking for drive table upgrade packages
Checking nodes...

Checking volumes...

Checking system LDs...

Checking ports...

Checking state of disks...
Volume creation may fail due to the following issues:

Component --------Description-------- Qty
PD Cages with unbalanced disks 2

Component -Identifier- ----------------------------Description-----------------------------
PD Cage:2 PDs FC/10K/450GB unbalanced. Primary path: 9 on Node:0, 11 on Node:1
PD Cage:4 PDs FC/10K/450GB unbalanced. Primary path: 9 on Node:2, 11 on Node:3

Re: 3PAR OS 3.2.1

Posted: Wed Oct 01, 2014 7:08 am
by Wolfee2075
Hi,
Can I upgrade from 3.1.2 to 3.2.1MU1 or do I have to go to 3.1.3 1st?

Thanks
New to 3par!
D.Wolf

Re: 3PAR OS 3.2.1

Posted: Wed Oct 01, 2014 11:06 am
by trentwtaylor
The service notes on 3.2.1 say you need to be at 3.1.2 MU3 + P41 prior to upgrading to 3.2.1 ... So it looks like you can skip 3.1.3

Re: 3PAR OS 3.2.1

Posted: Fri Oct 03, 2014 4:29 am
by cla@atea.dk
NOTE: Software upgrades to HP 3PAR OS 3.2.1 GA for systems that are in a Remote Copy
Synchronous Long Distance Replication relationships are currently not supported. HP 3PAR OS
3.2.1 support for these configuration will be enabled via P01.

NOTE: Software upgrades to HP 3PAR 3.2.1 GA for systems that use Remote Copy and CLX are
currently not supported. HP 3PAR OS 3.2.1 support for these configuration will be enabled via
P01.

Just don't know when P01 is coming??

Just officially downloaded it yesterday, and there's a new appliance for peer persistance too.
Remember that W2008 versions now requires persona 15 like 2012.

Anyone testet the mentioned speed improvement in this release??

Br
Claus

Re: 3PAR OS 3.2.1

Posted: Fri Oct 03, 2014 5:54 am
by mastrboy
I can't find anything at all in "HP 3PAR OS 3.2.1 Release Notes.pdf" about Dedupe :(
Did it not make it into this release?
We just got a 7450 and are waiting to test dedupe before putting this system into production...