IBM FlashSystem V9000

Transcription

1 IBM FlashSystem V9000 Firmware Version Release Notes July6, Applicable systems Product resources Bug severity legend Latest changes Overall 7.7 release features Issues fixed Known issues Currently supported specifications Upgrading firmware Overview of release Supported upgrade paths Preparing to upgrade Performing the upgrade Troubleshooting Contact information Release history Copyright notice... 19

2 1.0 Applicable systems These release notes apply to the following systems: IBM FlashSystem V9000, machine type and model (MTM) 9846-AC2 and 9846-AE2 IBM FlashSystem V9000, MTM 9848-AC2 and 9848-AE2 2.0 Product resources IBM FlashSystem V9000 product information resources guide users through the various features and components of the storage system, including usage and troubleshooting guides. To read about this storage system and learn how to use or troubleshoot, see the IBM Knowledge Center for IBM FlashSystem V9000 at or visit the IBM Redbooks website at for the IBM FlashSystem V9000 Product Guide. 3.0 Bug severity legend The following explains the bug severity ranking used in Section 4.2 for fixes made in the current release as well as fixes from previous releases listed in section 7.0: S1: Highest Recommend upgrade for all users as soon as possible. S2: Medium Recommend upgrade for all users at the next scheduled maintenance window. S3: Average Recommend upgrade at the next scheduled maintenance window for users experiencing these issues. Optional for all other users to upgrade at the next scheduled maintenance window. S4: Low Optional upgrade at the next scheduled maintenance window. May be performed at the discretion of the user if the issue is having a negative impact. S5: Lowest Upgrade is not necessary. This would include a mostly cosmetic or minor annoyance fix. 4.0 Latest changes This is a major release including new features described in section 4.1 below and minor fixes for prior releases. After initial configuration of the hardware is complete, IBM strongly recommends that you make sure that your IBM FlashSystem firmware is up-to-date. Visit IBM Fix Central using the link below to see if any updates are available for your system Overall 7.7 release features The following are features included in all 7.7 version firmware releases including the current release: Support is now available for flash-optimized tiered storage with the attachment of SAS enclosures to a FlashSystem V9000. Support is now available for deduplication and the virtualization of a FlashSystem A9000 from a V9000 system. 2 Copyright IBM Corporation 2016

3 4.2 Issues fixed The following is the only fix included in this release and the severity level for that fix. Use the severity level as described in Section 3.0 to aid in your decision to upgrade. The issue resolved is one found in SVC. The issue Authorized Program Analysis Report (APAR) number is included. For more information, visit Fix Central for the SVC 7.7 release notes. For issues fixed in prior releases, see section 7.0. S1 APAR-HU When upgrading to from x or x releases and then creating a DRAID array, a node reset may result in repeated node asserts and require data to be recovered. 4.3 Known issues The following is a list of known issues and information related those these issues which exist for this release: 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. If using IP replication, please review the set of restrictions published in the Configuration Limits and Restrictions document for your product. Windows 2008 host paths may become unavailable following a Storwize V7000 node canister or SVC node replacement procedure. Documentation is available for this issue at the following URL: Intra-System Global Mirror not supported. More information is available at the following URL: Host Disconnects Using VMware vsphere Update 2 and vsphere 6.0. More information is available at the following URL: Currently supported specifications SCSI-SAM-3 SCSI-SPC-3 SCSI-SBC-2 SCSI-FCP-3 SCSI-SRP FC-PH-3 FC-AL-2 SCSI Architecture Model v3 SCSI Primary Commands v3 SCSI Block Commands v2 Fibre Channel Protocol v3 SCSI RDMA Protocol v1 Fibre Channel Physical and Signaling Interface v3 Fibre Channel Arbitrated Loop v2 Version

4 5.0 Upgrading firmware Use the following sections to perform code upgrades for your systems to the current release. Warning: Please read all the instructions below before upgrading. 5.1 Overview of release If you are upgrading to this release and your system is healthy, you can perform a Concurrent Code Upgrade (CCU). A CCU is a non-disruptive upgrade and is the preferred upgrade method. For general instructions on performing upgrades, refer to the FlashSystem Knowledge Center using the following URL: From this link, you can access the appropriate FlashSystem page through the following path: System Storage Flash Storage Flash high availability systems IBM FlashSystem V9000 Upgrading 5.2 Supported upgrade paths The following upgrade paths are supported for this release: Copyright IBM Corporation 2016

5 5.3 Preparing to upgrade A CCU is a non-disruptive upgrade, which means that the system remains online throughout the process and that you can continue to access data normally. As a precaution, it is recommended that the upgrade occur during a time of reduced traffic. During the upgrade, the interface adapters in each control node are taken offline temporarily in order to be upgraded. This might impact performance or throughput. The impact is more noticeable under heavy load conditions. With a properly configured multi-path configuration, access to your data is maintained at all times. In order to ensure a successful, non-disruptive upgrade, you should verify that your interface ports are all online and all the system hardware is functioning normally. Ideally, you should have the following: All host interfaces should be online. An active multi-path configuration is required to ensure no loss of access during the upgrade. Information on this topic is available in IBM Knowledge Center under the Fibre Channel host attachments topic found using the following URL: svc_fibrechannel_cover.html All batteries should be online and charged at least 85%. Use the CLI command lsenclosurebattery to verify battery charge. If using encryption, ensure that both USB keys are inserted during the CCU. From the CLI, issue lsportusb to view if USBs have been inserted as an alternative to a physical check. From the GUI, navigate to Settings Security Encryption to view ports and encryption status. All hardware should be online and functioning normally. There should be no unfixed alerts in the event log (see the exceptions below). Important: Before you begin the upgrade, we recommend that you perform a backup of your data and a backup of the FlashSystem configuration. To back up the configuration, log into the cluster management IP address and issue the following command using an account with Administrator privileges: svcconfig backup Optionally, you can copy the configuration backup file from the FlashSystem to your workstation using secure copy (scp) on Linux or PuTTY secure copy (pscp.exe) on Windows as in the following examples: (Using Linux) scp username@cluster_ip:/dumps/svc.config.backup.*. (Using Windows) pscp username@cluster_ip:/dumps/svc.config.backup.*. Note: Do not ignore the periods shown above at the end of each command. In addition, replacement of italicized descriptions with appropriate information is required. Version

