Release Note for V9000 Family Block Storage Products


This release note applies to the following systems: This is the release note for the 7.7 release and details the issues resolved in all Program Temporary Fixes (PTFs) between 7.7.0.0 and 7.7.0.5. This document will be updated with additional information whenever a PTF is released.

This document was last updated on 20 August 2020.

  1. New Features
  2. Known Issues and Restrictions
  3. Issues Resolved
    1. Security Issues Resolved
    2. APARs Resolved
  4. Supported upgrade paths
  5. 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 7.7.0.0 release:

2. Known Issues and Restrictions

Details Introduced

Systems using Internet Explorer 11 may receive an erroneous "The software version is not supported" message when viewing the "Update System" panel in the GUI. Internet Explorer 10 and Firefox do not experience this issue.

7.4.0.0

If using IP replication, please review the set of restrictions published in the Configuration Limits and Restrictions document for your product.

7.1.0.0

Windows 2008 host paths may become unavailable following a node replacement procedure.

Refer to this flash for more information on this restriction

6.4.0.0

Intra-System Global Mirror not supported.

Refer to this flash for more information on this restriction

6.1.0.0

Host Disconnects Using VMware vSphere 5.5.0 Update 2 and vSphere 6.0.

Refer to this flash for more information

n/a

If an update stalls or fails then Contact IBM Support for Further Assistance

n/a

3. Issues Resolved

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

A release may contain fixes for security issues, fixes for APARs/FLASHs 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-2016-5385 ssg1S1009581 7.7.0.4
CVE-2016-5386 ssg1S1009581 7.7.0.4
CVE-2016-5387 ssg1S1009581 7.7.0.4
CVE-2016-5388 ssg1S1009581 7.7.0.4
CVE-2016-4461 ssg1S1010883 7.7.0.3
CVE-2016-4430 ssg1S1009282 7.7.0.3
CVE-2016-4431 ssg1S1009282 7.7.0.3
CVE-2016-4433 ssg1S1009282 7.7.0.3
CVE-2016-4436 ssg1S1009282 7.7.0.3
CVE-2016-3092 ssg1S1009284 7.7.0.3
CVE-2017-6056 ssg1S1010022 7.7.0.0
CVE-2016-1978 ssg1S1009280 7.7.0.0
CVE-2015-5345 ssg1S1005846 7.7.0.0
CVE-2015-5346 ssg1S1005846 7.7.0.0
CVE-2015-5351 ssg1S1005846 7.7.0.0
CVE-2016-0706 ssg1S1005846 7.7.0.0
CVE-2016-0714 ssg1S1005846 7.7.0.0
CVE-2016-0763 ssg1S1005846 7.7.0.0
CVE-2015-5174 ssg1S1005846 7.7.0.0
CVE-2016-0797 ssg1S1005848 7.7.0.0
CVE-2016-0705 ssg1S1005848 7.7.0.0
CVE-2016-0785 ssg1S1005849 7.7.0.0
CVE-2016-2162 ssg1S1005849 7.7.0.0

3.2 APARs and Flashes Resolved

