with IBM Corp.IBM XIV Stora ge System Gen3 V ersion 11.6.0.b Release Notes IBM Fifth Edition...

IBM XIV Storage System Gen3Version 11.6.0.b

Release Notes

IBM

Fifth Edition (January 2016)

This edition applies to IBM XIV Storage System Gen3 version 11.6.0.b. Newer document editions may be issued forthe same product version in order to add missing information, update information, or amend typographical errors.The edition is reset to 'First Edition' for every new product version.

© Copyright IBM Corporation 2011, 2016.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 1What's new in version 11.6.0.b . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 1Hot upgrade from earlier versions . . . . . . . . . . . . . . . . . . . . . . . . . . .. 2Management and automation tools . . . . . . . . . . . . . . . . . . . . . . . . . . .. 3Fixed issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 4Fixes and features of previous versions . . . . . . . . . . . . . . . . . . . . . . . . .. 5Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 6Known issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 7Related information and publications . . . . . . . . . . . . . . . . . . . . . . . . . .. 13Getting information, help, and service . . . . . . . . . . . . . . . . . . . . . . . . .. 14

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 15Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 17

© Copyright IBM Corp. 2011, 2016 iii

iv IBM XIV Storage System Gen3

Overview

IBM® XIV® Storage System Gen3 is a high-end, grid-scale, hostspot-free diskstorage system that delivers high performance, smart scaling, distributed data,automatic load balancing, and a multitude of advanced enterprise-class storagefeatures and capabilities – all with extreme ease of use.

IBM XIV is ideal for cloud environments, offering high service levels for dynamicworkloads and easy hyper-scaling, while supporting multi-tenant environments,flexible consumption models, and robust cloud automation and integrationcapabilities. IBM XIV offers security and data protection through advanced remotemirroring, hot encryption, and self-healing mechanisms.

For more detailed information about IBM XIV Storage System Gen3, refer to itsuser documentation and online information.

What's new in version 11.6.0.bVersion 11.6.0.b of IBM XIV Storage System Gen3 is a major release that includesthe following new features and improvements.

General availability date: 4 June 2015 (released initially as 11.6.0.a)

IBM Real-time Compression™

Version 11.6.0.b introduces support for IBM Real-time Compression, allowing XIVGen3 systems to compress volumes in real time, as opposed to data being storedfirst and then compressed at a later time. By employing the field-proven IBMRandom Access Compression Engine (RACE) technology together with the IntelHyper-Threading multi-core technology that is incorporated in the XIV grid, XIVGen3 systems can effectively increase usable capacity per rack.

This includes:v Creation of new compressed volumesv Nondisruptive conversion of existing volumes from non-compressed to

compressed, and vice versav Reclamation of the saved space as usable capacity, reducing the risk of

over-provisioningv Average of 50% capacity gain on mixed compressible workloadsv Compressed data is replicated faster as opposed to non-compressed data, freeing

up bandwidth for other usesv Ease of compression management from the XIV GUI, including the ability to

calculate and view potential capacity savings.

Note: The IBM Real-time Compression feature must be ordered and licensedseparately. Contact your IBM Sales representative for more information.

For more information about IBM Real-time Compression on XIV Gen3 systems, seethe IBM XIV Product Overview publication (ibm.com/support/knowledgecenter/STJTAG).

© Copyright IBM Corp. 2011, 2016 1

http://www.ibm.com/support/knowledgecenter/STJTAG/com.ibm.help.xivgen3.doc/xiv_pubsrelatedinfoic_xiv11.6.dita

Support for integration with Microsoft Azure Site Recovery

Version 11.6.0.b allows IBM XIV Gen3 systems to be integrated with MicrosoftAzure Site Recovery to provide site-to-site disaster recovery for Hyper-Venvironments.

