release notes for version 11.3.0 second edition - ibm · management requirements for effective...

IBM XIV Gen3 Storage System

Release Notes for version 11.3.0Second edition

��

Contents

Release Notes . . . . . . . . . . . . 1What's new in IBM XIV software version 11.3.0 . . . 1Availability of code load . . . . . . . . . . 1Availability of Host Attachment Kits (HAK) . . . . 1Miscellaneous . . . . . . . . . . . . . . 2Limitations . . . . . . . . . . . . . . . 2Known issues . . . . . . . . . . . . . . 3

SYS-34235 . . . . . . . . . . . . . . 3SYS-148227 . . . . . . . . . . . . . . 3SYS-152613 . . . . . . . . . . . . . . 3SYS-171172 . . . . . . . . . . . . . . 4SYS-172696 . . . . . . . . . . . . . . 4SYS-180287 . . . . . . . . . . . . . . 4SYS-191045 . . . . . . . . . . . . . . 4SYS-191368 . . . . . . . . . . . . . . 4SYS-244218 . . . . . . . . . . . . . . 5SYS-244455 . . . . . . . . . . . . . . 5SYS-248188 . . . . . . . . . . . . . . 5SYS-248452 . . . . . . . . . . . . . . 5SYS-252614 . . . . . . . . . . . . . . 5SYS-252743 . . . . . . . . . . . . . . 6SYS-252858 . . . . . . . . . . . . . . 6SYS-253004 . . . . . . . . . . . . . . 6SYS-257063 . . . . . . . . . . . . . . 7

SYS-259268 . . . . . . . . . . . . . . 7SYS-260214 . . . . . . . . . . . . . . 7SYS-261241 . . . . . . . . . . . . . . 7SYS-261265 . . . . . . . . . . . . . . 8SYS-261371 . . . . . . . . . . . . . . 8SYS-261516 . . . . . . . . . . . . . . 8SYS-261524 . . . . . . . . . . . . . . 8SYS-261545 . . . . . . . . . . . . . . 8SYS-261567 . . . . . . . . . . . . . . 9SYS-261828 . . . . . . . . . . . . . . 9SYS-261875 . . . . . . . . . . . . . . 9SYS-261890 . . . . . . . . . . . . . . 9XIV logo LED . . . . . . . . . . . . 10

Fixed issues . . . . . . . . . . . . . . 10SYS-251334 . . . . . . . . . . . . . 10SYS-254726 . . . . . . . . . . . . . 10SYS-255376 . . . . . . . . . . . . . 10SYS-260184 . . . . . . . . . . . . . 10

Copyrights . . . . . . . . . . . . . . 11Definitions of problem severity . . . . . . . . 11Contacting IBM Support . . . . . . . . . . 11Documentation format. . . . . . . . . . . 12Notices and trademarks . . . . . . . . . . 12

© Copyright IBM Corp. 2013 iii

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

Release Notes

These release notes are for IBM XIV Gen3 Storage System Version 11.3.0.

Release date27 June 2013

What's new in IBM XIV software version 11.3.0IBM XIV software version 11.3.0 for IBM XIV Storage System Gen3 delivers thefollowing:

IBM Hyper-Scale MobilityIBM Hyper-Scale Mobility is a powerful new feature that enables migrationof a volume from one XIV frame to another with no interference to hostapplications. IBM Hyper-Scale Mobility helps streamline operationalprocesses that typically challenge traditional systems, including capacityover-provisioning (with thinly-provisioned systems), load balancing amongmultiple systems, and technology refresh scenarios (e.g. arraydecommissioning). IBM Hyper-Scale Mobility brings dramatic operationalflexibility to data centers and helps clients address scalability andmanagement 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 applicationsv 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 drivesIBM XIV software version 11.3.0 features support for 4TB drives. Supportfor 4TB drives increases the system's maximum usable capacity per rack upto 325TB and reduces the TCO/Power per TB.

Systems featuring 4 TB disk drive modules have 48 GB RAM per module.

