Symptom
After a version is released, its formal patch is released. The path of the formal patch is not in the specified upgrade path. In normal cases, the version with the patch installed cannot be upgraded to a specified version released earlier than the patch. However, in special scenarios, such an upgrade is required. In this case, the cross-version check needs to be skipped so that the upgrade can be performed.
Alarm Information
A message is displayed on the upgrade interface, indicating that pre-upgrade processing fails and the upgrade cannot continue.
Possible Causes
In normal cases, a version with a patch installed cannot be upgraded to a specified version released earlier than the patch. However, there are special scenarios where a patch is installed on a device before delivery and the device needs to be upgraded to a specified version released earlier than the patch.
Fault Diagnosis
A message is displayed on the upgrade tool interface, indicating that the current version cannot be upgraded to the target version and the upgrade cannot continue. After analysis, R&D engineers conclude that the cross-version check needs to be skipped so that the upgrade can continue.
Solution
- Create an empty filenamed ignoreCheckCrossVer.txt, and place it to a specified directory (OceanStor Toolkit root directory\tools\ArrayUpgrade\packages\ArrayUpgrade\product\Target version\).
For example, to upgrade the system to V300R002C00, place the ignoreCheckCrossVer.txt file to OceanStor Toolkit root directory\tools\ArrayUpgrade\packages\ArrayUpgrade\product\V3V300R002C00\.
- Restart the upgrade tool, and perform the upgrade as prompted.
Check After Recovery
To avoid adverse impact on the next upgrade, check whether the ignoreCheckCrossVer.txt file exists in OceanStor Toolkit root directory\tools\ArrayUpgrade\packages\ArrayUpgrade\product\Target version\ after the current upgrade is successful. If the file exists, delete it.
Applicable Versions
All versions that support pre-upgrade processing