6 5.4 Performing the upgrade It is highly recommended that the upgrade be performed using the web-based cluster management interface known as the management GUI. Access this option through Settings System Update System in the GUI. Using the management GUI, you will be prompted to install and run the software upgrade test utility and the software update package from a single GUI panel. The software upgrade test utility is designed to detect and warn of various conditions that might prevent a successful upgrade. The upgrade test utility can be run either during the upgrade using the Update and Test button or by itself with the Test only button. Once the utility finishes running certain checks for vulnerabilities, the software update utility will allow you to upload the firmware file and start the upgrade. For more detailed instructions and information for using the upgrade utility from the CLI or the GUI, see the release notes for the upgrade utility, which is located on Fix Central. The upgrade can proceed successfully without the Call Home feature enabled, but IBM highly recommends that the feature be enabled. The upgrade can also be performed using the applysoftware command in the CLI. This requires that you manually upload the latest release to the/upgrade directory on the cluster management node. The upgrade test utility must be run before the upgrade can start. 5.5 Troubleshooting Use the following sections to troubleshoot problems that may occur during the upgrade process Stalled upgrade If the upgrade completion percentage does not increase for more than two hours, the upgrade may have stalled. Upgrade status is viewed by issuing the lsupdate CLI command or by going to Settings System Update System in the GUI. Both show a Stalled status. If the upgrade stalls or if you have alerts which cannot be cleared, contact IBM Support. Support contact information is provided in Section 6.0 of this document Failures during upgrade You may get a battery or quorum alert during upgrade. These alerts are expected and should be automatically cleared when the upgrade is completed. They may be visible from the Events view of the management GUI if the filter is set to "Show All," but they should no longer appear in the Recommended Actions, Unfixed Messages, or Alerts views. If you see unfixed battery or quorum alerts after an upgrade is complete, contact IBM Support. If the upgrade has stalled due to a hardware failure, you ll see the current status of Hardware Failed. If you suspect a hardware failure, issue the lsupdate command from the management CLI to confirm the state of your system. This command shows that the system is in a hardware_failed state and the event log contains a "System upgrade suspended" event. You may resume the upgrade by issuing the command applysoftware -resume force for the following conditions: PSU unsupported events Battery fault type 1 events that are fixed and online according to the CLI command lsenclosurebattery Fan events If the upgrade cannot be resumed or you have other alerts which cannot be cleared, contact IBM Support. All releases include a battery reconditioning feature which calibrates the gauge that reports the amount of charge on the batteries. On systems that have been installed for 10 months or more or systems that have experienced several power outages, the recommendation to run "battery reconditioning" will appear in the event log shortly after upgrading. This is normal. Use the management GUI to run the DMP for this error. 6 Copyright IBM Corporation 2016

7 6.0 Contact information Call IBM at IBM-SERV ( ). To find contact information for a specific region, visit the IBM directory of worldwide contacts at Release history The following sections include a list of all fixes and improvements for previous releases. Reference Section 3.0 for explanations of each severity level. For fixes in the current release, see section 4.2. Release The following issues were fixed in release : APAR-HU Volumes going offline briefly may disrupt the operation of remote copy functionality leading to a loss of access by hosts. (S2) APAR-HU Quorum lease times are not set correctly impacting system availability. (S2) APAR-HU Improvement to DRAID dependency calculation when handling multiple drive failures. (S2) APAR-HU After a power failure both nodes may repeatedly assert and then attempt an auto-node rescue. This will remove hardened data and require a T3 data recovery. (S2) APAR-HU Spectrum Virtualize iscsi target ignores maxrecvdatasegmentlength leading to host IO error. (S2) APAR-HU 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 assert(s2) APAR-HU When a node assert occurs on one node in an IO group, that is the primary site for GMCV relationships, due to an issue within FlashCopy then the other node in that IO group may also assert. (S2) APAR-HU In a HyperSwap topology, when volumes, which are still in a relationship, are forcefully removed then a node may assert. (S2) APAR-HU T2 recovery may occur when max replication delay is used and remote copy IO is delayed. (S2) APAR-HU In a HyperSwap topology, where host IO to a volume is being directed to both volume copies, for specific workload characteristics, IO received within a small timing window could cause asserts on two nodes within separate IO groups. (S2) APAR-HU A limitation in the RAID anti-deadlock page reservation process may lead to an mdisk group going offline. (S2) FLASH During a Concurrent Code Upgrade (CCU) from version to there is a 50 second I/O (input/output) stall. (S3) FLASH An internal error is raised from a SVC controller node during a CCU from version to (S3) APAR-HU When a tier in a storage pool runs out of free extents Easy Tier can adversely affect performance. (S3) APAR-HU Remote copy relationships may be stopped and lose synch when a single node assert occurs at the secondary site. (S3) APAR-HU Single node assert due to an accounting issue within the cache component. (S3) APAR-HU For certain IO patterns a SAS firmware issue may lead to transport errors that become so prevalent that they cause a drive to become failed. (S3) APAR-HU After upgrade from v7.5 or earlier to v all nodes may assert at the same time resulting in a T2 data recovery. (S3) APAR-HU An unresponsive test command, possible due to a congested network, may result in a single node assert. (S3) Version