Availability of code loadThis version supports code load from all versions since 11.0.

The following topic, Preparing for code load, is available on the InformationCenter, detailing the steps required from the customer in order to prepare for thecode load. http://publib.boulder.ibm.com/infocenter/ibmxiv/r2/topic/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 bedownloaded from the IBM Fix Central website: http://www.ibm.com/support/fixcentral

© Copyright IBM Corp. 2013 1

http://publib.boulder.ibm.com/infocenter/ibmxiv/r2/topic/com.ibm.help.xivgen3.doc/Gen3/xiv_po_11_1_02.html

http://publib.boulder.ibm.com/infocenter/ibmxiv/r2/topic/com.ibm.help.xivgen3.doc/Gen3/xiv_po_11_1_02.html

http://www.ibm.com/support/fixcentral

http://www.ibm.com/support/fixcentral

IBM Storage Host Software Solutions Information CenterFor detailed usage information, refer to the IBM Storage Host SoftwareSolutions Information Center: http://publib.boulder.ibm.com/infocenter/strhosts/ic.

Miscellaneousv 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,536.

Limitations1. 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 Managerversion 3.2 or earlier, is not supported.

3. IBM Hyper-Scale Mobility cannot be applied directly on a volume that belongsto a consistency group. Before such a volume can be moved using IBMHyper-Scale Mobility, it must be removed from the consistency group.

4. IBM Hyper-Scale Mobility does not apply to volume snapshots. When themigration is changed to proxy state, all snapshots of the pertinent migratedvolume are deleted automatically.

5. IBM Hyper-Scale Mobility does not migrate a volume that is in a mirroringrelationships. 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 WindowsServer hosts, and are backed-up using Microsoft Volume Shadow Copy Service,with IBM XIV Provider for Microsoft Windows Volume Shadow Copy Service(VSS) version 2.3.2 or earlier, is not supported.To use Hyper-Scale Mobility in this case, IBM XIV Provider for MicrosoftWindows Volume Shadow Copy Service (VSS) version 2.4.0 or later must beinstalled.

Note: IBM Tivoli Storage FlashCopy Manager for Windows is relying onMicrosoft Volume Shadow Copy Service. To use Hyper-Scale Mobility with IBMTivoli Storage FlashCopy Manager for Windows, IBM XIV Provider forMicrosoft Windows Volume Shadow Copy Service (VSS) version 2.4.0 or latermust be installed.

7. Using Hyper-Scale Mobility to mobilize volumes that are mapped to WindowsServer hosts, and are protected by IBM Storage Enabler for Windows FailoverClustering version 1.1.0 or earlier, is not supported.To use Hyper-Scale Mobility in this case, IBM Storage Enabler for WindowsFailover Clustering version 1.2.0 or later must be installed.

Additional information may be available from the respective release notes of theproducts mentioned in the limitations:

2 IBM XIV Gen3 Storage System: Release Notes for version 11.3.0 Second edition

http://publib.boulder.ibm.com/infocenter/strhosts/ic

http://publib.boulder.ibm.com/infocenter/strhosts/ic

1. For IBM Tivoli Storage FlashCopy Manager for Unix and Linux please refer torelease notes of version 4.1 or later.

2. For IBM XIV Provider for Microsoft Windows Volume Shadow Copy Servicerelease notes, please refer to: http://pic.dhe.ibm.com/infocenter/strhosts/ic/topic/com.ibm.help.strghosts.doc/vss-homepage.html.

3. For IBM Storage Enabler for Windows Failover Clustering, release notes, pleaserefer to: http://pic.dhe.ibm.com/infocenter/strhosts/ic/index.jsp?topic=%2Fcom.ibm.help.strghosts.doc%2Fmscs-homepage.html.

Known issues

SYS-34235When an SNMP server is defined by the server's DNS name, only its IPv4 addressrecords are looked up and used.

Workaround:To communicate with an SNMP server that supports only IPv6, use itsIPv6 address rather than the host name.

Severity:Service

Affected version:11.1.0 and up