By using the Storage Management Initiative Specification (SMI-S) API, MicrosoftAzure Site Recovery can utilize XIV systems to orchestrate replication and failoverfor virtual machines running on Hyper-V host servers managed by MicrosoftSystem Center Virtual Machine Manager (SCVMM) clouds.

For more information, see the IBM XIV Product Overview publication.

Automatic shutdown in extreme overheating conditions

Starting from software version 11.6.0.b, when particular extreme overheatingconditions are met and the administrator has not yet shut down the system, thesystem automatically performs self shutdown.

For more detailed information about this feature, see ‘Temperature threshold andevents’ in the IBM XIV Gen3 Planning Guide publication.

Additional improvements

For information about additional improvements in version 11.6.0.b, see “Fixedissues” on page 4.

Hot upgrade from earlier versionsVersion 11.6.0.b supports direct hot upgrade from the following XIV Gen3 softwareversions.v 11.5.1.bv 11.5.1.av 11.5.0.av 11.4.2.dv 11.4.2.cv 11.4.2.av 11.4.1.bv 11.4.1.a

Earlier 11.x versions can be upgraded to 11.6.0.b by applying two consecutive hotupgrades.

The upgrade must be performed only by an authorized IBM service technician.

Before initiating the upgrade, some preparation steps are required. For moreinformation, see 'Non-disruptive code load' in the IBM XIV Product Overviewpublication.

2 IBM XIV Storage System Gen3

Management and automation toolsIBM XIV Gen3 version 11.6.0.b can be managed and monitored with the followingsoftware management tools.v IBM XIV Management Tools version 4.6 or laterv IBM Hyper-Scale Manager version 1.7 or laterv IBM XIV Mobile Dashboard (for monitoring only) version 1.4.0.1 or later

Note: Although earlier management tool versions might be able to detect andmanage XIV systems of version 11.6.0.b, the latest XIV functional features aresupported only by the management tool versions specified above.

XIV customers are entitled to free use of these management tools, which can bedownloaded at any time from the IBM Fix Central website (ibm.com/support/fixcentral).

The Mobile Dashboard application can be downloaded and installed at any timeand from Apple Store (iOS version) or Google Play (Android version).

IBM Spectrum Control Base Edition

IBM XIV Gen3 version 11.6.0.b is supported by IBM Spectrum Control Base Editionversion 2.1.0 or later, which provides the following VMware platform integrationtools.v IBM Storage Provider for VMware VASAv IBM Storage Enhancements for VMware vSphere Web Clientv IBM Storage Plug-in for VMware vCenter Orchestratorv IBM Storage Management Pack for VMware vCenter Operations Manager

For more information, see IBM Spectrum Control Base Edition on IBM KnowledgeCenter (ibm.com/support/knowledgecenter/STWMS9).

XIV customers are entitled to free use of IBM Spectrum Control Base Edition,which can be downloaded at any time from the IBM Fix Central website(ibm.com/support/fixcentral).

Available cloud storage solutions

IBM XIV Storage System Gen3 version 11.6.0.b can be integrated with variousindependent software vendor (ISV) platform, application, virtualization, and cloudenvironments.

To facilitate this integration, IBM provides the following software solutions, alsoreferred to as cloud storage solutions.

Cloud storage solution Version Compatibility note

IBM XIV Host Attachment Kit 2.4.0 or later Available for IBM AIX®,HP Unix, Linux,Oracle Solaris, and MicrosoftWindows Server

IBM XIV Provider for Microsoft WindowsVolume Shadow Copy Service (VSS)

2.7.0 or later

Overview 3

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

https://itunes.apple.com/us/app/ibm-xiv-mobile-dashboard-for/id503500546?mt=8

https://play.google.com/store/apps/details?id=com.ibm.xiv.mobile.android

http://www.ibm.com/support/knowledgecenter/STWMS9

http://www.ibm.com/support/knowledgecenter/STWMS9


Cloud storage solution Version Compatibility note

IBM XIV Storage Replication Adapter(SRA)