8 APAR-HU Multiple node asserts can occur due to an unstable Remote Copy domain after an upgrade to v7.6.0.x. (S3) APAR-HU svcconfig backup fails when an IO group name contains a hyphen. (S3) APAR-HU SVC supports SSH connections using RC4 based ciphers. (S3) APAR-HU Single node assert due to an invalid FCoE frame from a HP-UX host. (S3) FLASH An OK button in the GUI user properties panel is clickable before a password is entered. (S4) FLASH Tool tips on the Access Audit Log GUI panel hinder access to control functions. (S5) FLASH Comment field in the GUI event notifications setup is in the wrong section. (S5) FLASH Comment field in the GUI system setup is in the wrong section. (S5) Release The following issues were fixed in release : FLASH Internal error during error handling causes loss of access. (S1) FLASH Just a Bunch Of Flash (JBOF) errors incorrectly shows an XBAR fail causing loss of system access. (S1) FLASH-17921, Incorrect device discovery during CCU can cause access and data loss. (S1) APAR-HU A node assert on a cluster, with Global Mirror (GM) secondary volumes, can also result in a delayed response to hosts that are performing I/O to the GM primary volumes. (S1) APAR-HU Compressed volumes larger than 96 TiB may experience a loss of access to the volume. For more details, refer to the following Flash: (S1) FLASH-17718, Internal error encountered with Assert File /build/tms/lodestone15b/160225_0020/src/user/ic/icee_smi.c Line 889 Info (null). (S2) FLASH-17874, Prevent base SVC install packages from running on V9000. (S2) FLASH-17957, After High Temp Shutdown of system, Array did not come back online. (S2) APAR-HU Prior asserts, perhaps due to a hardware error, can induce a "dormant state" within the FlashCopy code that may result in further asserts. (S2) APAR-HU Node asserts leading to both nodes going into 564 error state. (S2) APAR-HU When creating a snapshot on an ESX host, using VVols, a data recovery may occur. APAR-IT Node asserts due to a timing window in the cache component. For more details, refer to the following Flash: (S2) FLASH For earlier 7.6 versions, the Power Interposer Board (PIB) cannot be replaced in the field without the array being removed on the enclosure. (S3) FLASH-17500, Internode communication issue causes CCU to stall. (S3) FLASH Rare assert encountered. (S3) FLASH Battery failure Directed Maintenance Procedure (DMP) for error code 1114 indicates Unable to proceed. (S3) FLASH DMP for error 1114 for battery fault does not wait for a low charge battery FRU to charge. (S3) FLASH-17887, Repeated CRC errors between interface and XBAR can fail flash module. (S3) FLASH Emulex HBA update for SVC nodes to handle multiple illegal frames. (S3) FLASH-17494, Call home backlog held up newer call home event from reaching Service Center due to processing on the SVC nodes. (S3) FLASH Battery percent_charge stays at old value if battery is removed or goes offline. FLASH Cluster created with an 8x4 configuration reports degraded path with the 8 th node included. (S3) APAR-HU Storage pool free capacity may be incorrectly reported by the CLI. (S3) 8 Copyright IBM Corporation 2016

9 APAR-HU In certain configurations, throttling too much may result in dropped I/O (Input/Output), which can lead to a single node assert. (S3) APAR-HU Batteries may be seen to continuously recondition. (S3) APAR-HU When using GMCV relationships, if a node in an I/O group loses communication with its partner, it may assert. (S3) APAR-HU Where nodes are missing configuration files, some services will be prevented from starting. (S3) APAR-HU Single node assert on the configuration node due to GUI contention. (S3) APAR-IT CLI command lsportsas may show unexpected port numbering. (S3) FLASH-16113, Recover system links to blank page. (S4) FLASH-17833, PLIC & PLTX has issues and requires enhancements. (S4) FLASH Available capacity value is wrong. (S4) FLASH The Update GUI panel gives the example for an SVC update package rather than a V9000 update package. (S4) FLASH-17886, Reads of Invalid pages in JBOF are not logged. (S5) Release The following issues were fixed in release : FLASH Authentication bypass using HTTP verb tampering is possible. FLASH PSoC issues eventually lead to both canisters going into service state. (S1) FLASH Degraded components are included in the system thermal algorithm. (S1) FLASH Issues result when the same call home manager processes run simultaneously. (S1) FLASH Improved data checking of zero and xor page data. (S2) FLASH Improve error handling of unresponsive flash chip. (S2) FLASH A canister node goes into service state 574 after a battery is degraded. (S2) FLASH Upgrade failed with the message Unable to communicate with Systemmgr. (S2) FLASH Fix interface error reporting. (S2) FLASH Systems created in x are at risk of quorum devices having incorrect short lease expiry timeout and could lease expire on node failover. (S2) APAR-HU01016, HU Node asserts can occur when a port scan is received on port (S2) APAR-HU Dual node assert due to issues with the call home process. (S2) APAR-HU An issue with the CAW lock processing, under high SCSI-2 reservation workloads, may cause node asserts. (S2) FLASH Call home configuration cannot complete if network infrastructure is not ready. (S3) FLASH Double allocation of memory without the necessary free space leads to memory allocation failure. (S3) FLASH-17135, Issues result when the same call home manager processes run simultaneously. (S3) APAR-HU Processing of lsnodebootdrive output may adversely impact management GUI performance. (S3) APAR-HU Incremental FlashCopy always requires a full copy. (S3) APAR-HU Single node assert due to 16Gb HBA firmware behavior. (S3) APAR-HU GUI operation with large numbers of volumes may adversely impact performance. (S3) APAR-HU Management GUI incorrectly displays FC mappings that are part of GMCV relationships. (S3) APAR-HU Where hosts share volumes using a particular reservation method, if the maximum number of reservations is exceeded, this may result in a single node assert. (S3) APAR-HU Single node assert due to an I/O timeout in cache. (S3) APAR-HU When removing multiple nodes from a cluster, a remaining node may assert. (S3) Version

