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 a.. 1 Support for hardware components for Model Availability of code load Availability of the Technician Assistant tool Availability of Host Attachment Kits (HAK) Limitations Enhancements SYS SYS SYS SYS SYS Fixed 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 SYS SYS SYS Known issues SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS XIV logo LED 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 7 Mar 2013 What's new in IBM XIV software version a IBM XIV software version a for IBM XIV Storage System Gen3 delivers the following performance enhancements over previous models: 1. Up to 5 times performance increase in iscsi throughput with 10 Gigabit Ethernet (GbE) ports 2. Up to 4.5 times performance boost for database-like workloads with SSD read-caching (optional) 3. Sequential read performance as high as 13.7 GB/s 4. Support for Windows Server 2012, including space reclamation 5. Drive rebuild times as fast as 26 minutes for a fully utilized 2 TB hard disk drive under heavy load 6. Features enhancements in: Security, Hot upgrade, System health monitoring & validation, Traces & logs 7. Improvements intended to reduce the possibility of loss of or damage to data. Support for hardware components for Model 214 Availability of code load 1. Up to twelve 10GbE ports for connecting to iscsi-attached hosts or twenty-two 1GbE ports 2. Up to 15 CPUs providing ninety physical cores (180 logical cores using Intel Hyper-Threading technology) 3. More energy-efficient hardware that can reduce power consumption by up to 16% compared to previous models 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.xiv.doc/xiv_po_11_1_02.html Availability of the Technician Assistant tool The following Technician Assistant version is supported in this release: v Version 4.6 or newer. Availability of Host Attachment Kits (HAK) The latest IBM XIV Host Attachment Kit (HAK) version can be downloaded from the IBM Fix Central website: Copyright IBM Corp

6 For detailed usage information, refer to the IBM Storage Host Software Solutions Information Center: Limitations This version is supported only on IBM XIV Gen3 Storage System models. Enhancements SYS Increase the maximum number of targets from 8 to SYS Adding monitoring of flow control to external Ethernet ports. Medium SYS XIV introduces a support for up to 512 consistency groups per System SYS The support_center_define XCLI command is no longer available for the user. Medium SYS The all_mapping_list XCLI command is not available in user level and up 2 IBM XIV Gen3 Storage System: Release Notes for version Second edition

7 Fixed issues SYS Writing to the remote system during synchronous mirroring, older data may overrun newer data, if the older write is aborted, redirected and executed after the newer write. High impact and up SYS Module guided repair corrupts the Switch routing tables, thus disconnects some of the Modules. HYPER SYS Data migration: under certain circumstances, when performing a Data Migration without a source update, incorrect data may be stored on the XIV Storage System. HYPER and up SYS Firmware upgrade leaves the system in maintenance mode. HYPER SYS Resizing a volume immediately after the last snapshot is deleted may lead to a data corruption. HYPER , a, b, SYS The Infiniband Master SM memory leak issue can create a condition where a module fails after a specific time (for example, 224 days after a code load). High impact Release Notes 3

8 and up SYS Writing to the remote system during asynchronous mirroring, older data may overrun newer data, if the write to the mirror fails and soon after the data is updated by the host. HYPER and up SYS In a system that has SSD caching and either the vol_copy XCLI command was used, or a snapshot was unlocked and written to, and in addition suffered from an SSD drive failure, or disk failure, the data cached on the SSD may be corrupted. Workaround Customers who do not use the Volume Copy command and do not unlock snapshots are not exposed. HYPER , a, b, SYS The SSD_DOES_NOT_EXIST event is erroneously sent for failed modules and up SYS Running the dns_test XCLI command results, for each DNS server, with an A record for servers specified as IPv4 addresses and an AAAA record for servers specified as IPv6 addresses. The expected result is both A and AAAA records for each server, regardless of the IP version and up. SYS Configuring an IP interface with an IPv4 address, then trying to disable IPv4 by setting the address to will not work. The original IPv4 address will be kept and up 4 IBM XIV Gen3 Storage System: Release Notes for version Second edition

