IBM Storage Integration Serverdelivery04.dhe.ibm.com/.../0/IBM_Storage_Integration_Server_1.2.2_… · IBM DS8000® 6.3.x – relevant to the ... Red Hat Enterprise Linux (RHEL) 6.3

IBM Storage Integration ServerVersion 1.2.2

Release Notes

��

First Edition (June 2014)

This edition applies to version 1.2.2 of the IBM Storage Integration Server software package. Newer documenteditions may be issued for the same product version in order to add missing information or amend typographicalerrors. The edition is reset to 'First Edition' for every new product version.

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

Contents

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Compatibility and requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Supported storage systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Supported operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Minimum server hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . 2Supported VMware platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Supported browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Change log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Version 1.2.2 (June 2014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Version 1.2.1 (May 2014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Version 1.2.0 (March 2014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Version 1.1.0 (October 2013) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Known issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Related information and publications . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Getting information, help, and service . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

© Copyright IBM Corp. 2013, 2014 iii

iv IBM Storage Integration Server

Overview

The IBM® Storage Integration Server is a centralized server system thatconsolidates a range of IBM storage provisioning, automation, and monitoringsolutions through a unified server platform.

The IBM Storage Integration Server provides a single server back-end location andenables centralized management of IBM storage resources for the use ofIndependent Software Vendor (ISV) platforms and frameworks, which currentlyinclude VMware vCenter Server, VMware vSphere Web Client, and VMwarevSphere APIs for Storage Awareness (VASA).

The following IBM storage solution components are included in the softwarepackage:v IBM Storage Provider for VMware VASA – Improves the ability to monitor and

automate storage-related operations on VMware platforms.v IBM Storage Enhancements for VMware vSphere Web Client – Integrate into the

VMware vSphere Web Client platform and enable VMware administrators toindependently and centrally manage their storage resources on IBM storagesystems.

You can download the IBM Storage Integration Server software package at anytime from the IBM Fix Central website (ibm.com/support/fixcentral).

Compatibility and requirementsThis section specifies the compatibility and requirements of version 1.2.2 of theIBM Storage Integration Server.

Note: For information about the compatibility and requirements of a previousversion, refer to its relevant release notes.

Supported storage systemsThe IBM Storage Integration Server supports different IBM storage systems aslisted in the following table.

Storage system Microcode version Compatibility note

IBM DS8000® 6.3.x – relevant to the 8700and 8800 Series

7.0, 7.1, 7.2 – relevant tothe 8870 Series

v Not supported by theIBM Storage Providerfor VMware VASA

v Supported only by theIBM StorageEnhancements forVMware vSphere WebClient

IBM Flex System® V7000 7.1.0, 7.2.0 N/A

IBM SAN Volume Controller 7.1.0, 7.2.0 Microcode 7.2.0 PTF (withsecurity fix) is alsosupported

© Copyright IBM Corp. 2013, 2014 1

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

Storage system Microcode version Compatibility note

IBM Storwize® V3500 7.1.0, 7.2.0 Microcode 7.2.0 PTF (withsecurity fix) is alsosupported

IBM Storwize V3700 7.1.0, 7.2.0 Microcode 7.2.0 PTF (withsecurity fix) is alsosupported



IBM Storwize V7000 Unified 1.4.2, 1.4.3 Only block-type storage issupported. File shares andfile systems are notsupported.

IBM XIV® Storage System 10.2.4.x

11.0.x, 11.1.x, 11.2.x, 11.3.x,11.4.x

N/A

Supported operating systemsThe IBM Storage Integration Server software can be installed on the followingLinux version.

Operating system Architecture

Red Hat Enterprise Linux (RHEL) 6.3 or 6.4 x64

Note: The IBM Storage Enhancements for VMware vSphere Web Client areautomatically deployed and enabled on the VMware vSphere Web Client Server, byregistering the vSphere Web Client Server on the connected IBM StorageIntegration Server. For more information, refer to the user guide.

Minimum server hardware requirementsThe Linux server upon which the IBM Storage Integration Server is installedshould meet the following minimum hardware requirements.v 64-bit dual-core CPUv At least 4 GB of RAMv At least 15 GB of free disk space

Supported VMware platformsThe IBM Storage Integration Server is compatible with the following VMwareplatforms and frameworks:v VMware vSphere Web Client Server 5.1 or 5.5v VMware APIs for Storage Awareness (VASA) 5.0, 5.1, or 5.5v VMware vCenter Server Appliance (VCSA) 5.5

2 IBM Storage Integration Server

Supported browsersThe IBM Storage Integration Server can be accessed and managed with thefollowing web browsers:v Microsoft Internet Explorer 9.0 or laterv Mozilla Firefox 21.0 or laterv Google Chrome 27.0 or later

The IBM Storage Enhancements for VMware vSphere Web Client can be used onany browser that is supported by VMware vSphere Web Client Server. Forup-to-date information, refer to the vSphere 5 Documentation Center(pubs.vmware.com/vsphere-50/index.jsp).

Change logThis section summarizes the changes that were made in different released versionsof the IBM Storage Integration Server.

Version 1.2.2 (June 2014)Version 1.2.2 resolves the following critical issue.

Ticket ID Description

HSGSVR-261914 Fixed: OpenSSL 1.0.1g includes an additional securityvulnerability (CVE-2014-0224, part of the Heartbleedbug) that could have an impact on the connection tostorage arrays.

Version 1.2.2 uses OpenSSL version 1.0.1h, whichresolves this security issue.

Attention: To further protect the Red Hat EnterpriseLinux server upon which the IBM Storage IntegrationServer is installed, make sure that the operating systemuses the updated OpenSSL version as well.

Version 1.2.1 (May 2014)Version 1.2.1 adds support for Red Hat Enterprise Linux (RHEL) 6.4 and resolvesthe following critical issue.


HSGSVR-261835 Fixed: OpenSSL 1.0.1a-f security vulnerability (alsoknown as the Heartbleed bug) could have an impact onthe Integration Server connection to storage arrays.

Version 1.2.1 uses OpenSSL version 1.0.1g, whichresolves this security issue.

Attention: To further protect the Red Hat EnterpriseLinux server upon which the IBM Storage IntegrationServer is installed, make sure that the operating systemuses the updated OpenSSL version as well.

Overview 3

http://pubs.vmware.com/vsphere-50/topic/com.vmware.vsphere.solutions.doc_50/GUID-CC4604E4-B9A4-40FE-B0FA-3807906AFF85.html

http://en.wikipedia.org/wiki/Heartbleed



Version 1.2.0 (March 2014)Version 1.2.0 adds support for newer microcode versions of the supported IBMstorage systems.

Additional changes in version 1.2.0:


VWC-261300 Enhancement: Specifying the Integration Server URL onthe vSphere Web Client Server side is no longerrequired. The Integration Server connection throughport 8443 is now automatically defined for any vCenterserver that is registered (added) on the IBM StorageIntegration Server side.

VWC-261635 Enhancement: The IBM Storage Enhancements forVMware vSphere Web Client are now automaticallydeployed and enabled for each and every vCenterserver that is registered on the IBM Storage IntegrationServer side. Manual installation on the vSphere WebClient Server host is no longer required.

This includes support for VMware vCenter ServerAppliance (VCSA) version 5.5, which can be registeredon the Integration Server side like any other vCenterserver.

VWC-261650 Enhancement: In the Create New Volume wizard (IBMStorage Enhancements for VMware vSphere WebClient), an option to select the Logical Unit Number(LUN) for the new volume is now available.

HSGSVR-261544 Enhancement: Integration Server event logging is nowcompatible with the Rsyslog application, an open sourceutility for forwarding log messages over IP networks(for more information, see the Rsyslog website) . Twoconfiguration files, ibmsyslog.conf and ibmsyslog.conf,have been added to control the way Rsyslog collectsand distributes the Integration Server logs. For moreinformation, refer to the user guide.

HSGSVR-261657 Enhancement: All integration Server events arerecorded according to their type (Info, Error, orWarning) in the events.log file, located in/var/log/isis/.

HSGSVR-261661 Enhancement: Improved support for LightweightDirectory Access Protocol (LDAP) Active Directoryaccess through Transport Layer Security (TLS).

HSGSVR-261674 Enhancement: Added isis_ldap, a new CLI utility forconfiguring directory user access to the IBM StorageIntegration Server through LDAP authentication. Formore information, refer to the user guide.


http://www.rsyslog.com/doc/


HSGSVR-261717 Enhancement: New information is displayed perstorage array in both the GUI (Storage Arrays list) andCLI (isis_storage_array list):

v Time of the last storage array information update.v Any connection error (if and when it occurs).

HSGSVR-261470 Change: The import_vasa115 command has beendeprecated. The isis_configuration restore commandcan now be used for importing version 1.1.5 backups.For more information, refer to the user guide.

HSGSVR-261692 Change: Users are now required to indicate whether thestorage admin user (for adding storage arrays) isdefined locally on the storage arrays, or on a directoryserver. This indication is now displayed in both the GUIand CLI. If the storage admin account is defined on adirectory server, an account lock prevention mechanismis applied on the Integration Server side. For moreinformation, refer to the user guide.

VWC-261665 Change: The build number is also displayed as part ofthe IBM Storage Enhancements version.

HSGSVR-261549 Fixed: "Unexpected error" message appears whenremoving a storage array and clicking another tabbefore the operation is completed.

HSGSVR-261689 Fixed: In some cases, adding arrays withdirectory-based storage credentials might fail.

HSGSVR-261732 Fixed: Adding more than one DS8000 storage array tothe IBM Storage Integration Server causes malfunctions.

VWC-261541 Fixed: DS8000 volumes might be mapped but notattached to an ESXi host.

VWC-261664 Fixed: Creation of DS8000 volumes that are larger than16 TB fails (creation through the IBM StorageEnhancements for VMware vSphere Web Client).

Version 1.1.0 (October 2013)Version 1.1.0 of the IBM Storage Integration Server was the first released version,supporting a range of IBM storage systems and including the following featuresand primary components:v Web-based access to all Integration Server management functions using a

standard browser. Both the graphical user interface (GUI) and command-lineinterface (CLI) can be used for management.

v IBM Storage Provider for VMware VASA – Now a part of the IBM StorageIntegration Server package and featuring the following enhancements:– In addition to the XIV storage system, a range of IBM storage systems are

supported (see “Supported storage systems” on page 1).– Storage capabilities are automatically defined and assigned, eliminating the

need for manual definition and assignment.– The VASA access credentials ('VASA Secret' credentials) are defined separately

from the Integration Server user credentials.

Overview 5

– Configuration backups that were made with the previous release (IBMStorage Provider for VMware VASA, version 1.1.5) can be easily imported.

v IBM Storage Enhancements for VMware vSphere Web Client – A brand newaddition to the VMware vSphere Web Client platform, providing powerfulmanagement features and capabilities, including:– Full control over IBM storage volumes (LUNs), including volume creation,

resizing, renaming, migration to a different storage pool, mapping,unmapping, and deletion.

– Easy and integrated allocation of volumes to VMware datastores, used byvirtual machines that run on ESXi hosts, clusters, or datacenters.

– Storage pools that are attached to vCenter servers on the IBM StorageIntegration Server side.

For more information about the deployment and usage of the IBM StorageIntegration Server and its components, refer to the user guide.

Known issuesThis section details the known issues in version 1.2.2 of the IBM StorageIntegration Server and its solution components, along with possible solutions orworkarounds (if available).

Table 1. Known issues in IBM Storage Integration Server

Ticket ID Component Description

HSGSVR-261496 IBM Storage IntegrationServer

Volumes that were migrated from an XIV storagearray (A) to another XIV storage array (B) usingHyper-Scale Mobility (online volume migration)might not be manageable.

This specifically occurs if the volumes on the originalXIV storage array (A) are deleted from the storagearray (A), and then the same volume IDs are reusedon that storage array (A).

If both XIV systems (A and B) are connected to thesame IBM Storage Integration Server and thissituation occurs, it prevents the management of thesevolumes through the Integration Server.

Currently there is no solution or workaround for thislimitation (HSGSVR-261496).


DS8000 storage array information is not updated onthe Integration Server side after a connectivity break,or if the storage admin user group has been modifiedon the DS8000 side.

To resolve this issue, restart the Integration Serverservice:service ibm_storage_integration_server restart


Table 1. Known issues in IBM Storage Integration Server (continued)



For Storwize V7000 Unified storage arrays, themicrocode version number, build number, and systemID number are not consistent when appearing in theIntegration Server, vSphere Web Client, and storagesystem management GUIs. Different version numbersand system IDs are displayed on each platform.

Currently there is no solution or workaround for thislimitation (HSGSVR-261745).


The registration of the IBM Storage Integration Serveras a VASA storage provider on the vCenter Serverside might fail if an expired self-signed SSL certificateis present on the IBM Storage Integration Server.

To resolve this issue, replace the self-signed certificateas explained in the user guide.


After adding a SAN Volume Controller storage arrayon the IBM Storage Integration Server, the IBMStorage Provider for VMware VASA cannot detectSAN Volume Controller events.

To resolve this issue, remove and then add again theSAN Volume Controller storage array.


If the Integration Server fails to update storageinformation on a particular vCenter server due to aconnection problem, all other vCenter servers are notupdated as well.

To resolve this problem, reestablish the connectionwith the vCenter server, or remove it from the list ofvSphere Web Client servers.

Overview 7




Whenever a directory-based storage admin fails to login (from the Integration Server side) to any storagearray that is in use, the Integration Serverimmediately locks the storage admin user accountand all storage arrays become inaccessible on theIntegration Server side.

This behavior is part of the Integration Server design,in order to prevent repeated login attempt failuresafter which the directory server blocks that useraccount.

In such a case, update the storage admin credentialson the storage array with which the login has failed.Alternatively, you can remove the that specificstorage array from the Integration Server and thenreset the credentials.

You can find the relevant storage array by checkingthe events.log log file. For example:Mar 26 13:50:01 ronend-isis1 ERROR ID:ISIS-0008 |Severity:ERROR | Parameters:reason=Logging in toarray 2810-214-MN65025 has failed with the providedcredentials.,user_name=ronenu | Message:Storage credentials foruser ronenu were disabled. Reason: Logging in toarray 2810-214-MN65025 has failed with the providedcredentials.


After an upgrade or reinstallation of the IBM StorageIntegration Server, some DS8000 or SAN VolumeController storage array identifiers might change,causing the Integration Server to stop synchronizingwith these storage arrays.

To resolve this issue, use the Integration Server GUIor CLI to remove and then add back these storagearrays.





When replacing the self-signed SSL certificate files onthe IBM Storage Integration Server, changing thedefault path of these files causes the IBM StorageEnhancements for VMware vSphere Web Client not towork properly.

To avoid this problem, always use the defaultdirectory and specific filenames (vp.key, vp.crt) forthe SSL certificate files:

/opt/ibm/ibm_storage_integration_server/settings/ssl_cert/vp.key

/opt/ibm/ibm_storage_integration_server/settings/ssl_cert/vp.crt

For information about how to replace the self-signedSSL certificate files, refer to the user guide.

Table 2. Known issues in IBM Storage Provider for VMware VASA


VASAVP-261222 IBM Storage Provider forVMware VASA

Manual storage capability definitions that were madefor XIV arrays in version 1.1.5 cannot be imported,and are lost when upgrading to the IBM StorageIntegration Server release.

This is because storage capabilities in the latestrelease of the IBM Storage Provider for VMwareVASA (now part of the IBM Storage IntegrationServer) are automatically created and assigned.

Currently there is no solution or workaround for thislimitation (VASAVP-261222).

Overview 9

Table 2. Known issues in IBM Storage Provider for VMware VASA (continued)



When the IBM Storage Provider for VMware VASAand the IBM Tivoli® Storage Productivity Center(TPC) storage provider are registered on the sameVMware vCenter server, while the same storage arrayis configured for both, vCenter uses IBM TivoliStorage Productivity Center provider as the onlysource of information for that array's storage viewson vSphere Client.

In such a case, determine whether the IBM TivoliStorage Productivity Center capabilities are sufficientfor replacing the IBM Storage Provider for VMwareVASA. If the IBM Storage Provider for VMwareVASA is still needed, IBM TPC 5.2 (or later) providesa method of excluding storage arrays from a specificstorage provider, allowing you to remove the arrayassociation with the IBM TPC provider.

For more information, refer to the IBM Tivoli StorageProductivity Center documentation.


If spaces are included in the IP interface name (iSCSI)of an XIV storage array, that XIV array cannot bemonitored by the IBM Storage Provider for VMwareVASA, and information of that XIV array is notvisible to the relevant vCenter server.

To avoid this issue, do not include spaces in the IPinterface name of the XIV storage array.

Table 3. Known issues in IBM Storage Enhancements for VMware vSphere Web Client


VWC-261324 IBM Storage Enhancementsfor VMware vSphere WebClient

If a combination of both iSCSI and FC initiator porttypes is defined for an ESXi host, mapping volumesto that ESXi host causes both iSCSI and FC to beused for those volumes.

To avoid this situation, use the storage systemmanagement tools to define only one active protocoltype (iSCSI or FC) for the initiators of each ESXi host.


Table 3. Known issues in IBM Storage Enhancements for VMware vSphere Web Client (continued)



When using the storage system management GUI (asopposed to the IBM Storage Enhancements GUI invSphere Web Client) to map a single volume to morethan one ESXi hosts using different LUN IDs, thevolume is not properly recognized by vSphere WebClient and cannot be managed by the IBM StorageEnhancements. In addition, multiple errors mightoccur on the vSphere Web Client during the use ormodification of that volume.

To avoid this issue, always use the same LUN IDwhen mapping a volume to multiple ESXi hosts viathe storage system management GUI.


The Manage > Host Mapping tab of the IBMStorage Volume object shows incorrect mappinginformation. Hosts that cannot access the datastoreare shown as not being mapped to the LUN.

Currently there is no solution or workaround for thislimitation (VWC-261542).


The IBM Storage Enhancements for vSphere WebClient do not impose a limit on the number ofmapped volumes per ESXi host. However, since anyESXi host is limited to 256 LUNs, additional newlycreated volumes are not recognized and cannot beused with an ESXi host that already uses 256volumes.

To avoid this issue, do not map more than 256volumes to a single ESXi host.


If a volume is mapped to more than one ESXi hostwhile a virtual machine on one of these hosts usesthis volume as an RDM LUN, the volumeinformation might not be displayed correctly invSphere.

Currently there is no solution or workaround for thislimitation (VWC-261713).


If a volume is mapped to two or more ESXi hoststhat are managed by more than one vCenter server,volume operations fail.

To avoid this issue, do not map a specific volume toESXi hosts that are not managed by the same vCenterserver.

Overview 11

Table 3. Known issues in IBM Storage Enhancements for VMware vSphere Web Client (continued)



If a DS8000 volume is mapped using 255 as the LUNID, the volume cannot be mapped to other ESXi hostsanymore, even to hosts that their LUN 255 slot asavailable.

To avoid this issue, do not use LUN 255 whenmapping DS8000 volumes.

Related information and publicationsYou can find additional information and publications related to the IBM StorageIntegration Server on the following information sources.v IBM Storage Host Software Solutions Information Center

(publib.boulder.ibm.com/infocenter/strhosts/ic)v IBM DS8000 Information Center (publib.boulder.ibm.com/infocenter/dsichelp/

ds8000ic)v IBM Flex System Information Center (publib.boulder.ibm.com/infocenter/

flexsys/information)v IBM SAN Volume Controller Information Center (publib.boulder.ibm.com/

infocenter/svc/ic)v IBM Storwize V3500 Information Center (publib.boulder.ibm.com/infocenter/

storwize/v3500_ic)v IBM Storwize V3700 Information Center (publib.boulder.ibm.com/infocenter/



storwize/ic)v IBM Storwize V7000 Unified Information Center (publib.boulder.ibm.com/

infocenter/storwize/unified_ic)v IBM XIV Storage System Information Center (publib.boulder.ibm.com/

infocenter/ibmxiv/r2)v VMware Documentation (vmware.com/support/pubs)v VMware Product Support (vmware.com/support)v VMware Knowledge Base (kb.vmware.com)

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 (www.ibm.com/storage/support)v IBM Directory of Worldwide Contacts website (www.ibm.com/planetwide)


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

http://publib.boulder.ibm.com/infocenter/dsichelp/ds8000ic

http://publib.boulder.ibm.com/infocenter/flexsys/information

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

http://publib.boulder.ibm.com/infocenter/storwize/v3500_ic



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

http://publib.boulder.ibm.com/infocenter/storwize/unified_ic

http://publib.boulder.ibm.com/infocenter/ibmxiv/r2

http://www.vmware.com/support/pubs

http://www.vmware.com/support

http://kb.vmware.com

http://www.ibm.com

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

http://www.ibm.com/planetwide

Notices

These legal notices pertain to IBM Storage Host Software Solutions productdocumentation.

This information was developed for products and services offered in the U.S.A.

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. 2013, 2014 13

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.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.


TrademarksIBM, 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 (www.ibm.com/legal/us/en/copytrade.shtml).

VMware, ESX, ESXi, vSphere, and vCenter are trademarks or registered trademarksof VMware Corporation in the United States, other countries, or both.

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

Notices 15

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

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


��

Printed in USA

Documents

IBM Storage Integration Serverdelivery04.dhe.ibm.com/.../0/IBM_Storage_Integration_Server_1.2.2_… · IBM DS8000® 6.3.x – relevant to the ... Red Hat Enterprise Linux (RHEL) 6.3