10 APAR-HU With a partnership stopped at the remote site, the GUI stop button at the local site will be disabled. (S3) APAR-HU Systems which have undergone particular upgrade paths may be blocked from upgrading to version 7.6. (S3) APAR-HU Single node assert due to rare resource locking contention. (S3) APAR-IT A memory issue, related to the feature, may cause nodes to assert or go offline. FLASH The Firmware Versions section of system report is missing management FPGA information. (S4) FLASH Canister nodes should reboot in certain error conditions instead of requiring customer action. (S4) Release The following issues were fixed in release : APAR-HU Large increase in response time of Global Mirror primary volumes when replicating large amounts of data concurrently to secondary cluster. (S1) FLASH Degraded components are still used in the thermal algorithm. (S2) APAR-HU Single node assert, or unresponsive GUI, when creating compressed volumes. (S2) APAR-HU A data recovery operation may occur when max replication delay is used and remote copy I/O is delayed. (S2) APAR-HU Node warmstarts in two I/O groups when using HyperSwap on 7.6 releases. (S2) APAR-HU SVC reports incorrect SCSI TPGS data in an 8 node cluster causing host multi-pathing software to receive errors which may result in host outages. (S2) APAR-HU Dual node assert due to issue with call home process. (S2) FLASH In certain cases, chencryption and lsdrive commands will restart the cluster. (S3) APAR-HU Single node assert due to hung IO caused by cache deadlock. (S3) APAR-HU SVC CG8 nodes have internal SSDs but these are not displayed in "internal storage" page. (S3) FLASH The GUI for powering off a SVC node produces a misleading message. (S5) FLASH The GUI system view is missing some colons for Power Supply information. (S5) Release The following issues were fixed in release : FLASH Vulnerability in OpenSSL (CVE ). FLASH Vulnerabilities in Network Security Services or NSS (CVE , CVE , and CVE ). FLASH Vulnerability in Java (CVE ). FLASH HIPER (highly pervasive) Node failover during upgrade of replacement module can cause all modules to be reconfigured resulting in data loss. (S1) FLASH Inquiry command after LUN reset incorrectly returned Unit Attention. (S2) FLASH An MDisk goes offline when writing the end of memory with a fully allocated array while rebuild is in progress. (S2) FLASH Fault the Interface when FPGA buffer allocates or frees twice. (S2) FLASH Marking the event "Array mdisk is not protected by sufficient spares" as fixed should only fix the event in a system with three flash modules. (S2) FLASH DMP does not properly format Flash Module after replacement. (S2) FLASH A flashcard goes unresponsive when array certify is taking corrective action due to an error reporting issue. (S2) FLASH A DMP attempted to format the incorrect drive when fixing error code (S2) APAR-HU Single node assert, or unresponsive GUI, when creating compressed volumes. (S2) APAR-HU Both nodes in the same IO group assert. (S2) APAR-HU Node assert after upgrade to v7.6. (S2) 10 Copyright IBM Corporation 2016

11 FLASH Enable update to 7.6 firmware from and releases. (S3) FLASH Node 574 error on reboot. (S3) FLASH A rare scenario finds sequential fail logic to be too aggressive. (S3) FLASH Both nodes assert during power up. (S3) FLASH Interface improvements necessary. (S3) FLASH Improve signal margin on interface to/from RAID controller links. (S3) FLASH Sending test wizard fails with CMMVC5709E [-1] is not a supported parameter. APAR-HU Single node assert due to hung IO caused by cache deadlock. (S3) APAR-HU Where a boot drive has been replaced, with a new unformatted one, on a DH8 node the node may assert when the user logs in as superuser to the CLI via its service IP or they log into the node via the service GUI. Additionally, where the node is the configuration node this may happen when user logs in, as superuser, to the cluster via CLI or management GUI. (S3) FLASH Internal service errors found upon system set up. (S4) FLASH The DMP for event , error code 1067 has identification and description errors. (S4) FLASH The wrong product is given as example for the test utility and update files in the GUI. (S4) FLASH The field "Description" on the GUI easy setup has an inconsistent name on different panels. (S5) Release The following issues were fixed in release : FLASH Data stalls are possible with a fully allocated array while rebuild is in progress. (S1) APAR-HU Multiple node asserts due to invalid IP Quorum port connection. (S2) APAR-HU Single node assert stalls upgrade for systems presenting storage to large VMware configurations using SCSI CAW. (S3) Release The following issues were fixed in release : APAR-HU Batteries going on and offline can take node offline. (S2) APAR-HU00926, HU Where an array is not experiencing any I/O, a drive initialization may cause node asserts. (S2) FLASH Potential I/O stall for more than 30 seconds during upgrade. (S3) FLASH Pools and I/O groups do not appear in the drop down when creating a HyperSwap volume if a long site name is configured. (S4) FLASH CLI help files were not translated in the release. (S4) Release The following issues were fixed in release : FLASH HIPER (highly pervasive): Potential undetected data corruption may occur due to a low probability race condition. The race condition has been observed on a system with a specific workload that is doing 1 to 2 GB/s of read operations with 250 MB/s of write operations. The write operations were less than 4K in size. (S1) APAR-HU Stop with access resulted in a node assert after a recoveryvdiskbysystem command. (S1) APAR-HU Multiple node asserts in IO group after starting Remote Copy. (S1) APAR-HU Multiple node asserts when removing a Global Mirror relationship with secondary volume that has been offline. (S1) APAR-HU Large increase in response time of Global Mirror primary volumes due to intermittent connectivity issues. (S1) Version

