Release Note for systems built with IBM Storage Virtualize


This is the release note for the 8.6.2 release and details the issues resolved between 8.6.2.0 and 8.6.2.1. This document will be updated with additional information whenever a PTF is released.

Note: This release is a Non-Long Term Support (Non-LTS) release. Non-LTS code levels will not receive regular fix packs. Fixes for issues introduced in a Non-LTS release will be delivered in a subsequent Non-LTS or LTS release. If issues are encountered the only resolution is likely to be upgrade to a later LTS or Non-LTS release.

This document was last updated on 15 January 2025.

  1. New Features
  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 Update Matrices in the Useful Links section.


1. New Features

The following new features have been introduced in the 8.6.2.1 release: The following new features have been introduced in the 8.6.2 release:

2. Known Issues and Restrictions

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

The three site orchestrator is not compatible with the new SSH security level 4.This will be resolved in a future release of the orchestrator.

8.6.2.1

Removing a vVol child pool is currently not supported. Contact IBM Support if you have a requirement to delete a vVol child pool.

8.6.2.0

Due to a known issue, array expansion of DRAID1 arrays is not supported on this code level.

8.6.2.0

VMware Virtual Volumes (vVols) are not supported using IBM Spectrum Connect on 8.6.1 or later.

Systems using Spectrum Connect must migrate to use the embedded VASA provider on version 8.6.0 before upgrading to 8.6.1 or later.

8.6.1.0

Systems using VMware Virtual Volumes (vVols) may require reconfiguration before updating to 8.6.1 or later.

Refer to Updating to Storage Virtualize 8.6.1 or later using VMware Virtual Volumes (vVols)

8.6.1.0

All IO groups must be configured with FC target port mode set to 'enabled' before upgrading to 8.6.1.0 or later.

Enabling the FC target port mode configures multiple WWPNs per port (using the Fibre Channel NPIV technology), and separates the host traffic from all other traffic on different WWPNs

Important: Changing this setting is likely to require changes to zoning, and rescanning LUNs in all applications.

The product documentation contains topics called 'Enabling NPIV on an existing system' and 'Enabling NPIV on a new system' which contains details about how to make the changes.

8.6.1.0

IBM i is not supported as a host operating system when connected using directly attached Fibre Channel to FlashSystem or SAN Volume Controller systems running 8.6.1.0 or later versions.

IBM i is supported as a host operating system when connected to FlashSystem or SAN Volume Controller systems via a Fibre Channel switch

8.6.1.0

8.6.1 removes support for the CIM protocol. Applications that connect using the CIM protocol should be upgraded to use a supported interface, such as the REST interface.

IBM recommends that any product teams currently using CIM protocol comment on this Idea and IBM will contact you with more details about how to use a supported interface.

8.6.1.0

Systems using 3-site orchestrator cannot upgrade to 8.7.0.0

8.6.1.0

The following restrictions were valid but have now been lifted

Remote Support Assistance (RSA) cannot be enabled on FS9500 systems with MTM 4983-AH8. Attempting to enable RSA will fail with: CMMVC8292E The command failed because the feature is not supported on this platform.

This restriction has been lifted by SVAPAR-106693

8.6.0.0

Upgrading to 8.5.1 or higher was not supported on systems with Data Reduction Pools.

This restriction has been lifted by SVAPAR-105430

8.6.2.0

8.6.1 introduced support for policy-based High Availability, using two storage systems. Asynchronous policy-based Replication is not supported in this release and systems requiring this feature should use 8.6.0.

8.6.2.0

Mapping more than 512 volumes to a single host might fail with CMMVC5876E after upgrading to 8.6.1.0, even if the configuration is supported

8.6.2.0

Systems with RoCE adapters could not configure an MTU of greater than 1500 with 8.6.0 and 8.6.1 software.

8.6.2.0

3. Issues Resolved

