Release Note for systems built with IBM Spectrum Virtualize


This is the release note for the 8.5.4 release and details the issues resolved in 8.5.4.0. 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 28 October 2024.

  1. New Features
  2. Known Issues and Restrictions
  3. Issues Resolved
    1. 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.5.4 release:

2. Known Issues and Restrictions

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

Upgrade to 8.5.1 and higher is not currently supported on systems with compressed volume copies in Data Reduction Pools, to avoid SVAPAR-105430.

On a small proportion of systems, this can cause a node warmstart when specific data patterns are written to compressed volumes. This restriction will be lifted in a future release.

8.5.1.0

IBM Spectrum Virtualize for Public Cloud on Amazon Web Services (AWS) supports policy-based replication on c5.18xlarge platform only

8.5.4.0

IBM Spectrum Virtualize for Public Cloud on Amazon Web Services (AWS) does not support patch installation using 'applysoftware' or 'installsoftware' command line interface

8.5.4.0

IBM Spectrum Virtualize for Public Cloud on Amazon Web Services (AWS) does not support integration with IBM Storage Insights by using Call Home with cloud services

8.5.4.0
The following restrictions were valid but have now been lifted


3. Issues Resolved

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

A release may contain fixes for security issues, fixes for APARs or both. Consult 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-25681 6962203 8.5.4.0

3.1 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
HU02572 All HIPER When controllers running specified code levels with SAS storage are power cycled or rebooted, there is a chance that 56 bytes of data will be incorrectly restored into the cache, leading to undetected data corruption. The system will attempt to flush the cache before an upgrade, so this defect is less likely during an upgrade. (show details) 8.5.4.0 Drives
SVAPAR-90459 All HIPER Possible undetected data corruption or multiple node warmstarts if a Traditional FlashCopy Clone of a volume is created before adding Volume Group Snapshots to the volume (show details) 8.5.4.0 FlashCopy
HU02586 All Critical When deleting a safeguarded copy volume which is related to a restore operation and another related volume is offline, the system may warmstart repeatedly (show details) 8.5.4.0 Safeguarded Copy & Safeguarded Snapshots
SVAPAR-87729 All Critical After a system has logged '3201 : Unable to send to the cloud callhome servers', the system may end up with an inconsistency in the Event Log. This inconsistency can cause a number of symptoms, including node warmstarts (show details) 8.5.4.0 Call Home
SVAPAR-87846 All Critical Node warmstarts with unusual workload pattern on volumes with Policy-based replication (show details) 8.5.4.0 Policy-based Replication
SVAPAR-91111 All Critical USB devices connected to an FS5035 node may be formatted on upgrade to 8.5.3 software (show details) 8.5.4.0 Encryption
HU01782 All High Importance A node warmstart may occur due to a potentially bad SAS hardware component on the system such as a SAS cable, SAS expander or SAS HIC (show details) 8.5.4.0 Drives
HU02539 All High Importance If an IP address is moved to a different port on a node, the old routing table entries do not get refreshed. Therefore, the IP address maybe inaccessible through the new port (show details) 8.5.4.0
HU02558 FS5000, FS5100, FS5200, FS7200, FS7300, FS9100, FS9200, FS9500, SVC High Importance A timing window exists if a node encounters repeated timeouts on I/O compression requests. This can cause two threads to conflict with each other, thereby causing a deadlock condition to occur. (show details) 8.5.4.0 Compression
HU02589 FS5200, FS7200, FS9100, FS9200, FS9500 High Importance Reducing the expiration date of snapshots can cause volume creation and deletion to stall (show details) 8.5.4.0 FlashCopy, Policy-based Replication, Safeguarded Copy & Safeguarded Snapshots
SVAPAR-83290 FS5000 High Importance An issue with the Trusted Platform Module (TPM) in FlashSystem 50xx nodes may cause the TPM to become unresponsive. This can happen after a number of weeks of continuous runtime. (show details) 8.5.4.0
SVAPAR-84305 All High Importance A node may warmstart when attempting to run 'chsnmpserver -community' command without any additional parameter (show details) 8.5.4.0 System Monitoring
SVAPAR-85093 All High Importance Systems that are using Policy-Based Replication may experience node warmstarts, if host I/O consists of large write I/Os with a high queue depth (show details) 8.5.4.0 Policy-based Replication
SVAPAR-85396 FS5000, FS5100, FS5200, FS7200, FS7300, FS9100, FS9200, FS9500 High Importance Replacement Samsung NVME drives may show as unsupported, or they may fail during a firmware upgrade as unsupported, due to a VPD read problem (show details) 8.5.4.0 Drives
SVAPAR-89780 All High Importance A node may warmstart after running the flashcopy command 'stopfcconsistgrp' due to the flashcopy maps in the consistency group being in an invalid state (show details) 8.5.4.0 FlashCopy
SVAPAR-89951 All High Importance A single node warmstart might occur when a volume group with a replication policy switches the replication to cycling mode. (show details) 8.5.4.0 Policy-based Replication
SVAPAR-90395 FS9500, SVC High Importance FS9500 and SV3 might suffer from poor Remote Copy performance due to a lack of internal messaging resources (show details) 8.5.4.0 Global Mirror, Global Mirror With Change Volumes, HyperSwap, Metro Mirror
HU02594 All Suggested Initiating drive firmware update via management user interface for one drive class can prompt all drives to be updated (show details) 8.5.4.0 Drives, System Update
SVAPAR-89296 All Suggested Immediately after upgrade from pre-8.4.0 to 8.4.0 or later, EasyTier may stop promoting hot data to the tier0_flash tier if it contains non-FCM storage. This issue will automatically resolve on the next upgrade (show details) 8.5.4.0 EasyTier
SVAPAR-89781 All Suggested The 'lsportstats' command does not work via the REST API until code level 8.5.4.0 (show details) 8.5.4.0

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
Spectrum Virtualize Family of Products Inter-System Metro Mirror and Global Mirror Compatibility Cross Reference
Software Upgrade Test Utility
Software Upgrade Planning