12 APAR-HU Multiple node asserts when space efficient volumes are running out of capacity. (S1) FLASH Repeated interface panics causes an incorrect failure. (S2) APAR-HU Increased CPU utilization on nodes from Easy Tier processing. (S2) APAR-HU Node assert due to inconsistent Easy Tier status when Easy Tier is disabled on all managed disk group. (S2) APAR-HU Both nodes in a single IO group of a multi IO group system can assert due to misallocation of volume stats entries. (S2) APAR-HU FlashCopy volume offline due to a cache flush issue. (S2) APAR-HU SVC FC driver asserts when it receives an unsupported but valid FC command. (S2) APAR-HU Battery can charge too quickly on reconditioning and take node offline. (S2) APAR-HU Single node assert when removing an Mdisk group that had EasyTier activated. (S2) APAR-HU Loss of access to data when removing volumes associated with a GMCV relationship. (S2) APAR-HU Performance impact on read pre-fetch workloads due to cache pre-fetch changes. (S2) APAR-HU FlashCopy volumes may go offline during an upgrade. (S2) APAR-HU CCU checker causes both nodes to assert. (S2) APAR-HU Gb HBA causes mutiple node asserts when unexpected FC frame content received. (S2) APAR-HU Increase in workload may cause nodes to assert. (S2) APAR-HU Unable to remove ghost mdisks. (S2) APAR-HU00935 Single node assert fc_io.c line 1013 when using FlashCopy. (S3) FLASH A node timeout causes the Flash to fail. (S3) FLASH FC interface timeout issue results in a temporary error. (S3) FLASH Unexpected node assert. (S3) FLASH Failed encryption validation causes a VM timeout. (S3) FLASH Flash failure due to Gateway to node CRC errors. (S3) FLASH Flash card failures are a result of an unexpected power off. (S3) FLASH Mitigate flashcard encryption error. (S3) FLASH Performance improvements made. (S3) APAR-HU Single node assert on login attempt with incorrect password issued. (S3) APAR-HU When stopping a GMCV relationship clean up process at secondary site hangs to the point of a primary node assert. (S3) APAR-HU SVC reports invalid counters causing TPC to skip sample periods. (S3) APAR-HU Hang up of GM IO stream can effect MM IO in another remote copy stream. (S3) APAR-HU FlashCopy performance degraded. (S3) APAR-HU Node assert observed when 16 Gb FC or 10 Gb FCoE adapter detects heavy network congestion. (S3) APAR-HU Emulex firmware paused causes single node assert. (S3) APAR-HU Single node assert when receiving frame errors on 16GB Fibre Channel adapters. (S3) APAR-HU Single node assert when concurrently creating new volume host mappings. (S3) APAR-HU Support for Fujitsu Eternus DX100 S3 controller. (S3) APAR-HU SNMP and Call home stops working when node reboots. (S3) APAR-HU Volume hosted on Hitachi controllers show high latency due to high IO concurrency. (S3) APAR-HU Single node asserts due to FlashCopy chaining. (S3) APAR-HU Single node assert during code upgrade. (S3) APAR-IC The exact file requested is missing when copying statistic files between nodes presents event ID (S3) APAR-IT Freeze time update delayed after reduction of cycle period. (S3) APAR-HU Single node assert due to hung RC recovery caused by pinned write I/Os on incorrect queue. (S3) 12 Copyright IBM Corporation 2016

