This is the release note for the 8.7.2 release and details the issues resolved in between 8.7.2.0 and 8.7.2.2. This document will be updated with additional information whenever a PTF is released.
This document was last updated on 27 February 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 |
| The following restrictions were valid but have now been lifted | |
|
Policy-based replication and high availability were not supported on a FlashSystem 5045.
This restriction has now been lifted in 8.7.2.0 by SVAPAR-142939 |
8.7.1.0 |
|
Configurations using short distance partnerships using RDMA were not supported on 8.7.1.
This restriction has now been lifted in 8.7.2.0. |
8.7.0.0 |
|
Systems with ROCE Adapters could not have a MTU greater than 1500 on 8.6.0.0 or later. The workaround was to reduce the MTU to 1500.
This restriction has now been lifted in 8.7.2.0. |
8.6.0.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-0159 | 7184182 | 8.7.2.2 |
| CVE-2025-0160 | 7184182 | 8.7.2.2 |
| CVE-2024-6387 | 7183471 | 8.7.2.0 |
| CVE-2024-6409 | 7183471 | 8.7.2.0 |
| CVE-2023-2975 | 7183471 | 8.7.2.0 |
| CVE-2023-3446 | 7183471 | 8.7.2.0 |
| CVE-2023-3817 | 7183471 | 8.7.2.0 |
| CVE-2023-5678 | 7183471 | 8.7.2.0 |
| CVE-2022-2795 | 7183474 | 8.7.2.0 |
| CVE-2022-3094 | 7183474 | 8.7.2.0 |
| CVE-2022-3736 | 7183474 | 8.7.2.0 |
| CVE-2022-3924 | 7183474 | 8.7.2.0 |
| CVE-2023-4408 | 7183474 | 8.7.2.0 |
| CVE-2023-5517 | 7183474 | 8.7.2.0 |
| CVE-2023-5679 | 7183474 | 8.7.2.0 |
| CVE-2023-6516 | 7183474 | 8.7.2.0 |
| CVE-2023-50387 | 7183474 | 8.7.2.0 |
| CVE-2023-50868 | 7183474 | 8.7.2.0 |
| CVE-2023-6240 | 7183475 | 8.7.2.0 |
| CVE-2024-4032 | 7183477 | 8.7.2.0 |
| CVE-2024-28182 | 7183481 | 8.7.2.0 |
| CVE-2023-6356 | 7183482 | 8.7.2.0 |
| CVE-2023-6535 | 7183482 | 8.7.2.0 |
| CVE-2023-6536 | 7183482 | 8.7.2.0 |
| CVE-2023-5178 | 7183482 | 8.7.2.0 |
| CVE-2023-45871 | 7183482 | 8.7.2.0 |
APAR |
Affected Products |
Severity |
Description |
Resolved in |
Feature Tags |
|---|---|---|---|---|---|
|
|
| |||
| 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.2.2 | LDAP |
| 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.2.2 | Command Line Interface |
| SVAPAR-156168 | All | High Importance | A single node warmstart may occur after running the svcinfo traceroute CLI command. (show details) | 8.7.2.2 | 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.2.2 | Policy-based High availability, Snapshots |
| 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.2.2 | Policy-based High availability |
| SVAPAR-145976 | FS7300 | Suggested | On FlashSystem 7300, fan speeds can vary at 3 second intervals even at a constant temperature | 8.7.2.2 | Reliability Availability Serviceability |
| SVAPAR-150198 | All | Critical | Multiple node warmstarts (causing loss of access to data) may occur on 8.7.1 and 8.7.2 software, when deleting a volume that is in a volume group, and previously received a persistent reservation request. (show details) | 8.7.2.1 | Policy-based High availability, Policy-based Replication, Snapshots |
| SVAPAR-150433 | All | Critical | In certain policy-based 3-site replication configurations, a loss of connectivity between HA systems may cause I/O timeouts and loss of access to data. (show details) | 8.7.2.1 | Policy-based High availability, Policy-based Replication |
| SVAPAR-150764 | All | Critical | At 8.7.2.0, loss of access to vVols may occur after node failover if the host rebind operation fails. (show details) | 8.7.2.1 | vVols |
| SVAPAR-150663 | All | High Importance | Some FCM3 drives may go offline on upgrade to 8.7.2.0. (show details) | 8.7.2.1 | Drives |
| SVAPAR-140892 | FS7300, FS9200 | Suggested | Excessive numbers of informational battery reconditioning events may be logged. (show details) | 8.7.2.1 | Reliability Availability Serviceability |
| SVAPAR-151101 | All | Suggested | Unable to create new volumes in a volume group with a Policy-based High Availability replication policy using the GUI. The error returned is "The selected volume group is a recovery copy and no new volumes can be created in the group." (show details) | 8.7.2.1 | Policy-based High availability |
| SVAPAR-134589 | FS9500 | HIPER | A problem with NVMe drives on FlashSystem 9500 may impact node to node communication over the PCIe bus. This may lead to a temporary array offline. (show details) | 8.7.2.0 | Drives |
| SVAPAR-131228 | All | Critical | A RAID array temporarily goes offline due to delays in fetching the encryption key when a node starts up. (show details) | 8.7.2.0 | Distributed RAID, Encryption, RAID |
| SVAPAR-140079 | All | Critical | The internal scheduler is blocked after requesting more flashcopy bitmap memory. This will cause the creation of new snapshots and removal of expired snapshots to fail. (show details) | 8.7.2.0 | FlashCopy, Safeguarded Copy & Safeguarded Snapshots |
| SVAPAR-140781 | All | Critical | Successful login attempts to the configuration node via SSH are not communicated to the remote syslog server. Service assistant and GUI logins are correctly reported. (show details) | 8.7.2.0 | Security |
| SVAPAR-141098 | All | Critical | High peak latency causing access loss after recovering from SVAPAR-140079 and SVAPAR-140080. (show details) | 8.7.2.0 | FlashCopy, Safeguarded Copy & Safeguarded Snapshots |
| SVAPAR-141920 | All | Critical | Under specific scenarios, adding a snapshot to a volume group could trigger a cluster recovery causing brief loss of access to data. (show details) | 8.7.2.0 | FlashCopy |
| SVAPAR-142287 | All | Critical | Loss of access to data when running certain snapshot commands at the exact time that a Volume Group Snapshots is stopping (show details) | 8.7.2.0 | Snapshots |
| SVAPAR-143997 | All | Critical | A single node warmstart may occur when the upper cache reaches 100% full while the partner node in the I/O group is offline (show details) | 8.7.2.0 | Reliability Availability Serviceability |
| SVAPAR-144389 | SVC | Critical | In an SVC stretched cluster, adding a second vdisk copy to a PBR-enabled volume using the GUI does not automatically add a copy to the change volume. This can cause subsequent vdisk migration requests to fail. (show details) | 8.7.2.0 | Policy-based Replication |
| SVAPAR-147646 | FS5000, FS5100, FS5200, FS7200, FS7300, FS9100, FS9200, FS9500, SVC | Critical | Node goes offline when a non-fatal PCIe error on the fibre channel adapter is encountered. It's possible for this to occur on both nodes simultaneously. (show details) | 8.7.2.0 | Fibre Channel |
| SVAPAR-147870 | All | Critical | Occasionally, deleting a thin-clone volume that is deduplicated may result in a single node warmstart and a 1340 event, causing a pool to temporarily go offline. (show details) | 8.7.2.0 | Data Reduction Pools, Deduplication, Snapshots |
| SVAPAR-148049 | SVC | Critical | A config node may warmstart during the failback process of the online_spare node to the spare node after executing 'swapnode -failback' command, resulting in a loss of access. (show details) | 8.7.2.0 | Hot Spare Node |
| SVAPAR-153584 | All | Critical | A node warmstart may occur when a system using policy-based high availability loses connectivity to the remote system. In rare instances, both nodes in the system can warmstart at the same time. This is due to an inter-node messaging timing window. (show details) | 8.7.2.0 | Policy-based High availability |
| HU02293 | All | High Importance | MDisk Groups can go offline due to overall timeout if the backend storage is configured incorrectly after a hot spare node comes online (show details) | 8.7.2.0 | Hot Spare Node |
| HU02493 | SVC | High Importance | On certain controllers that have more then 511 LUNS configured, then mdisks may go offline (show details) | 8.7.2.0 | Backend Storage |
| SVAPAR-131999 | All | High Importance | Single node warmstart when an NVMe host disconnects from the storage (show details) | 8.7.2.0 | NVMe |
| SVAPAR-136677 | All | High Importance | An unresponsive DNS server may cause a single node warmstart and the email process to get stuck. (show details) | 8.7.2.0 | System Monitoring |
| SVAPAR-137361 | All | High Importance | A battery may incorrectly enter a failed state, if input power is removed within a small timing window (show details) | 8.7.2.0 | Reliability Availability Serviceability |
| SVAPAR-137512 | All | High Importance | A single-node warmstart may occur during a shrink operation on a thin-provisioned volume. This is caused by a timing window in the cache component. (show details) | 8.7.2.0 | Cache |
| SVAPAR-138832 | All | High Importance | Nodes using IP replication with compression may experience multiple node warmstarts due to a timing window in error recovery. (show details) | 8.7.2.0 | IP Replication |
| SVAPAR-139247 | All | High Importance | Very heavy write workload to a thin-provisioned volume may cause a single-node warmstart, due to a low-probability deadlock condition. (show details) | 8.7.2.0 | Thin Provisioning |
| SVAPAR-139260 | All | High Importance | Heavy write workloads to thin-provisioned volumes may result in poor performance on thin-provisioned volumes, due to a lack of destage resource. (show details) | 8.7.2.0 | Thin Provisioning |
| SVAPAR-144000 | All | High Importance | A high number of abort commands from an NVMe host in a short time may cause a Fibre Channel port on the storage to go offline, leading to degraded hosts. (show details) | 8.7.2.0 | Hosts |
| SVAPAR-144036 | FS5100, FS5200, FS7200, FS7300, FS9100, FS9200, FS9500 | High Importance | Replacement of an industry standard NVMe drive may fail until both nodes are warmstarted. (show details) | 8.7.2.0 | Reliability Availability Serviceability |
| SVAPAR-144068 | All | High Importance | If a volume group snapshot is created at the same time as an existing snapshot is deleting, all nodes may warmstart, causing a loss of access to data. This can only happen if there is insufficient FlashCopy bitmap space for the new snapshot. (show details) | 8.7.2.0 | Snapshots |
| SVAPAR-144069 | All | High Importance | On a system with SAS drives, if a node canister is replaced while an unsupported drive is in the enclosure, all nodes may warmstart simultaneously, causing a loss of access to data. (show details) | 8.7.2.0 | Drives |
| SVAPAR-144070 | All | High Importance | After changing the system name, the iSCSI IQNs may still contain the old system name. (show details) | 8.7.2.0 | iSCSI |
| SVAPAR-144272 | All | High Importance | IO processing unnecessarily stalled for several seconds following a node coming online (show details) | 8.7.2.0 | Performance |
| SVAPAR-145278 | All | High Importance | Upgrade from 8.7.0 to 8.7.1 may cause to an invalid internal state, if policy-based replication is in use. This may lead to node warmstarts on the recovery system, or cause replication to stop. (show details) | 8.7.2.0 | Policy-based Replication |
| SVAPAR-146097 | All | High Importance | On systems running 8.7.0 or 8.7.1 software with NVMe drives, at times of particularly high workload, there is a low probability of a single-node warmstart. | 8.7.2.0 | Drives |
| SVAPAR-146522 | All | High Importance | FlashCopy background copy and cleaning may get stuck after a node restarts. This can also affect Global Mirror with Change Volumes, volume group snapshots, and policy-based replication (show details) | 8.7.2.0 | FlashCopy, Global Mirror With Change Volumes, Policy-based Replication, Snapshots |
| SVAPAR-148251 | All | High Importance | Merging partitions on 8.7.1.0 software may trigger a single-node warmstart. (show details) | 8.7.2.0 | Policy-based High availability |
| SVAPAR-153269 | All | High Importance | A node warmstart may occur due to a stalled FlashCopy mapping, when policy-based replication is used with FlashCopy or snapshots (show details) | 8.7.2.0 | FlashCopy |
| SVAPAR-92804 | FS5000 | High Importance | SAS direct attach host path is not recovered after a node reboot causing a persistent loss of redundant paths. (show details) | 8.7.2.0 | Hosts |
| SVAPAR-114758 | All | Suggested | Following a cluster recovery, the names of some back end storage controllers can be lost resulting in default names such as controller0. (show details) | 8.7.2.0 | Backend Storage |
| SVAPAR-123614 | SVC | Suggested | 1300 Error in the error log when a node comes online, caused by a delay between bringing up the physical FC ports and the virtual FC ports (show details) | 8.7.2.0 | Hot Spare Node |
| SVAPAR-137322 | All | Suggested | A false 1627 event will be reported on an SVC stretched cluster after adding connectivity to more ports on a backend controller. (show details) | 8.7.2.0 | Backend Storage |
| SVAPAR-137906 | All | Suggested | A node warmstart may occur due to a timeout caused by FlashCopy bitmap cleaning, leading to a stalled software upgrade. (show details) | 8.7.2.0 | FlashCopy, System Update |
| SVAPAR-138286 | All | Suggested | If a direct-attached controller has NPIV enabled, 1625 errors will incorrectly be logged, indicating a controller misconfiguration. (show details) | 8.7.2.0 | Backend Storage |
| SVAPAR-138859 | FS5000, FS5100, FS5200 | Suggested | Collecting a Type 4 support package (Snap Type 4: Standard logs plus new statesaves) in the GUI can trigger an out of memory event causing the GUI process to be killed. (show details) | 8.7.2.0 | Support Data Collection |
| SVAPAR-139943 | All | Suggested | A single node warmstart may occur when a host sends a high number of unexpected Fibre Channel frames. (show details) | 8.7.2.0 | Fibre Channel |
| SVAPAR-140588 | All | Suggested | A node warmstart may occur due to incorrect processing of NVMe host I/O offload commands (show details) | 8.7.2.0 | NVMe |
| SVAPAR-142939 | FS5000 | Suggested | Upgrade to 8.7.1 on FS5045 with policy-based replication or high availability is not supported. (show details) | 8.7.2.0 | Policy-based Replication |
| SVAPAR-143621 | All | Suggested | REST API returns HTTP status 502 after a timeout of 30 seconds instead of 180 seconds (show details) | 8.7.2.0 | REST API |
| SVAPAR-144033 | All | Suggested | Spurious 1370 events against SAS drives which are not members of an array. (show details) | 8.7.2.0 | Reliability Availability Serviceability |
| SVAPAR-144062 | All | Suggested | A node may warmstart due to a problem with IO buffer management in the cache component. (show details) | 8.7.2.0 | Cache |
| SVAPAR-144271 | SVC | Suggested | An offline node that is protected by a spare node may take longer than expected to come online. This may result in a temporary loss of Fibre Channel connectivity to the hosts (show details) | 8.7.2.0 | Hot Spare Node |
| SVAPAR-144515 | All | Suggested | When trying to increase FlashCopy or volume mirroring bitmap memory, the GUI may incorrectly report that the new value exceeds combined memory limits. (show details) | 8.7.2.0 | FlashCopy, Volume Mirroring |
| SVAPAR-146064 | All | Suggested | Systems using asynchronous policy-based replication may incorrectly log events indicating the recovery point objective (RPO) has been exceeded. (show details) | 8.7.2.0 | Policy-based Replication |
| SVAPAR-146640 | All | Suggested | When volume latency increases from below 1ms to above 1ms, the units in the GUI performance monitor will not be incorrect. (show details) | 8.7.2.0 | Graphical User Interface |
| SVAPAR-152880 | All | Suggested | The service IP may not be available after a node reboot, if a timeout occurs when the system tries to bring up the IP address. (show details) | 8.7.2.0 | No Specific Feature |
| SVAPAR-93445 | FS5100, FS5200, FS7200, FS7300, FS9100, FS9200, FS9500 | Suggested | A single node warmstart may occur due to a very low-probability timing window related to NVMe drive management. (show details) | 8.7.2.0 | No Specific Feature |
| 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 | |
| Software Upgrade Test Utility | |
| Software Upgrade Planning | |
| IBM Storage Virtualize IP quorum application requirements |