3PAR 8200 Upgrade from 3.2.2.290 to 3.2.2 MU3 fails

[glanzmann]

Hello,
I try to to upgrade 3.2.2.290 to 3.2.2 MU3, which fails. I also tried to upgrade to 3.2.2 EMU2. But both times I get the following error message:

2016-08-31 144207 CEST - Online upgrades are disallowed from the current version (3.2.2.290)
2016-08-31 144207 CEST to the package version (3.2.2.390) unless 3.2.2.290-EGA is installed

I tried to download 3.2.2.290-EGA but it is unavailable on the HP 3PAR download page. Only patches for 3.2.2 EGA are available using this page. Has anyone else experienced this problem and has a resolution to it?

I opened a case with HP and will keep this thread updated while I do progress.

Cheers,
Thomas

[turbogizzmo]

What does checkupgrade return from the CLI?

[Leif]

There is a patch that has to be installed before upgrading between some of the different 3.2.2 versions.

3PAR 3.2.2 EGA Patch 35 must be installed prior to upgrading from 3PAR 3.2.2 EGA to a later version.

3PAR 3.2.2 MU1 Patch 37 must be installed prior to upgrading from 3PAR 3.2.2 MU1 to a later version.

[glanzmann]

The current system configuration is valid for proceeding with an online upgrade.

[glanzmann]

Hello,
I think my problem is that I have 3.2.2 and not 3.2.2 EGA. The 3PAR was one of the first shipped 8200. I just tried to apply 3.2.2 EGA P35 and it failed:

No InSplore running
Terminated InSplores
No InSplore running
Release version 3.2.2.290
Patches None

Component Name Version
CLI Server 3.2.2.290
CLI Client 3.2.2.290
System Manager 3.2.2.290
Kernel 3.2.2.290
TPD Kernel Code 3.2.2.290
Selected upgrade type patch

MESSAGE START State, No HP 3PAR OS upgrade in progress
STATE0

StoreServ release version 3.2.2.290
No InSplore currently running
Stopping spevent task for StoreServ hostname
Stopping spcollect tasks for StoreServ hostname
If running, stopping InSplore for StoreServ hostname


Transferring software may be a long running operation. Do not abort the operation.

Installing patch 3.2.2.290-P35
before patch install
Starting upgradesys -doupdate OS-3.2.2.290-P35
2016-08-31 162421 CEST Substituting package for staged
2016-08-31 162421 CEST Beginning upgrade of system software.
2016-08-31 162421 CEST
2016-08-31 162421 CEST Extracting...
2016-08-31 162421 CEST
2016-08-31 162421 CEST Applying new package...
2016-08-31 162421 CEST Performing pre-update checks...
2016-08-31 162422 CEST - This patch can only be applied against the following versions
2016-08-31 162422 CEST 3.2.2.EGA
2016-08-31 162422 CEST Update failed.

Cheers,
Thomas

[mehikko]

Hi

I think you must apply Patch P03 for 3.2.2 GA before MU3 install:

3.2.2 EGA
Component Version
OS 3.2.2.290 GA+P03

[glanzmann]

Hello Mehikko,
HPE support said the same thing. The problem is that I'm unable to download the patch because it is not listed and HPE support is currently unavailable to provide the same. I'll follow up with them tomorrow.

Cheers,
Thomas

[drunkmet]

You should have HP do this upgrade for you. There's a bunch of intermediate steps from 3.2.2 to 3.2.2 MU3 including running some custom shell scripts and it's not documented publicly anywhere.

It's a pain working with HP to plan and schedule the upgrade but your support agreement covers it. Take advantage of it.

[Richard Siemers]

You should have HP do this upgrade for you. There's a bunch of intermediate steps from 3.2.2 to 3.2.2 MU3 including running some custom shell scripts and it's not documented publicly anywhere.

It's a pain working with HP to plan and schedule the upgrade but your support agreement covers it. Take advantage of it.

Yes absolutely. Having recently done a similar upgrade from 3.2.1, I can certify with logs that support is doing several steps that are not customer facing. The tech had a SSH shell open to the service processor, and at the same time, had a root shell open directly to the node. Not the tcl shell we see when we SSH in, but the os level bash shell. At several points he was pasting multipage long shell scripts over and running them locally on the node. The scripts looping through proprietary commands which I assume were core Inserv executables.

That said, as a customer, you should be able to get all the root access to the nodes, sp, or whatever you like. I was told that HP will not reveal the existing root passwords, but have on occasion worked with the customer to change these passwords to something the customer desires.

[glanzmann]

Hello,
after HPE support provided the file 'OS-3.2.2.290-EGA.iso' via a FTP site, I was able to upgrade to 3.2.2 MU3 with the intermediate step 3.2.2-EGA. The update took 7 hours. Most time was spend on the tunesys after upgradeding to 3.2.2-EGA and the upgrade of the cages (19-25 minutes per cage). No problems occurred. Two disks which had a speed of 6 Gbit instead of 12 Gbit had 12 Gbit speed after the upgrade.

Cheers,
Thomas