SYS-148227In rare cases, during Hot Upgrade procedure, Unit Attention is not sent to thehosts.

The SCSI protocol uses Unit Attentions as a means for the storage controller tocommunicate with the host. When one host releases a LUN reservation, all otherhosts that work with this LUN receive a Unit Attention updating them that theycan access the data again. The Unit Attention arrives at the host as a response thenext time the host issues an IO.

The problem occurs whenever there was a code load between the time the unitattention was created and the time it is sent to the host.

SeverityModerate

Affected versions:11.0.0 and up.

SYS-152613Under very heavy ESX load, an unresponsive module may cause loss of access tohosts. This is a known ESX issue that was fixed in ESX version 4.1.

RE VMWare ticket: KB1016626.

SeverityModerate


Release Notes 3

http://pic.dhe.ibm.com/infocenter/strhosts/ic/topic/com.ibm.help.strghosts.doc/vss-homepage.html

http://pic.dhe.ibm.com/infocenter/strhosts/ic/topic/com.ibm.help.strghosts.doc/vss-homepage.html

http://pic.dhe.ibm.com/infocenter/strhosts/ic/index.jsp?topic=%2Fcom.ibm.help.strghosts.doc%2Fmscs-homepage.html

http://pic.dhe.ibm.com/infocenter/strhosts/ic/index.jsp?topic=%2Fcom.ibm.help.strghosts.doc%2Fmscs-homepage.html

SYS-171172A delay during XIV boot can be detected in the XCLI session. During that time,XCLI commands can only be accessed using a developer account.

WorkaroundContact XIV Support.

SeverityModerate


SYS-172696The IBM XIV Storage System works around various NTP issues by blockingNTP-driven time changes that are larger than 2 hours. For accurate timemanagement, initially set the time to the correct value using the time_set XCLIcommand. After that, the system-clock will be well adjusted by NTP

SeverityService


SYS-180287The list of events reported by an event_list XCLI command via one managementIP address may be different comparing to running the same command via anothermanagement IP address.

SeverityService


SYS-191045The GUI erroneously displays hosts that are deleted from the system. When a newhost is added, the position on the statistics is reused and the new host will beshown.

SeverityService


SYS-191368Events sent to the Service Center via SMTP are sent through the Management IPinterface, instead of the VPN interface.

WorkaroundWhen configuring the VPN interface netmask, consider Service Center'ssubnet as well.

SeverityService



SYS-244218The ILLEGAL_BITS_VALUE completion code is returned whenever the length of aprivate key is not a multiply of 8.

SeverityService

Affected versions11.2.0 and up

SYS-244455The newline parameter of the pki_set_pkcs12 SSL import command does notsupport an * as a value.

Workaround:Use the -w0 parameter when using the base64. For example:{{base64 -w0myCert.pfx}}.

Severity:Minor


SYS-248188Asynchronous mirroring: whenever the clocks of the master and slave systemsdiffer by a gap that is greater than the RPO , the slave enters an RPO lagging state,while the master is in an OK state.

WorkaroundDouble check that the clock is set correctly on both systems.

SeverityModerate


SYS-248452When using the ipinterface_create XCLI command, and providing an illegalmodule number, the command returns a completion code of an illegal port.

WorkaroundPlease do not create a port on modules that don't have interfaces for this,or that don't exist.

SeverityService


SYS-252614Running the host_update XCLI command with the iscsi_chap_name parameterwithout specifying the -y flag, the command may fail.

Release Notes 5

Workaround:Make sure you specify the -y flag.

Severity:Service


SYS-252743Entering several certificates to the certificate parameter, ipsec_connection_*XCLI commands processes only the first certificate.

WorkaroundExecute the relevant XCLI command for one certificate at a time.

SeverityMedium


SYS-252858The Cache node may fail on any of the following scenarios:v Reactivating an asynchronous mirroring during initialization after pool depletion

during rebuild / redist and performing IOS to the mirrored volume.v Activating an asynchronous mirroring offline initialization during rebuild / redist

