This is the release note for the 8.7.3 release and details the issues resolved in between 8.7.3.0 and 8.7.3.1. This document will be updated with additional information whenever a PTF is released.
This document was last updated on 8 April 2025.
Note. Detailed build version numbers are included in the Concurrent Compatibility and Code Cross Reference in the Useful Links section.
| Details | Introduced |
|---|---|
|
IBM SAN Volume Controller Systems with multiple I/O groups are not supported. |
8.7.1.0 |
|
Systems configured with a data reduction pool are not supported on 8.7.3 at this time. |
8.7.3.0 |
| The following restrictions were valid but have now been lifted | |
|
Upgrade to 8.7.3.0 was not supported on FS5200 (32GB cache per node) with two iWARP adapters and FS5300 (32GB cache per node) with one or more iWARP adapters and FS5300 (128GB cache per node) with 2 iWARP adapters. |
8.7.3.0 |
A release may contain fixes for security issues, fixes for APARs or both. Consult both tables below to understand the complete set of fixes included in the release.
CVE Identifier |
Link for additional Information |
Resolved in |
|---|---|---|
| ||
| CVE-2025-0160 | 7184182 | 8.7.3.0 |
| CVE-2025-0159 | 7184182 | 8.7.3.0 |
APAR |
Affected Products |
Severity |
Description |
Resolved in |
Feature Tags |
|---|---|---|---|---|---|
|
|
| |||
| SVAPAR-157007 | All | Critical | On heavily loaded systems, a dual node warmstart may occur after an upgrade to 8.7.3.0, 8.7.0.3, or 8.6.0.6 due to an internal memory allocation issue causing brief loss of access to the data. (show details) | 8.7.3.1 | System Update |
| SVAPAR-157355 | All | Critical | Multiple node warmstarts under very heavy work-loads from NVMe over FC hosts. (show details) | 8.7.3.1 | NVMe Hosts |
| SVAPAR-157593 | All | Critical | Mapping an HA volume to a SAN Volume Controller or FlashSystem is not supported. This may cause loss of access to data on the system presenting the HA volume. (show details) | 8.7.3.1 | Hosts, HyperSwap, Policy-based High availability, Storage Virtualisation |
| SVAPAR-146576 | All | High Importance | When a quorum device is disconnected from a system twice in a short period, multiple node warmstarts can occur. | 8.7.3.1 | Policy-based High availability |
| SVAPAR-148364 | All | High Importance | Systems whose certificate uses a SHA1 signature may experience node warmstarts. LDAP authentication using servers returning an OCSP response signed with SHA1 may fail. (show details) | 8.7.3.1 | LDAP, Security |
| SVAPAR-158915 | All | High Importance | A single node warmstart may occur if a host issues more than 65535 write requests, to a single 128KB region of a policy-based replication or HA volume, within a short period of time. (show details) | 8.7.3.1 | Policy-based High availability, Policy-based Replication |
| SVAPAR-155824 | FS5200 | Suggested | FS5200 and FS5300 systems with iWARP adapters and 8.7.0.3 or 8.7.3.0 software may experience an out-of-memory condition. (show details) | 8.7.3.1 | Reliability Availability Serviceability |
| SVAPAR-156586 | All | Suggested | Cloud callhome stops working after downloading software directly to the system, or upgrading to 8.7.0.2 or later. (show details) | 8.7.3.1 | Call Home |
| SVAPAR-157700 | All | Suggested | Systems on 8.7.3 may be unable to establish a partnership for policy-based replication or high availability, with systems on lower code levels that have volume group snapshots. (show details) | 8.7.3.1 | Policy-based High availability, Policy-based Replication |
| SVAPAR-147906 | SVC | Critical | All nodes may warmstart in a SAN Volume Controller cluster consisting of SV3 nodes under heavy load, if a reset occurs on a Fibre Channel adapter used for local node to node communication. (show details) | 8.7.3.0 | Inter-node messaging |
| SVAPAR-148504 | All | Critical | On a system using asynchronous policy-based replication, a timing window during volume creation may cause node warmstarts on the recovery system. (show details) | 8.7.3.0 | Policy-based Replication |
| SVAPAR-148987 | SVC | Critical | SVC model SV1 nodes running 8.5.0.13 may be unable to access keys from USB sticks when using USB encryption (show details) | 8.7.3.0 | Encryption |
| SVAPAR-149983 | All | Critical | During an upgrade from 8.5.0.10 or higher to 8.6.0 or higher, a medium error on a quorum disk may cause a node warmstart. If the partner node is offline at the same time, this may cause loss of access. (show details) | 8.7.3.0 | System Update |
| SVAPAR-151285 | All | Critical | In a system with multiple I/O groups and a Data Reduction Pool, multiple nodes may warmstart (causing loss of access to data) if all thin or compressed volumes are deleted in one of the I/O groups, and a new volume is then created. This can only happen if the I/O group's node hardware has been upgraded to a different model. (show details) | 8.7.3.0 | Data Reduction Pools |
| SVAPAR-151639 | All | Critical | If Two-Person Integrity is in use, multiple node warmstarts may occur when removing a user with remote authentication and an SSH key. (show details) | 8.7.3.0 | LDAP |
| SVAPAR-152118 | All | Critical | Large FlashCopy dependency chains with lots of mappings stopping at the same time could cause a loss of access to data on systems running 8.7.0 (show details) | 8.7.3.0 | FlashCopy, Snapshots |
| SVAPAR-155437 | All | Critical | When enabling replication for a volume group, there is a very low probability that the DR system might detect an invalid state, due to a timing window between creation of the volume group and the volumes. If this happens, both nodes at the DR system might warmstart at the same time. (show details) | 8.7.3.0 | Policy-based Replication |
| SVAPAR-155568 | FS9500, SVC | Critical | On FS9500 or SV3 systems, batteries may prematurely hit end of life and go offline. (show details) | 8.7.3.0 | Reliability Availability Serviceability |
| SVAPAR-155656 | All | Critical | Multiple node asserts when removing a VDisk copy (or adding a copy with the autodelete parameter) from a policy-based replication recovery volume (show details) | 8.7.3.0 | Policy-based High availability, Policy-based Replication |
| SVAPAR-146591 | All | High Importance | Single node asserts may occur in systems using policy-based high availability if the active quorum application is restarted. (show details) | 8.7.3.0 | Policy-based High availability |
| SVAPAR-147361 | All | High Importance | If a software upgrade completes at the same time as performance data is being sent to IBM Storage Insights, a single node warmstart may occur. (show details) | 8.7.3.0 | Call Home, System Monitoring |
| SVAPAR-147647 | All | High Importance | A 32Gb Fibre Channel adapter may unexpectedly reset, causing a delay in communication via that adapter's ports. (show details) | 8.7.3.0 | Fibre Channel |
| SVAPAR-148032 | All | High Importance | When using policy-based high availability, a specific, unusual sequence of configuration commands can cause a node warmstart and prevent configuration commands from completing. (show details) | 8.7.3.0 | Policy-based High availability |
| SVAPAR-148495 | All | High Importance | Multiple node warm-starts on systems running v8.7 due to a small timing window when starting a snapshot if the source volume does not have any other snapshots. This issue is more likely to occur on systems using policy-based replication with no user-created snapshots. (show details) | 8.7.3.0 | Policy-based Replication, Snapshots |
| SVAPAR-150832 | All | High Importance | Upgrading a FlashSystem 5200 to a FlashSystem 5300 may fail if policy-based replication is enabled. The first node to upgrade may assert repeatedly, preventing a concurrent upgrade. (show details) | 8.7.3.0 | Reliability Availability Serviceability |
| SVAPAR-152379 | All | High Importance | When using policy-based high availability with multiple partitions, where partitions are replicating in both directions, it is possible to see a single node warmstart on each system. This is due to a deadlock condition related to I/O forwarding, triggered by a large write or unmap spike at the non-preferred site for the partition. (show details) | 8.7.3.0 | Policy-based High availability |
| SVAPAR-152925 | All | High Importance | The lsfabricport command may fail to return output, if a remote Fibre Channel port has an unknown port speed. In 8.7.2, this will prevent configuration backup from completing. (show details) | 8.7.3.0 | Command Line Interface |
| SVAPAR-154100 | All | High Importance | A node warmstart may occur to clear the condition when Fibre Channel adapter firmware has started processing a target I/O request, but has failed the request with status "Invalid Receive Exchange Address". (show details) | 8.7.3.0 | Fibre Channel |
| SVAPAR-154399 | All | High Importance | Policy-based high availability may be suspended and unable to restart after an upgrade to 8.7.2.x, due to a timing window. (show details) | 8.7.3.0 | Policy-based High availability |
| SVAPAR-154502 | All | High Importance | A single node warmstart may occur on systems with a very large number of vdisk-host maps, caused by a timeout during host Unit Attention processing. (show details) | 8.7.3.0 | Hosts |
| SVAPAR-154963 | All | High Importance | On systems with 8.7.2 software, a single node assert may occur due to a race condition when deleting volumes, hosts or host mappings that are part of a policy-based high availability partition. (show details) | 8.7.3.0 | Policy-based High availability |
| SVAPAR-156155 | All | High Importance | Repeated node warmstarts may occur if an unsupported direct-attached Fibre-channel host sends unsolicited frames to the nodes. (show details) | 8.7.3.0 | Fibre Channel |
| SVAPAR-156168 | All | High Importance | A single node warmstart may occur after running the svcinfo traceroute CLI command. (show details) | 8.7.3.0 | Inter-node messaging |
| SVAPAR-156332 | All | High Importance | Using the GUI to create a clone or thin-clone from a snapshot may fail with an CMMVC1243E error, if the snapshot is in an HA partition. (show details) | 8.7.3.0 | Policy-based High availability, Snapshots |
| SVAPAR-156345 | All | High Importance | A node warmstart on a system using policy-based replication has a low probability of causing another node to also warmstart. (show details) | 8.7.3.0 | Policy-based Replication |
| SVAPAR-156522 | All | High Importance | Compare and Write (CAW) I/O requests might be rejected with a SCSI Busy status after a failure to create volumes in the second location of a PBHA partition (show details) | 8.7.3.0 | Policy-based High availability |
| SVAPAR-145892 | All | Suggested | An unfixed error might display an incorrect fixed timestamp (show details) | 8.7.3.0 | Reliability Availability Serviceability |
| SVAPAR-145976 | FS7300 | Suggested | On FlashSystem 7300, fan speeds can vary at 3 second intervals even at a constant temperature | 8.7.3.0 | Reliability Availability Serviceability |
| SVAPAR-148287 | All | Suggested | On FS9500, FS5xxx or SV3 systems running 8.7.x software, it is not possible to enable USB encryption using the GUI, because the system does not correctly report how many USB devices the key has been written to. The command-line interface is not affected by this issue. (show details) | 8.7.3.0 | Graphical User Interface |
| SVAPAR-152076 | All | Suggested | The GUI may notify the user about all new releases, even if the system is configured to notify only for Long-Term Support releases. (show details) | 8.7.3.0 | Graphical User Interface |
| SVAPAR-152472 | FS5000 | Suggested | Volume group details view in the GUI might show a blank page for FlashSystem 5045 systems running 8.7.1 (show details) | 8.7.3.0 | Graphical User Interface |
| SVAPAR-152912 | All | Suggested | The finderr CLI command may produce no output on 8.7.0, 8.7.1 or 8.7.2. (show details) | 8.7.3.0 | Command Line Interface |
| SVAPAR-153310 | All | Suggested | Adding an HA policy to a partition may fail with a CMMVC1249E error. This will only happen if a DR partition in a 3-site configuration is deleted, a new partition is created with the same ID, and the user attempts to add an HA policy to that partition. (show details) | 8.7.3.0 | Policy-based High availability, Policy-based Replication |
| SVAPAR-156141 | All | Suggested | Fibre Channel host ports might ignore PLOGI requests for a very short duration after port startup (show details) | 8.7.3.0 | Fibre Channel |
| SVAPAR-156142 | All | Suggested | Persistent reservation requests for volumes configured with Policy-based High Availability might be rejected during a small timing window after a node comes online (show details) | 8.7.3.0 | Policy-based High availability |
| SVAPAR-156146 | All | Suggested | The GUI's encryption panel displays "Encryption is not fully enabled" when encryption is enabled but the encryption recovery key has not been configured. (show details) | 8.7.3.0 | Encryption, Graphical User Interface |
| SVAPAR-156174 | All | Suggested | A single node warmstart may happen due to unexpected duplicate OXID values from a Fibre Channel host (show details) | 8.7.3.0 | Fibre Channel |
| SVAPAR-156179 | All | Suggested | The supported length of client secret for SSO and MFA configurations is limited to 64 characters. (show details) | 8.7.3.0 | Security |
| SVAPAR-156182 | All | Suggested | A single node warmstart has a low probability of occurring on a system using policy-based high availability, if another node goes offline. (show details) | 8.7.3.0 | No Specific Feature |
| SVAPAR-156358 | All | Suggested | A temporary failure to download the list of available patches may cause a 4401 event ("Patch auto-update server communication error") to be logged. (show details) | 8.7.3.0 | Call Home |
| Description | Link |
|---|---|
| Product Documentation | |
| Concurrent Compatibility and Code Cross Reference | |
Support Information pages providing links to the following information:
|
|
| IBM Storage Virtualize Policy-based replication and High Availability Compatibility Cross Reference | |
| Concurrent Compatibility and Code Cross Reference | |
| Software Upgrade Test Utility | |
| Software Upgrade Planning | |
| IBM Storage Virtualize IP quorum application requirements |