Reference Severity Description Resolved in Feature Tags
HU01193 S1 HIPER (Highly Pervasive): A drive failure whilst an array rebuild is in progress can lead to both nodes in an I/O group warmstarting 7.7.0.5 Distributed RAID
HU01447 S1 HIPER (Highly Pervasive): The management of FlashCopy grains during a restore process can miss some IOs 7.7.0.5 FlashCopy
HU01340 S1 A port translation issue between v7.5 or earlier and v7.7.0 or later requires a T2 recovery to complete an upgrade 7.7.0.5 System Update
HU01109 S2 Multiple nodes can experience a lease expiry when a FC port is having communications issues 7.7.0.5
HU01184 S2 When removing multiple MDisks a T2 may occur 7.7.0.5
HU01185 S2 iSCSI target closes connection when there is a mismatch in sequence number 7.7.0.5 iSCSI
HU01219 S2 Single node warmstart due to an issue in the handling of ECC errors within 16G HBA firmware 7.7.0.5
HU01221 S2 Node warmstarts due to an issue with the state machine transition in 16Gb HBA firmware 7.7.0.5
HU01223 S2 The handling of a rebooted node's return to the cluster can occasionally become delayed resulting in a stoppage of inter cluster relationships 7.7.0.5 Metro Mirror
HU01226 S2 Changing max replication delay from the default to a small non-zero number can cause hung IOs leading to multiple node warmstarts and a loss of access 7.7.0.5 Global Mirror
IT16012 S2 Internal node boot drive RAID scrub process at 1am every Sunday can impact system performance 7.7.0.5 Performance
HU01017 S3 The result of CLI commands are sometimes not promptly presented in the GUI 7.7.0.5 Graphical User Interface
HU01050 S3 DRAID rebuild incorrectly reports event code 988300 7.7.0.5 Distributed RAID
HU01187 S3 Circumstances can arise where more than one array rebuild operation can share the same CPU core resulting in extended completion times 7.7.0.5
HU01198 S3 Running the Comprestimator svctask analyzevdiskbysystem command may cause the config node to warmstart 7.7.0.5 Comprestimator
HU01213 S3 The LDAP password is visible in the auditlog 7.7.0.5 LDAP
HU01214 S3 GUI and snap missing EasyTier heat map information 7.7.0.5 Support Data Collection
HU01227 S3 High volumes of events may cause the email notifications to become stalled 7.7.0.5 System Monitoring
HU01234 S3 After upgrade to 7.6 or later iSCSI hosts may incorrectly be shown as offline in the CLI 7.7.0.5 iSCSI
HU01247 S3 When a FlashCopy consistency group is stopped more than once in rapid succession a node warmstart may result 7.7.0.5 FlashCopy
HU01269 S3 A rare timing conflict between two process may lead to a node warmstart 7.7.0.5
HU01292 S3 Under some circumstances the re-calculation of grains to clean can take too long after a "FlashCopy done" event has been sent resulting in a node warmstart 7.7.0.5 FlashCopy
HU01374 S3 Where an issue with Global Mirror causes excessive I/O delay, a timeout may not function resulting in a node warmstart 7.7.0.5 Global Mirror
HU01399 S3 For certain config nodes the CLI Help commands may not work 7.7.0.5 Command Line Interface
HU01405 S3 SSD drives with vendor ID IBM-C050 and IBM-C051 are showing up as not being supported 7.7.0.5
IT16337 S2 Hardware offloading in four-port 16G FC adapters has introduced a deadlock condition that causes many driver commands to time out leading to a node warmstart. For more details refer to the following Flash 7.7.0.4
HU01258 S3 A compressed volume copy will result in an unexpected 1862 message when site/node fails over in a stretched cluster configuration 7.7.0.4 Compression
IT17102 S3 Where the maximum number of I/O requests for a FC port has been exceeded, if a SCSI command, with an unsupported opcode, is received from a host then the node may warmstart 7.7.0.4
HU00271 S2 An extremely rare timing window condition in the way GM handles write sequencing may cause multiple node warmstarts 7.7.0.3 Global Mirror
HU01141 S2 Node warmstart, possibly due to a network problem, when a CLI mkippartnership is issued. This may lead to loss of the config node, requiring a T2 recovery 7.7.0.3 IP Replication
HU01182 S2 Node warmstart due to 16Gb HBA firmware receiving an invalid SCSI TUR command 7.7.0.3
HU01194 S3 A single node warmstart may occur if CLI commands are received from the VASA provider in very rapid succession. This is caused by a deadlock condition which prevents the subsequent CLI command from completing 7.7.0.3 VVols
HU01212 S3 GUI displays an incorrect timezone description for Moscow 7.7.0.3 Graphical User Interface
FLASH-19098 S3 V9000 AE2 systems show email_state is disabled after CCL 7.7.0.3 System Update
FLASH-19273 S4 After flash module replacement and boot upgrade, lsdrive output shows incorrect firmware version 7.7.0.3 System Update
HU01208 S1 After upgrading to v7.7 and later from v7.5 and earlier, and then creating a DRAID array with a node reset, the system may encounter repeated node warmstarts which will require a T3 recovery 7.7.0.2 Distributed RAID
FLASH-16342 S1 Improve internal Flash checking to prevent access loss 7.7.0.1
HU00719 S2 After a power failure both nodes may repeatedly warmstart and then attempt an auto-node rescue. This will remove hardened data and require a T3 data recovery 7.7.0.1
HU00897 S2 Spectrum Virtualize iSCSI target ignores maxrecvdatasegmentlength leading to host I/O error 7.7.0.1 iSCSI
HU01007 S2 When a node warmstart occurs on one node in an I/O group, that is the primary site for GMCV relationships, due to an issue within FlashCopy, then the other node in that I/O group may also warmstart 7.7.0.1 FlashCopy
HU01039 S2 When volumes, which are still in a relationship, are forcefully removed then a node may experience warmstarts 7.7.0.1 HyperSwap
HU01062 S2 T2 recovery may occur when max replication delay is used and remote copy I/O is delayed 7.7.0.1 Global Mirror
HU01067 S2 In a HyperSwap topology, where host I/O to a volume is being directed to both volume copies, for specific workload characteristics, I/O received within a small timing window could cause warmstarts on two nodes within separate I/O groups 7.7.0.1
HU01186 S2 Volumes going offline briefly may disrupt the operation of Remote Copy leading to a loss of access by hosts 7.7.0.1 Global Mirror
HU01188 S2 Quorum lease times are not set correctly impacting system availability 7.7.0.1
HU01189 S2 Improvement to DRAID dependency calculation when handling multiple drive failures 7.7.0.1 Distributed RAID
HU00521 S3 Remote Copy relationships may be stopped and lose synch when a single node warmstart occurs at the secondary site 7.7.0.1 Global Mirror
HU00910 S3 Handling of I/O to compressed volumes can result in a timeout condition that is resolved by a node warmstart 7.7.0.1 Compression
HU00928 S3 For certain I/O patterns a SAS firmware issue may lead to transport errors that become so prevalent that they cause a drive to become failed 7.7.0.1
HU01003 S3 An extremely rapid increase in read IOs on a single volume can make it difficult for the cache component to free sufficient memory quickly enough to keep up, resulting in a single node warmstart 7.7.0.1
HU01059 S3 When a tier in a storage pool runs out of free extents Easy Tier can adversely affect performance 7.7.0.1 EasyTier
HU01069 S3 After upgrade from v7.5 or earlier to v7.6.0.1-3 all nodes may warmstart at the same time resulting in a T2 data recovery 7.7.0.1 System Update
HU01074 S3 An unresponsive testemail command, possible due to a congested network, may result in a single node warmstart 7.7.0.1
HU01075 S3 Multiple node warmstarts can occur due to an unstable Remote Copy domain after an upgrade to v7.6.0 7.7.0.1 Global Mirror
HU01089 S3 svcconfig backup fails when an I/O group name contains a hyphen 7.7.0.1
HU01110 S3 V9000 supports SSH connections using RC4 based ciphers 7.7.0.1
HU01156 S3 Single node warmstart due to an invalid FCoE frame from a HP-UX host 7.7.0.1 Hosts
HU01274 S3 DRAID lsarraysyncprogress command may appear to show array synchronisation stuck at 99% 7.7.0.1 Distributed RAID
FLASH-15888 S3 During a Concurrent Code Upgrade (CCU) from version 7.6.0.2 to 7.6.0.3 there is a 50 second I/O (input/output) stall 7.7.0.1 System Update
FLASH-16887 S3 An internal error is raised from a controller node during a CCU from version 7.4.1.4 to 7.6.1.1 7.7.0.1 System Update
FLASH-16414 S4 An OK button in the GUI user properties panel is clickable before a password is entered 7.7.0.1 Graphical User Interface
FLASH-14460 S5 Tool tips on the Access Audit Log GUI panel hinder access to control functions 7.7.0.1 Graphical User Interface
FLASH-16415 S5 Comment field in the GUI email event notifications setup is in the wrong section 7.7.0.1 Graphical User Interface
FLASH-17562 S5 Comment field in the GUI system setup is in the wrong section 7.7.0.1 Graphical User Interface

4. Supported upgrade paths

Please refer to the Concurrent Compatibility and Code Cross Reference for Spectrum Virtualize page for guidance when planning a system upgrade.

5. Useful Links

Description Link
Support Website IBM Knowledge Center
IBM FlashSystem Fix Central V9000
Updating the system IBM Knowledge Center
IBM Redbooks Redbooks
Contacts IBM Planetwide