Release Note for systems built with IBM Storage Virtualize


This is the release note for the 8.7.1 release and details the issues resolved in 8.7.1.0. This document will be updated with additional information whenever a PTF is released.

This document was last updated on 25 February 2025.

  1. What's new in 8.7.1
  2. Known Issues and Restrictions
  3. Issues Resolved
    1. Security Issues Resolved
    2. APARs Resolved
  4. Useful Links

Note. Detailed build version numbers are included in the Concurrent Compatibility and Code Cross Reference in the Useful Links section.


1. What's new in 8.7.1

The following new features have been introduced in the 8.7.1.0 release:

The following features are no longer supported on 8.7.1.0 and later:


2. Known Issues and Restrictions

Note: For clarity, the terms "node" and "canister" are used interchangeably.
Details Introduced

Configurations using short distance partnerships using RDMA are not supported on 8.7.1.

This restriction will be lifted in a future software version.

8.7.0.0

Due to SVAPAR-142939, policy-based replication and high availability are not supported on a FlashSystem 5045.

This restriction will be lifted in a future software version.

8.7.1.0

IBM SAN Volume Controller Systems with multiple I/O groups are not supported.

This restriction will be lifted in the next long-term support release.

8.7.1.0
The following restrictions were valid but have now been lifted

Due to SVAPAR-138214, if Veeam 12.1 is used with Storage Virtualize 8.5.1 or later, and the Veeam user is in an ownership group, this might cause node warmstarts.

This has been resolved in 8.7.1.0

8.5.1.0

3. Issues Resolved

This release contains all of the fixes included in the 8.7.0.0 release, plus the following additional fixes.

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.

3.1 Security Issues Resolved

Security issues are documented using a reference number provided by "Common Vulnerabilities and Exposures" (CVE).
CVE Identifier
Link for additional Information
Resolved in
  • No matches found
  • No matches found
  • No matches found
  • No matches found
  • No matches found

3.2 APARs Resolved

Show details for all APARs
APAR
Affected Products
Severity
Description
Resolved in
Feature Tags
  • No matches found
  • No matches found
  • No matches found
  • No matches found
  • No matches found
  • No matches found
  • No matches found
  • No matches found
  • No matches found
  • No matches found
  • No matches found
  • No matches found
  • No matches found
  • No matches found
  • No matches found