13 APAR-HU Single node assert due to a race condition reordering of the background process when allocating IO blocks. (S3) FLASH The upgrade utility does not report a failed drive. (S4) FLASH Service manager panic experienced during upgrade. (S4) FLASH Properly cabled fixed configurations always raise a false "Minimum cabling rules not met alert. (S4) FLASH Stalled upgrade reports an upgrade failure error even after the upgrade completes successfully. (S4) FLASH Incomplete chenclosurecanister command can cause the nodes to assert. (S4) FLASH A node assert is experienced during upgrade. (S4) FLASH A mandatory parameter is not included in the ping CLI help. (S5) Release The following issues were fixed in : FLASH Remediate a vulnerability in Java (CVE ). FLASH Remediate multiple vulnerabilities related to Network Security services (NSS) (CVE , CVE , CVE ). FLASH Remediate a vulnerability in OpenSSL (CVE ). FLASH Remediate a vulnerability in Apache Struts (CVE ). FLASH Remediate a vulnerability in cross-site request forgery (CSRF) (CVE ). APAR-HU The extent database defragmentation process can create duplicates whilst copying extent allocations resulting in a node assert to recover the database. (S1) APAR-HU Single node assert when receiving frame errors on 16GB Fibre Channel adapters. (S1) APAR-HU Large increase in response time of Global Mirror primary volumes when replicating large amounts of data concurrently to secondary cluster. (S1) APAR-HU Large increase in response time of Global Mirror primary volumes due to intermittent connectivity issues. (S1) APAR-HU Both nodes in the same IO group assert. (S1) APAR-HU Multiple node asserts when VDisks that are part of FlashCopy maps go offline (e.g due to insufficient space). (S1) FLASH DMP for error code 1690 failed to properly format a flash module after its replacement. (S2) FLASH Marking Array Mdisk is not protected by sufficient spares event as fixed should not work. (S3) APAR-HU Single node assert due to hung IO caused by cache deadlock. (S3) APAR-HU Where a boot drive has been replaced, with a new unformated one, on a DH8 node the node may assert when the user logs in as superuser to the CLI via its service IP or they log into the node via the service GUI. Additionally where the node is the config node this may happen when the user logs in, as superuser, to the cluster via CLI or management GUI. (S3) APAR-HU Performance statistics BBCZ counter values reported incorrectly. (S3) APAR-HU SVC CG8 nodes have internal ssds but these are not displayed in "internal storage" page. (S3) APAR-HU Single node assert due to a race condition reordering of the background process when allocating IO blocks. (S3) Release The following issues were fixed in release : FLASH-14845, Remediate vulnerability in PAM or Pluggable Authentication Module (CVE ). FLASH-13369, Remediate vulnerability in nss-softokn (CVE ). Version

14 FLASH HIPER (highly pervasive) Node failover during upgrade of replacement module can cause all modules to be reconfigured resulting in data loss. (S1) FLASH-15672, An Mdisk goes offline when writing the end of memory with a fully allocated array while rebuild is in progress. (S1) FLASH HIPER (highly pervasive): Potential undetected data corruption may occur due to a low probability race condition. The race condition has been observed on a system with a specific workload that is doing 1 to 2 GB/s of read operations with 250 MB/s of write operations. The write operations were less than 4K in size. (S1) APAR-HU Loss of access to data when moving volumes to another IO group using the GUI. APAR-HU Enhanced recovery procedure for compressed volumes affected by APAR HU For more details refer to the following Flash: (S1) FLASH Repeated interface panics due to a bad interface cable can cause unnecessary component failures. (S2) FLASH A flashcard can become unresponsive when array certify is running while hardware errors are being found. (S2) APAR-HU After upgrade to V both nodes assert. (S2) APAR-HU Read/write performance latencies due to high CPU utilization from Easy Tier 3 processes on the configuration node. (S2) APAR-HU Performance impact on read pre-fetch workloads. (S2) APAR-II Reduced performance for volumes which have the configuration node as their preferred node due to GUI processing the update of volume attributes where there is a large number of changes required. (S2) APAR-HU Multiple node asserts when using a Metro Mirror or Global Mirror volume that is greater than 128TB. (S2) APAR-HU Node asserts when Spectrum Virtualize iscsi target receives garbled packets. (S2) APAR-HU Multiple asserts due to FlashCopy background copy limitation. (S2) FLASH The nodes warmstart after being powered on due to an error in call home. (S3) FLASH Node assert occurs when unmanaging an enclosure. (S3) FLASH VPD mismatch due to 8 Gb to 16 Gb conversion causes node asserts on upgrades to 1.3 firmware levels. (S3) FLASH Stalled upgrade reports an erroneous Failed to upgrade error. (S3) FLASH Code upgrade stalls with internal error. (S3) FLASH Node timeout results in flash failure. (S3) FLASH Gateway to node CRC errors result in flash failure. (S3) FLASH Flash card failures occurred due to unexpected power off. (S3) FLASH Mitigation for flashcard encryptor error. (S3) FLASH Improve signal integrity between canisters. (S3) Release The following issues were fixed in release : FLASH Include all of the following relevant fixes from the SVC release, version : (S1) HU Loss of access to data when a volume that is part of a Global Mirror Change Volumes relationship is removed with the 'force' flag. HU Both nodes shutdown when power is lost to one node for more than 15 seconds. HU Multiple node asserts leading to loss of access to data when the link used for IP Replication experiences packet loss and the data transfer rate occasionally drops to zero. HU Single node assert due to HBA firmware behavior. HU The serial number value displayed in the GUI node properties dialog is incorrect. 14 Copyright IBM Corporation 2016

