IBM XIV Gen3 Storage System. Release Notes for version Second edition

Transcription

1 IBM XIV Gen3 Storage System Release Notes for version Second edition

2

3 Contents Release Notes What's new in IBM XIV software version Availability of code load Availability of Host Attachment Kits (HAK) Miscellaneous Limitations Known issues SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS XIV logo LED Fixed issues SYS SYS SYS SYS Copyrights Definitions of problem severity Contacting IBM Support Documentation format Notices and trademarks Copyright IBM Corp iii

4 iv IBM XIV Gen3 Storage System: Release Notes for version Second edition

5 Release Notes These release notes are for IBM XIV Gen3 Storage System Version Release date 27 June 2013 What's new in IBM XIV software version Availability of code load IBM XIV software version for IBM XIV Storage System Gen3 delivers the following: IBM Hyper-Scale Mobility IBM Hyper-Scale Mobility is a powerful new feature that enables migration of a volume from one XIV frame to another with no interference to host applications. IBM Hyper-Scale Mobility helps streamline operational processes that typically challenge traditional systems, including capacity over-provisioning (with thinly-provisioned systems), load balancing among multiple systems, and technology refresh scenarios (e.g. array decommissioning). IBM Hyper-Scale Mobility brings dramatic operational flexibility to data centers and helps clients address scalability and management requirements for effective cloud computing. Key values: v IBM Hyper-Scale Mobility facilitates efficient placement of data on storage systems in a manner that is transparent to host applications v IBM Hyper-Scale Mobility minimizes downtime and administrative effort typically warranted under the following use case scenarios: A specific volume needs be migrated to another frame Capacity is over-provisioned and storage space is depleted Storage in multiple systems needs be load-balanced Support for 4TB drives IBM XIV software version features support for 4TB drives. Support for 4TB drives increases the system's maximum usable capacity per rack up to 325TB and reduces the TCO/Power per TB. Systems featuring 4 TB disk drive modules have 48 GB RAM per module. This version supports code load from all versions since The following topic, Preparing for code load, is available on the Information Center, detailing the steps required from the customer in order to prepare for the code load. com.ibm.help.xivgen3.doc/gen3/xiv_po_11_1_02.html Availability of Host Attachment Kits (HAK) IBM XIV Host Attachment Kit The latest IBM XIV Host Attachment Kit (HAK) version can be downloaded from the IBM Fix Central website: support/fixcentral Copyright IBM Corp

6 IBM Storage Host Software Solutions Information Center For detailed usage information, refer to the IBM Storage Host Software Solutions Information Center: strhosts/ic. Miscellaneous Limitations v The total number of hosts available for use is 994. v Systems with up to 3 failed drives can be upgraded. v The vol_mapping_list command is allowed for all users with read-only permission. v Systems featuring 4 TB disk drive modules have a maximum pool size capacity of 325 TB. v The total number of mirroring-related volumes on a single system includes IBM Hyper-Scale Mobility (non-proxy), and cannot exceed 1, IBM Hyper-Scale Mobility applies to systems located within the same data center. 2. Using Hyper-Scale Mobility to mobilize volumes that are mapped to Unix or Linux hosts, and are backed-up using IBM Tivoli Storage FlashCopy Manager version 3.2 or earlier, is not supported. 3. IBM Hyper-Scale Mobility cannot be applied directly on a volume that belongs to a consistency group. Before such a volume can be moved using IBM Hyper-Scale Mobility, it must be removed from the consistency group. 4. IBM Hyper-Scale Mobility does not apply to volume snapshots. When the migration is changed to proxy state, all snapshots of the pertinent migrated volume are deleted automatically. 5. IBM Hyper-Scale Mobility does not migrate a volume that is in a mirroring relationships. Before a volume can be moved using IBM Hyper-Scale Mobility, its mirroring relationship must be deleted. 6. Using Hyper-Scale Mobility to mobilize volumes that are mapped to Windows Server hosts, and are backed-up using Microsoft Volume Shadow Copy, with IBM XIV Provider for Microsoft Windows Volume Shadow Copy (VSS) version or earlier, is not supported. To use Hyper-Scale Mobility in this case, IBM XIV Provider for Microsoft Windows Volume Shadow Copy (VSS) version or later must be installed. Note: IBM Tivoli Storage FlashCopy Manager for Windows is relying on Microsoft Volume Shadow Copy. To use Hyper-Scale Mobility with IBM Tivoli Storage FlashCopy Manager for Windows, IBM XIV Provider for Microsoft Windows Volume Shadow Copy (VSS) version or later must be installed. 7. Using Hyper-Scale Mobility to mobilize volumes that are mapped to Windows Server hosts, and are protected by IBM Storage Enabler for Windows Failover Clustering version or earlier, is not supported. To use Hyper-Scale Mobility in this case, IBM Storage Enabler for Windows Failover Clustering version or later must be installed. Additional information may be available from the respective release notes of the products mentioned in the limitations: 2 IBM XIV Gen3 Storage System: Release Notes for version Second edition

