Release Note for systems built with IBM Storage Virtualize

This is the release note for the 9.1.2 release and details the issues resolved in between 9.1.2.0 and 9.1.2.1. This document will be updated with additional information whenever a PTF is released.

This document was last updated on 16 April 2026.

  1. What's new in 9.1.2
  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 9.1.2

The following new feature has been introduced in the 9.1.2.1 release:

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

The following features were introduced in the 9.1.1.0 release:

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


2. Known Issues and Restrictions

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

Expansion of RAID arrays containing NVMe drives is not supported. This restriction will be lifted in a future release under SVAPAR-194749.

If you plan to expand a RAID array, wait for a version with this fix.

9.1.2.0

 .

IBM SAN Volume Controller Systems with multiple I/O groups are not supported on non-LTS Releases.

This restriction is lifted in long term support (LTS) releases.

8.7.1.0
The following restrictions were valid but have now been lifted

Systems that were running 9.1.0.x and 9.1.1.x required port 8443 to be opened between partnered systems when setting up partnerships for policy-based replication (asynchronous or high-availability) or partition migration.

This port needed to be opened in addition to the ports described in the Product documentation here

This restriction has been lifted in 9.1.2.0 by SVAPAR-184208.

9.1.0.0

3. Issues Resolved

This release contains all of the fixes included in the 9.1.1.2 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

3.2 APARs Resolved

