Release Note for systems built with IBM Storage Virtualize

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

This document was last updated on 27 July 2026.

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

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


2. Known Issues and Restrictions

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

FS7600 and FS9600 may incorrectly log 1008 (temperature sensor failure) or 1694 (enclosure electronics failure) errors, due to a transient sensor read failure.

These errors will automatically fix within 5 minutes of being logged, and can be ignored.

This issue will be resolved in a future software release under SVAPAR-212969.

9.1.2.0

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

9.1.3.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

Expansion of RAID arrays containing any NVMe drives was not supported. This restriction has been lifted for all drives except FCM5 in 9.1.3.0 under SVAPAR-194749.

9.1.2.0


3. Issues Resolved

This release contains all of the fixes included in the 9.1.2.1 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
CVE-2025-67735 7280219 9.1.3.0
CVE-2025-48976 7280368 9.1.3.0
CVE-2025-48988 7280368 9.1.3.0
CVE-2025-49125 7280368 9.1.3.0
CVE-2025-53506 7280368 9.1.3.0
CVE-2025-52434 7280368 9.1.3.0
CVE-2025-55752 7280368 9.1.3.0
CVE-2025-61795 7280368 9.1.3.0

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.3.0 Command Line Interface, Graphical User Interface
SVAPAR-207797 All HIPER Loss of access to data when adding VDisk access to an IO group if the VDisk is mapped to NVMe hosts that are not part of the IO group (show details)
Symptom Loss of Access to Data
Environment Systems with multiple IO groups and NVMe hosts
Trigger Adding VDisk access to an IO group
Workaround

Before adding VDisk access to a new IO group, review the list of hosts with mappings for the VDisk using svcinfo lsvdiskhostmap .

This will return a list of hosts and protocol (SCSI or NVMe). If the VDisk is mapped to NVMe hosts, ensure that all hosts are part of the IO group access should be added to.

svcinfo lshostiogrp can be used to see which IO groups a host is part of. Use this for all hosts with mappings for the volume. If a host is not part of the IO group for which access is being added, use svctask addhostiogrp -iogrp .

