The software upgrade test utility is run prior to initiating a Concurrent Code Upgrade (CCU) to check the system for issues which might prevent a successful update.
If any issues are found, the upgrade utility presents a warning message with details of the issue and the methods to resolve them.
It is recommended that the upgrade is not started until these issues are resolved.
IBM Support also recommends that the upgrade utility is run at least a full day prior to starting the concurrent upgrade so that any issues can be resolved without delaying the planned upgrade.
Note: For firmware versions 1.2.0.11 and later, the test utility must be run before proceeding with the upgrade.
For earlier firmware versions, installing and running the utility is optional, but highly recommended.
A new check has been added to ensure that each of the system flash modules are not missing firmware information.
In the rare case that this happens, the update utility will block the user from upgrading and inform them that they should contact IBM Support.
To view what other checks are done when running the update utility, see Update history.
The upgrade test utility can be installed and run using either the Command-line Interface (CLI) or the Graphical User Interface (GUI).
Users are strongly recommended to use the GUI to upgrade.
Instructions on running the utility with or without an upgrade are provided on the next page.
Upgrade information and instructions are provided in product release notes.
Refer to the release notes for the specific firmware version you are upgrading to.
For general instructions on performing upgrades, refer to the IBM FlashSystem Knowledge Center.
From this link, you can access the appropriate FlashSystem page through one of the following paths:
System Storage > Flash Storage > Flash high availability systems > IBM FlashSystem 840 > Upgrading
System Storage > Flash Storage > Flash high availability systems > IBM FlashSystem 900 > Upgrading
System Storage > Flash Storage > Flash high availability systems > IBM FlashSystem V840 > Upgrading
The test utility can be run through the GUI without starting an upgrade.
Simply navigate to Settings > System > Update System and select Test Only.
Provide the file for the test utility, enter a supported firmware version that you plan to move to, and select Test.
To run the upgrade test utility using the GUI, follow these steps:
Navigate to Settings > System > Update System as shown in the figure below and select Update.
Use the folder icon and browse to select the file for the upgrade test utility. Select the appropriate upgrade file before clicking Update, as shown below.
Wait for the upgrade utility to run.
If there are any issues with the system that might cause the upgrade to fail, a message appears prompting you to go to the Update System page and read more about the issues the upgrade utility found, as seen in below.
Click Go to Update System and then click on Read more to view details on the issues, including how to resolve them. Correct any issues before continuing with the upgrade.
To run the upgrade test utility using the CLI, follow these steps:
Copy the test utility file to the /upgrade directory on the system’s configuration node using the management IP address from an external location. Use one of the following methods:
Using Linux, issue the following comamnd: scp upgrade_fileusername@management_ip:/upgrade/
Using Linux, issue the following comamnd: pscp upgrade_fileusername@management_ip:/upgrade/
Issue the following command to install the upgrade utility: applysoftware -file TMS9840_INSTALL_svcupgradetest_1.36
Once a success message is received for installing the utility, issue the following command to run the upgrade utility using the firmware version number (1.x.x.x) of the firmware you are upgrading to: svcupgradetest -v 1.x.x.x
Once the utility has finished running, the utility alerts you of any errors with your system that may prevent the upgrade from completing successfully.
Recommended actions are given to resolve any issues existing with the system. Resolve any issues before proceeding with the upgrade.
The following describes the updates made to past versions of the upgrade utility. If you wish to see the latest update, see Latest changes.
Version 1.35 - A check has been added to prevent upgrade on systems that currently have a battery reconditioning in progress.
Version 1.32 - A check has been added to prevent upgrade on systems with batteries that are not online.
This includes batteries that are 'offline' and 'degraded.' Click here for more information.
The update test utility also now accounts for a lack of a flash module spare on RAID 0 systems.
Version 1.29 - A check has been added to prevent systems that have an array, but no spare drive from upgrading.
Version 1.28 - A check has been added to prevent upgrades for 1.4.x systems with encryption keys in the prepared state.
These keys must be committed or canceled before proceeding with the upgrade.
Version 1.24 - A check has been added to present users with firmware levels below 1.2.0.12 with the message 'error in verifying signature of file.'
Version 1.23 - A check has been added to prevent an upgrade for iSCSI systems to firmware version 1.4.4.2 due to a known issue.
Version 1.22 - A check has been added to prevent an upgrade to a version below 1.2.1.9 for users with Pass 5 systems.
Version 1.20 - A check has been added to ensure that the maximum number of host ports used does not exceed 32.
If host ports used exceeds this number, the user will not be able to proceed with the upgrade.
Version 1.18 - A 'Test only' option is now available through the GUI which allows users to run the test utility without upgrading.
In addition, users with the user name 'service' are warned that they will not have access to this user if they upgrade and should take action to create a new user with a different name.
Version 1.17 - Reporting has been improved to include all errors and warnings for all issues found in the same report.
Version 1.14 - The utility now verifies that Call home is not only configured, but also enabled. If both of these things are not done, a warning is issued.
Call home messages are sent when the utility starts, gives a warning, fails, or finishes successfully.
The utility now verifies that an array is present and fully online.
Version 1.8 - The utility verifies that the user is upgrading from one of the four supported versions when upgrading to a firmware version later than 1.2.0.12.
The four supported levels are 1.1.3.7, 1.1.3.8, 1.2.0.11, and 1.2.0.12.
Version 1.6 - Updated utility verifies whether midplane paths have been disabled and that the system is properly encrypted.
Additionally, the utility now overwrites a previously installed utility, if necessary.
Version 1.5 - Updated utility creates a file upon successfully completing, enabling the CCL upgrade to start.
Version 1.4 - Updated utility verifies that the Call Home notification feature is configured on the system.
A warning is issued if the Call Home feature is not configured.
Version 1.3 - Updated utility checks for a potential canister power off issue during CCL.
Version 1.2 - Updated utility runs a CPLD diagnostic.
Version 1.1 - Updated utility runs a diagnostic on PSUs.
Version 1.0 - Runs a diagnostic on fans, batteries, and flash modules.
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of IBM Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol, indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available here.
The following terms are trademarks of other companies:
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
Other product and service names might be trademarks of IBM or other companies.