Show details for all APARs
APAR Affected Products Severity Description Resolved in Feature Tags
SVAPAR-198196 All HIPER Cisco Duo multi-factor authentication may fail, due to a change in which certificates are accepted by the server. (show details)
Symptom Configuration
Environment Systems using Cisco Duo multi-factor authentication
Trigger None
Workaround Install a patch, available from IBM support.
9.1.2.1 Command Line Interface, Graphical User Interface
SVAPAR-192675 All Critical FS5300 node canisters upgrading to 8.7.0.10, 9.1.0.4 or 9.1.1.2 may fail to boot, causing a 1073 error to appear in the eventlog. (show details)
Symptom Loss of Redundancy
Environment FS5300
Trigger Upgrading to 8.7.0.10, 9.1.0.4 or 9.1.1.2
Workaround None
9.1.2.1 System Update
SVAPAR-200133 FS7600, FS9600 Critical FlashSystem 7600 and FlashSystem 9600 nodes may log temperature sensor errors or fail to reboot correctly, due to an unresponsive service processor (show details)
Symptom Loss of Access to Data
Environment FS7600 and FS9600
Trigger None
Workaround None
9.1.2.1 Reliability Availability Serviceability
SVAPAR-199322 All Suggested Systems on 9.1.1 or 9.1.2 software with more than 24 FlashCore Modules may experience a node warmstart, due to a memory allocation issue. (show details)
Symptom Single Node Warmstart
Environment Systems with FCMs
Trigger Large numbers of FCM drives
Workaround None
9.1.2.1 Drives
SVAPAR-173936 All Critical A timing window can lead to a resource leak in the thin-provisioning component. This can lead to higher volume response times, and eventually a node warmstart caused by an I/O timeout. (show details)
Symptom Performance
Environment Systems using thin-provisioned volumes.
Trigger None
Workaround Warmstarting the affected node will clear the issue.
9.1.2.0 Thin Provisioning
SVAPAR-180211 All Critical On systems with High Speed Ethernet partnerships, network connectivity issues may result in a multiple node reboots and loss of access to data. (show details)
Symptom Loss of Access to Data
Environment Systems using High Speed Ethernet partnerships.
Trigger Network issues
Workaround None
9.1.2.0 IP Replication
SVAPAR-181568 All Critical I/O timeouts may lead to node warmstarts, if a volume is added to a volume group which is using policy-based replication, and has a DR test active. (show details)
Symptom Multiple Node Warmstarts
Environment Systems using policy-based replication
Trigger Starting a DR test, then adding a volume to the volume group before the DR test ends.
Workaround None
9.1.2.0 Policy-based Replication
SVAPAR-183539 All Critical Hosts using NVMe over FC may not connect to systems with 64G FC adapters (show details)
Symptom Loss of Access to Data
Environment Hosts with NVMe over FC, on systems with 64G FC adapters
Trigger None
Workaround None
9.1.2.0 Fibre Channel, NVMe Hosts
SVAPAR-184023 All Critical Node assert when using NVMe hosts during high workload or events that cause IO delays. (show details)
Symptom Loss of Access to Data
Environment NVMe hosts using Flashsystems.
Trigger During cases where NVMe hosts are sending high workload to a Flashsystem, or there is an event that causes IO delays such as a Flashsystem upgrade, the assert can be triggered.
Workaround None
9.1.2.0 NVMe Hosts
SVAPAR-187529 All Critical Node Asserts caused by an unsupported number of NVMe over FC hosts logging in to the node canister. (show details)
Symptom Multiple Node Warmstarts
Environment System using NVMe over FC with 8.7.3 or later
Trigger New Host logging in to the system pushing the system above the supported limit
Workaround None
9.1.2.0 NVMe Hosts
SVAPAR-189679 FS7200, FS7300 Critical On FS7200 and FS7300, a PCIe timeout may cause node warmstarts or fibre channel port re-initialization, potentially leading to loss of access to data. (show details)
Symptom Loss of Access to Data
Environment Flashsystem 7200 and 7300 with fibre channel adapters
Trigger None
Workaround None
9.1.2.0 Fibre Channel
SVAPAR-191534 All Critical The RAID background parity scrub process might stall or run very slowly on arrays using NVMe drives (show details)
Symptom None
Environment Systems with NVMe drives, running software levels 8.6.2-9.1.1.
Trigger Scrub process encounters a certain data pattern on unallocated extents on the array
Workaround None
9.1.2.0 RAID
HU02477 FS5200, FS7200, FS7300, FS9200, FS9500, SVC High Importance A node warmstart may occur when a system using IP replication experiences network instability. (show details)
Symptom Single Node Warmstart
Environment Systems configured with IP partnership, IP Replication failover
Trigger Unstable network between partnered nodes
Workaround None
9.1.2.0 IP Replication
SVAPAR-171790 All High Importance Triggering a livedump may cause a single node warmstart (show details)
Symptom Single Node Warmstart
Environment All
Trigger Collecting a snap option 4 which is Standard logs plus new statesaves.
Workaround None
9.1.2.0 Reliability Availability Serviceability
SVAPAR-180424 All High Importance PBHA IP quorum application does not work on 9.1 when using externally-signed or self-signed system certificate and internal_communication certificate (show details)
Symptom Error in Error Log
Environment Systems using Policy-based High availability
Trigger Deploying an IP quorum application on systems with an externally-signed or self-signed certificate
Workaround Install full certificate chain in the system certificate of each system or add the full certificate chain of each system in the truststore of the respective partner system. Afterwards create a new IP quorum application
9.1.2.0 Policy-based High availability
SVAPAR-182188 All High Importance A single node warmstart may occur when the Ransomware Threat Detection process stops functioning (show details)
Symptom Single Node Warmstart
Environment Systems using Ransomware Threat Detection
Trigger None
Workaround None
9.1.2.0 Reliability Availability Serviceability
SVAPAR-183978 All High Importance Policy-based HA or replication partnerships between systems running 9.1 and 8.7.0 may not work correctly due to a internal firewall issue. (show details)
Symptom Configuration
Environment Policy-based HA or replication partnerships between systems running 9.1 and above and 8.7.0.7 and above.
Trigger None.
Workaround None.
9.1.2.0 Policy-based High availability, Policy-based Replication
SVAPAR-186006 All High Importance Some 64Gb Fibre Channel SFPs with FRU PN 78P7709 are not recognised by the adapter, preventing the port from being used. (show details)
Symptom Loss of Redundancy
Environment Systems with 64Gb FC adapters
Trigger None
Workaround None
9.1.2.0 Fibre Channel
SVAPAR-186062 All High Importance Snapshots are not populated in refresh from snapshots grid when volume group ID is higher than 127 (show details)
Symptom Configuration
Environment Create volume group with id higher than 127
Trigger Refresh the VG from snapshot
Workaround None
9.1.2.0 Graphical User Interface
SVAPAR-186752 All High Importance RAID array expansion may take much longer than expected, due to an internal data migration bottleneck. This is more likely to happen on systems with large numbers of thin volumes. (show details)
Symptom Performance
Environment Systems with large numbers of thin volumes
Trigger RAID array expansion
Workaround None
9.1.2.0 RAID
SVAPAR-187071 All High Importance If a snapshot is taken while the production volume is offline, I/O requests may not be processed correctly, leading to I/O timeouts and multiple node warmstarts. (show details)
Symptom Multiple Node Warmstarts
Environment Systems using volume group snapshots
Trigger Snapshot taken while the production volume is offline.
Workaround None
9.1.2.0 Snapshots
SVAPAR-187237 All High Importance A failed attempt to create a system certificate can trigger a node warmstart, due to incomplete error handling. (show details)
Symptom Single Node Warmstart
Environment Systems running 9.1.0 or 9.1.1
Trigger System certificate creation
Workaround None
9.1.2.0 Reliability Availability Serviceability
SVAPAR-187600 All High Importance A 2100 error may occur on 9.1.0 or later systems when a partnered system upgrades from below 9.1.0 to 9.1.0 or higher, temporarily blocking replication configuration during the upgrade. (show details)
Symptom Error in Error Log
Environment Systems running 9.1.0 with policy-based replication or HA
Trigger Upgrade
Workaround Stop the partnership for any system that is upgrading from pre-9.1.0 to 9.1.0 or above.
9.1.2.0 Policy-based Replication
SVAPAR-187637 All High Importance In rare situations, the system may temporarily misinterpret the state of a remote host cluster object. This may result in an internal recovery attempt and the reporting of a 4100 error, without any customer-initiated action. (show details)
Symptom Error in Error Log
Environment System configured with policy-based high availability and host clusters
Trigger None
Workaround None
9.1.2.0 Policy-based High availability
SVAPAR-192370 All High Importance A node warmstart may occur due to a Fibre Channel adapter firmware issue. (show details)
Symptom Single Node Warmstart
Environment Systems configured with Fibre Channel adapters.
Trigger None.
Workaround None.
9.1.2.0 Fibre Channel
SVAPAR-192446 All High Importance A compressed RAID array may run out of space while a space reclamation triggered by reclaim_se is running and at the same time free capacity is consumed by write workload on the array (show details)
Symptom Loss of Access to Data
Environment Systems with compressed arrays using the reclaim_se feature
Trigger Space reclamation running while write workload consumes significant amounts of capacity on a compressed array
Workaround Stop reclaim_se
9.1.2.0 Thin Provisioning
SVAPAR-192610 All High Importance A single node warmstart may occur after running the refreshfromsnapshot command. (show details)
Symptom Single Node Warmstart
Environment Systems using volume group snapshots with 9.1.1 software.
Trigger A timing window in which refreshfromsnapshot is triggered for a volume group that has a bitmap merge in progress.
Workaround None
9.1.2.0 FlashCopy, Snapshots
SVAPAR-192874 All High Importance When using the GUI to modify hosts, it only lists I/O group 0. This can prevent configuration actions if an I/O group exists that has an ID that is non-zero. (show details)
Symptom Configuration
Environment Systems using storage partitions.
Trigger None
Workaround Use the CLI to modify the host.
9.1.2.0 Hosts
SVAPAR-192918 All High Importance Backend unmap of unused extents may stall, resulting in physical capacity not being reclaimed on FlashCore Modules (show details)
Symptom Performance
Environment Systems unmap feature enabled.
Trigger None
Workaround None
9.1.2.0 Drives
SVAPAR-193035 All High Importance A battery communication error may cause a node to go offline, and report a battery-related node error. (show details)
Symptom Loss of Redundancy
Environment None
Trigger A temporary internal problem causing interruption to communications with batteries.
Workaround Exit Service mode
9.1.2.0 Reliability Availability Serviceability
SVAPAR-193057 All High Importance A limitation affecting the quad-port 32Gb Fibre Channel adapter with FRU PN 03GH768 may prevent some ports from being used. (show details)
Symptom Configuration
Environment IBM Storage FlashSystem 5300 with FRU PN 03GH768.
Trigger None
Workaround None
9.1.2.0 Fibre Channel
SVAPAR-193064 All High Importance Offline node canister caused by a fault while sending configuration changes to Storage Insights using callhome (show details)
Symptom Configuration
Environment None
Trigger None
Workaround No Value
9.1.2.0 Call Home
HU01504 All Suggested The output from lscontroller may include the nodes of the local system, if NPIV is enabled. (show details)
Symptom None
Environment None
Trigger None
Workaround None
9.1.2.0 Command Line Interface
SVAPAR-181551 All Suggested After a node has been removed from the system configuration, error code 2015 (invalid patch state) may be logged incorrectly. (show details)
Symptom Configuration
Environment None
Trigger Removing a node from the system.
Workaround None
9.1.2.0 Reliability Availability Serviceability
SVAPAR-184208 All Suggested Partnership setup using the management GUI fails, if the partnered systems cannot communicate via port 8443 (show details)
Symptom Configuration
Environment Systems that need to be in a partnership
Trigger Setting up a partnership via the management GUI
Workaround Open port 8443 between the two systems in the firewall.
9.1.2.0 Policy-based High availability, Policy-based Replication
SVAPAR-184527 All Suggested A system using policy-based replication may produce incorrect performance statistics, which suggest that high availability is configured. (show details)
Symptom Configuration
Environment Systems using policy-based replication.
Trigger None
Workaround None
9.1.2.0 Policy-based Replication
SVAPAR-185630 All Suggested The GUI may incorrectly show Ransomware Threat Detection is disabled. The feature will still work as expected. (show details)
Symptom Error in Error Log
Environment Systems with Ransomware Threat Detection which don't have a Storage Insights Pro license.
Trigger None
Workaround None
9.1.2.0 Security
SVAPAR-185861 All Suggested Systems using 3-site replication (HA+DR) can experience a warmstart when the site link configuration changes, while some IO is outstanding. (show details)
Symptom Single Node Warmstart
Environment Systems using 3-site HA+DR
Trigger A slow link to the DR site
Workaround none
9.1.2.0 Policy-based High availability
SVAPAR-186575 All Suggested A 4110 error may be raised if the REST API authentication token expires and the REST API is receiving a large number of requests (show details)
Symptom Error in Error Log
Environment Systems using Policy-based replication, Policy-based High Availability or FlashSystem grid.
Trigger REST API token expires
Workaround none
9.1.2.0 FlashSystem Grid, Policy-based High availability, Policy-based Replication
SVAPAR-186698 All Suggested Snaps collected from Storage Insights do not contain enclosure dumps and battery snaps (show details)
Symptom None
Environment Systems with cloud callhome enabled
Trigger Collecting a snap remotely
Workaround Collect a snap using the GUI or CLI
9.1.2.0 Support Data Collection
SVAPAR-187532 All Suggested The GUI does not offer the capacity-optimized option when linking pools for PBHA, if child pools are in use. (show details)
Symptom Configuration
Environment Systems running 9.1.0 with PBHA
Trigger Configuring PBHA with child pools
Workaround Use CLI to select capacity_optimized
9.1.2.0 Policy-based High availability
SVAPAR-187754 All Suggested The GUI may show "Internal Server Error 500", if SSO is in use and the GUI has been open for more than 30 minutes before attempting to login. (show details)
Symptom Configuration
Environment SSO login
Trigger If the browser remains open for more than 30 min and user click Sign in with SSO
Workaround Remove the /sso from the browser address, then click the sign in with SSO button again
9.1.2.0 Graphical User Interface
SVAPAR-188203 All Suggested After clearing I/O statistics files, a node warmstart may occur due to a timing window where a duplicate statistics file is detected. (show details)
Symptom Single Node Warmstart
Environment System using CCH(cloudcallhome)
Trigger None
Workaround None
9.1.2.0 Call Home
SVAPAR-188555 All Suggested System has invalid internal communication certificate or invalid text representation of system certificate (show details)
Symptom Configuration
Environment Systems with internal communication certificates or externally signed system certificates
Trigger Automatic creation of internal communication certificate on 9.1 or installation of externally signed system certificate
Workaround Re-install the certificates
9.1.2.0 No Specific Feature
SVAPAR-192363 All Suggested Attempting to enable the encryption recovery key with insufficient permissions may result in an "Array index out of range" error, instead of the expected permissions error. (show details)
Symptom Configuration
Environment All systems at 8.6.2 or higher.
Trigger Attempting to enable the encryption recovery key without sufficient permissions.
Workaround Use a Security Administrator user to enable the recovery key.
9.1.2.0 Graphical User Interface
SVAPAR-192438 All Suggested The GUI does not show information in the "View login Status" and "View FDMI details" panels for directly attached host ports (show details)
Symptom None
Environment Systems with directly attached hosts
Trigger Opening the GUI host port details
Workaround None
9.1.2.0 Graphical User Interface
SVAPAR-192506 All Suggested The configuration GUI may become unresponsive when saving preferences due to a memory leak. (show details)
Symptom Configuration
Environment Empty port_set field
Trigger Trying to save GUI preferences
Workaround No Value
9.1.2.0 Graphical User Interface
SVAPAR-192765 All Suggested The GUI incorrectly prevents restore of volumes within a snapshot, if any other volumes have been added or resized. (show details)
Symptom Configuration
Environment Systems using volume group snapshots
Trigger None
Workaround Use the CLI.
9.1.2.0 Snapshots
SVAPAR-192766 All Suggested When the GUI is used to power down the system, a warning about missing USB encryption keys may be displayed, even if USB encryption is not in use. (show details)
Symptom Configuration
Environment Systems using internal key management for encryption.
Trigger Attempting to power down the system
Workaround None
9.1.2.0 Graphical User Interface
SVAPAR-192781 All Suggested The system may incorrectly show already installed patches as available to install. (show details)
Symptom Configuration
Environment None.
Trigger None.
Workaround None.
9.1.2.0 Security
SVAPAR-192782 All Suggested Adding a system to a FlashSystem Grid using the GUI may fail due to a certificate exchange issue. (show details)
Symptom Configuration
Environment Systems trying to use FlashSystem Grid.
Trigger Adding a new system to a FlashSystem Grid.
Workaround None.
9.1.2.0 FlashSystem Grid, Graphical User Interface
SVAPAR-192785 All Suggested A node canister may fail to upgrade due to an issue in the Fibre Channel adapter firmware. (show details)
Symptom Loss of Redundancy
Environment Systems configured with Fibre Channel adapters.
Trigger Upgrading to 8.5.4, 8.6.0, 8.6.2 or 8.7.0.
Workaround None
9.1.2.0 Fibre Channel, System Update
SVAPAR-193135 All Suggested lsencryption and lsportusb commands may report inconsistent information about the number of validated USB encryption keys. (show details)
Symptom Configuration
Environment Systems using USB encryption
Trigger rekey operations
Workaround Perform a USB encryption rekey
9.1.2.0 Encryption

4. Useful Links

Description Link
  • FlashSystem.ai
    		•
    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
    Concurrent Compatibility and Code Cross Reference
    Software Upgrade Test Utility
    Software Upgrade Planning
    IBM Storage Virtualize IP quorum application requirements