2.2.1 or later For use with VMware vCenterSite Recovery Manager

IBM Storage Driver for OpenStack 1.5.0 or later Version 1.5.0 supports onlythe OpenStack Kilo release

IBM Storage Enabler for WindowsFailover Clustering

1.2.0 or later Version 1.2.0 does not supportcompressed volumes (throughthe IBM Real-timeCompression feature)

IBM Storage Management Pack forMicrosoft System Center OperationsManager

2.4.0 or later

XIV customers are entitled to free use of the IBM cloud storage solutions, whichcan be downloaded at any time from the IBM Fix Central website(ibm.com/support/fixcentral).

For more information about the available cloud storage solutions for XIV, seePlatform and application integration on IBM Knowledge Center (ibm.biz/BdXy4c).

Fixed issuesVersion 11.6.0.b of IBM XIV Storage System Gen3 includes the following fixes.

Ticket ID Description

SYS-269182 Fixed: In extremely rare situations on systems with SSD cachingenabled, when two read operations are sent by the host to thesame address, the second read operation might return incorrectdata from the cache, which could result in undetected datacorruption. Subsequent reads to the same address (after the datais no longer in the cache) returns the correct data.

Severity: High Impact

Affected versions: 11.1.0 or later

SYS-252743 Fixed: When entering several certificates to the certificateparameter, ipsec_connection_* XCLI commands processes onlythe first certificate.

Severity: Service


SYS-265572 Fixed: If any of the parameters of pool_change_config are invalid,the command might start running and then fail halfway through.

Severity: Service




http://www.ibm.com/support/knowledgecenter/STJTAG/hsg/hsg_kcwelcomepage_xiv.html

Ticket ID Description

SYS-266212 Fixed: If a solid-state drive fails during the encryption process,the SSD_HAS_FAILED_WHILE_ENABLING_ENCRYPTION event might notbe issued.

Severity: Service


SYS-266220 Fixed: The format=full parameter on the XCLI help command isnot supported.


Severity: Service

SYS-266221 Fixed: The ldap_user_list role=storageadmin XCLI commanddoes not list domain administrators.

Severity: Service


SYS-266476 Fixed: When using the muti-tenancy feature in LDAPauthentication mode, a domain with which users are currentlyassociated cannot be deleted.

Severity: Service


SYS-266853 Fixed: In the XCLI help, the descriptions of the domain_manageand domain_move_gp commands are incorrect.

Severity: Service


SYS-267911 Fixed: IBM Hyper-Scale Manager supports LDAP UPN modeonly when there are no domains configured on the system. Ifdomains are configured on the system, LDAP UPN mode is notsupported.

Severity: Service


Fixes and features of previous versionsIBM XIV Storage System Gen3 version 11.6.0.b includes all the features and fixesthat were included in previous 11.x versions.

To obtain information regarding previously introduced XIV Gen3 features or issuesthat were resolved in previous versions, see the XIV Gen3 release notes page onIBM Knowledge Center (ibm.com/support/knowledgecenter/STJTAG).

Overview 5

http://www.ibm.com/support/knowledgecenter/STJTAG/com.ibm.help.xivgen3.doc/Gen3/xiv_gen3releasenotes.dita

http://www.ibm.com/support/knowledgecenter/STJTAG/com.ibm.help.xivgen3.doc/Gen3/xiv_gen3releasenotes.dita

LimitationsThe following functional limitations apply to IBM XIV Storage System Gen3 andmay remain in effect in future XIV software versions.

Limitations with IBM Real-time Compression

The following limitations apply to the IBM Real-time Compression feature whenused on XIV Gen3 systems:v The minimum volume size that can be compressed is 103 Gigabytes (GB). The

compression option is blocked for smaller volumes.v The maximum volume size that can be compressed is 10 Terabytes (TB). The