Once all hosts have been added to the IO group, addvdiskaccess -iogrp can be run safely.
9.1.3.0 NVMe Hosts
SVAPAR-170709 All Critical A node warmstart may occur if a large volume is frequently being expanded, and snapshots are also being frequently triggered. If both nodes have been running continuously for the same length of time, both nodes may warmstart, causing a loss of access to data. (show details)
Symptom Loss of Access to Data
Environment Volume Group Snapshot
Trigger Creation of frequent snapshots, on a system where a large volume is frequently being expanded (for example, systems with Data Reduction Pools).
Workaround Manually restarting one of the nodes can help avoid both nodes encountering the issue simultaneously.
9.1.3.0 Snapshots
SVAPAR-178710 All Critical Node warmstarts may occur when excessive errors related to IP Security are logged. (show details)
Symptom Single Node Warmstart
Environment IP Security is enabled on an remote copy partnership and errors are being logged due to actions such as certificate or truststore misconfiguration.
Trigger IP Security related errors being logged excessively due to actions such as certificate or truststore misconfiguration.
Workaround Stop the partnership to stop the asserts. Then fix whatever is causing the excessive ip security related errors before starting the partnership again.
9.1.3.0 IP Replication
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.3.0 NVMe Hosts
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.3.0 System Update
SVAPAR-194749 All Critical Expansion of arrays containing NVMe drives is not supported in 9.1.2. (show details)
Symptom Configuration
Environment Systems with DRAID arrays containing NVMe drives
Trigger Attempting to expand an array
Workaround None
9.1.3.0 RAID
SVAPAR-197291 All Critical Adding a disaster recovery link to a partition on an FS5000 system with insufficient memory may trigger repeating node warmstarts. (show details)
Symptom Multiple Node Warmstarts
Environment Low memory systems
Trigger Adding a disaster recovery link to a partition on a system with insufficient memory.
Workaround None
9.1.3.0 Storage Partitions
SVAPAR-197978 All Critical During error recovery for an NVMe host communication problem there may be multiple node warmstarts. (show details)
Symptom Multiple Node Warmstarts
Environment Systems with NVMe hosts
Trigger None
Workaround None
9.1.3.0 NVMe Hosts
SVAPAR-198540 All Critical Multiple node asserts after system inadvertently performs VDisk compression and filesystem analysis on snapshots (show details)
Symptom Multiple Node Warmstarts
Environment System with snapshots
Trigger System inadvertently performs VDisk compression and filesystem analysis on snapshots
Workaround Disable automatic VDisk analysis
9.1.3.0 Snapshots
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.3.0 Reliability Availability Serviceability
SVAPAR-200406 FS5300 Critical On Flashsystem 5300 Ethernet ports 2 and 3 may be unable to bring the link online if using a RJ45 SFP after upgrading to 8.7.0.11, 9.1.0.5, or 9.1.2.x (show details)
Symptom Loss of Access to Data
Environment Flashsystem 5300 using RJ45 SFPs in ports 2 or 3
Trigger Upgrading to 8.7.0.11, 9.1.0.5, or 9.1.2.x
Workaround None
9.1.3.0 IP Replication, iSCSI
SVAPAR-200927 All Critical A node with thin provisioned volumes may warmstart when another node in the cluster reboots or warmstarts. (show details)
Symptom Single Node Warmstart
Environment All systems with thin provisioned volumes
Trigger Reboot other nodes in the cluster
Workaround None
9.1.3.0 Thin Provisioning
SVAPAR-201241 All Critical Loss of access to data when removing a Fibre Channel IO port from a Fibre Channel host portset with auto zoning enabled if the portset is used by an NVMe host (show details)
Symptom Loss of Access to Data
Environment Systems using NVMe hosts
Trigger Removing a Fibre Channel IO port from a Fibre Channel host portset
Workaround Remove all NVMe hosts from the portset before removing the Fibre Channel IO port from the portset
9.1.3.0 NVMe Hosts
SVAPAR-203803 All Critical Adding a snapshot to a volume group may cause multiple node warmstarts, leading to a brief loss of access to data. This can only happen if volume are mirrored, and the snapshot is created in a specific pool. (show details)
Symptom Loss of Access to Data
Environment Systems using volume group snapshots.
Trigger Attempting to add a snapshot to a volume group that contains mirrored volumes while specifying the snapshot pool.
Workaround Avoid specifying the snapshot pool.
9.1.3.0 Snapshots
SVAPAR-203804 All Critical A single-node restart may occur due an I/O timeouts on volumes that are part of policy-based HA. (show details)
Symptom Single Node Warmstart
Environment Systems running policy-based HA.
Trigger None.
Workaround None.
9.1.3.0 Policy-based High availability
SVAPAR-204459 All Critical Array bad blocks may be reported following array expansion with Data Reduction Pools (show details)
Symptom Data Integrity Loss
Environment None
Trigger Expand an array on DRP
Workaround None
9.1.3.0 Distributed RAID
SVAPAR-204466 All Critical Refresh from snapshot may result in multiple node warmstarts and loss of access to data, if volumes have been resized since the snapshot was taken. (show details)
Symptom Loss of Access to Data
Environment Systems using volume group snapshots as well as policy-based replication
Trigger Refresh from snapshot following a volume resize
Workaround None
9.1.3.0 Snapshots
SVAPAR-205746 All Critical Multiple warmstarts may cause a loss of access to data, when moving a volume between volume groups in which high availability is in use, and policy based replication was previously in use. (show details)
Symptom Loss of Access to Data
Environment Systems which performed the following series of operations:

  1. Have two or more volume groups, one which are configured with policy based replication, and one which is not.
  2. While running system code 9.1.0.2 or later, configure policy based high availability to the replicated volume group.
  3. Either remove or retain policy based replication.
  4. Move a volume between a volume group which was originally replicated, and one which was not.