and performing IOS to the mirrored volume.v Reactivating an synchronous mirroring after the slave has changed role to

master and back during rebuild / redist by running the snapshot_create XCLIcommand and performing IOS to the mirrored volume.

ImpactPerformance hit or statistics loss in case of more than one Cache nodefailure.

SeverityHigh Impact


SYS-253004Resizing a pool (reducing its volume capacity) does not trigger theSTORAGE_POOL_VOLUME_USAGE_INCREASED event when crossing the preset threshold.

WorkaroundPay special attention when resizing down a pool.

SeverityService



SYS-257063When using IBM Hyper-Scale Mobility, on the Proxy phase, while the host ismapped to both the source volume and the destination volume (the source volumeserves as a proxy to the destination), the system will not display a warning uponunmapping host from the proxy.

Workaround:Prior to unmapping the Proxy, verify that:v The host is mapped to the volume on the Destination systemv IOs are actually being executed on that path

You can do that either from the host side or by using the XIV statistictools on the Destination system.

Severity:Improvement


SYS-259268Upon module's boot completion, the 8 BIOS indicator LEDs on the back are turnedoff.

SeverityService


SYS-260214The ipinterface_update XCLI command has no default value and cannot define anIPv6 address if an IPv4 address was not previously defined.

Workaround:Set an IPv4 address to the VPN interface. Then, set an IPv6 address.

Severity:Service


SYS-261241Specifying a very high initialization rate for IBM Hyper-Scale Mobility through themax_init_rate XCLI command might impact the host I/O rate.

Workaround:To increase the rate of IBM Hyper-Scale Mobility migration, use the defaultinitialization rate initially, and gradually increase the rate while observinghost I/O rate.

Severity:Moderate


Release Notes 7

SYS-261265The perf_class_list XCLI command does not display more than 55 hostsassociated with a performance class.

Severity:Service


SYS-261371The statistics reported by the system for the I/O rates between an IBMHyper-Scale Mobility proxy system and its IBM Hyper-Scale Mobility destinationsystem 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 andthe destination.

SeverityService


SYS-261516The update_host XCLI command might fail if the –y argument is not specified.

WorkaroundUse the force option (-y).

SeverityService

Affected versions11.0.0

SYS-261524The data migration commands dm_define and dm_activate might fail if themigration source is an XIV system with version 11.3.0.

Workaround:Wait 10 seconds, then run the command again. If the command does notexecute successfully after the first retry, retry again (up to the maximumnumber of connections from the first gateway to the data migration sourcesystem).

Severity:Service


SYS-261545When a host is mapped to a volume in Proxy state, and also mapped to thatvolume’s destination volume on another system, if connectivity is lost between thesystems, host I/Os to the destination volume might not get a response for up to 1minute.


WorkaroundEnsure that both systems are connected with a full redundancy FCnetwork (going through two separate FC switches).

SeverityHigh impact


SYS-261567When using IBM Hyper-Scale Mobility, during the Proxy phase, while the host ismapped to both the source volume and the destination volume (the source volumeserves as a proxy to the destination), if the user tries to delete the target using thetarget_delete XCLI command, the command succeeds without cleaning up theproxy volumes.

Workaround:Delete a target only after deleting all volumes in Proxy state using thattarget.

Severity:Service


SYS-261828The number of spare drives reported by the system may be wrong. This does notaffect the ability of the system to use the spare capacity.

SeverityService


SYS-261875SCSI Unit attentions might not be delivered correctly in an IBM Hyper-ScaleMobility environment.

Please contact IBM service if you plan to use IBM Hyper-Scale Mobility in aclustered environment.

SeverityHigh impact


SYS-261890Creating an IBM Hyper-Scale Mobility relationship on a system where a migrationtarget has been deleted can lead to loss of access.

WorkaroundDo not delete a target that has been used for IBM Hyper-Scale Mobilityrelationships.

Release Notes 9

SeverityHigh impact


XIV logo LEDIn 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 thefront 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.

Fixed issues