compression option is blocked for larger volumes.v Up to 1024 volumes can be compressed on a single XIV system.v Only thin-provisioned volumes can be compressed.v Shrinking a compressed volume is not supported.v Snapshots cannot be converted from compressed to uncompressed and vice

versa.Snapshots that already existed before a volume was converted fromnon-compressed to compressed are not converted and are not available with theconverted volume.

v When migrating volumes using IBM Hyper-Scale Mobility, compression ordecompression operations can only begin after the migration is complete.

v Locked volumes must be unlocked before compression or decompression canbegin.

v In a mirroring relation, both the source and target volumes must be compressed,or both must be uncompressed.

v To convert a mirrored volume from uncompressed to compressed (or vice versa),the mirroring relationship for that volume must first be removed and thenrecreated after the conversion.

v When two-way or three-way mirroring is used, compressed volumes on thesecondary or tertiary system cannot be mapped to hosts.

v IBM PowerHA® Enterprise Edition is not supported.v The latency of synchronously mirrored compressed volumes could be higher

than that of synchronously mirrored uncompressed volumes. As a result, if thedistance between the production and recovery sites is extremely large, hostdisconnections might occur. It is, therefore, recommended to test the latency on atest volume before using synchronous mirroring with compressed volumes inthe production environment.

v The system continuously assesses potential saving ratio at a pace ofapproximately 20 volumes per hour. Until the initial assessment of anynon-compressed volume is complete, its potential saving ratio is not displayed.

v The calculated potential saving percentage of a decompressed volume (convertedfrom compressed to non-compressed) could be different than the savingpercentage that was originally calculated for the same volume prior to itscompression. This occurs if most of the data on the volume comprises zeros,while other data is sparsely distributed.

v VMware Virtual Volumes (VVols) are not supported with compressed volumes.


Limitations with IBM Hyper-Scale Mobility

The following limitations apply to the IBM Hyper-Scale Mobility (volumemigration) feature when used with XIV Gen3 systems:v Can be used only with systems that are located within the same data center.v Cannot be used on a volume that belongs to a consistency group. The volume

must first be removed from the consistency group.v Does not apply to volume snapshots. When the migration is changed to proxy

state, all snapshots of the pertinent migrated volume are deleted automatically.v Does not migrate volume mirroring relationships. Before a volume can be

moved, its mirroring relationship must be deleted.

Known issuesThis section details the known issues in IBM XIV Storage System Gen3, along withpossible solutions or workarounds (if available). High-impact issues are listed first.

Important:

v The issues listed below apply to version 11.6.0.b or earlier versions. As long asa newer version has not yet been released, a newer release notes edition forversion 11.6.0.b might be issued to provide a more updated list of known issuesand workarounds.

v When a newer version is released for general availability, the release notes ofversion 11.6.0.b will no longer be updated. Accordingly, check the release notesof the newer version to learn whether any newly discovered issues affect version11.6.0.b or whether the newer version resolves any of the issues listed below.

Ticket ID SeverityAffectedversions Description

SYS-260642 HighImpact

11.4.0or later

The following XCLI commands require a user name as aparameter, but appear to run successfully even if the specifieduser does not exist:

v encrypt_recovery_key_generate

v encrypt_keyserver_rekey

v encrypt_recovery_key_rekey

Workaround: Before running these commands, use the user_listXCLI command to make sure that the user exists.


11.5.1or later

On systems with 6 TB drives, a single restore of a volume from asnapshot or a consistency group (CG) cannot be handled whenthe total hard size of the volumes involved (including all theirsnapshots) exceeds 90% of the system's entire usable capacity.

Workaround: Avoid creating a single volume or a single CG witha total hard size that exceeds 50% of the system usable capacity.

Overview 7



11.6.0 orlater

The XCOPY (Extended Copy) SCSI command, which is part ofthe VMware vSphere API for Array Integration (VAAI)specification, is not supported with compressed volumes. Thisimpacts the speed of VMware environment copy operations byautomatically falling back to a host-based copy. The impactedcopy operations are virtual machine cloning, virtual machinecreation from a template, and vSphere Storage vMotion, withinthe same storage array.