This release contains all of the fixes included in the 8.6.0.0 and 8.6.1.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
CVE-2023-48795 7154643 8.6.2.1
CVE-2023-22081 7114770 8.6.2.0
CVE-2023-22067 7114770 8.6.2.0
CVE-2023-5676 7114770 8.6.2.0
CVE-2023-43042 7064976 8.6.2.0
CVE-2023-46589 7114769 8.6.2.0
CVE-2023-45648 7114769 8.6.2.0
CVE-2023-42795 7114769 8.6.2.0
CVE-2024-21733 7114769 8.6.2.0
CVE-2023-47700 7114767 8.6.2.0
CVE-2023-34396 7065010 8.6.2.0
CVE-2023-50164 7114768 8.6.2.0
CVE-2023-21930 7065011 8.6.2.0
CVE-2023-21937 7065011 8.6.2.0
CVE-2023-21938 7065011 8.6.2.0

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-117738 All HIPER The configuration node may go offline with node error 565, due to a full /tmp partition on the boot drive. (show details) 8.6.2.1 Reliability Availability Serviceability
SVAPAR-105861 SVC HIPER A cluster recovery may occur when an attempt is made to create a mirrored snapshot with insufficient volume mirroring bitmap space in the IO group (show details) 8.6.2.0 FlashCopy, Safeguarded Copy & Safeguarded Snapshots, Volume Mirroring
SVAPAR-104533 All Critical Systems that encounter multiple node asserts, followed by a system T3 recovery, may experience errors repairing Data Reduction Pools (show details) 8.6.2.0 Data Reduction Pools
SVAPAR-105430 All Critical When hardware compression is suspended mid IO to a DRP compressed volume, it may cause the IO to hang until an internal timeout is hit and a node warmstarts. (show details) 8.6.2.0 Compression, Data Reduction Pools
SVAPAR-107270 All Critical If an upgrade from a level below 8.6.x, to 8.6.0 or 8.6.1 commits, whilst FlashCopy is preparing to start a map, a bad state is introduced that prevents the FlashCopy maps from starting. (show details) 8.6.2.0 Global Mirror With Change Volumes, Policy-based Replication
SVAPAR-107547 All Critical If there are more than 64 logins to a single Fibre Channel port, and a switch zoning change is made, a single node warmstart may occur. (show details) 8.6.2.0 Reliability Availability Serviceability
SVAPAR-107734 All Critical When issuing IO to an incremental fcmap volume that is in a stopped state, but has recently been expanded, and it also has a partner fcmap, may cause the nodes to go into a restart. (show details) 8.6.2.0 FlashCopy
SVAPAR-110735 All Critical Additional policing has been introduced to ensure that FlashCopy target volumes are not used with policy-based replication. Commands 'chvolumegroup -replicationpolicy' will fail if any volume in the group is the target of a FlashCopy map. 'chvdisk -volumegroup' will fail if the volume is the target of a FlashCopy map, and the volume group has a replication policy. (show details) 8.6.2.0 FlashCopy, Policy-based Replication
SVAPAR-111257 All Critical If many drive firmware upgrades are performed in quick succession, multiple nodes may go offline with node error 565 due to a full boot drive. (show details) 8.6.2.0 Drives
SVAPAR-111705 All Critical If a Volume Group Snapshot fails and the system has 'snapshotpreserveparent' set to 'yes', this may trigger multiple node warmstarts. (show details) 8.6.2.0 FlashCopy
SVAPAR-111994 All Critical Certain writes to deduplicated and compressed DRP vdisks may return a mismatch, leading to a DRP pool going offline. (show details) 8.6.2.0 Compression, Data Reduction Pools, Deduplication
SVAPAR-112007 All Critical Running the 'chsystemlimits' command with no parameters can cause multiple node warmstarts. (show details) 8.6.2.0 Command Line Interface
SVAPAR-112107 FS9500, SVC Critical There is an issue that affects PSU firmware upgrades in FS9500 and SV3 systems that can cause an outage. This happens when one PSU fails to download the firmware and another PSU starts to download the firmware. It is a very rare timing window that can be triggered if two PSUs are reseated close in time during the firmware upgrade process. (show details) 8.6.2.0 System Update
SVAPAR-93709 FS9500 Critical A problem with NVMe drives may impact node to node communication over the PCIe bus. This may lead to a temporary array offline. (show details) 8.6.2.0 Drives, RAID
SVAPAR-104159 All High Importance Nodes configured with 32GB or less of RAM, and specific 25Gb ethernet adapters, under some circumstances may run out of memory. This can cause a single node warmstart. (show details) 8.6.2.0 Reliability Availability Serviceability
SVAPAR-104250 All High Importance There is an issue whereby NVMe CaW (Compare and Write) commands can incorrectly go into an invalid state, thereby causing the node to assert to clear the bad condition (show details) 8.6.2.0 Hosts, NVMe
SVAPAR-105727 All High Importance An upgrade within the 8.5.0 release stream from 8.5.0.5 or below, to 8.5.0.6 or above, can cause an assert of down-level nodes during the upgrade, if volume mirroring is heavily utilised (show details) 8.6.2.0 Volume Mirroring
SVAPAR-106874 FS5200, FS7200, FS7300, FS9100, FS9200, FS9500, SVC High Importance A timing window may cause a single node warmstart, while recording debug information about a replicated host write. This can only happen on a system using Policy Based Replication. (show details) 8.6.2.0 Policy-based Replication
SVAPAR-107815 All High Importance There is an issue between 3-Site, whilst adding snapshots on the auxfar site, that causes the node to warmstart (show details) 8.6.2.0 3-Site using HyperSwap or Metro Mirror
SVAPAR-107866 & SVAPAR-110742 All High Importance A System is unable to send email to email server because the password contains a hash '#' character. (show details) 8.6.2.0
SVAPAR-108715 All High Importance The Service Assistant GUI on 8.5.0.0 and above incorrectly performs actions on the local node instead of the node selected in the GUI. (show details) 8.6.2.0 Graphical User Interface
SVAPAR-108831 FS9500, SVC High Importance FS9500 and SV3 nodes may not boot with the minimum configuration consisting of at least 2 DIMMS. (show details) 8.6.2.0 Reliability Availability Serviceability
SVAPAR-110426 All High Importance When a security admin other than superuser runs security patch related commands 'lspatch' and 'lssystempatches' this can cause a node to warmstart (show details) 8.6.2.0 Security
SVAPAR-110743 All High Importance Email becoming stuck in the mail queue caused a delay in the 'upgrade commit was finished' message being sent, therefore causing 3 out of 4 nodes to warmstart, and then rejoin the cluster automatically within less than three minutes. (show details) 8.6.2.0 System Update
SVAPAR-110765 All High Importance In a 3-Site configuration, the Config node can be lost if the 'stopfcmap or 'stopfcconsistgrp ' commands are run with the '-force' parameter (show details) 8.6.2.0 3-Site using HyperSwap or Metro Mirror
SVAPAR-110819 & SVAPAR-113122 All High Importance A single-node warmstart may occur when a Fibre Channel port is disconnected from one fabric, and added to another. This is caused by a timing window in the FDMI discovery process. (show details) 8.6.2.0 Fibre Channel
SVAPAR-111996 FS9500, SVC High Importance After upgrading to a level which contains new battery firmware, the battery may be offline after the upgrade. (show details) 8.6.2.0 Reliability Availability Serviceability, System Update
SVAPAR-112119 All High Importance Volumes can go offline due to out of space issues. This can cause the node to warmstart. (show details) 8.6.2.0
SVAPAR-112203 All High Importance A node warmstart may occur when removing a volume from a volume group which uses policy-based Replication. (show details) 8.6.2.0 Policy-based Replication
SVAPAR-112525 All High Importance A node assert can occur due to a resource allocation issue in a small timing window when using Remote Copy (show details) 8.6.2.0 Global Mirror, Global Mirror With Change Volumes, HyperSwap, Metro Mirror
SVAPAR-91357 FS5000, FS5100, FS5200, FS7200, FS7300, FS9100, FS9200, FS9500 High Importance Cancelling a drive software upgrade may cause multiple node warmstarts, due to a timing window. (show details) 8.6.2.0 Drives
SVAPAR-99175 All High Importance A node may warmstart due to an invalid queuing mechanism in cache. This can cause IO in cache to be in the same processing queue more than once. (show details) 8.6.2.0 Cache
SVAPAR-99354 All High Importance Missing policing in the 'startfcconsistgrp' command for volumes using volume group snapshots, resulting in node warmstarts when creating a new volume group snapshot (show details) 8.6.2.0 FlashCopy
SVAPAR-100924 FS9500, SVC Suggested After the battery firmware is updated, either using the utility or by upgrading to a version with newer firmware, the battery LED may be falsely illuminated. (show details) 8.6.2.0
SVAPAR-102382 All Suggested Fibre Channel Read Diagnostic Parameters (RDP) indicates that a short wave SFP is installed when infact an long wave SFP is installed. (show details) 8.6.2.0 System Monitoring
SVAPAR-106693 FS9500 Suggested Remote Support Assistance (RSA) cannot be enabled on FS9500 systems with MTM 4983-AH8 (show details) 8.6.2.0 Support Remote Assist
SVAPAR-107558 All Suggested A Volume Group Snapshot (VGS) trigger may collide with a GMCV or Policy based Replication cycle causing the VGS trigger to fail. (show details) 8.6.2.0 FlashCopy, Global Mirror With Change Volumes, Policy-based Replication
SVAPAR-107733 All Suggested The 'mksnmpserver' command fails with 'CMMVC5711E [####] is not valid data' if auth passphrase contains special characters, such as '!' (show details) 8.6.2.0
SVAPAR-107852 All Suggested A Policy-Based High Availability node may warmstart during IP quorum disconnect and reconnect operations. (show details) 8.6.2.0 IP Quorum
SVAPAR-108469 All Suggested A single node warmstart may occur on nodes configure to use a secured IP partnership (show details) 8.6.2.0 IP Replication
SVAPAR-108476 All Suggested Remote users with public SSH keys configured cannot failback to password authentication. (show details) 8.6.2.0 Security
SVAPAR-108551 All Suggested An expired token in the GUI file upload process can cause the upgrade to not start automatically after the file is successfully uploaded. (show details) 8.6.2.0 System Update
SVAPAR-109289 All Suggested Buffer overflow may occur when handling the maximum length of 55 characters for either Multi-Factor Authentication (MFA) or Single Sign On (SSO) client secrets (show details) 8.6.2.0 Backend Storage
SVAPAR-110059 All Suggested When using Storage Insights without a data collector, an attempt to collect a snap using Storage Insights may fail. (show details) 8.6.2.0 Support Data Collection
SVAPAR-110745 All Suggested Policy-based Replication (PBR) snapshots and Change Volumes are factored into the preferred node assignment. This can lead to a perceived imbalance of the distribution of preferred node assignments. (show details) 8.6.2.0 Policy-based Replication
SVAPAR-110749 All Suggested There is an issue when configuring volumes using the wizard, the underlying command that is called is the 'mkvolume' command rather than the previous 'mkvdisk' command. With 'mkvdisk' it was possible to format the volumes, whereas with 'mkvolume' it is not possible (show details) 8.6.2.0
SVAPAR-111021 All Suggested Unable to load resource page in GUI if the IO group ID:0 does not have any nodes. (show details) 8.6.2.0 System Monitoring
SVAPAR-111187 All Suggested There is an issue if the browser language is set to French, that can cause the SNMP server creation wizard not to be displayed. (show details) 8.6.2.0 System Monitoring
SVAPAR-111239 All Suggested In rare situations it is possible for a node running Global Mirror with Change Volumes (GMCV) to assert (show details) 8.6.2.0 Global Mirror With Change Volumes
SVAPAR-111989 All Suggested Downloading software with a Fix ID longer than 64 characters fails with an error (show details) 8.6.2.0 Support Remote Assist
SVAPAR-111991 All Suggested Attempting to create a truststore fails with a CMMVC5711E error if the certificate file does not end with a newline character (show details) 8.6.2.0 IP Replication, Policy-based Replication, vVols
SVAPAR-111992 All Suggested Unable to configure policy-based Replication using the GUI, if truststore contains blank lines or CRLF line endings (show details) 8.6.2.0 Graphical User Interface, Policy-based Replication
SVAPAR-112243 All Suggested Prior to 8.4.0 NTP was used. After 8.4.0 this was changed to 'chronyd'. When upgrading from a lower level to 8.4 or higher, systems may experience compatibility issues. (show details) 8.6.2.0
SVAPAR-112711 All Suggested IBM Storage Virtualize user interface code will not respond to a malformed HTTP POST with expected HTTP 401 message. (show details) 8.6.2.0 Graphical User Interface
SVAPAR-114081 All Suggested The lsfabric command may show FC port logins which no longer exist. In large environments with many devices attached to the SAN, this may result in an incorrect 1800 error being reported, indicating that a node has too many logins. (show details) 8.6.2.0 Reliability Availability Serviceability
SVAPAR-96952 All Suggested A single node warmstart may occur when updating the login counts associated with a backend controller. (show details) 8.6.2.0 Backend Storage

4. Useful Links

Description Link
Product Documentation
Update Matrices, including detailed build version
Support Information pages providing links to the following information:
  • Interoperability information
  • Product documentation
  • Limitations and restrictions, including maximum configuration limits
Storage Virtualize Family of Products Inter-System Metro Mirror and Global Mirror Compatibility Cross Reference
Software Upgrade Test Utility
Software Upgrade Planning