IBM System Storage SAN Volume Controller ++++++++++++++++++++++++++++++++++++++++ ------------------------------------------------------------------------------- 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.1.0.11 of the IBM System Storage SAN Volume Controller . This release of software is a service release and 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/2145 ------------------------------------------------------------------------------- 2. Available Education A course on SAN Volume Controller Planning and Implementation is available. 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 nodes 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 If you are running a version of SVC software older than 6.1.0.0 then you will have to perform multiple upgrades to install the 7.1.0 software on your system. Please see the following web page for the full upgrade compatibility matrix. http://www-01.ibm.com/support/docview.wss?uid=ssg1S1001707 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 Direct upgrades to V7.1 from V6.1 are supported only for systems that do not have iSCSI configured. For these upgrade paths it is mandatory that the SAN Volume Controller and Storwize V7000 Software Upgrade Test Utility is run prior to the upgrade. This will ensure that the system configuration does not include iSCSI, permitting the upgrade to be applied. http://www.ibm.com/support/docview.wss?uid=ssg1S4000585 When upgrading an existing system running V6.3 or earlier to V6.4, an alert will be logged for each node installed with 10Gb Ethernet hardware, indicating that the FCoE functionality has not yet been enabled. The alert is: - Node error : 841 (as seen on node front panel or service assistant) - Cluster error: 1199 (as seen using system management GUI/CLI) - Description : Detected hardware needs activation These alerts are expected and do not indicate an actual error. Any 10Gb iSCSI functions previously in use continue to operate as normal. Once the system software upgrade has completed, the FCoE functionality can be enabled on each node by following the fix procedures for these events using the management GUI. Note that the FCoE activation procedure involves a node reboot and it is therefore recommended to allow time for host multipathing to recover between activation of different nodes in the same I/O group. Refer to the following Flash for further information: http://www.ibm.com/support/docview.wss?uid=ssg1S1004195 It is not possible to activate the FCoE function if the system has a remote copy partnership with another system which is running a software release earlier than 6.4.0.0 ------------------------------------------------------------------------------- 5. Software Levels 2145 Software: 2145 Release Level 7.1.0.11 (80.5.1410080000) ------------------------------------------------------------------------------- 6. Problems Resolved and New Features New features in 7.1.0 Support for SAS hosts Second Fibre Channel HBA Ability to configure FC ports for specific traffic types This release contains all fixes included in the 6.4.1.4 release. Issues resolved in this release (7.1.0.11): Bash vulnerabilities CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187, CVE-2014-6277, CVE-2014-6278 APARs resolved in previous 7.1.x releases: 7.1.0.10 OpenSSL vulnerability CVE-2014-0224 7.1.0.9 OpenSSL vulnerabilities (CVE-2014-0160 and CVE-2014-0076) 7.1.0.8 Critical Fixes HU00178 Loss of access to data when expanding volume size of an offline compressed volume High Importance Fixes HU00161 Daily configuration backup not being distributed to non configuration nodes HU00220 Security issue CVE-2014-0880 HU00226 Offline compressed volume caused by fault during automatic space reclamation Suggested Fixes HU00242 Host workloads can generate a large amount of compression metadata on disk, reducing compression savings APARs resolved in previous 7.1.x releases: 7.1.0.7 High Importance Fixes HU00137 Long I/O wait following path failure of V7000 behind SVC HU00145 Node warmstart triggered by livedump taking too long to complete HU00167 Node assert due to decompression issue Suggested Fixes HU00069 IERR log file incorrectly generated on power loss 7.1.0.6 Critical Fixes IC92390 Node asserts whilst processing multiple SCSI CAW commands HU00016 Node error 578 caused by a large number of failed SSH connections on 7.1.0 High Importance Fixes HU00121 Node assert due to memory issues when using compressed volumes HU00123 Compressed Volume offline after running repairsevdiskcopy Suggested Fixes IC89214 Fibre channel logins fail to establish between clusters due to dropped FC frames 7.1.0.5 Critical Fixes HU00002 Multiple node asserts during upgrades when using VMware hosts with VAAI HU00014 Multiple repeated node asserts when large numbers of volume-to-host mappings are created HU00018 Node asserts when FlashCopy bitmaps reside in different IO group than FlashCopy source volumes HU00021 IO group-wide performance impacts when receiving large numbers of aborts from hosts 7.1.0.3 Critical Fixes IC93153 Loss of host access caused by mishandling of SCSI Persistent reserves during upgrades IC94405 Global Mirror Change Volume target not correctly updated with source data when relationship is stopped if the source volume is in any FlashCopy maps other than those managed by Global Mirror High Importance Fixes IC92386 Node assert when software upgrade completes on system with mirrored thin provisioned volumes IC94322 Node error 588 on 7.1.0 systems IC94935 Node assert when an I/O is sent beyond the end of a compressed volume IC94937 Node assert due to timing window when using compression 7.1.0.2 Critical Fixes IC91058 Multiple node asserts when fixing an event log entry if more than 5 event log entries have the root sequence number of the event being fixed IC91425 Multiple node asserts when moving a volume that is the target of a stopping FlashCopy map to another IO group Suggested Fixes IC90824 Configuration backup could only be run by superuser 7.1.0.1 Critical Fixes IC88865 Loss of access to data when system is logging a very large number of errors about backend storage IC90295 Node warmstarts during migrations caused by persistent reservations on image mode managed disks IC90476 Loss of access to data when an LDAP server 0 is not configured IC90637 Node warmstarts caused by RNID frames sent to FCoE ports from SAN management tool IC90872 Multiple node warmstarts caused by slow I/O from backend storage IC91255 Using two or more FlashCopy maps with the same target volume may result in inconsistent data on the target volume High Importance Fixes IC83241 Single node warmstart due to delays processing Global Mirror IOs IC86399 Single node warmstart when significantly increasing the size of a volume IC86591 Slow response time when host fails to send data after system sends XFER_RDY IC86971 Global Mirror slowdown when host fails to send data after system sends XFER_RDY IC87048 Single node warmstart due to inter-cluster communication issues IC88869 iSCSI Performance issues IC90060 Single node warmstart caused by timing window in EasyTier IC90442 Single node warmstart caused by unexpected settings in FCP frame IC90821 Single node warmstart caused by frequent GUI logins IC92028 Cache not sending enough IOs to compression IC92138 Single node assert when force deleting a volume involved in FlashCopy maps IC92803 Single node assert caused by SCSI Compare and Write command Suggested Fixes IC93083 Flash Copy exceeds configured background copy rate IC93088 1625 errors when removing unmanaged mdisk IC84694 Incorrect Fix Procedure for 1840 event IC82729 1692 Fix Procedure not marking event as fixed IC86279 Incorrect title for Edit Port panel in iSCSI GUI IC86505 Fibre Channel ports will not function if connected to a switch port with a Domain ID ending in 'FF' IC87229 GUI shows empty tables when CPU utilisation is high IC87339 GUI dialog hangs at Synchronizing memory cache after changing enclosure ID IC88220 Slow boot time and possible node warmstart during the detection of ethernet ports IC89378 DS3000, DS4000 and DS5000 managed disks not using preferred controller IC89661 Unable to create snap package if too many files exist IC91142 Temporarily unable to create FlashCopy of Global Mirror Change Volume Secondary volume after stopping the Global Mirror IC91336 Intel FCoE software initiator fails to detect LUNS IC91993 GUI shows wrong Metro/Global Mirror direction when stopped IC92075 Single node assert due to resource leak in FCoE driver ------------------------------------------------------------------------------- 7. Further Documentation The latest version of all SAN Volume Controller documentation can be downloaded from the support website: http://www.ibm.com/storage/support/2145 ------------------------------------------------------------------------------- 8. Known Issues and Restrictions in this Level 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 Inter-cluster Metro Mirror and Global Mirror Compatibility Cross Reference Refer to the following flash for more information on this restriction: 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 a SAN Volume Controller or Storwize V7000 Code 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.1.0 are documented in the SVC 7.1 Configuration Limits and Restrictions document which is available from: http://www-01.ibm.com/support/docview.wss?rs=591&uid=ssg1S1004368 ------------------------------------------------------------------------------- 10. Supported Hardware This release of SAN Volume Controller software is supported on the following node hardware types: * 2145-CG8 * 2145-CF8 * 2145-8G4 * 2145-8A4 * 2145-8F4 * 2145-8F2 -------------------------------------------------------------------------------