SYS-251334When a pool is changed from thin to thick or from thick to thin, a SCSI UnitAttention is not raised.

SeverityModerate


SYS-254726Systems with 10GB interface cards allow the user to define 4 ports although onlytwo ports exist.

SeverityService

Affected versions:11.2.0 and up

SYS-255376When a zone disconnects or changes during mirroring, target connectivity mightnot connect automatically.

SeverityService


SYS-260184When using Data Migration without source updating and a read from the sourcevolume fails, the XIV system may incorrectly indicate that the data on the sourcevolume and target volume has been synchronized when, in fact, it is not. As aresult, 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 thetime the system's periodical data scrubbing process (which can take up to 24 days


to complete depending on configuration) reaches the incorrect data, the scrubprocess is capable of detecting that the primary and secondary partitions differ andshould alert IBM service personnel of the issue if the remote support features havebeen enabled on the system.

SeverityHyper


Copyrights© Copyright IBM Corporation 2013. US Government Users Restricted Rights - Use,duplication or disclosure restricted by GSA ADP Schedule Contract with IBMCorp.

References in this documentation to IBM® products, programs, or services do notimply that IBM intends to make these available in all countries in which IBMoperates. Any reference to an IBM product, program or service is not intended tostate or imply that only IBM's product, program or service may be used. Anyfunctionally equivalent product, program or service that does not infringe any ofIBM's intellectual property rights may be used instead of the IBM product,program or service. Evaluation and verification of operation in conjunction withother products, except those expressly designated by IBM, are the user'sresponsibility.

Definitions of problem severityThe 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 moreoccurrences.

ModerateA function not operational and/or performance might be degraded.

ServiceA recoverable error (no impact) and service improvement.

ImprovementsChanges made for the purpose of better usability and serviceability.

Contacting IBM SupportThe release is supported via:

Voice callsWill come into Level 1 or Front Line Support as they do for the currentproduct.

Customers will use the appropriate support phone number for theirrespective countries; refer to the World Wide Directory for the supportnumbers by country. http://www.ibm.com/planetwide

Release Notes 11

Documentation formatThe 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 aweb-based format or accessible PDF document for a publications, send a requestby email to [email protected]. In the request, be sure to include the IBMpublication number and title.

When you sent information to IBM, you grant IBM a nonexclusive right to use todistribute the information in any way it believes appropriate without incurring anyobligation to you.

Notices and trademarksNotices

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer ofexpress or implied warranties in certain transactions, therefore, this statement maynot apply to you. This information could include technical inaccuracies ortypographical errors. Changes are periodically made to the information herein;these changes will be incorporated in new editions of the publication. IBM maymake 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, orboth. Microsoft, Windows, and Windows Server are trademarks of MicrosoftCorporation in the United States, other countries, or both. Intel, Intel logo, IntelInside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon,Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks ofIntel Corporation or its subsidiaries in the United States and other countries. Othercompany, product, or service names may be trademarks or service marks of others.

THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICESAND INFORMATION

The license agreement for this product refers you to this file for details concerningterms and conditions applicable to third party software code included in thisproduct, and for certain notices and other information IBM must provide to youunder its license to certain software code. The relevant terms and conditions,notices and other information are provided or referenced below. Please note thatany non-English version of the licenses below is unofficial and is provided to youfor your convenience only. The English version of the licenses below, provided aspart of the English version of this file, is the official version. Notwithstanding theterms and conditions of any other agreement you may have with IBM or any of itsrelated or affiliated entities (collectively "IBM"), the third party software codeidentified below are "Excluded Components" and are subject to the following termsand conditions:v the Excluded Components are provided on an "AS IS" basis


mailto:[email protected]?subject=IBM XIV Storage System accessible publications request

v IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIESAND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS,INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OFNON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIEDWARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE

v IBM will not be liable to you or indemnify you for any claims related to theExcluded Components

v 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

��

Printed in USA

release notes for version 11.3.0 second edition - ibm · management requirements for effective...

Documents