1 of 10 6/5/2015 1:12 PM This is the release note for the 7.5.0 release and details the issues resolved in all Program Temporary Fixes (PTFs) between 7.5.0.0 and 7.5.0.0. This document will be updated with additional information whenever a new PTF is released. This document was last updated on 5 June 2015. 1. New Features 2. Known Issues and Restrictions 3. Issues Resolved 3.1. Security Issues Resolved 3.2. APARs Resolved 4. Useful Links Note. Detailed build version numbers are included in the Update Matrices in the Useful Links section The following new features have been introduced in the 7.5.0.0 release: Multi Site Volumes (HyperSwap) Priority Flow Control (lossless ethernet support for 10GB iscsi ports) Increase in number of concurrent SSH connections supported Easy Tier 3 migration rate improvement Optimizing Easy Tier 3 warm demote VMware version 6 support (support for vvols will be added in a future PTF) 16GB FC direct attach IP partnership, service assistant ping to help debug connection problems Microsoft offloaded data transfers (MS ODX) support
2 of 10 6/5/2015 1:12 PM Increased FlashCopy bitmap space Child pool volume migration & ownership Software upgrade test utility changes '-iogrp' now optional flag for mkvdisk command Volume Fast Format Fast granularity I/O throttling - part 1 Note: For clarity, the term "node" will be used to refer to a SAN Volume Controller node or Storwize system node canister. Details Systems with more than 512 WWPNs in a single host object must reconfigure the host before upgrading to V7.5.0. Introduced 7.5.0.0 Refer to this Technote for more information on this restriction Software update to V7.5.0. may fail if the system date is set to any date prior to December 2014 with the following message: CMMVC6347E The specific update package cannot be installed on this hardware level Updates from releases prior to 7.4.0.0, to 7.4.0.0 or later will be required to run an additional update step (if the nodes contain 8GB or more RAM). The update will complete in the following order: 7.4.0.0 1. 2. Phase one is a standard update, taking approximately 30 minutes per node plus a 30 minute wait half way through the update (e.g. 4.5 hours for a system with 8 nodes or 4 control enclosures) Once the standard update has completed, the system will then wait for the user to validate that multi-pathing has recovered successfully. The system will log an event in the event log indicating that the update still needs to complete an extra step. 3. The user should follow the Fix Procedure for the event to allow the second phase to start 4. In phase two, each node in the system is then warm started one at a time. This will take approximately 2 minutes per node plus an additional 30 minutes wait half way through. (e.g. 45 minutes for a system with 8 nodes or 4 control enclosures)
3 of 10 6/5/2015 1:12 PM Details Introduced 5. 6. Once the second phase of the update has completed, the system will perform firmware updates to any enclosures attached to the system When the firmware update has updated all of the enclosure components, the update is complete. The GUI will provide step-by-step progress of this update, or it can be monitored using the new lsupdate command. Systems running V6.4.0 or earlier will be have to perform multiple updates to install release V7.5.0. Please see the appropriate update matrix for your product to determine the correct set of updates required. 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. For Systems using IP replication and running V7.4.0.0 or later. SVC/Storwize software is designed to throttle back the replication throughput if packet loss is seen on an IP link used for replication. After the throughput has been reduced, it will not be increase again. To work around this issue, stop then restart the remote partnership which will increase the throughput. This issue will be addressed in future PTF under APAR HU00745. Starting with V7.4.0.0, the $IFS special bash variable ("Internal Field Separator") is read-only. In previous releases, authenticated SSH users could change the $IFS variable, to help parse Command Line Interface (CLI) output which might contain spaces in object names. To avoid potential security issues, an attempt to change $IFS will fail with the message "rbash: IFS: readonly variable " Scripts which use $IFS will need to be refactored -- for example, they could process the CLI output on a host system, instead of doing so on the CLI itself. Alternatively, they could use the read -d option to parse CLI output with a particular field separator. Using the software update test utility before installing an update is mandatory. Failing to successfully run the utility will result in the update failing with the following message: 7.4.0.0 7.4.0.0 7.4.0.0 7.3.0.4 CMMVC5996E The specific upgrade package cannot be installed over the current version Updates from releases prior to V7.3.0, to V7.3.0 or later will disable the cache when the update starts and the cache will remain disabled until the update completes, at which time it will be automatically re-enabled. Global Mirror relationships must be stopped when upgrading to V7.4.0 or later 7.3.0.0 7.2.0.0 Refer to this flash for more information on this restriction An automatic update may stall if the Enhanced Stretched System function is configured on a system with exactly four 7.2.0.0
4 of 10 6/5/2015 1:12 PM Details nodes and non-mirrored VDisks. It is therefore recommended to update such systems using the manual update procedure documented in the Knowledge Center. This does not apply to conventional Stretched Systems or Enhanced Stretched Systems with two, six or eight nodes. This also does not apply to enhanced stretched systems that solely contain mirrored VDisks with a copy in both site 1 and site 2 document for your product. 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 SAN Volume Controller node replacement procedure Introduced 7.1.0.0 6.4.0.0 Refer to this flash for more information on this restriction Intra-System Global Mirror not supported 6.1.0.0 Refer to this flash for more information on this restriction Host Disconnects Using VMware vsphere 5.5.0 Update 2 and vsphere 6.0 Refer to this flash for more information If an update stalls or fails then Contact IBM Support for Further Assistance The following restrictions were valid for previous PTFs, but have now been lifted This release contains all of the fixes included in the 7.4.0.4 release, plus the following additional fixes. A release may contain fixes for security issues, fixes for APARs or both. Consult both tables below to understand the complete set of fixes included in the release. 3.1 Security Issues Resolved
5 of 10 6/5/2015 1:12 PM Security issues are documented using a reference number provided by "Common Vulnerabilities and Exposures" (CVE). CVE Identifier Link for additional Information Resolved in Select Versions None LINK 3.2 APARs Resolved Show details for all APARs APAR Affected Products Severity Description Resolved in Feature Tags Select Products Select Severity Select Versions Select Tags HU00499 SVC, V7000, V5000, V3700 HU00804 V7000, V5000, V3700, V3500 HIPER Critical Loss of access to data when a volume that is part of a Global Mirror Change Volumes relationship is removed with the 'force' flag. Loss of access to data due to SAS recovery mechanism operating on both nodes in IO group simultaneously (show HU00638 All Critical Multiple node asserts when there is high backend latency (show HU00671 V7000, V5000, V3700, V3500 Critical 1691 RAID parity incorrect due to memory copy limitiation (show 7.5.0.0 Global Mirror With Change Volumes 7.5.0.0 7.5.0.0 Hosts 7.5.0.0 Backend Storage
6 of 10 6/5/2015 1:12 PM APAR Affected Products Severity Description Resolved in Feature Tags Select Severity HU00764 All Critical Loss of access to data due to persistent reserve host registration keys exceeding the current supported value of 256 HU00811 SVC, V7000, V5000 Critical Loss of access to data when SAN connectivity problems leads to backend controller being detected as incorrect type HU00281 All High Importance Single node assert due to internal code exception 7.5.0.0 Hosts 7.5.0.0 Backend Storage 7.5.0.0 HU00519 SVC, V7000, V5000, V3700 High Importance Single node assert due to flash copy deadlock condition HU00644 All High Importance Multiple node asserts when node port recieves duplicate frames during a specific IO timing window HU00659 SVC, V7000, V5000, V3700 High Importance Global Mirror with Change Volumes freeze time reported incorrectly 7.5.0.0 FlashCopy 7.5.0.0 HU00673 V7000, V5000, V3700, High Importance Drive slot is not 7.5.0.0 7.5.0.0 Global Mirror With Change Volumes
7 of 10 6/5/2015 1:12 PM APAR Affected Products Severity Description Resolved in Feature Tags Select Severity V3500 recognised following 'drive auto manage' procedure HU00675 All High Importance Node assert following node start up/restart due to invalid CAW domain state HU00726 SVC, V7000, V5000 High Importance Single node assert due to stuck IO following offline mdisk group condition HU00735 All High Importance Host IO statistics incorrectly including logically failed writes HU00806 SVC, V7000 High Importance mkarray command fails when creating an encrypted array due to pending bitmap state HU00807 SVC, V7000, V5000, V3700 HU00468 V7000, V5000, V3700, V3500 High Importance Suggested Increase in node cpu usage due to FlashCopy mappings with high cleaning rate (show Drive firmware task not removed from GUI 'running tasks' display following completion of drive firmware update 7.5.0.0 7.5.0.0 Storage Virtualisation 7.5.0.0 System Monitoring 7.5.0.0 Encryption 7.5.0.0 FlashCopy 7.5.0.0 Graphical User Interface
8 of 10 6/5/2015 1:12 PM APAR Affected Products Severity Description Resolved in Feature Tags Select Severity action HU00525 All Suggested Unable to manually mark 'monitoring' events in the event log as fixed (show HU00737 All Suggested GUI does not warn of lack of space condition when collecting a Snap, this results in some files missing from the Snap HU00805 V7000, V5000, V3700, V3500 Suggested Some SAS ports are displayed in hexadecimal values instead of decimal values in the performance statistics xml files HU00808 All Suggested NTP trace logs not collected on configuration node (show IC92356 V7000 Suggested Improve DMP for handling 2500 event for V7000 using Unified storage 7.5.0.0 System Monitoring 7.5.0.0 Graphical User Interface 7.5.0.0 System Monitoring 7.5.0.0 Support Data Collection 7.5.0.0 Graphical User Interface Description Link
9 of 10 6/5/2015 1:12 PM Description Link Support Websites SAN Volume Controller Storwize V7000 Storwize V5000 Storwize V3700 Storwize V3500 Update Matrices, including detailed build version SAN Volume Controller Storwize V7000 Storwize V5000 Storwize V3700 Storwize V3500 Support Information pages providing links to the following information: Interoperability information Product documentation Limitations and restrictions, including maximum configuration limits SAN Volume Controller Storwize V7000 Storwize V5000 Storwize V3700 Storwize V3500 Supported Drive Types and Firmware Levels V7000 V5000 V3500 & V3700 SAN Volume Controller and Storwize Family Inter-cluster Metro Mirror and Global Mirror Compatibility All Products
10 of 10 6/5/2015 1:12 PM Description Cross Reference Software Upgrade Test Utility Link All Products