Note: There are no other impacts and no intervention is required.VMware vSphere automatically detects the lack of XCOPYsupport and performs the operation on the host.

Workaround: No workaround is currently available.

SYS-253004 Moderate 11.0.0or later

Resizing a pool (reducing its volume capacity) does not triggerthe STORAGE_POOL_VOLUME_USAGE_INCREASED event when crossingthe preset threshold.

Workaround: No workaround is currently available. Accordingly,use caution when resizing down a storage pool.


In a multi-site mirroring relation, if the destination remainsconnected to the source after the source is disconnected from thehost and the secondary source, establishing an asynchronousmirror from the secondary source to the destination requires afull resynchronization.



When changing a volume to read only, the system does not raisea SCSI Unit Attention to make the host aware of the change.



If a mirroring-related snapshot (LRS) of an active xmirror relationis deleted on the source volume due to lack of space in thestorage pool, subsequent xmirror_activate commands on thesource volume fail with a misleading return code(XMIRROR_SLAVE_HAS_MORE_RECENT_DATA).

Workaround:

1. Remove the asynchronous source-destination mirror relation.2. Ensure that the storage pool has enough space on the source.3. Reestablish the asynchronous source-destination mirror

relation.4. Reestablish and activate the xmirror relation.

During this process, the source-secondary synchronous mirrorrelation can continue working.




The multi-tenancy feature does not support Sun directory orOpen LDAP group objects. Static groups reflecting domainadministrators fail to log in, and receive an unrecognized rolecompletion code.

Workaround: Instead of the an LDAP group object attribute, usethe description string as hard-coded value per user. For moreinformation, refer to the IBM XIV Storage System Architecture andImplementation Redbook.


When a compressed volume is in a three-way mirroringrelationship, any crash of the source volume might result in asituation where the tertiary site volume has more recent datathan on the secondary site volume. In such a case, the regularrecovery process does not work.

Workaround: To resolve this issue:

1. Disable the three-way mirroring.2. Recreate asynchronous mirroring with the tertiary site

mirrored to the primary site.3. Wait for the volume to synchronize.4. Reestablish the three-way mirroring.


The time required for decompressing a volume is proportional tothe volume size, and the time required for compressing a volumeis proportional to the amount of data that the volume contains.As a result, decompressing a volume is typically much slowerthan compressing the same volume.



When setting Microsoft Azure Site Recovery protection betweentwo sites using storage area network (SAN) replication, if anon-2810 XIV machine type is selected as the storage provider oneither the local site or remote site, protection operations fail.

In such cases, errors such as 'No SAN capabilities detected forthe cloud' or 'No peer relationship found between these twoSAN arrays' might be encountered.

This issue is not encountered if both the local site and remote siteuse the 2810 XIV machine type.


Overview 9


SYS-257063 Service 11.3.0or later

When using IBM Hyper-Scale Mobility (volume migration) and ahost is mapped to both the source volume and the destinationvolume, the system does not display a warning upon theunmapping of the source volume from the host.

Workaround: Prior to unmapping the source volume, verify that:

v The host is mapped to the volume on the destination system.v I/Os are running on that path.

This can be done from the host side or by using the XIV statistictools on the destination system.


Deleting a user certificate reverts the system to the genericcertificate instead of to the unique system certificate.

Workaround: Set the system-unique certificate as a default beforeremoving the user certificate.


When issuing the encrypt_enable XCLI command immediatelyafter defining a key server:

v The command returns Command executed successfully.v Encryption is not enabled.v The ENCRYPT_ENABLE_NOT_COMPLETED event is issued.

Workaround: Wait 10 seconds and then retry.


In a multi-site mirroring relation, if the secondary source isdeleted by using the delete_xmirror command with force=yes, asubsequent xmirror_activate command might return a successreturn code, even though no secondary source volume is defined.