15 FLASH x1 fixed configurations raise a false Minimum cabling rules not met event. (S2) FLASH Running the canister intercommunication error DMP (error code 1007) yields an Unable to Proceed message. (S2) FLASH Possible upgrade issues can take place for enclosures with encrypted arrays. (S2) FLASH Remediate vulnerabilities in Java (CVE , CVE , CVE , and CVE ). (S2) FLASH When trying to install some packages, a Error in verifying the signature of the update package message is produced. (S3) FLASH If a CCL is performed while the flash modules are in a Waiting state, the modules can write over used flash and this therefore causes a fault when read. (S4) Release The following issues were fixed in release : FLASH-10119, HIPER (highly pervasive): Potential undetected data corruption may occur from an interface error. In rare cases, the FlashSystem V9000 can write inconsistent data to a host. This is considered a highly pervasive problem involving firmware versions 7.4.x.x. (S1) FLASH Remediate security vulnerabilities in OpenSSL (CVE , CVE , CVE , and CVE ). (S1) FLASH Remediate security vulnerabilities in Java CPU (CVE , CVE , and CVE ). (S1) FLASH Remediate security vulnerability in Apache Struts (CVE ). (S1) FLASH-12692, FLASH Improve canister replacement DMPs. (S2) FLASH Unable to add storage enclosure at a higher version than the current configuration. (S2) FLASH Both canisters incorrectly downgrade at the same time during a failed CCU (PMR). (S2) FLASH-10600, FLASH Adding a second building block with down-level firmware to existing cluster does not complete (PMR ). (S2) FLASH MDisk reports degraded ports, but the DMP does not offer a real fix to the issue (PMR). (S2) FLASH Canister to canister communication, error 1007 identifies the incorrect canister for replacement (PMR). (S2) FLASH Node error , Inter-canister PCIe link failure is seen too often. (S2) FLASH Scaled up configuration encryption validation only runs on one enclosure. (S2) FLASH False disk encryption error (085158) reported (PMR). (S2) FLASH Errors incorrectly blame flash module instead of quorum device. (S2) FLASH Unexpected Input/output (I/O) errors causes controller node assertions every 30 minutes (PMR). (S2) FLASH Enclosure canister failed to come online after a cold start (PMR). (S2) FLASH Candidate drives are exposed when they are not ready for I/O resulting in false failures during FRU replacements. (S2) FLASH The RAID controller incorrectly marked as failed instead of flashcard in a particular double flashcard failure scenario. (S2) FLASH Unexpected canister power off can cause a warm start on remaining canister. (S2) FLASH Fan fault events incorrectly appear during the enclosure boot upgrade. (S2) FLASH I/O latency spikes due to periodic encryption validation. (S3) FLASH Move key validation from 30 to 1440 minutes. (S3) FLASH-9731, FLASH Flash sustained write performance improvements. (S3) FLASH Flash endurance improvements. (S3) FLASH There is no GUI option to add new expansion enclosure to existing pool when scaling up. (S3) Version

16 FLASH After a port between AC2 and AE2 goes down and is recovered, it incorrectly appears as a phantom controller (PMR). (S3) FLASH Issuing cpenclosuredumps following cleardumps does not copy any file. (S3) FLASH Unsupported 4th adapter in the AC nodes results in service 564 state (PMR). (S3) FLASH Issuing lsdependentvdisks -drive 0 causes recoverable a warm start on node (PMR). (S3) FLASH There is an issue on performance reporting with 16Gb FC. (S3) FLASH Stale interface logins are not removed on failure. (S3) FLASH-11128, FLASH-12620, FLASH-12690, FLASH Canister replacement DMP improvements. (S3) FLASH Canister warm start DMP improvement. (S3) FLASH Flashcard reporting incorrect temperature on node timeout resulting in false critical temperature failure. (S4) FLASH Flash improvements in error path identification. (S4) FLASH Logging improvements. (S4) FLASH GUI incorrectly shows member drives with Suitability "Wrong Slot" (PMR). (S4) FLASH Issuing clearenclosuredumps works only for one canister with new -canister option. (S4) FLASH Cabling code not working as designed. (S4) FLASH Management controller packet handling improvement. (S4) FLASH Build string truncated in lsservicestatus and the Service Assistant GUI. (S4) FLASH Improve canister node error reporting. (S4) FLASH Issuing lsdumps prefix with an invalid directory causes a node failover. (S4) FLASH Improve logging. (S5) FLASH Snap output is missing results from lsnodebattery. (S5) FLASH svc_snap performance improvements. (S5) Release The following issues were fixed in release : FLASH Remediate a vulnerability in nss-softokn (CVE ). FLASH Remediate multiple vulnerabilities related to Apache Struts (CVE ). FLASH Remediate a vulnerability in PAM (CVE ). FLASH Remediate a vulnerability in Java (CVE ). FLASH Remediate NSS-related vulnerabilities (CVE , CVE , CVE ). FLASH Remediate a vulnerability in OpenSSL (CVE ). APAR-HU Large increase in response time of Global Mirror primary volumes due to intermittent connectivity issues. (S1) APAR-HU Large increase in response time of Global Mirror primary volumes when replicating large amounts of data concurrently to secondary cluster. (S1) APAR-HU A node assert on a cluster with Global Mirror secondary volumes can also result in a delayed response to hosts performing I/O to the Global Mirror primary volumes. (S1) FLASH DMP for error code 1690 formats an incorrect flashcard after the faulted card is replaced. (S2) APAR-HU When a node running iscsi encounters a PDU with AHS it will assert. (S2) APAR-HU The extent database defragmentation process can create duplicates whilst copying extent allocations resulting in a node assert to recover the database. (S2) APAR-HU Single node assert due to hung IO caused by cache deadlock. (S3) APAR-HU Where a boot drive has been replaced, with a new unformated one, on a DH8 node the node may assert when the user logs in as superuser to the CLI via its service IP or they log into the node via the service GUI. Additionally, where the node is the config node 16 Copyright IBM Corporation 2016

