------------------------------------------------------------------------------- Software name IBM Storwize V7000 for Lenovo Controller Firmware Update Bundle Supported Model System name IBM Storwize V7000 for Lenovo Version 8.1.3.6 Issue date Apr 25, 2019 Prerequisites: None ------------------------------------------------------------------------------- WHAT THIS PACKAGE DOES ------------------------------------------------------------------------------- This firmware update enables you to update the controller firmware via; 1. IBM Storwize V7000 for Lenovo - Web User Interface. 2. IBM Storwize V7000 for Lenovo - Command Line Interface (CLI). ------------------------------------------------------------------------------- Version history ------------------------------------------------------------------------------- The following versions of Controller Firmware that been released to date. Summary of Changes Where: < > Package version [Important] Important update (New) New function or enhancement (Fix) Correction to existing function - [Important] The following issues have been resolved with this release: When creating a Hyperswap relationship using addvolumecopy, or similar methods, the system should perform a synchronisation operation to copy the data of the original copy to the new copy. In some cases this synchronisation is skipped, leaving the new copy with bad data (all zeros) (HU01865) - HyperSwap Where systems are connected to controllers, that have FC ports that are capable of acting as initiators and targets, when NPIV is enabled then node warmstarts can occur (HU01876) - Backend Storage When FlashCopy mappings are created, with a grain size of 64KB, it is possible for an overflow condition in the bitmap to occur. This can resulting in multiple node warmstarts with a possible loss of access to data (HU01910) - FlashCopy When two IOs attempt to access the same address, the state of the data may be incorrectly set to invalid causing offline volumes and, possibly, offline pools (HU01928) - Data Reduction Pools Due to an issue in Data Reduction Pools, when the system attempts an upgrade, there may be node warmstarts (HU01957) - Data Reduction Pools, System Update IO performance may be adversely affected towards the end of DRAID rebuilds. For some systems there may be multiple warmstarts leading to a loss of access (IT25850) - Distributed RAID Lease expiry can occur between local nodes when remote connection is lost, due to the mishandling of messaging credits (IT27460) - Reliability Availability Serviceability Until the initial synchronisation process completes, high system latency may be experienced when a volume is created with two compressed copies or when space-efficient copy is added to a volume with an existing compressed copy (HU01507) - Volume Mirroring Entering multiple addmdisk commands, in rapid succession, to more than one storage pool, may cause node warmstarts (HU01761) - Backend Storage The Unmap function can leave volume extents, that have not been freed, preventing managed disk and pool removal (HU01886) - SCSI Unmap When an array is in a quiescing state, for example where a member has been deleted, IO may become pended leading to multiple warmstarts (HU01972) - RAID, Distributed RAID Due to a timing window issue, stopping a FlashCopy mapping, with the -autodelete option, may result in a Tier 2 recovery (HU01617) - FlashCopy A timing window issue in the DRAID6 rebuild process can cause node warmstarts with the possibility of a loss of access (HU01913) - Distributed RAID Where Data Reduction Pools have been created on earlier code levels, upgrading the system, to an affected release, can cause an increase in the level of concurrent flushing to disk. This may result in a loss of access to data (HU01918) - Data Reduction Pools - (Fix) The following issues have been resolved with this release: Single node warmstart due to an accounting issue within the cache component (HU00744) Volume copy deletion, in a DRP, triggered by rmvdiskcopy rmvolumecopy or addvdiskcopy -autodelete (or similar) may become stalled with the copy being left in "deleting" status (HU01869) - Data Reduction Pools Systems, with encryption enabled, that are using key servers to manage encryption keys, may fail to connect to the key servers if the servers' SSL certificates are part of a chain of trust (HU01795) - Encryption The GUI Dashboard and the CLI lssystem command report physical capacity incorrectly (HU01916) - Graphical User Interface, Command Line Interface Timing window issue in the DRP rehoming component can cause a single node warmstart (IT28433) - Data Reduction Pools The system is unable to authenticate SKLM key servers if a chain of signed certificates have been installed on the key servers (IT28654) - Encryption - [Important] The following issues have been resolved with this release: Where Data Reduction Pools have been created on earlier code levels, upgrading the system, to an affected release, can cause an increase in the level of concurrent flushing to disk. This may result in a loss of access to data (HU01918) - Data Reduction Pools - (New) The following new feature has been introduced in the 8.1.3.4 release: Write Cache optimization for Data Reduction Pools. (Note: This means that the write cache fullness for Data Reduction Pools will be lower than for standard pools) - [Important] The following issues have been resolved with this release: Invoking a chrcrelationship command, when one of the relationships in a consistency group is running in the opposite direction to the others, may cause a node warmstart followed by a T2 recovery (HU01825) - FlashCopy Clusters using Data Reduction Pools can experience multiple warmstarts, on all nodes, putting them in a service state (HU01855) - Data Reduction Pools When a Data Reduction Pool is removed and the -force option is specified there may be a temporary loss of access (HU01862) - Data Reduction Pools During an upgrade from v7.8.1 or earlier to v8.1.3 or later if a mdisk goes offline then at completion all volumes may go offline (HU01878) - System Update As writes are made to a Data Reduction Pool it is necessary to allocate new physical capacity. Under unusual circumstances it is possible for the handling of an expansion request to stall further IO leading to node warmstarts (HU01885) - Data Reduction Pools A cache-protection mechanism flag setting can become stuck leading to repeated stops of consistency group synchronisation (HU01661) - HyperSwap Hitachi G1500 backend controllers may exhibit higher than expected latency (HU01797) - Backend Storage Switching replication direction, for HyperSwap relationships, can lead to long IO timeouts (HU01824) - HyperSwap Bursts of IO to Samsung Read-Intensive Drives can be interpreted as dropped frames, against the resident slots, leading to redundant drives being incorrectly failed (HU01842) - Drives - (Fix) The following issues have been resolved with this release: FlashCopy map progress appears to be stuck at zero percent (HU01760) - FlashCopy An issue, in the HBA adapter, is exposed where a switch port keeps the link active but does not respond to link resets resulting in a node warmstart (HU01778) - Reliability Availability Serviceability An issue in the monitoring of SSD write endurance can result in false 1215/2560 errors in the Event Log (HU01786) - Drives Using the chhost command will remove stored CHAP secrets (HU01791) - iSCSI An issue in the HBA adapter firmware may result in node warmstarts (IT22591) - Reliability Availability Serviceability Attempting to remove a copy of a volume which has at least one image mode copy and at least one thin/compressed copy in a Data Reduction Pool will always fail with a CMMVC8971E error (IT25457) - Data Reduction Pools - [Important] The following issues have been resolved with this release: Node warmstarts may occur during deletion of deduplicated volumes, due to a timing-related issue (HU01828) - Deduplication FlashCopy handling of medium errors, across a number of drives on backend controllers, may lead to multiple node warmstarts (HU01847) - FlashCopy When the last deduplication-enabled volume copy, in a Data Reduction Pool, is deleted the pool may go offline temporarily (HU01850) - Data Reduction Pools, Deduplication The garbage collection rate can lead to Data Reduction Pools running out of space even though reclaimable capacity is available (HU01852) - Data Reduction Pools Total used capacity of a Data Reduction Pool, within a single I/O group, is limited to 256TB. Garbage collection does not correctly recognise this limit. This may lead to a pool running out of free capacity and going offline (HU01858) - Data Reduction Pools LDAP server communication fails with SSL or TLS security configured (HU01870) - LDAP - (Fix) The following issues have been resolved with this release: On the "Create Volumes" page the "Accessible I/O Groups" selection may not update when the "Caching I/O group" selection is changed (HU01790) - Graphical User Interface In Data Reduction Pools, volume size is limited to 96TB (HU01815) - Data Reduction Pools - [Important] The following issues have been resolved with this release: When a deduplicated volume is deleted there may be multiple node warmstarts and offline pools (HU01851) - Deduplication In systems, where a VVols metadata volume has been created, an upgrade to v8.1.3 or later will cause a node warmstart, stalling the upgrade (HU01837) - VVols, System Update - [Important] The following issues have been resolved with this release: Multiple warmstarts may be experienced due to an issue with DRP garbage collection where data for a volume is detected after the volume itself has been removed (HU01835) - Data Reduction Pools An issue in statistical data collection can prevent Easy Tier from working with Data Reduction Pools (HU01829) - EasyTier, Data Reduction Pools When removing large numbers of volumes each with multiple copies it is possible to hit a timeout condition leading to warmstarts (HU01840) - SCSI Unmap - (New) The following new features have been introduced in 8.1.3 release: Support for deduplicated volumes RESTful API support Enhanced Call Home - [Important] The following issues have been resolved with this release: A node removal operation during an array rebuild can cause a loss of parity data leading to bad blocks (HU01708) - RAID After a failed mkhost command for an iSCSI host any IO from that host will cause multiple warmstarts (HU01774) - iSCSI Migrating a volume to an image-mode volume on controllers that support (unmap will trigger repeated cluster recoveries (HU01780) - SCSI Unmap Manual (user-paced) upgrade to 8.1.2 may invalidate hardened data putting all nodes in service state if they are shutdown and then restarted. Automatic upgrade is not affected by this issue (HU01798) - System Update USB encryption key can become inaccessible after upgrade. If the system is later rebooted then any encrypted volumes will be unavailable HU01802 (HU01802) - Encryption During a system upgrade the processing required to upgrade the internal mapping between volumes and volume copies can lead to high latency impacting host IO (HU01804) - System Update, Hosts An issue in the handling of extent allocation in Data Reduction Pools can result in volumes being taken offline (HU01809) - Data Reduction Pools A problem with the way IBM FlashSystem FS900 handles SCSI WRITE SAME commands (without the Unmap bit set) can lead to port exclusions (HU01752) - Backend Storage An issue with CPU sharing between compression and other components can result in a node warmstarts that impact performance (HU01781) - Compression Excessive debug logging in the Data Reduction Pools component can adversely impact system performance (HU01818) - Data Reduction Pools - (Fix) The following issues have been resolved with this release: If during an array rebuild another drive fails the high processing demand in RAID for handling many medium errors during the rebuild can lead to a node warmstart (HU01460) - RAID An IO lock handling issue between nodes can lead to a single node warmstart (HU01724) - RAID A thread locking issue in the Remote Copy component may cause a node warmstart (HU01795) Under some rare circumstance a node warmstart may occur whilst creating volumes in a Data Reduction Pool (HU01800) - Data Reduction Pools An issue in the handling of unmaps for mdisks can lead to a node warmstart (HU01801) - SCSI Unmap When an unusual IO request pattern is received it is possible for the handling of Data Redution Pool metadata to become stuck, leading to a node warmstart (HU01820) - Data Reduction Pools Whilst replacing a control enclosure midplane, an issue at boot can prevent VPD being assigned, delaying a return to service (IT24900) - Reliability Availability Serviceability ------------------------------------------------------------------------------- Limitations and considerations ------------------------------------------------------------------------------- Customers using the REST API to list more than 2000 objects may experience a loss of service from the API as it restarts due to memory constraints. This is a restriction that may be lifted in a future PTF. ------------------------------------------------------------------------------- It is not possible to access the REST API using a cluster's IPv6 address. This is a restriction that may be lifted in a future PTF. ------------------------------------------------------------------------------- TRADEMARKS ----------------------------------------------------------------------------- * The following are registered trademarks of Lenovo. Lenovo The Lenovo Logo ThinkServer * Intel is a registered trademark of Intel Corporation. * Microsoft and Windows are registered trademarks of Microsoft Corporation. * IBM is a registered trademark of International Business Machines Other company, product, and service names may be registered trademarks, trademarks or service marks of others. LENOVO PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. Lenovo may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. BY FURNISHING THIS DOCUMENT, LENOVO GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. (C) Copyright Lenovo 2001-2018. All rights reserved.