Plugin 16.58.0 upgrade to current

[jdiaz220481]

I have an environment with plugin 15.68.0 looking in the compatibility table I have Omnistack 3.7.9.279, I need to do the upgrade, but what would happen and how would it be, will they have a document with the activities, should I go to 4.2 directly?

[gustenar]

Hello @jdiaz220481 

Thank you for using HPE SimpliVity Forum. 

The interoperability guide will tell you if your equipment is eligible for an upgrade to the latest software available, it is based on the model of your product. The Simplivity Upgrade Guide is the document you want to check for guidance on making the upgrades, check pre-requisites, etc. See the link here:

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

Hope it helps!

[gustenar · Accepted solution]

@jdiaz220481 

Some additional resources regarding software upgrades you may find useful: 

HPE SimpliVity - Upgrade Process - Overview (Part 1)

HPE SimpliVity - Upgrade Process - Software and Documentation (Part 2)

[jdiaz220481]

hi @gustenar
Thanks for the answer, review the documentation based on the equipment and the matrix, the videos are very helpful Regards.

[jdiaz220481]

@gustenar 

Based on the documentation, it was possible to upgrade to 4.1.2 are the packages that I was able to download from HPE, the packages vCenter Server Appliance 6.7 U3r, HPE SimpliVity Custom ESXi 6.7 U3 EP24 offline bundle and the plug in 4.1.2.162, I had some problems a host that did not turn on naturally from the upgrade process and I had to give it a reset from the iLO after that it started up normally I configured the new arbiter and I was able to commit it, but when entering the simplicity actions they show nothing and in federaion shows “HPE SimpliVity Plug-in cannot complete the task because it cannot contact the Virtual Controller.”

[jdiaz220481]

The problem was mine, the computers were not inside the Cluster, when I added them the actions worked correctly

[jdiaz220481]

I share the process that I carry out, current version:
Plug-in version: 16.58.0
VCenter 6.7.0.21000
VMware ESXi 6.7.0.17098360

Upgraded to the following version:
Plugin: 4.1.2.162
vCenter 6.7.0-(53000) - 19832974
VMware ESXi 6.7.0.19997733 - ESXi670-20220700

The Upgrade was performed based on the information in the URL: https://www.hpe.com/us/en/collaterals/collateral.a50005929enw.html
With the support of the videos, the upgrade of node1 was carried out without problems, the machines were moved without problem to node 2, after finishing and being online, the machines on were moved to node 1, in node2 they began to perform the worse upgrade this threw a pink screen error for this node we had to enter node2 and apply a forced reboot, it entered and finished the upgrade, then it was configured in the new arbiter and the commit could be made, for the vcenter instead After doing the upgrade, a new one was installed with the plugin for this version.

This was done in a lab and run 2 times and had the same behavior.