17 this may happen when the user logs in, as superuser, to the cluster via CLI or management GUI. (S3) APAR-HU Running GMCV relationships are not consistently displayed in GUI. (S3) APAR-HU Technician port inittool redirects to SAT GUI. (S3) FLASH Add Pass 5 CPLD support. (S4) Release The following issues were fixed in release : FLASH-13527, Vulnerabilities in OpenSSL (CVE , CVE , CVE , and CVE ). FLASH-12502, Vulnerabilities in Java CPU (CVE , CVE , CVE , and CVE ). FLASH Vulnerability in Apache Struts (CVE ). FLASH Vulnerabilities in Java Quarterly (CVE , CVE , and CVE ). FLASH HIPER (highly pervasive): Potential undetected data corruption may occur due to a low probability race condition. The race condition has been observed on a system with a specific workload that is doing 1 to 2 GB/s of read operations with 250 MB/s of write operations. The write operations were less than 4K in size. (S1) FLASH-10119, HIPER: Potential undetected data corruption may occur from interface error. FlashSystem 840 and 900 products can write inconsistent data to a host. This is considered a highly pervasive problem involving firmware versions 1.1.x.x and 1.2.x.x. (S1) APAR-HU Offline Volume due to misreported Thin Provisioned volume integrity. (S1) APAR-HU Enhanced recovery procedure for compressed volumes affected by APAR HU For more details refer to the following Flash: (S1) APAR-HU Potential data loss scenario when using compressed volumes on SVC and Storwize V7000 running software versions 7.3, 7.4 or 7.5. For more details, refer to the following Flash: (S1) APAR-HU Multiple node asserts leading to loss of access to data when the link used for IP Replication experiences packet loss and the data transfer rate occasionally drops to zero. (S1) APAR-HU Loss of access to data when moving volumes to another IO group using the GUI. (S1) APAR-HU Loss of access to data when adding a Global Mirror Change Volume relationship to a consistency group on the primary site, when the secondary site does not have a secondary volume defined. (S1) APAR-HU Loss of access to data when SAN connectivity problems leads to backend controller being detected as incorrect type. (S1) FLASH-15207, Repeated interface panics due to a bad interface cable can cause unnecessary component failures. (S2) FLASH-14793, A flashcard can become unresponsive when array certify is running while hardware errors are being found. (S2) FLASH-12271, The RAID controller was falsely marked as "failed" instead of a flashcard in a particular double flashcard failure scenario. (S2) FLASH Unexpected Input/output (I/O) errors causes controller node assertions every 30 minutes. APAR-HU Multiple node asserts when using a Metro Mirror or Global Mirror volume that is greater than 128TB. (S2) APAR-HU Single node assert due to bug in 16GB fibre channel adapter firmware. (S2) Version

18 APAR-II Reduced performance for volumes which have the configuration node as their preferred node due to GUI processing the update of volume attributes where there is a large number of changes required. (S2) APAR-HU IP Replication does not return to using full throughput following packet loss on IP link used for replication. (S2) APAR-HU Global Mirror with Change Volumes freeze time reported incorrectly. (S2) APAR-HU Single node assert due to invalid VDisk memory allocation pointer. (S2) FLASH Flash fail due to node timeout. (S3) FLASH Flash failure due to GWY/Node CRC errors. (S3) FLASH Flash card failures due to unexpected power off. (S3) FLASH Mitigation for flashcard encryptor error. (S3) FLASH Improve signal integrity between canisters. (S3) FLASH-12758, Latency spikes caused by encryption key validation. (S3) APAR-HU Read/write performance latencies due to high CPU utilization from Easy Tier 3 processes on the configuration node. (S3) APAR-HU Performance statistics BBCZ counter values reported incorrectly. (S3) APAR-HU The serial number value displayed in the GUI node properties dialog is incorrect. (S3) APAR-HU The Volumes by Pool display in the GUI shows incorrect Easy Tier status. (S3) APAR-HU GUI response slow when filtering a large number of volumes. (S3) APAR-HU The catxmlspec CLI command (used by external monitoring applications such as Spectrum Control Base) not working. (S3) Release The following issue was fixed in release : FLASH This release includes one fix which addresses an array rebuild omission issue found in the IBM FlashSystem V9000 for 5.7 TB flash modules. (S1) Release The following issues were fixed in release : FLASH Improved handling of retention scan. (S1) FLASH Fixed canister warm start connection issue. (S2) FLASH Node goes into service state with error 564 after exiting service state with error 657 due to double battery removal. (S2) FLASH Improved handling of canister failover during a CCU for canisters at different firmware levels. (S2) FLASH Improved array reaction to simultaneous flash and interface failure. (S2) FLASH Encryption validation supported for larger environments. (S3) FLASH Improvements made to interface behavior during cable pulls and host connects and disconnects. (S3) FLASH Issuingcharraymember command can cause node failover. (S3) FLASH Improved behavior of batteries upon re-insertion. (S3) FLASH Changed default snap to not include historical stats to their reduce size. (S4) FLASH Call home event spamming on successful read retries fixed. (S4) FLASH Interface DRAM ECC failure incorrectly flags flash failure fixed. (S4) FLASH-10079, Improved output displayed for lsarraymemberprogress command. (S4) FLASH Improved Flash during CCU from code version (S4) FLASH Fixed array creation in the management GUI s setup wizard. (S4) FLASH Adjusted enclosure WWPN displayed information on the DMP for error code (S4) FLASH Improved error reporting for enclosure canister failure. (S4) FLASH Improved CLI reporting after canister failover. (S4) FLASH Irrelevant cabling events are no longer reported after upgrading. (S4) 18 Copyright IBM Corporation 2016