Troubleshooting
Problem
With the introduction of IBM Security Verify Access v10.x, there now exist multiple potential upgrade paths. While most upgrade paths are technically possible, not all are recommended due to the inherent differences between the implementation of IBM Security Access Manager and IBM Security Verify Access. Some upgrade paths now also require action before upgrade and require guidance from IBM Support before an upgrade attempt.
This document aims to identify the supported upgrade paths and scenarios when guidance from IBM Support is needed.
Resolving The Problem
The following table shows the supported upgrade paths. Cells marked with an 'X' indicate supported paths. Cells marked with a '!' indicate technically possible, but nonrecommended, upgrade paths. Blank cells represent unsupported upgrade paths. Cells that contain a number in parentheses have extra corresponding notes after the table.
Also note customers are expected to operate on the latest fix pack and available interim fix in order to receive full defect support and protection from security updates. For example, the “Current Fixed Version” of V10.0 would be considered something based on v10.0.8 plus any published fixpacks or interim fixes.
Fix Central should be consulted for the absolute latest available versions.
Also note customers are expected to operate on the latest fix pack and available interim fix in order to receive full defect support and protection from security updates. For example, the “Current Fixed Version” of V10.0 would be considered something based on v10.0.8 plus any published fixpacks or interim fixes.
Fix Central should be consulted for the absolute latest available versions.
| FROM \ TO | 9.0.7.1 | 9.0.7.2 | 10.0.0 | 10.0.1 | 10.0.2 | 10.0.3.1 | 10.0.4 | 10.0.5 | 10.0.6 | 10.0.7 | 10.0.8 | |
| Before (4) 9.0.7.1 | ! | ! | X | X | X | X | X | X(3) | X(3) | X(3) | X(3) | |
| 9.0.7.1 (4) | !(1) | X(1) | X(1) | X(1) | X(1) | X | X(3) | X(3) | X(3) | X(3) | ||
| 9.0.7.2 (4) | !(2) | X(1) | X(1) | X | X | X(3) | X(3) | X(3) | X(3) | |||
| 10.0.0 | X | X | X | X | X(3) | X(3) | X(3) | X(3) | ||||
| 10.0.1 | X | X | X | X(3) | X(3) | X(3) | X(3) | |||||
| 10.0.2 | X | X | X(3) | X(3) | X(3) | X(3) | ||||||
| 10.0.3.1 | X | X(3) | X(3) | X(3) | X(3) | |||||||
| 10.0.4 | X | X | X | X | ||||||||
| 10.0.5 | X | X | X | |||||||||
| 10.0.6 | X | X | ||||||||||
| 10.0.7 | X | |||||||||||
(1) If you originally installed the Appliance at this level of firmware (that is, 9.0.7.1 or 9.0.7.2) contact IBM support before you upgrade the appliance. Refer to the guidance in "How to determine the firmware upgrade history of an IBM Security Access Manager / IBM Security Verify Access appliance?"
(2) While it is technically possible to perform this upgrade, this upgrade path is not recommended by IBM since it regresses functions and might cause the databases to become inconsistent.
(3) Due to a change in package signature and verification, upgrades from versions before 10.0.4.0 first require the installation of isva-signing.fixpack to enable uploading the new firmware package file. The isva-signing.fixpack is available from Fix Central within 10.0.5-ISS-ISVA-FP0000. The isva-signing.fixpack allows appliances at versions before 10.0.4.0 to validate and install new upgrade packages for version 10.0.5.0 and newer. If you are upgrading from a version before 10.0.4.0, you do not need to upgrade to the 10.0.5 firmware level as an intermediate step, but you do need to apply the isva-signing.fixpack. If you upgrade from version 10.0.4.0 or newer, do not install isva-signing.fixpack.
(4) For upgrades from a release that is out of support, plan for extra time and testing. Support for compatibility and interoperability with these multiple level upgrades is offered on a best-effort basis, such as going from ISAM 7 to ISVA 10. Upgrade from out of support versions are no longer tested as part of a routine release cycle. Additionally, security enhancements (including cipher suites or other product changes) might limit or prevent interoperability and upgrades across some versions, requiring extra custom steps.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSZU8Q","label":"IBM Security Access Manager"},"ARM Category":[{"code":"a8m0z000000cxuHAAQ","label":"Security Verify Access"},{"code":"a8m0z000000cxuNAAQ","label":"Security Verify Access-\u003EAppliance Administration"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"},{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSRGTL","label":"IBM Security Verify Access"},"ARM Category":[{"code":"a8m0z000000cxuHAAQ","label":"Security Verify Access"},{"code":"a8m0z000000cxuNAAQ","label":"Security Verify Access-\u003EAppliance Administration"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
25 June 2024
UID
ibm16340107