Hi,
In previous firmware levels, the upgrade of a SVC \ V7000 had 2 steps:
1 Running the test utility
2 Apply the real firmware.
With the GUI I had the option to run only step 1. I could stop before running the actual update.
I noticed that with for example 7.4.0.6. both steps are running, with no option to stop after running the test utility. With this I started an upgrade during a time frame which was not the most ideal one.
Is there a reason why this changed and how to run the test separate?
Thanks
Answer by Andrew_Martin (883) | Nov 20, 2015 at 09:16 AM
Hi,
Yes - the GUI made the process of running an upgrade more streamlined by reducing the number of clicks to do a real upgrade.
Unfortunately in the process the made it impossible to run the upgrade test without performing the upgrade.
The GUI team have resolved this issue in newer releases by adding a "test only" button - which only runs the upgrade test utility - but that's no use until after you have upgraded.
At the moment - the only way to perform the upgrade test utility without upgrade is to use the CLI.
Cheers
Andrew
Answer by Marcel Anthonijsz (1) | May 26, 2016 at 09:55 AM
We also got hit by this "feature" as I suggested to a colleague to run the test utility to preview if any disks needed to be upgraded. To his amazement, the process continued to upgrade the V3700 (during production time!) and we had to make some quick phone calls.
Luckily no one was affected by the decreased performance during the upgrade, but we were not happy at that moment.
Good to see it has been "resolved" by a test only button...
So far my good advice to a colleague ;-)
SVC V7000 GUI Mdisks by pool issue 0 Answers
SVC: Managed disk is not on the preferred path. 2 Answers
SVC 7.7.1.1 HostCluster 2 Answers
SVC Stretched cluster and 4 nodes 2 Answers