7 1. For IBM Tivoli Storage FlashCopy Manager for Unix and Linux please refer to release notes of version 4.1 or later. 2. For IBM XIV Provider for Microsoft Windows Volume Shadow Copy release notes, please refer to: topic/com.ibm.help.strghosts.doc/vss-homepage.html. 3. For IBM Storage Enabler for Windows Failover Clustering, release notes, please refer to: %2Fcom.ibm.help.strghosts.doc%2Fmscs-homepage.html. Known issues SYS When an SNMP server is defined by the server's DNS name, only its IPv4 address records are looked up and used. Workaround: To communicate with an SNMP server that supports only IPv6, use its IPv6 address rather than the host name. : Affected version: and up SYS In rare cases, during Hot Upgrade procedure, Unit Attention is not sent to the hosts. The SCSI protocol uses Unit Attentions as a means for the storage controller to communicate with the host. When one host releases a LUN reservation, all other hosts that work with this LUN receive a Unit Attention updating them that they can access the data again. The Unit Attention arrives at the host as a response the next time the host issues an IO. The problem occurs whenever there was a code load between the time the unit attention was created and the time it is sent to the host. Moderate : and up. SYS Under very heavy ESX load, an unresponsive module may cause loss of access to hosts. This is a known ESX issue that was fixed in ESX version 4.1. RE VMWare ticket: KB Moderate : and up. Release Notes 3

8 SYS A delay during XIV boot can be detected in the XCLI session. During that time, XCLI commands can only be accessed using a developer account. Workaround Contact XIV Support. Moderate : and up. SYS The IBM XIV Storage System works around various NTP issues by blocking NTP-driven time changes that are larger than 2 hours. For accurate time management, initially set the time to the correct value using the time_set XCLI command. After that, the system-clock will be well adjusted by NTP : and up. SYS The list of events reported by an event_list XCLI command via one management IP address may be different comparing to running the same command via another management IP address. : and up. SYS The GUI erroneously displays hosts that are deleted from the system. When a new host is added, the position on the statistics is reused and the new host will be shown. : and up. SYS Events sent to the Center via SMTP are sent through the Management IP interface, instead of the VPN interface. Workaround When configuring the VPN interface netmask, consider Center's subnet as well. 4 IBM XIV Gen3 Storage System: Release Notes for version Second edition

9 : and up. SYS The ILLEGAL_BITS_VALUE completion code is returned whenever the length of a private key is not a multiply of 8. SYS The newline parameter of the pki_set_pkcs12 SSL import command does not support an * as a value. Workaround: Use the -w0 parameter when using the base64. For example:{{base64 -w0 mycert.pfx}}. : Minor Affected version: SYS Asynchronous mirroring: whenever the clocks of the master and slave systems differ by a gap that is greater than the RPO, the slave enters an RPO lagging state, while the master is in an OK state. Workaround Double check that the clock is set correctly on both systems. Moderate SYS When using the ipinterface_create XCLI command, and providing an illegal module number, the command returns a completion code of an illegal port. Workaround Please do not create a port on modules that don't have interfaces for this, or that don't exist. SYS Running the host_update XCLI command with the iscsi_chap_name parameter without specifying the -y flag, the command may fail. Release Notes 5

