Upgrading To 4.0 From Previous Versions **Important Information Before Upgrading**

[MikeSeden]

 This is mostly for a VMware/vSphere upgrade. But good reading for Microsoft as well.

Working the 3rd shift I seem to get a lot of upgrade problems when people are moving to SimpliVity 4.0. Things like vCenter reporting  datastores inaccessible and VMs inaccessible or Miscellaneous Upgrade Manager errors about the Federation and Clusters. In the process of an upgrade they can be quite alarming. Since the customer  was granted root access in version 3.7.3, they have been able to upgrade their nodes by themselves. Upgrading became a paid service. As a Tech Solutions Consultant, we assist with the upgrade when a problem arises. solve the problem  and let the customer go back to the upgrade. If another issue arises, we will always assist in fixing the issue that is causing the problem but we really don't do the upgrades anymore.

Now to my point

1. Make sure you have the current software from your customer portal. The current offline bundle from the customer portal is: 

                   * RECOMMENDED * HPE OmniStack for Microsoft Hyper-V and VMware vSphere
Type: Software - Storage
Version: 4.0.0(6 Jan 2020)
Operating System(s): Microsoft Windows Server 2016
VMware vSphere 6.5
VMware vSphere 6.7

Some of the things you may need:

• HPE SimpliVity ESXi Offline Bundles-
• HPE_SimpliVity_ESXi_6.5U3_EP16_Offline_Bundle_Q8A57-11081_hpe-esxi6.5u3ep16-14874964-650.U3.10.4.5.41-offline-bundle.zip
• HPE_SimpliVity_ESXi_6.7U3_Offline_Bundle_Q8A57-11082_hpe-esxi6.7u3-14320388-670.U3.10.4.5.19-offline-bundle.zip
• HPE_OmniStack_Software_4.0.0_Q8A57-11078.zip
• RFE WebClient 4.0.0-
• HPE-SimpliVity-Plug-in-for-vSphere-Client-linux-x64-4.0.0.179.run
• HPE-SimpliVity-Plug-in-for-vSphere-Client-windows-4.0.0.179.exe
• simplivity-arbiter-4.0.0.620.msi
• simplivity-deployment-manager-4.0.0.358.msi
• svt-vmm-add-in-4.0.0.309.zip
• HPE SimpliVity OmniStack 4.0.0 Interoperability Guide
• HPE OmniStack 4.0.0 for vSphere UpgradeGuide

If you feel you don't have everything you need call us and we can get it for you. Next and the most important is the order in which we update things. There is a step by step list in th the upgrade guide but it boils down to this: 

1. Upgrade vCenter manually to 6.7U3
2. Upgrade Arbiter
3. Upgrade SimpliVity vCenter plugin
4. Run Upgrade Manager to upgrade SimpliVity from 3.X.X to 4.0.0

At this point if you have properly staged everything in the prerequisites (Gen 10 firmware ,ESXi bundle) and done steps 1, 2 and 3 you should not have any problems.

I am not saying that you won't have a problem, and I do reccommend our Upgrade and Deployment Services, but if you do- we are here to help in any way we can.  +1 866-211-5211, Option 4, Option 1

[DavS]

Is vCenter 6.7 U3 build 14368073 supported with 4.0.0?
It is currently not listed in the "HPE SimpliVity OmniStack 4.0.0 Interoperability Guide".

So I assume the answer is no. Do you know when if/when 14368073 sill be supported?

[AnkiN]

Hello @DavS ,

Thanks for using HPE SimpliVity Fourum.

Based on your query regarding the interoperatibity of vCenter 6.7 U3 with the HPE OmniStack with 4.0, I find that the mention vCenter is supported.

You can take a look for the below link at page no 17 which states that it's supported.
https://support.hpe.com/hpesc/public/docDisplay?docId=a00090815en_us

Let me know if you have any queries.

[DavS]