9 SYS Data migration configuration using Target ports is not supported. It is however possible, causing an error message without system impact and up SYS Infiniband switch failure leads to a loss of access. Medium SYS Asynchronously mirroring an empty consistency group on the master with an empty consistency group on the slave (for the purpose of populating the master consistency group with volumes that will be mirrored) and then rebooting the master, breaks the mirroring and up SYS In case of inefficiencies in the fabric configurations, the host might lose one of the paths to XIV due to many login/logouts commands sent simultaneously, leading to a high memory consumption. The path becomes automatically available, resetting the memory consumption and up SYS Internal error message and command failure will appear when running the ipsec_generate_certificate_request XCLI command before running the ipsec_generate_key XCLI command. Moderate and up SYS Infiniband card failure leads to a loss of access. Release Notes 5

10 Medium SYS The Cache node fails due to a disk error. Medium a, b, b-1, SYS The Subnet Monitor does not update the routing tables upon a change to the fabric. Medium SYS An event indicating that the Switch voltage is back to normal is missing SYS On rare occasions after hot upgrade, the CF content might be corrupted SYS On rare occasions, running an LDAP XCLI command might result in INTERNAL_ERROR, Details: Internal error SYS Infiniband connectivity between the modules might get stuck due to hardware errors. 6 IBM XIV Gen3 Storage System: Release Notes for version Second edition

11 SYS On HPUX, runnig the unmap_volume XCLI command followed by the map_volume XCLI command on the very same LUN ID takes a long time to complete, since the system doesn't send the correct unit-attentions b. SYS The mirror_deactivate XCLI command return an error for consistency group. Medium SYS Deleting an ad-hoc sync job times out SYS Mirroring relations are not synchronized after an hot upgrade SYS XRay collection impacts the system's performance SYS The ldap_search XCLI command is now available for the user. Medium b Release Notes 7

12 Known issues SYS No notification is seen in case the Manager is handling a critical issue in the system (such as double disk failure) SYS Reoccurring IPSEC_TUNNEL_CLOSED and IPSEC_TUNNEL_OPENED events may appear when an IPsec tunnel is open. Customers are advised to ignore these events and up SYS On rare occasions during a failover, a service might fail and will not be able to automatically restart and up SYS Systems may only be able to allocate about 99% of their capacity to storage pools. High impact and a 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. 8 IBM XIV Gen3 Storage System: Release Notes for version Second edition

13 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 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 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 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 When an SNMP server is defined by the server's DNS name, only its IPv4 address records are looked up and used. Release Notes 9

14 Workaround To communicate with an SNMP server that supports only IPv6, use its IPv6 address rather than the host name 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 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 and up SYS The ILLEGAL_BITS_VALUE completion code is returned whenever the length of a private key is not a multiply of 8. Minor 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 10 IBM XIV Gen3 Storage System: Release Notes for version Second edition

15 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. 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. Trivial SYS When a pool is changed from thin to thick or from thick to thin, a SCSI Unit Attention is not raised. SYS Downsizing a storage pool does not free the hard capacity. Medium SYS Running the host_update XCLI command with the iscsi_chap_name parameter without specifying the -y flag, the command may fail. Workaround Make sure you specify the -y flag. Trivial Release Notes 11

16 SYS Entering several certificates to the certificate parameter, ipsec_connection_* XCLI commands process 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. 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. Minor SYS GB Ethernet systems allow to define ports 3 and 4, although they are not defined as 10GB. Workaround Do not define these ports for a 10GB system. Medium 12 IBM XIV Gen3 Storage System: Release Notes for version Second edition

17 Copyrights SYS The GUI might become overloaded when connected to more then 8 XIV systems. Minor 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. 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 - An irrecoverable error with potential loss data. v Serious - An irrecoverable error with potential loss of access to data. 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: Release Notes 13

18 Documentation format Notices and trademarks Notices 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. 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 14 IBM XIV Gen3 Storage System: Release Notes for version Second edition

19 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 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 15

20 16 IBM XIV Gen3 Storage System: Release Notes for version Second edition

21

22 Printed in USA