OneView and C7000 supported upgrade path matrix

[CadenLange]

Hi

I'm in the process of planning a OneView appliance upgrade path from 4.10 to 6.x. This is currently managing a VMware 6.5 environment running on a C7000 chassis and also some additional DL servers. I'm looking to as much of this as an 'online' operation and trying to find a interoperability matrix between OneView versions, C7000 frimware versions, BL server SPP and DL server SPP etc so I can map out the upgrade steps for each element to maintain supportability during the upgrade activity.

There is a good support matrix for OneView and Synergy which clearly shows what versions of OneView support which Synergy SPPs and which versions of VMware - should I be using this for C7000 environments also? or is there a separate matrix for C7000 environments?

thanks in advance

[support_s]

System recommended content:

1. HPE OneView Support Matrix and HPE OneView Release Notes

2. HPE OneView 6.4 Support Matrix

If the above information is helpful, then please click on "Thumbs Up/Kudo" icon.

Thank you for being a HPE community member.

[DanCernese]

I can address this specifically:  

"There is a good support matrix for OneView and Synergy which clearly shows what versions of OneView support which Synergy SPPs and which versions of VMware - should I be using this for C7000 environments also? [NO!] or is there a separate matrix for C7000 environments?"

For c7000 and rack servers, the same strict support matrix is not required.  Those platforms are only constrained by the minimum versions in the OneView support matrix for each version of OneView.. ..and they do not change often.  Some people are surprised at how broad that support is, but you can trust the published support matrix documentation.

I recommend mapping out your OneView version update choices and use the support center to download each version's support matrix and verify when you will be required to update an iLO, an OA, or a VCM, for example.

[DanCernese · Accepted solution]

Independent of the monitored or managed nodes, the HPE OneView version 4.10.04 can update to 4.20.02 and then to 5.00.02 (which takes longer than most updates) and from there you can go to 5.20.01 or 5.30 => 5.40(milestone) => 6.00.01(milestone) => 6.30(milestone) => 6.50

..but I didn't do the research for each version's minimum supported iLO/OA/VCM.

(I thought 4.10.04 can go directly to 5.00.2 but the virtual appliance matrix (even on Synergy) seems to be missing that, I'll follow up to fix that.)

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

Each release note document also says which versions it can update from.  

p.s. updates starting with 6.0 are faster

[CadenLange]

Hi Dan

I'm just looking a little closer at this and have an additional query as I currently have OV 4.10.01 installed

The link you provided in your post shows an update option from 4.10.01 directly to 4.20.02 

And yet when I check in the 4.20.02 release notes on page 8  it states:

"HPE OneView may only be updated directly to version 4.20.02 from version 4.20.01 or later. Upgrading from versions earlierthan 4.20.01 require first upgrading to version 4.10.04 or 4.20.01.01 before following the pre-update requirement"

Is there either an error in the release notes or on the upgrade matrix??

[DanCernese]

We are cleaning up the table, it continues to have some inaccuracies in the 4.10/4.20, I believe the last edit might need reviewing again.  For now, follow the release notes document.

[CadenLange]

OK thanks - so I'll need to introduce an extra step in my plan to include 4.10.01.-> 4.20.01 before getting to 4.20.02 etc

Is there any rule of thumb for upgrade durations? I've done quite a few Synergy Composer upgrades with OneView but is that directly comparable with OneView appliances? Can I perhaps assume that, as a OneView for Synergy upgrade needs to complete both the active and standby composers it takes twice the time of a non-synergy OneView appliance?

I'm trying to put together a realistic schedule for these upgrades but can't find any reference in the release notes on timings. How long should I allow to get from:

 4.10.01 to 4.20.01  1-2Hrs?      then 4.20.01 to 4.20.02 <1Hr    then 4.20.02 to 5.20.01  3-4Hrs?     then 5.20.01 to 5.4  1-2Hrs?

I understand that the later upgrades complete faster so they should be less of an issue for me.

[CadenLange]

HI Dan

I've found the published update timinmgs in the OneView installation guides so I'm happy I can now create a rough schedule for the upgrades. Essentailly it's saying that an upgrade from 4.10..x from 4.2.x is about 1Hr, from 4.2 to 5.2 is about 1.5Hrs and from 5.2 to 5.4 about 1Hr again - that's all good and I'll allow myself 6Hrs for the whole lot. (I'll take backups and VM snapshots after each upgrade of course)

Please can you confirm for me that I can upgrade from 4.10.01 -> 4.20.01 -> 5.20.01

I know you said there is still a little 'tidying' to do with the support matrix so just wanted to check the above is a supported path. Initially I thought I may need to also include an additional step from 4.20.01 -> 4.20.02 but now I think I can go straight from 4.20.01 -> 5.20.01. Please will you confirm this is correct

Thanks again