Yes, Page 17 shows that 1467737 is supported, I found that before I asked the question about 14368073. 

My question is 14368073 supported?

If not do you know when 14368073 will be supported?

Thanks.

[AnkiN]

Hi @DavS ,

Checking on to the vmware's website with the build numbers for vcenter, it looks like the Build 14368073 is wrt to the vCenter webclient. However the vCenter bild remains 14367737 for vCneter 6.7 U3.

[cheesi]

Hi HPe Team,

i only wanted to be sure what are the right steps for an SimpliVity upgrade.

1.Check if the Federation is healthy 

2. Upgrade the Aribter

3. Use the DM for the OVC SW (Simplivity Version) upgrade

4. Upgrade the FW 

5. Upgrade the ESXI

Naturally I'm checking all Version in the Interoperability matrix

Thanks for your help!

[cheesi]

No one have an answer for me ?

[db13]

Hi @cheesi . The Upgrade Manager will orchestrate the upgrade of FW, ESXi image and OmniStack software. You are correct in the order that you have, will the understanding that the Upgrade Manager will perform in the order needed.

1. Check if the Federation is healthy
2. Arbiter (DO NOT REMOVE EXISTING VERSION OF ARBITER)
3. HPE SimpliVity Plug-in for vSphere Client
4. Upgrade FW, ESXi and OmniStack using Upgrade Manager (Requires VMware vSphere Enterprise Plus or higher license)

Please find link to Upgrade Manager below...
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00090804en_us 

[DeclanOR]

Hi @cheesi 

Take a look at this video which will explain how the fully orchestrated ESXi/OVC/FW upgrade is done.

https://hpesimplivityvideos.brightcovegallery.com/detail/videos/install-upgrade/video/6117232112001/hpe-simplivity-lifecycle-management-using-simplivity-upgrade-manager?autoStart=true

NOTE: To avail of this fully automated upgrade, you will need to have eneterprise plus ro higher vSphere licensing, as we leverage VMware vMotion during the process.

Also, you forgot to mention the web client plugin. Arbiter and web client plugin need to be upgraded firstly. The order doesn't matter for these two components. If you have linked mode VC's, all VC's will need to have plugin upgraded.

We also have videos explaining how to upgrade VCSA plugin if you need to reference them:

https://support.hpe.com/hpesc/public/videoDisplay?videoId=vtc00000008en_us

Hope this helps!

DeclanOR

