IBM Storwize V7000 ++++++++++++++++++ ------------------------------------------------------------------------------- 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 6.4.1.5 of the Storwize V7000 (2076) software. This release of software is a new release and delivers new features in addition to resolving APARs as 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/V7000 ------------------------------------------------------------------------------- 2. Available Education A course on Storwize V7000 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 node canisters are taken offline to perform the upgrade and the write cache is flushed when each node canister 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 code upgrade, you must first ensure that all host paths are available and operating correctly. Check there are no unfixed errors in the event log. Use normal service procedures to resolve any errors before proceeding. Before upgrading, we recommend 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=ssg1S1003705 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 When upgrading an existing system to 6.4.x, an alert will be logged for each node canister installed with 10Gb Ethernet hardware, indicating that the FCoE functionality has not yet been enabled. The alert is: - Node error : 841 (as seen using the service assistant GUI/CLI) - 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. 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.x ------------------------------------------------------------------------------- 5. Code Levels 2076 Software: 2076 Release Level 6.4.1.5 (75.8.1307290000) ------------------------------------------------------------------------------- 6. Problems Resolved and New Features New features in Storwize V7000 6.4.1.0 None APARs resolved in this release (6.4.1.5): Critical Fixes IC88865 Loss of access to data when system is logging a very large number of errors about backend storage IC90637 Node warmstarts caused by RNID frames sent to FCoE ports from SAN management tool IC91255 Using two or more FlashCopy maps with the same target volume may result in inconsistent data on the target volume IC91064 Node asserts caused by memory leak in iSCSI IC91058 Node asserts when fixing event logs entries that have more than 5 associated events 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 IC88869 iSCSI Performance issues IC92028 Cache not sending enough IOs to compression IC92803 Single node assert caused by SCSI Compare and Write command IC91644 Increased write latency during high bandwidth read activity Suggested Fixes IC87229 GUI shows empty tables when CPU utilisation is high IC89378 DS3000, DS4000 and DS5000 managed disks not using preferred controller IC90771 Drive replacement fix procedure does not remove old drive IC91142 Temporarily unable to create FlashCopy of Global Mirror Change Volume Secondary volume after stopping the Global Mirror APARs resolved in previous 6.4.x releases: 6.4.1.4 Critical Fixes IC83684 Prevent hardware issue on one node canister from affecting the other node canister in the enclosure IC89463 Loss of access to data during upgrade if a FC target is involved in a Metro/Global Mirror relationship IC89865 Loss of access to data during an upgrade if an unbalanced array exists during the upgrade IC90822 Mirrored thin provisioned volumes will not always survive the loss of a single copy High Importance Fixes IC86860 Single node assert during upgrade to 6.4.x IC89902 A combination of failures on a drive causes an array to go offline IC90455 Node assert when a SCSI compare and write times out Suggested Fixes IC90246 Metro/Global Mirror relationships cannot be started 6.4.1.3 Critical Fixes IC89206 Hitachi storage system LUNs offline after upgrade to 6.4.1.2 IC89355 Loss of access to hosts using SCSI3 persistent reservations during upgrades to 6.4.x High Importance Fixes IC89102 GUI inaccessible when web browser locale set to unsupported language IC89224 Multiple node asserts when handling excessively delayed SCSI Compare and Write commands (VMware VAAI) Suggested Fixes IC86270 Incomplete highlighting in GUI of newly host-mapped volumes APARs resolved in previous 6.4.x releases: 6.4.1.2 High Importance Fixes IC86864 Unexpected node reboot during enclosure firmware download IC87158 Repeated node asserts due to excessive numbers of SSH connections 6.4.1.1 None 6.4.1.0 Critical Fixes IC81045 Offline node canisters due to internal enclosure communication issues IC81273 All nodes assert simultaneously when a Global Mirror Change Volume is created using the volume ID of a volume that had previously been a FlashCopy target of a volume in a remote copy relationship IC81418 All nodes assert simultaneously when a migration of a volume to image mode fails IC81942 Performance degradation when array scrub is active IC82222 Node canister left cluster unexpectedly IC83420 Node assert and loss of CLI/GUI access when a FlashCopy map stop command is issued while autodelete is enabled IC84731 DS3000 and DS4000 MDisks >2TB in size taken offline after upgrading to 6.4.0.0 IC84736 All nodes assert simultaneously when deleting a cluster partnership IC84869 Multiple node asserts when using VMware VAAI with 6.4.0.x IC84909 iSCSI hosts unable to clear SCSI-2 reservations IC85294 Node assert when using iSCSI host attachment IC86533 Multiple node asserts when starting a FlashCopy map whose target volume is both the target of another FlashCopy map and the primary volume for a Remote Copy relationship IC86602 Multiple node asserts caused by corrupt VPD IC86702 Faulty enclosure PSU causes enclosure offline IC87152 All nodes assert simultaneously when running lsdependentvdisks during an upgrade from 5.1.0 IC87343 Multiple node asserts when starting large numbers of remote copy relationships in parallel High Importance Fixes IC78453 Incorrect FlashCopy consistency groups stopping IC80224 Performance impact due to GUI resource issue IC81042 Image mode to image mode migration fails IC81757 Offline mdisk triggered by storage controller transport errors IC83129 Node assert and loss of CLI/GUI when setting time to invalid value using CLI command setsystemtime IC83241 Node assert caused by sequence number processing delays in Global Mirror IC83628 Node assert due to internal thin provisioning allocation IC84697 Degraded iSCSI performance on node Ethernet port 2 issue IC85692 Node assert when using SCSI Compare and Write (VMware VAAI) IC85744 Node assert when using SCSI Compare and Write (VMware VAAI) IC86059 Taking an incremental FlashCopy of a Global Mirror Change Volume target volume may result in a data integrity issue IC86220 Node asserts when exceeding maximum limit of WWPN connections to HP storage devices IC87100 Node assert caused by offline change volume at auxiliary site IC88060 Node assert caused by FlashCopy map with an offline target volume IC88061 Not using all paths to a storage system after an upgrade Suggested Fixes IC79220 Migration task progress not automatically updated in GUI IC79278 GUI volume capacity not rounded to two decimal places IC81729 Node assert when receiving SCSI Inquiry C2 command from unmapped host IC82729 Fix procedure unable to clear 1692 errors IC83053 Node assert due to internal locking issue IC83059 Cannot access Service GUI of non-configuration node after node software downgrade IC83455 FlashCopy incorrectly identified as containing a dependent remote copy relationship in GUI if duplicate volume name exists in remote cluster and that volume is in a remote copy relationship IC83470 Tier 3 recovery fails due to use of admin rather than superuser role IC83624 Incorrect FlashCopy license errors when using Global Mirror with Change Volumes IC84388 UDID of volumes mapped to OpenVMS hosts lost after Cluster Error 1001 IC84814 Unexpected cache synchronous destage events during normal operation IC85056 iSCSI Hosts will now show as online if a host has a login to all mapped IO groups IC85387 Bad blocks may be falsely reported as data inconsistency on RAID arrays IC85435 Incorrect WWPN values in CLI and GUI views after upgrade to 6.4.0 IC85708 Unable to collect Debug Data through GUI if java heapdump exists IC86219 Node assert during T3 recovery when remote authentication user has been configured without SSH key IC86221 GMT+6 timezone missing from GUI IC86505 Fibre channel port will not log into the switch if NportID ends with 0xff IC86836 Fix procedure unable to fix 3015 error ------------------------------------------------------------------------------- 7. Further Documentation The latest version of all Storwize V7000 documentation can be downloaded in PDF format from the support website: http://www.ibm.com/storage/support/storwize/V7000 ------------------------------------------------------------------------------- 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 Refer to the following technote for more information on this restriction: http://www.ibm.com/support/docview.wss?uid=ssg1S1004125 Global Mirror Relationships Must Be Stopped Before Reading From Auxiliary Change Volumes Refer to the following technote for more information on this restriction: http://www.ibm.com/support/docview.wss?uid=ssg1S1003947 Intra-Cluster Global Mirror Not Supported With V6.x Code Refer to the following flash for more information on this restriction: http://www.ibm.com/support/docview.wss?uid=ssg1S1003725 Please read the following flashes before upgrading: http://www.ibm.com/support/docview.wss?uid=ssg1S1004124 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 Use of a standards-compliant browser, such as Firefox, is recommended for using the Storwize V7000 Management GUI. Use of Internet Explorer is supported but may result in slower performance of the GUI. ------------------------------------------------------------------------------- 9. Maximum Configurations The maximum configurations for Storwize V7000 6.4.1.3 are documented in the IBM Storwize V7000 6.4 Configuration Limits and Restrictions document which is available from: http://www.ibm.com/support/docview.wss?uid=ssg1S1004114 ------------------------------------------------------------------------------- 10. Supported Hardware This release of Storwize V7000 software is supported on the following hardware types: Control enclosures: * 2076-112 * 2076-124 * 2076-312 * 2076-324 Expansion enclosures: * 2076-212 * 2076-224 -------------------------------------------------------------------------------