10 Workaround: Make sure you specify the -y flag. : Affected version: SYS Entering several certificates to the certificate parameter, ipsec_connection_* XCLI commands processes only the first certificate. Workaround Execute the relevant XCLI command for one certificate at a time. Medium SYS The Cache node may fail on any of the following scenarios: v v v Reactivating an asynchronous mirroring during initialization after pool depletion during rebuild / redist and performing IOS to the mirrored volume. Activating an asynchronous mirroring offline initialization during rebuild / redist and performing IOS to the mirrored volume. Reactivating an synchronous mirroring after the slave has changed role to master and back during rebuild / redist by running the snapshot_create XCLI command and performing IOS to the mirrored volume. Impact Performance hit or statistics loss in case of more than one Cache node failure. High Impact SYS Resizing a pool (reducing its volume capacity) does not trigger the STORAGE_POOL_VOLUME_USAGE_INCREASED event when crossing the preset threshold. Workaround Pay special attention when resizing down a pool. 6 IBM XIV Gen3 Storage System: Release Notes for version Second edition

11 SYS When using IBM Hyper-Scale Mobility, on the Proxy phase, while the host is mapped to both the source volume and the destination volume (the source volume serves as a proxy to the destination), the system will not display a warning upon unmapping host from the proxy. Workaround: Prior to unmapping the Proxy, verify that: v The host is mapped to the volume on the Destination system v IOs are actually being executed on that path You can do that either from the host side or by using the XIV statistic tools on the Destination system. : Improvement Affected version: and up SYS Upon module's boot completion, the 8 BIOS indicator LEDs on the back are turned off. SYS The ipinterface_update XCLI command has no default value and cannot define an IPv6 address if an IPv4 address was not previously defined. Workaround: Set an IPv4 address to the VPN interface. Then, set an IPv6 address. : Affected version: SYS Specifying a very high initialization rate for IBM Hyper-Scale Mobility through the max_init_rate XCLI command might impact the host I/O rate. Workaround: To increase the rate of IBM Hyper-Scale Mobility migration, use the default initialization rate initially, and gradually increase the rate while observing host I/O rate. : Moderate Affected version: and up Release Notes 7

12 SYS The perf_class_list XCLI command does not display more than 55 hosts associated with a performance class. : Affected version: and up SYS The statistics reported by the system for the I/O rates between an IBM Hyper-Scale Mobility proxy system and its IBM Hyper-Scale Mobility destination system might be higher than those reported from the host to the proxy system. This results from host IOs broken down into several IOs between the proxy and the destination and up SYS The update_host XCLI command might fail if the y argument is not specified. Workaround Use the force option (-y) SYS The data migration commands dm_define and dm_activate might fail if the migration source is an XIV system with version Workaround: Wait 10 seconds, then run the command again. If the command does not execute successfully after the first retry, retry again (up to the maximum number of connections from the first gateway to the data migration source system). : Affected version: and up SYS When a host is mapped to a volume in Proxy state, and also mapped to that volume s destination volume on another system, if connectivity is lost between the systems, host I/Os to the destination volume might not get a response for up to 1 minute. 8 IBM XIV Gen3 Storage System: Release Notes for version Second edition