[Moderator edit: Removed the broken link. Please refer to https://support.hpe.com/]

[cheesi]

Thanks for your answers. But UM istn working for us. So i have to do the upgrade manually and i wanted to be sure that i have the right steps.

1.Check if the Federation is healthy 

2. Upgrade vCenter

3. Upgrade the Aribter/ vCenter Plugin

4. Upgrade the OVC host with the iso

5. Upgrade the FW 

6. Upgrade the ESXI

[DaveOb]

 1  Check if the Federation is healthy 

2. Upgrade the Aribter

3. Use the DM for the OVC SW (Simplivity Version) upgrade

4. Upgrade the FW 

5. Upgrade the ESXI

install the newer plugin

Naturally I'm checking all Version in the Interoperability matrix

Looks perfectly fine as long as you stay within the interoperability guide especially when it comes to Virtual center.DM with HPE hardware can automate the ESXi and FW  for legany hardware a manual approch is needed.

[MikeSeden]

If upgrade manager isn't working I suggest you open a support ticket to find out why. You might have another underlying issue. We don't do the upgrade for you but we will help you solve the problems you are having with the upgrade.

[RIPEX]

Hi Team,

I am upgrating a federation with 02 Clusters. The first cluster upgraded perfectly, all that remains to be done is Commit, however when trying to update the second Cluster the Upgrade Manager returns me the error: Failed to prepare the cluster for upgrade.

Check list:

Federation - OK
VMs - OK
Arbiter -  Ugraded
Plugin for vSphere Web Client - Updated

Does anyone have any idea what may be causing the error in upgrading the second Cluster?
Is there any Log that I can analyze?

Thanks!

[EduardoMoreira]

Hi everyone,

I have the same issue.

Does someone know how to solve this problem?

Thank you.

[MikeSeden]

This might be the issue-

If there is an empty vCenter Server cluster object anywhere in inventory, it will cause upgrades to fail with a false positive error during pre-validation, "Verify Node Compute Cluster Deployment".

Or it could be an issue with the rest certificate.

If you can't fix it open a support ticket for us to figure out what the issue is. We are here to help-

[fahlis]

Hi all!

I can confirm that if you have an empty cluster withiin the same Datacenter it will fail to upgrade. I actually had this issue which ended up in a Case nr: 5345604914

I asked the HPE Tech Consultant why this is not documented anywhere in the administration/deployment/upgrade guides. He said it was knwon among SVT Team.

I really hope you will document this in the future as I'm sure many more of us SimpliVity consultants are not aware of it.

Br / Tony

[DeclanOR]

Hi @fahlis 

There are many reasons why an upgrade may fail. An empty cluster is indeed one. This is documented in a public facing KB article.

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=sf000063567en_us

Customers and indeed internal support members should always keep an eye on our knowledge base for new knowledge articles. Searching HPESC portal with the error message reported during the failed upgrade would have resulted in this article being presented as the first article. 

We do try and document as many issues as possible. However, it is not always possible to document "all" possible issues. This specific issue for example is related to a configuration of the VMware environment as opposed to a product defect.

Thanks,

DeclanOR

[fahlis]

@DeclanOR 

Thanks for the link. I did search the HPESC portal with the error message I saw in the orchestrator logfile prior to creating the case. Perhaps the KB was created or modified after my case was solved

My case was created 03/05-2020 and this KB was posted/updated 03/26-2020
Anyways, great that we do have a KB for it now.

//Tony

[DeclanOR]

Hi @fahlis 

Thanks for the reply. Yes......I believe this article was published after that date. Maybe this acrticle was created as a result of your case!!lol  Main thing is that it's here now for anybody else that goes searching. I actually recorded an upgrade video today which will be going live shortly. I think you will find it very interesting.

Thanks,

DeclanOR.

[fahlis]

Hi @DeclanOR 

Waiting with anticipation for your new video

Br / Tony

[DeclanOR]

Hi @fahlis 

Here are the three upgrade videos which went live today:

Upgrade Part 1

Upgrade Part 2

Upgrade Part 3

Part 3 is the one that you will find most interesting and coincidental to this conversation I think.

Thanks,

DeclanOR

[fahlis]

@DeclanOR 

Great guides, I just watched them. Perhaps you can do guides for CLI upgrade also?

As I have had various problems with the upgrade manager that ended up in a support case and in the end CLI upgrade, I think it would be great to share that with others in a video.

Keep up the good work

Br / Tony

[DeclanOR]

Hi @fahlis 

Thanks for the positive feedback. CLI is another possible addition yes. Upgrade Manager has improved substantially throughout recent releases however, so hopefully the need to rely on Cli has equally reduced. Definitely a great suggestion, so lets see how things progress. Thanks for viewing the videos - I take it you noticed the empty cluster issue I hit while recording also!? 

Thanks,

DeclanOR

[fahlis]

Hi @DeclanOR 

Indeed I saw the issue with Empty cluster

Br / Tony

[Kevin4]

I just did an upgrade from 3.7.7 to 4.0.1 that I had to get support involved because it failed thru the GUI and CLI.  After a few hours, and let support sleep on and get back to me the next day(VMs were still up). On the omnistack VM, there is .vcconfig file  The svssizeGB needs to be 108, mine was at 107 causing it to fail.   After that is changing that value and restarting svtfs on each one in the cluster that upgrade was able to successfully complete.  I thought I would share, as it might benifit someone else.