Domain administrators from different domains that share aresource, can view and delete the metadata of that resource.



snmpwalk for volume statistics may take a long time whenmultiple volumes are defined.



When associating separate LDAP groups to separate domains, anLDAP directory user cannot belong to more than one group if notmentioned specifically by the group name in the format ofuser@domain1/domain2.

If a user is not defined in such a way and the memberOf fieldcontains more than one group, an LDAP_USER_CONFIG_ERROR eventis issued.





In IP filtering, FQDN host names are not supported by theip_access_group_remove_address command.

Workaround: Use an IP address instead.


When using the multi-tenancy feature, the system does not blockapplication administrators, who belong to user groups in theglobal domain, from being designated as IBM Hyper-ScaleManager users.

Workaround: Remove any application administrator from the listof IBM Hyper-Scale Manager users.


When working with IP filtering, a subnet cannot be added to anIP access group if an IPO, that is part of the subnet, alreadyexists in the access group.

Although the ip_access_group_add_address command is issuedwithout an error, the subnet is not added.



CIM is not multi-tenant aware and cannot be used by a domainadministrator.

Workaround: Use the credentials of a global (non-domain) user,and set the domain access policy to OPEN (default policy).


IP filtering does not work for an IP range.

Workaround: Define an IP range by using an IP mask.


When using IP filtering, there is no validation that a valid IPaddress is entered to the IP Access Group.



When adding IP addresses to an IP Access Group for IP filtering,two addresses cannot be added with the same IP, but withdifferent netmasks.



When using the ldap_user_list command with a validadministrator role that does not allow input for this particularcommand, the status string does not indicate the invalid inputcorrectly: Illegal value 'string' for argument 'argument' ofcommand 'command'.


Overview 11



When three-way mirroring is being used, trying create a mirrorsnapshot on the asynchronous secondary system results in afailure (error event: XMIRROR_SNAPSHOT_MIRROR_NOT_SUPPORTED)because such operation is not supported with three-waymirroring. The prompted error message, however, is incorrect:Volume is part of an xmirror, snapshot mirrors are notsupported for xmirrors. Snapshot mirrors are supported on asynchronous secondary system.



1024-bit SSH keys that were in use prior to a software upgrade toversion 11.6.x are no longer valid because 2048-bit SSH keys arerequired starting from version 11.6.x. Trying to use an 1024-bitSSH results in the following error message: WARNING: REMOTEHOST IDENTIFICATION HAS CHANGED!

Workaround: Remove the old SSH key from the$HOME/.ssh/known_hosts file, or delete the file entirely.


When decompressing a compressed volume that belongs to aperformance class, the decompression might take longer time tocomplete because the volume performance is constrained by theperformance class.

Workaround: Remove the performance class assignment until theconversion completes.


After a compressed VMFS5 volume is converted back to anuncompressed volume, the volume does not support VMwareVAAI SCSI commands.

Workaround: To avoid this issue, the VMFS5 volume type mustfirst be converted from ATS Only to ATS + SCSI reservation. Usethe following ESXi CLI command to disable ATS locking:vmkfstools --configATSOnly 0device-path

For more information, see VMware KB article 2006858(kb.vmware.com/kb/2006858).


Obtaining the initial compression analysis of potential capacitysaving for 1000 volumes might take up to 48 hours, dependingon the load in the system.



When volume compression is enabled, the general expectationwould be that the cache hit ratio should increase, since some ofthe data is compressed and therefore the cache can contain moredata. However, depending on the workload mix, the cache hitratio might start to decline after a certain system load isexceeded.

Workaround: Reduce the system load. For example, migratesome volumes to less loaded systems.


http://kb.vmware.com/kb/2006858



When changing or switching a mirror relation role whilecompressed volumes are used, after the secondary systembecomes a the primary system, the correct compression rate forthe new primary system is not shown immediately.



