Upgrade Order (OVC, vSphere ESXi, VCSA & SPP Firmwares)

[J-Philippe]

Hi guys,

I've planned to upgrade a GEN 10 Simplivity Cluster.
Interop matrix checked, all target versions are supported.

OVC
Actual 4.01.444 / Target 4.1.1 U1

vSphere
Actual 6.7.0 / Target 7.0 u3c

vCSA

Actual 6.7.0 5000 / Target 7.0 u2d

Upgrade Order :

-1 Upgrade Arbiter with the version include in the 4.1.1 Upgrade package
-2 Upgrade OVC & Commit 4.01 to 4.1.1 U1
-3 Upgrade VCSA 6.7 to 7
-4 Install the New Plugin with the version include in the 4.1.1 Upgrade package
-5 Upgrade ESXi 6.7 to 7
-6 Upgrade the Firmware to SVTSP-2022_624.05

Can you confirm me that the upgrade order / path is OK ?

Best Regards
Jean-Philippe

[support_s]

System recommended content:

1. HPE OmniStack 4.1.1U1 for vSphere Deployment Guide

2. HPE OmniStack 4.1.0 for vSphere Administration Guide.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[sampiyonts]

Hello,

Yes the path is correct,

Good Luck,

[J-Philippe]

Thank you, 

I've notice that I was wrong concerning firmware. The actual firmware package will bring the node out of the matrix in 4.1.1 U1.

Upgrading first the firmware in the last SVTSPP allow me to stick to the matrix in the current version 4.0.1 and in the target version 4.1.1 U1.

It's not working with the Upgrade Manager so the HPE support advise me to upgrade like the way we do for other Proliat servers through the iLO virual console. 

[sampiyonts]

The path you specified is correct. After all the processes are finished, you can pass the SPPs one by one via ILO (the method i always use) I don't do SPPs with update manager

[sampiyonts]

by the way, you can check out the newly released 4.1.2 instead of 4.1.1U1.

https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00123773en_us

[egoqed]

hi  

i would not commit directly.....

let the infra running for a couple of days ...then commit. you are taking the rollback option this way.

yes you wont benefit from the new features the first few day ...but who cares if cou hava a safe rollback option.

at leas I do it this way (never needed rollback yet)

cheers

[J-Philippe]

Hi  egoqed,

in my case it was not possible because to ensure vSphere 7 to run I must commit the 4.1.1u1 upgrade.

But in another situation it can be good to know.

[J-Philippe · Accepted solution]

Hi, here it is a feedback I want to share.

Was not my first upgrade but each time I prefer to ensure the upgrade path.

I've finally started to upgrade the firmware (in a classic way as the upgrade manager didn't want to do it => always having issue with this feature, even the SimpliVity support team ask to  proceed with the iLO...) to stick the interop matrix.

All the step worked fine (thanks the upgrade manager in this situation). Once again the most important is to review the interop matrix and download the correct binaries.

With 4.1.1 U1 you have to add the .sig files and for ESXi an interop catalog file  in the folder of the upgrade manager do not forget to do it. If you add it after juste close and start again the upgrade manager.