13 Workaround Ensure that both systems are connected with a full redundancy FC network (going through two separate FC switches). High impact SYS When using IBM Hyper-Scale Mobility, during the Proxy phase, while the host is mapped to both the source volume and the destination volume (the source volume serves as a proxy to the destination), if the user tries to delete the target using the target_delete XCLI command, the command succeeds without cleaning up the proxy volumes. Workaround: Delete a target only after deleting all volumes in Proxy state using that target. : Affected version: and up SYS The number of spare drives reported by the system may be wrong. This does not affect the ability of the system to use the spare capacity. SYS SCSI Unit attentions might not be delivered correctly in an IBM Hyper-Scale Mobility environment. Please contact IBM service if you plan to use IBM Hyper-Scale Mobility in a clustered environment. High impact SYS Creating an IBM Hyper-Scale Mobility relationship on a system where a migration target has been deleted can lead to loss of access. Workaround Do not delete a target that has been used for IBM Hyper-Scale Mobility relationships. Release Notes 9

14 Fixed issues High impact XIV logo LED In rare cases and only in strong presence of a 150 MHz-induced radio frequency (RF) pulse toward the XIV system (types 114 and 214), the LED-lighted logo on the front door might cause module 5 to report a high-temperature internal event; therefore, the cable that feeds the XIV front-door LED is intentionally disconnected. As a result, the XIV front-door LED is no longer lit. There is no customer impact, and no is action required. SYS When a pool is changed from thin to thick or from thick to thin, a SCSI Unit Attention is not raised. Moderate SYS Systems with 10GB interface cards allow the user to define 4 ports although only two ports exist. : SYS When a zone disconnects or changes during mirroring, target connectivity might not connect automatically. : and up SYS When using Data Migration without source updating and a read from the source volume fails, the XIV system may incorrectly indicate that the data on the source volume and target volume has been synchronized when, in fact, it is not. As a result, the data on the target volume on the XIV system might be incorrect. Should this occur, and the host has not yet overwritten the incorrect data by the time the system's periodical data scrubbing process (which can take up to 24 days 10 IBM XIV Gen3 Storage System: Release Notes for version Second edition

15 to complete depending on configuration) reaches the incorrect data, the scrub process is capable of detecting that the primary and secondary partitions differ and should alert IBM service personnel of the issue if the remote support features have been enabled on the system. Hyper : and up Copyrights Copyright IBM Corporation US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. References in this documentation to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program or service is not intended to state or imply that only IBM's product, program or service may be used. Any functionally equivalent product, program or service that does not infringe any of IBM's intellectual property rights may be used instead of the IBM product, program or service. Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, are the user's responsibility. Definitions of problem severity Contacting IBM Support The following definitions denote issues severity: High impact v Acute / Serious Acute - An irrecoverable error with potential loss of data. Serious - An irrecoverable error with potential loss of access to data. v HYPER - An high impact problem that is pervasive: 3 or more occurrences. Moderate A function not operational and/or performance might be degraded. A recoverable error (no impact) and service improvement. Improvements Changes made for the purpose of better usability and serviceability. The release is supported via: Voice calls Will come into Level 1 or Front Line Support as they do for the current product. Customers will use the appropriate support phone number for their respective countries; refer to the World Wide Directory for the support numbers by country. Release Notes 11

16 Documentation format Notices and trademarks Notices The publications for this product are in Adobe Portable Document Format (PDF) and should be compliant with accessibility standards. If you experience difficulties when you use the PDF files and want to request a web-based format or accessible PDF document for a publications, send a request by to starpubs@us.ibm.com. In the request, be sure to include the IBM publication number and title. When you sent information to IBM, you grant IBM a nonexclusive right to use to distribute the information in any way it believes appropriate without incurring any obligation to you. INTERNATIONAL BUSINESS MACHINES CORPORATION 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. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Trademarks Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, and Windows Server are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others. THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-english version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version. Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions: v the Excluded Components are provided on an "AS IS" basis 12 IBM XIV Gen3 Storage System: Release Notes for version Second edition

17 v v v IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE IBM will not be liable to you or indemnify you for any claims related to the Excluded Components IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components. Release Notes 13

18 14 IBM XIV Gen3 Storage System: Release Notes for version Second edition

19

20 Printed in USA