Cache hit latency for compressed volumes, as displayed in XIVTOP, is consistently incorrect and much higher than the actualone.

Workaround: In the XIV performance view, use an aggregatefilter and do not select the Hit or Miss filters. For higheraccuracy, use external tools to measure the latency on the host.


In some rare cases, upon the enabling of drive encryption, asolid-state drive (SSD) might fail, resulting inCOMPONENT_TEST_OF_SSD_HAS_FAILED event for this drive. The SSDcache on the related module remains unavailable until theproblem is fixed.

Workaround: No workaround is currently available. For apossible solution, contact IBM Support.


In a Microsoft Azure Site Recovery configuration, when aFailover operation is followed by Disable Protection, MicrosoftSystem Center Virtual Machine Manager (SCVMM) might promptan exception such as: Replication group '$cgname' wasunexpectedly found to be in a replication relationship.

The exception is the result of a failure to automatically delete themirror relationship on the target location. This might happeneven if the communication between the source and target sites isoperational.

Workaround: Using XIV CLI or GUI, delete the consistencygroup mirror from the storage array on the target location beforeinvoking Disable Protection. This can be applied before or afterthe exception occurs.

Related information and publicationsYou can find additional information and publications related to IBM XIV StorageSystem Gen3 on the following information sources.v IBM XIV Storage System marketing website (ibm.com/systems/storage/disk/

xiv)v IBM XIV Storage System on IBM Knowledge Center (ibm.com/support/

knowledgecenter/STJTAG)v IBM Storage Redbooks® website (redbooks.ibm.com/portals/storage)

Overview 13

http://www.ibm.com/systems/storage/disk/xiv

http://www.ibm.com/support/knowledgecenter/STJTAG

http://www.redbooks.ibm.com/portals/storage

Getting information, help, and serviceIf you need help, service, technical assistance, or want more information about IBMproducts, you can find various sources to assist you. You can view the followingwebsites to get information about IBM products and services and to find the latesttechnical information and support.v IBM website (ibm.com®)v IBM Support Portal website (ibm.com/storage/support)v IBM Directory of Worldwide Contacts website (ibm.com/planetwide)v IBM service requests and PMRs (ibm.com/support/servicerequest/Home.action)

Use the Directory of Worldwide Contacts to find the appropriate phone number forinitiating voice call support. Voice calls arrive to Level 1 or Front Line Support.


http://www.ibm.com

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

http://www.ibm.com/planetwide

http://www.ibm.com/support/servicerequest/Home.action

Notices

These legal notices pertain to the information in this IBM product documentation.

This information was developed for products and services offered in the U.S.A.However, you may be required to own a copy of the product or product version inthat language in order to access it.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law: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 states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

© Copyright IBM Corp. 2011, 2016 15

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM CorporationAttn: Office of Legal Counsel650 Harry RoadSan Jose, CA 95120-6099U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.


TrademarksIBM, XIV, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.

Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Copyright and trademarkinformation website (ibm.com/legal/us/en/copytrade.shtml).

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

Microsoft, Windows, Windows Server, and the Windows logo are trademarks orregistered trademarks of Microsoft Corporation in the United States, othercountries, or both.

VMware, ESX, ESXi, vSphere, vCenter, and vCloud are trademarks or registeredtrademarks of VMware Corporation in the United States, other countries, or both.

Other product and service names might be trademarks of IBM or other companies.

Notices 17

http://www.ibm.com/legal/us/en/copytrade.shtml

http://www.ibm.com/legal/us/en/copytrade.shtml

IBM®

Printed in USA

with IBM Corp.IBM XIV Stora ge System Gen3 V ersion 11.6.0.b Release Notes IBM Fifth Edition...

Documents

Transcript of with IBM Corp.IBM XIV Stora ge System Gen3 V ersion 11.6.0.b Release Notes IBM Fifth Edition...