Trigger Moving volumes between groups that have been exposed to the series of events detailed
Workaround Avoid moving volumes between groups on systems which are exposed
9.1.3.0 Policy-based High availability
SVAPAR-210979 FS5300 Critical FS5300 nodes may reboot during upgrade to 8.7.0.12, 9.1.0.6 or 9.1.2.2, due to an issue with ethernet firmware update. (show details)
Symptom Loss of Redundancy
Environment FS5300
Trigger Software upgrade
Workaround None
9.1.3.0 System Update
SVAPAR-216220 All Critical A node reboot or node error 652 may occur on FS5300 or FS5600, due to an issue with the periodic battery health test. (show details)
Symptom Loss of Redundancy
Environment FS5300 and FS5600
Trigger None
Workaround None
9.1.3.0 Reliability Availability Serviceability
SVAPAR-162932 All High Importance A single node warmstart may occur due to a small timing window when automatically performing volume analysis (show details)
Symptom Single Node Warmstart
Environment Systems running 8.7.0 or later
Trigger None
Workaround None
9.1.3.0 Reliability Availability Serviceability
SVAPAR-189513 All High Importance Flashsystem auto renewed SSL certificates created by 8.7 or later software may cause authentication errors. (show details)
Symptom Configuration
Environment Systems with an auto-renewing SSL certificate running 8.7 or later.
Trigger After upgrading to 8.7 or later, if a certificate is auto renewed, authentication errors may happen for clients attempting to connect to the system via the certificate.
Workaround Recreate the certificate.
9.1.3.0 Security
SVAPAR-190941 FS5200, FS7200, FS7300, FS9200, FS9500 High Importance Replacement of an FCM with a downlevel drive can result in a stalled copyback, due to automatic drive firmware update after copyback has started. (show details)
Symptom Loss of Redundancy
Environment Systems running 8.7.0 or later with FCMs
Trigger Replacement of an FCM into an array which is awaiting either copyback or rebuild in place.
Workaround Reseat the FCM or power cycle the slot and return the drive to the array.
9.1.3.0 Drives
SVAPAR-193193 FS9500 High Importance Node warmstart on FS9500 systems with a large configuration including Data Reduction Pools after node startup (show details)
Symptom Single Node Warmstart
Environment FlashSystem 9500 with a large configuration including Data Reduction Pools
Trigger Node warmstart or reboot
Workaround If redundancy permits, remove the node from the system and add it back
9.1.3.0 Data Reduction Pools
SVAPAR-193920 All High Importance If a thin clone volume goes offline (for example due to an out-of-space condition), a timing window may cause I/O delays on the source volume, leading to a node warmstart. (show details)
Symptom Single Node Warmstart
Environment Systems with thin clone volumes.
Trigger None
Workaround Ensure that out-of-space (OOS) conditions are avoided for thin clone volumes.
9.1.3.0 Thin Provisioning
SVAPAR-193993 All High Importance Intensive configuration activity (such as creation of multiple volumes) may cause increased RAID array response times, due to an interaction with Ransomware Threat Detection. This may lead to High Availability being suspended. (show details)
Symptom Performance
Environment Systems with FCM4 or FCM5, and Ransomware Threat Detection enabled
Trigger Intensive configuration activity. eg. Delete a large number of volumes.
Workaround None
9.1.3.0 Distributed RAID, Performance, Policy-based High availability
SVAPAR-198473 All High Importance Flashsystems may stop accepting NVMe over TCP discovery connection requests on a port, if there are many TCP handshake failures due to high packet drops in a network environment. (show details)
Symptom Loss of Access to Data
Environment Flashsystem using NVMe over TCP enviornment.
Trigger Many packet drops in a network environment that can cause TCP handshake failures.
Workaround Reboot the node with the port that stopped accepting discovery connection requests.
9.1.3.0 NVMe Hosts
SVAPAR-199388 All High Importance If multiple REST API clients download performance data files at the same time, the files may contain incorrect information. (show details)
Symptom Configuration
Environment None
Trigger Multiple REST API clients download performance data files at the same time.
Workaround When using REST API clients to download performance data, allow only one client to download at a time.
9.1.3.0 REST API
SVAPAR-202524 All High Importance A single node assert may occur due to a timing window encountered when deleting a large number of volumes associated with FlashCopy or Volume Group Snapshots. (show details)
Symptom Single Node Warmstart
Environment Systems using FlashCopy or Volume Group Snapshots.
Trigger Deleting a large number of volumes associated with FlashCopy or Volume Group Snapshots.
Workaround None.
9.1.3.0 FlashCopy, Snapshots
SVAPAR-204150 All High Importance A single-node warmstart may occur due to a Fibre Channel error recovery issue, leading to an I/O timeout. (show details)
Symptom Single Node Warmstart
Environment Systems with Fibre Channel adapters.
Trigger None.
Workaround None.
9.1.3.0 Fibre Channel
SVAPAR-204185 All High Importance Enabling encryption with the GUI may fail with a request to create key server-specific certicate, on 9.1.0 systems with an externally-signed certificate. (show details)
Symptom Configuration
Environment 9.1.0 systems using encryption with externally-signed certificates
Trigger Enabling encryption using the GUI
Workaround Use the CLI to enable encryption.
9.1.3.0 Encryption
SVAPAR-204264 All High Importance An unexpected node reboot may occur when an large number of invalid requests are sent to the system REST API. (show details)
Symptom Single Node Warmstart
Environment Environments using the REST API.
Trigger Sending a large number of invalid REST API requests
Workaround Determine the source of the invalid REST API requests and stop it.
9.1.3.0 REST API
SVAPAR-204455 All High Importance Repeated node asserts may occur when the number of logins per WWPN per node for a single host exceeds the supported limit of four. (show details)
Symptom Multiple Node Warmstarts
Environment Systems using Fibre Channel host connections.
Trigger The supported limit of host port logins per WWPN per node is exceeded.
Workaround Configure zoning to limit host port logins to a maximum of four logins per WWPN per node.
9.1.3.0 Fibre Channel
SVAPAR-205888 All High Importance A node may go offline on FS50xx systems, requiring a node reseat to recover. This is due to a problem in the kernel crash recovery mechanism. (show details)
Symptom Loss of Redundancy
Environment FS50xx systems
Trigger None
Workaround Reseat the node canister to bring it back online.
9.1.3.0 Reliability Availability Serviceability
SVAPAR-207376 All High Importance The refresh from snapshot view in the GUI may not load if there are snapshots in the system that are not part of any volume group. (show details)
Symptom Configuration
Environment Systems using snapshots.
Trigger Snapshots that are not part of any volume group.
Workaround Use the command-line interface (CLI). If the GUI is needed, remove the snapshots that are not part of any volume group.
9.1.3.0 Graphical User Interface
SVAPAR-210961 All High Importance HA may suspend in a 3-site PBHA+Async DR environment if resuming production on the DR link fails (show details)
Symptom Loss of Redundancy
Environment 3-site PBHA + Async DR
Trigger Resuming production on the DR link while the recovery system has offline volumes or has stopping FlashCopy maps
Workaround Resolve the underlying condition (bring volumes online or consider increasing the FlashCopy clean rate)
9.1.3.0 Policy-based High availability, Policy-based Replication
SVAPAR-212070 All High Importance Paths to HA volumes on the non-active management system remain offline after splitting a partition (show details)
Symptom Loss of Redundancy
Environment PBHA
Trigger Splitting a partition that has no host mappings
Workaround Stop and restart the partnership
9.1.3.0 Policy-based High availability
SVAPAR-212897 All High Importance A single node warmstart may occur during normal I/O request processing, due to a low-probability timing window in the cache component. (show details)
Symptom Single Node Warmstart
Environment None
Trigger None
Workaround None
9.1.3.0 Cache
SVAPAR-133113 All Suggested A system may encounter a single node warmstart due to an internal counter used for a secured IP partnership unexpectedly increasing. (show details)
Symptom Single Node Warmstart
Environment Systems using secured IP partnerships.
Trigger None
Workaround None
9.1.3.0 IP Replication
SVAPAR-189195 All Suggested GUI may fail during snap collection due to an out-of-memory condition. (show details)
Symptom Configuration
Environment None
Trigger Collecting a snap
Workaround None
9.1.3.0 Support Data Collection
SVAPAR-193296 All Suggested After upgrade to 9.1.0 or later, volumes using asynchronous DR replication in a partition may not correctly transition to the online state. (show details)
Symptom Configuration
Environment Systems using asynchronous DR replication within a partition
Trigger Upgrade from pre-9.1.0 to 9.1.0 or later
Workaround Making the recovery copy independent, and then restarting replication will update the recovery volumes status.
9.1.3.0 Policy-based High availability, Policy-based Replication
SVAPAR-193365 All Suggested Syslog entries containing non-UTF8 characters may be sent to syslog servers, causing log decoding exceptions and dropped events (show details)
Symptom Error in Error Log
Environment Systems running 9.1.0 onwards with syslog enabled
Trigger None
Workaround None
9.1.3.0 System Monitoring
SVAPAR-198600 SVC Suggested The GUI may not allow a volume copy to be added, on systems with stretched topology. (show details)
Symptom Configuration
Environment Systems running 9.1.0 onwards with stretched topology
Trigger Try to add a volume copy to a vdisk
Workaround Instead use the command-Line Interface
9.1.3.0 Graphical User Interface
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.3.0 Drives
SVAPAR-199481 All Suggested Code level 9.1.0 GUI does not sort host cluster list by name. (show details)
Symptom Configuration
Environment Code level 9.1.0.x
Trigger Click on "Name" column header in the Host Cluster view.
Workaround None
9.1.3.0 Graphical User Interface
SVAPAR-199483 All Suggested Code level 9.1.0 GUI has a "Modify shared volume mappings" action for host clusters. This option only permits shared volume mappings to be added. There is a separate "Remove volume mappings" action. (show details)
Symptom Configuration
Environment Code level 9.1.0
Trigger Use Host Clusters --> "Modify shared volume mappings" to remove shared volume mappings.
Workaround Use the "Remove volume mappings" action for the host cluster.
9.1.3.0 Graphical User Interface
SVAPAR-199486 All Suggested When attempting to map volumes to a host cluster, the following message is displayed when no volumes are available for mapping: "No volumes found. No volumes are currently mapped to the host cluster" (show details)
Symptom Configuration
Environment Code level 9.1.0
Trigger Map volumes to host cluster.
Workaround Ignore the second sentence in the message ("No volumes are currently mapped to the host cluster").
9.1.3.0 Graphical User Interface
SVAPAR-199516 All Suggested Selecting an item in the GUI may cause another object's details to be automatically collapsed, or a selected radio button to be cleared. (show details)
Symptom Configuration
Environment Code level 9.1.0.
Trigger Expand an object to reveal the details. eg. Expand parent pool to reveal child pools. Start a task that requires selecting a single object from a list. eg. Migrating a vdisk copy will require the destination pool to be selected from a list.
Workaround None.
9.1.3.0 Graphical User Interface
SVAPAR-199679 All Suggested The GUI does not allow users to add an existing volume to a volume group within an ownership group. The "Add existing volumes" GUI panel will report "No items found." (show details)
Symptom Configuration
Environment Ownership groups. Volume Groups
Trigger Ownership group user attempts to add an existing volume to a volume group within the ownership group.
Workaround Perform the action via the CLI.
9.1.3.0 Graphical User Interface
SVAPAR-202056 All Suggested Due to a timing window during upgrade from pre-9.1.0.0 to 9.1.0.3 or later releases, the system may have an invalid internal communication certificate. (show details)
Symptom Configuration
Environment Systems running 9.1.0.3 or later releases with internal communication certificate.
Trigger Automatic creation of internal communication certificate on 9.1.0.3 or later releases.
Workaround Re-install the certificate.
9.1.3.0 Policy-based High availability, Policy-based Replication
SVAPAR-204146 All Suggested A system update may fail to start due to a node with an invalid patching state. (show details)
Symptom Configuration
Environment All
Trigger Starting an upgrade
Workaround None
9.1.3.0 System Update
SVAPAR-204219 All Suggested HTTP headers returned by the REST API may contain unexpected values for X-Frame-Options and Content-Security-Policy (show details)
Symptom Configuration
Environment None
Trigger None
Workaround None
9.1.3.0 REST API
SVAPAR-204230 All Suggested A node warmstart may occur on systems using policy-based replication, during recovery from both nodes in an I/O group being offline at the same time. (show details)
Symptom Multiple Node Warmstarts
Environment Systems using policy-based replication at 8.7.0 or later.
Trigger A hardware or software issue which causes both nodes to be offline at the same time.
Workaround No Value
9.1.3.0
SVAPAR-204252 All Suggested Node warmstart can occur immediately after node startup, if the node has fibre channel adapters. (show details)
Symptom Single Node Warmstart
Environment Systems with fibre channel adaptes
Trigger Node startup
Workaround No work around. The issue happens rarely and when it does the warmstart clears the error.
9.1.3.0 Fibre Channel
SVAPAR-204284 All Suggested The GUI may show an HTTP 500 error when trying to log in using multi-factor authentication with IBM Security Verify (show details)
Symptom Configuration
Environment Systems using IBM Security Verify
Trigger Using MFA to access to GUI
Workaround Append "gui#dashboard" to the URL, for example https://<cluster_Name >/gui#dashboard.
9.1.3.0 Graphical User Interface
SVAPAR-204460 All Suggested Drive upgrade may fail, if in an array with slow-write priority set to the non-default "redundancy" value. (show details)
Symptom Error in Error Log
Environment RAID arrays with slow-write priority set to redundancy.
Trigger Drive upgrade
Workaround Use "charray -slowwritepriority latency <mdisk> to set array to latency, and firmware update should download and complete as intended.
9.1.3.0 Drives
SVAPAR-204464 All Suggested Direct-attached 16Gb Qlogic host adapters may auto-negotiate a speed of 8Gb (show details)
Symptom Error in Error Log
Environment Systems with Fibre Channel adapters.
Trigger None
Workaround None
9.1.3.0 Fibre Channel
SVAPAR-204626 All Suggested A node warmstart may occur on a system with 4 port 32Gb FC adapters, if the adapter or SFPs are running at high temperature. (show details)
Symptom Single Node Warmstart
Environment Systems with 4 port 32Gb FC adapters
Trigger High adapter or SFP temperature
Workaround No Value
9.1.3.0 Fibre Channel
SVAPAR-204678 All Suggested When using 3-site HA+DR, last_write_time may not be cleared after exiting recovery mode (show details)
Symptom Configuration
Environment Systems using HA+DR
Trigger Exiting recovery mode
Workaround None
9.1.3.0 Policy-based High availability
SVAPAR-205254 All Suggested Volumegroup synchronisation progress is not displayed correctly in some configurations with 3-site high availability + disaster recovery (show details)
Symptom Configuration
Environment HA+DR configurations
Trigger High availability or asynchronous disaster recovery volumegroup is synchronising
Workaround None
9.1.3.0 Policy-based High availability, Policy-based Replication
SVAPAR-205918 All Suggested On systems running 8.7.0.0 and above "lssystem" command output lists tier0_flash capacity as 0, even if there is tier0 flash drives present (show details)
Symptom Configuration
Environment System with Tier0 flash drives
Trigger Run "lssystem" command
Workaround None
9.1.3.0 Command Line Interface
SVAPAR-208937 All Suggested The Remove volume mappings view in the GUI may fail to load for host clusters that have replication recovery volumes mapped. (show details)
Symptom Configuration
Environment Systems using policy-based replication and host clusters.
Trigger Mapping policy-based replication recovery volumes to host clusters.
Workaround Use the CLI to remove the volume mappings.
9.1.3.0 Graphical User Interface, Host Cluster
SVAPAR-209638 All Suggested The volumes view in the GUI may show an incorrect state for volume copy ID 1. (show details)
Symptom Configuration
Environment Code level 9.1.0.0 or higher. Mirrored volumes.
Trigger Volume copy 1 state is different from volume copy 0 state.
Workaround Use the volume copy detailed view or the CLI.
9.1.3.0 Graphical User Interface
SVAPAR-209674 All Suggested The GUI does not allow a user to change the SCSI ID, when creating a volume mapping from the host cluster view. (show details)
Symptom Configuration
Environment 9.1.0 systems with host clusters
Trigger Add volume mapping from host cluster view.
Workaround Use the CLI
9.1.3.0 Host Cluster
SVAPAR-209691 All Suggested Removing a host from a host cluster does not offer an option to keep the mappings in the 9.1.0 GUI. (show details)
Symptom Configuration
Environment 9.1.0 Host Clusters
Trigger Remove a host from a host cluster via the GUI.
Workaround Use the CLI.
9.1.3.0 Host Cluster
SVAPAR-212821 All Suggested Attempting to change the amount of snapshot paging bitmap allowance may cause a loss of access to data, on systems which do not support this command (show details)
Symptom Loss of Access to Data
Environment No Value
Trigger Attempting to change the amount of snapshot paging bitmap allowance, on systems which do not support this command
Workaround None
9.1.3.0 Snapshots
SVAPAR-212842 All Suggested If a USB device is inserted while the GUI USB panel is visible, the list may not be updated until the page is manually refreshed. (show details)
Symptom Configuration
Environment None
Trigger Inserting a USB device while the configure USB panel is open.
Workaround Refresh the GUI page.
9.1.3.0 Graphical User Interface
SVAPAR-212846 All Suggested I/O requests to a RAID array may be delayed longer than expected during a software upgrade. (show details)
Symptom Performance
Environment Systems on 8.7.0 or later software
Trigger Software upgrade.
Workaround None
9.1.3.0 RAID
SVAPAR-212853 All Suggested The "satask downloadsoftware -abort" command may fail to abort the download request. (show details)
Symptom Configuration
Environment None
Trigger Executing satask downloadsoftware -abort when the system is in "waiting for download" state.
Workaround Warmstart the configuration node
9.1.3.0 Graphical User Interface
SVAPAR-212854 All Suggested The Preferred Release recommendation in the Management GUI (Settings > System > Update System), may incorrectly suggest a software release older than the currently installed version. (show details)
Symptom None
Environment Systems on 8.7.0.10 or later.
Trigger None
Workaround None
9.1.3.0 System Update
SVAPAR-212864 All Suggested Systems running 9.1.2 software may generate invalid performance statistics files, preventing successful processing by performance tools. (show details)
Symptom None
Environment Systems on 9.1.2 software.
Trigger None
Workaround None
9.1.3.0 Deduplication
SVAPAR-212865 All Suggested The System Update page in the Management GUI may be displayed incorrectly when the GUI language is set to German. (show details)
Symptom Configuration
Environment Management GUI language is set to German.
Trigger Upgrade to 9.1.1
Workaround Change the language to any language other than German
9.1.3.0 System Update
SVAPAR-212899 All Suggested In lsportfc view, the port_max_speed field may not be populated (report as 0gb) depending on the adapter location, even though the adapter is operating correctly. (show details)
Symptom Configuration
Environment Systems with specific hardware configurations where platform port mapping differs from logical FC port mapping
Trigger None
Workaround None
9.1.3.0 Command Line Interface

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
    Software Upgrade Test Utility
    Software Upgrade Planning
    IBM Storage Virtualize IP quorum application requirements