SVAPAR-136256 All HIPER Each ethernet port can only have a single management IP address. Attempting to add a second management IP to the same port may cause multiple node warmstarts and a loss of access to data. (show details) 8.7.1.0 Reliability Availability Serviceability
SVAPAR-140080 All HIPER Tier 2 warmstarts ending with nodes in service state while processing a long list of expired snapshots. (show details) 8.7.1.0 FlashCopy, Safeguarded Copy & Safeguarded Snapshots
SVAPAR-135022 All Critical When using Policy Based High Availability, a storage partition can become suspended due to a disagreement in the internal quorum race state between two systems, causing a loss of access to data. (show details) 8.7.1.0 Policy-based Replication
SVAPAR-137485 FS5000 Critical Reseating a FlashSystem 50xx node canister at 8.7.0.0 may cause the partner node to reboot, causing temporary loss of access to data. (show details) 8.7.1.0 Reliability Availability Serviceability
SVAPAR-141112 All Critical When using policy-based high availability and volume group snapshots, it is possible for an I/O timeout condition to trigger node warmstarts. This can happen if a system is disconnected for an extended period, and is then brought back online after a large amount of host I/O to the HA volumes. (show details) 8.7.1.0 Policy-based Replication
SVAPAR-142040 All Critical A timing window related to logging of capacity warnings may cause multiple node warmstarts on a system with low free physical capacity on an FCM array. (show details) 8.7.1.0 Reliability Availability Serviceability
SVAPAR-142045 All Critical A system which was previously running pre-8.6.0 software, and is now using policy-based high availability, may experience multiple node warmstarts when a PBHA failover is requested by the user. (show details) 8.7.1.0 Policy-based Replication
SVAPAR-143480 All Critical When using asynchronous policy based replication on low bandwidth links with snapshot clone/restore, an undetected data corruption may occur. This issue only affects 8.7.0.0. (show details) 8.7.1.0 Policy-based Replication
SVAPAR-147978 All Critical A system running 8.7.0 and using policy-based replication may experience additional warmstarts during the recovery from a single node warmstart (show details) 8.7.1.0 Policy-based Replication
SVAPAR-111173 All High Importance Loss of access when two drives experience slowness at the same time (show details) 8.7.1.0 RAID
SVAPAR-136427 All High Importance When deleting multiple older snapshots versions, whilst simultaneously creating new snapshots, the system can run out of bitmap space resulting in a bad snapshot map, repeated asserts, and a loss of access. (show details) 8.7.1.0 FlashCopy
SVAPAR-138214 All High Importance When a volume group is assigned to an ownership group, creating a snapshot and populating a new volume group from the snapshot will cause a warmstart of the configuration node when 'lsvolumepopulation' is run. (show details) 8.7.1.0 FlashCopy
SVAPAR-140926 All High Importance When a cluster partnership is removed, a timing window can result in an I/O timeout and a node warmstart. (show details) 8.7.1.0 Policy-based Replication
SVAPAR-141684 All High Importance Prevent drive firmware upgrade with both '-force' and '-all' parameters, to avoid multiple drives going offline due to lack of redundancy. (show details) 8.7.1.0 Drives
SVAPAR-142081 All High Importance If an error occurs during creation of a replication policy, multiple node warmstarts may occur, causing a temporary loss of access to data. (show details) 8.7.1.0 Policy-based Replication
SVAPAR-145355 All High Importance On FS5045 with policy-based high availability or replication, an out-of-memory issue may cause frequent 4110 events. (show details) 8.7.1.0 Policy-based High availability, Policy-based Replication
SVAPAR-152902 All High Importance If a system is using asynchronous policy-based replication, certain unusual host I/O workloads can cause an I/O timeout to be incorrectly detected, triggering node warmstarts at the recovery site. (show details) 8.7.1.0 Policy-based Replication
SVAPAR-153246 All High Importance A hung condition in Remote Receive IOs (RRI) for volume groups can lead to warmstarts on multiple nodes. (show details) 8.7.1.0 Policy-based Replication
SVAPAR-89331 All High Importance Systems running 8.5.2 or higher using IP replication with compression may have low replication bandwidth and high latency due to an issue with the way the data is compressed. (show details) 8.7.1.0 IP Replication
SVAPAR-130984 All Suggested Configuring Policy-based replication in the GUI fails if the system authentication service type is unused. (show details) 8.7.1.0 Policy-based Replication
SVAPAR-135742 All Suggested A temporary network issue may cause unexpected 1585 DNS connection errors after upgrading to 8.6.0.4, 8.6.3.0 or 8.7.0.0. This is due to a shorter DNS request timeout in these PTFs. (show details) 8.7.1.0 Reliability Availability Serviceability
SVAPAR-138418 All Suggested Snap collections triggered by Storage Insights over cloud callhome time out before they have completed (show details) 8.7.1.0 Reliability Availability Serviceability
SVAPAR-139118 All Suggested When logged into GUI as a user that is a member of the FlashCopy Administrator group, the GUI does not allow flashcopies to be created and options are greyed out. (show details) 8.7.1.0 Graphical User Interface
SVAPAR-139205 All Suggested A node warmstart may occur due to a race condition between Fibre Channel adapter I/O processing and a link reset. (show details) 8.7.1.0 Fibre Channel
SVAPAR-140994 All Suggested Expanding a volume via the GUI fails with CMMVC7019E because the volume size is not a multiple of 512 bytes. (show details) 8.7.1.0 Reliability Availability Serviceability
SVAPAR-141019 All Suggested The GUI crashed when a user group with roles 3SiteAdmin and remote users exist (show details) 8.7.1.0 3-Site using HyperSwap or Metro Mirror, Graphical User Interface
SVAPAR-141467 All Suggested SNMPv3 traps may not be processed properly by the SNMP server configured in the system. (show details) 8.7.1.0 System Monitoring
SVAPAR-141559 All Suggested GUI shows: 'error occurred loading table data.' in the volume view after the first login attempt to the GUI. Volumes will be visible inside the 'Volumes by Pool'. This is evoked if we create volumes with either a number between dashes, or numbers after dashes, or other characters after numbers (show details) 8.7.1.0 Graphical User Interface
SVAPAR-141937 All Suggested In a Policy-based high availability configuration, when a SCSI Compare and Write command is sent to the non-Active Management System, and communication is lost between the systems while it is being processed, a node warmstart may occur. (show details) 8.7.1.0 Policy-based Replication
SVAPAR-142093 All Suggested The 'Upload support package' option is missing from the Support Package GUI (show details) 8.7.1.0 Graphical User Interface
SVAPAR-142190 All Suggested The user role descriptions in the GUI are wrong for the CopyOperator. (show details) 8.7.1.0 Graphical User Interface
SVAPAR-142193 All Suggested If an IP Replication partnership only has link2 configured, then the GUI Partnership shows type Fibre Channel for the IPV4 connection. (show details) 8.7.1.0 IP Replication
SVAPAR-142194 All Suggested GUI volume creation does not honour the preferred node that was selected. (show details) 8.7.1.0 Graphical User Interface
SVAPAR-148643 All Suggested Changing the management IP address on 8.7.0 software does not update the console_IP field in lspartnership and lssystem output. This can cause the management GUI and Storage Insights to display the wrong IP address. (show details) 8.7.1.0 Graphical User Interface

4. Useful Links

Description Link
Product Documentation
Concurrent Compatibility and Code Cross Reference
Support Information pages providing links to the following information:
  • Interoperability information
  • Product documentation
  • Configuration Limits
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