IBM Storwize V5000 ++++++++++++++++++++++++++++++++++++++++ ------------------------------------------------------------------------------- CONTENTS 1. Introduction 2. Available Education 3. Pre-Requisites 4. System Upgrade Information 5. Software Levels 6. Problems Resolved and New Features 7. Further Documentation 8. Known Issues and Restrictions in this Level 9. Maximum Configurations 10. Supported Hardware ------------------------------------------------------------------------------- 1. Introduction This document describes how to install version 7.2.0.10 of the IBM Storwize V5000. This release delivers fixes to resolve the APARs detailed in section 6. Please refer to the Recommended Software List and Supported Hardware List on the support website: http://www.ibm.com/storage/support/storwize/v5000 ------------------------------------------------------------------------------- 2. Available Education For further information or enrolment, contact your local IBM representative. Visit the support website for online learning materials and tutorials, IBM Redbooks and training information. ------------------------------------------------------------------------------- 3. Pre-Requisites Before installing this software level please check the following pre-requisites are met. Also please note the concurrent upgrade (upgrade with I/O running) restrictions. Performance of the system will be degraded during the software upgrade process while node canisters are taken offline to perform the upgrade and the write cache is flushed when each node is restarted. IBM recommends you perform the upgrade at a time of lower overall I/O activity and when you do not expect significant spikes in the system workload. If you are performing a concurrent software upgrade, you must first ensure that all host paths are available and operating correctly. Check there are no unfixed errors in the event log or in the service GUI. Use normal service procedures to resolve any errors before proceeding. Before upgrading, IBM recommends using the software upgrade test utility "upgradetest". Refer to the following URL for further information: http://www.ibm.com/support/docview.wss?uid=ssg1S4000585 Please see the following web page for the full upgrade compatibility matrix. http://www.ibm.com/support/docview.wss?uid=ssg1S1004336 Note: Once an upgrade has completed, it is not possible to downgrade the software to an earlier level without deleting and manually rebuilding the system in its entirety, including restoring all volume data from an external backup. ------------------------------------------------------------------------------- 4. System Upgrade Information IMPORTANT: Systems with the 10 Gb/s Ethernet adapter will take longer to upgrade each node when installing 7.2.0 for the first time. This is due to an upgrade of the firmware on this adapter, and each node canister may take around 40 minutes to complete the upgrade. This additional delay will not affect systems upgrading from V7.2.0.x to a later release of 7.2.0. Global Mirror Relationships Must Be Stopped When Upgrading to V7.2.0 http://www-01.ibm.com/support/docview.wss?uid=ssg1S1004472 ------------------------------------------------------------------------------- 5. Software Levels 2077/2078 Software: 2077/2078 Release Level 7.2.0.10 (88.0.1411100000) ------------------------------------------------------------------------------- 6. Problems Resolved and New Features New features in 7.2.0 * Multi-drive firmware download * Configurable port masking * Global Mirror performance improvements * Direct-attached SAS migration from IBM DS3000 storage subsystems * Support for remote copy replication using native IP links New in 7.2.0.1 * Multi-language support New in 7.2.0.6 * Increased write throughput due to full stride write enhancements * SCSI WriteSame to drives has been disabled to improve performance of writing zeros to drives. Note this may slow down initialisation of arrays under some scenarios. This does not affect SCSI WriteSame from hosts to the system. This release contains all fixes included in the 7.1.0.6 release. Issues resolved in this release (7.2.0.10): SSL vulnerability CVE-2014-3566 APARs resolved in previous 7.2.x releases: 7.2.0.9 Bash vulnerabilities CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187, CVE-2014-6277, CVE-2014-6278 7.2.0.8 Critical Fixes HU00280 Multiple node asserts triggered by a Global Mirror disconnection HU00450 Manual upgrade with stopped Global Mirror relationships can not complete non-disruptively due to dependent volumes High Importance Fixes HU00176 Node assert due to an IO deadlock when using the remote copy functions HU00253 Global Mirror with Change Volumes does not resume copying after an IO group goes offline at secondary cluster HU00264 Node assert caused by an AIX host logout colliding with a new SCSI check condition being generated HU00274 Quiesce and resume of host IO when Global Mirror consistency group reaches consistent_synchronized HU00293 Node canister fails to boot after hard shutdown IC90374 Node assert due to a IO deadlock when using the FlashCopy functions Suggested Fixes HU00109 Fix procedure for 1920 Global Mirror event fails to resolve the issue HU00134 Stopped Global Mirror Change Volumes relationship cannot be added to a stopped consistency group HU00223 Fix procedure for 1685 failed to leave drives in correct state HU00241 GUI runs out of resources to issue commands to the system HU00252 Service Assistant GUI fails to run commands with a message that the user is not logged in as superuser HU00272 RAID resync progress incorrectly reported as 0% after upgrade 7.2.0.7 OpenSSL vulnerability CVE-2014-0224 High Importance Fixes HU00348 Offline MDiskgroup when using Thin Provisioning 7.2.0.6 Critical Fixes HU00126 Multiple node asserts after node failures if using thin provisioning HU00191 Multiple node asserts if iSCSI alias contains one or more spaces HU00245 Multiple node asserts when secondary system running 7.2.0 and systems become disconnected HU00275 Multiple node asserts when secondary system running 7.2.0 and systems become disconnected High Importance Fixes HU00254 Single node assert when two systems disconnect from each other HU00270 Unnecessary delays during node restarts Suggested Fixes HU00027 iSCSI performance degradation with large application I/O operations HU00175 Performance degradation when cache gets stuck at 80% full HU00246 Global Mirror Secondary Write Lag performance metric reported in microseconds instead of milliseconds on 7.2.0 secondary clusters HU00258 Global Mirror Change Volumes on secondary system do not automatically shrink when running V7.2.0 HU00260 Global Mirror internal tracing insufficient for problem determination in certain scenarios APARs resolved in previous 7.2.x releases: 7.2.0.5 OpenSSL vulnerabilities (CVE-2014-0160 and CVE-2014-0076) 7.2.0.4 Suggested Fixes HU00256 Invalid output on STDERR causing TPC probes to fail on V7.2.0.0 or later 7.2.0.3 High Importance Fixes HU00220 Security issue CVE-2014-0880 7.2.0.2 Critical Fixes HU00230 Loss of access to data when stopping Metro/Global Mirror relationships on 7.2.0.1 High Importance Fixes HU00160 Node asserts during Global Mirror replication HU00161 Daily configuration backup not being distributed to non configuration nodes HU00229 Node assert caused by lock contention APARs resolved in previous 7.2.x releases: 7.2.0.1 NONE 7.2.0.0 Critical Fixes HU00014 Loss of access to data in systems with a large number of volumes mapped to hosts HU00019 Multiple node asserts when inter-canister link can not be initialised IC88865 Node asserts caused by handling excessive number of faults from backend storage IC90476 Node asserts if the ldap server with id 0 is not configured IC91332 No configuration node after upgrading with GMCV active IC92665 Node assert when an iSCSI initiator has the same IQN as the iSCSI target High Importance Fixes HU00132 Node assert when repairing killsectors on RAID 10 arrays IC87264 Node assert caused by timing window shortly after starting an incremental FlashCopy IC89608 Node assert caused by XCOPY command to a recently offline volume IC91336 Unable to detect Storwize LUNs when connecting backend storage using FCoE IC94392 System was returning different messages for invalid username and invalid password IC95107 Node assert when large numbers of space efficient volumes come online at the same time on a single node Suggested Fixes HU00069 IERR log file incorrectly generated on power loss HU00108 GUI incorrectly warns that certain ldap username strings are invalid HU00110 GUI issues command without details in progress dialog HU00112 GUI fails to complete operations, with no way to close the task dialog box HU00127 Incorrect progress information for Global Mirror with Change Volumes HU00129 System not clearing up old enclosure dumps HU00169 Too many error log dumps stored on a node IC92993 Drive replacement DMP failed to fix drive that was dead on arrival IC93080 Unexpected enclosure in system after Cluster Recovery (T3) procedure IC94781 Health status pod not auto-updating when issues are resolved ------------------------------------------------------------------------------- 7. Further Documentation The latest version of all Storwize V5000 documentation can be downloaded from the support website: http://www.ibm.com/storage/support/storwize/v5000 ------------------------------------------------------------------------------- 8. Known Issues and Restrictions in this Level If using IP replication, please review the set of restrictions published in the V7.2 Configuration Limits and Restrictions document. Moving Volumes to Another I/O Group Without Stopping Host Activity is Not Supported for All Operating Systems http://www.ibm.com/support/docview.wss?uid=ssg1S1004125 Intra-Cluster Global Mirror Not Supported Refer to the following flash for more information on this restriction: http://www.ibm.com/support/docview.wss?uid=ssg1S1003725 SAN Volume Controller or Storwize Family Inter-cluster Metro Mirror and Global Mirror Compatibility Cross Reference http://www.ibm.com/support/docview.wss?uid=ssg1S1003646 Use of a standards-compliant browser, such as Firefox, is recommended for using the SVC Management GUI. Use of Internet Explorer is supported but may result in slower performance of the GUI. If an upgrade stalls or fails then Contact IBM Support for Further Assistance http://www.ibm.com/support/docview.wss?uid=ssg1S1002894 ------------------------------------------------------------------------------- 9. Maximum Configurations The maximum configurations for 7.2.0 are documented in the 7.2 Configuration Limits and Restrictions document which is available from: http://www-01.ibm.com/support/docview.wss?rs=591&uid=ssg1S1004512 ------------------------------------------------------------------------------- 10. Supported Hardware This release of Storwize V5000 software is supported on the following node hardware types: Control enclosures: * 2077-12C * 2077-24C * 2078-12C * 2078-24C Expansion enclosures: * 2077-12E * 2077-24E * 2078-12E * 2078-24E -------------------------------------------------------------------------------