IBM Storage Integration Serer Version 1.2.2 Release Notes
First Edition (June 2014) This edition applies to ersion 1.2.2 of the IBM Storage Integration Serer software package. Newer document editions may be issued for the same product ersion in order to add missing information or amend typographical errors. The edition is reset to 'First Edition' for eery new product ersion. Copyright IBM Corporation 2013, 2014. US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents Oeriew................................... 1 Compatibility and requirements............................. 1 Supported storage systems............................. 1 Supported operating systems............................. 2 Minimum serer hardware requirements......................... 2 Supported VMware platforms............................ 2 Supported browsers................................ 3 Change log.................................... 3 Version 1.2.2 (June 2014).............................. 3 Version 1.2.1 (May 2014).............................. 3 Version 1.2.0 (March 2014).............................. 4 Version 1.1.0 (October 2013)............................. 5 Known issues................................... 6 Related information and publications........................... 12 Getting information, help, and serice.......................... 12 Notices................................... 13 Trademarks................................... 15 Copyright IBM Corp. 2013, 2014 iii
i IBM Storage Integration Serer
Oeriew The IBM Storage Integration Serer is a centralized serer system that consolidates a range of IBM storage proisioning, automation, and monitoring solutions through a unified serer platform. The IBM Storage Integration Serer proides a single serer back-end location and enables centralized management of IBM storage resources for the use of Independent Software Vendor (ISV) platforms and frameworks, which currently include VMware Center Serer, VMware Sphere Web Client, and VMware Sphere APIs for Storage Awareness (VASA). The following IBM storage solution components are included in the software package: IBM Storage Proider for VMware VASA Improes the ability to monitor and automate storage-related operations on VMware platforms. IBM Storage Enhancements for VMware Sphere Web Client Integrate into the VMware Sphere Web Client platform and enable VMware administrators to independently and centrally manage their storage resources on IBM storage systems. You can download the IBM Storage Integration Serer software package at any time from the IBM Fix Central website (ibm.com/support/fixcentral). Compatibility and requirements This section specifies the compatibility and requirements of ersion 1.2.2 of the IBM Storage Integration Serer. Note: For information about the compatibility and requirements of a preious ersion, refer to its releant release notes. Supported storage systems The IBM Storage Integration Serer supports different IBM storage systems as listed in the following table. Storage system Microcode ersion Compatibility note IBM DS8000 6.3.x releant to the 8700 and 8800 Series 7.0, 7.1, 7.2 releant to the 8870 Series Not supported by the IBM Storage Proider for VMware VASA Supported only by the IBM Storage Enhancements for VMware Sphere Web Client 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 (with security fix) is also supported Copyright IBM Corp. 2013, 2014 1
Storage system Microcode ersion Compatibility note IBM Storwize V3500 7.1.0, 7.2.0 Microcode 7.2.0 PTF (with security fix) is also supported IBM Storwize V3700 7.1.0, 7.2.0 Microcode 7.2.0 PTF (with security fix) is also supported IBM Storwize V5000 7.1.0, 7.2.0 Microcode 7.2.0 PTF (with security fix) is also supported IBM Storwize V7000 7.1.0, 7.2.0 Microcode 7.2.0 PTF (with security fix) is also supported IBM Storwize V7000 Unified 1.4.2, 1.4.3 Only block-type storage is supported. File shares and file systems are not supported. 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 systems The IBM Storage Integration Serer software can be installed on the following Linux ersion. Operating system Red Hat Enterprise Linux (RHEL) 6.3 or 6.4 Architecture x64 Note: The IBM Storage Enhancements for VMware Sphere Web Client are automatically deployed and enabled on the VMware Sphere Web Client Serer, by registering the Sphere Web Client Serer on the connected IBM Storage Integration Serer. For more information, refer to the user guide. Minimum serer hardware requirements The Linux serer upon which the IBM Storage Integration Serer is installed should meet the following minimum hardware requirements. 64-bit dual-core CPU At least 4 GB of RAM At least 15 GB of free disk space Supported VMware platforms The IBM Storage Integration Serer is compatible with the following VMware platforms and frameworks: VMware Sphere Web Client Serer 5.1 or 5.5 VMware APIs for Storage Awareness (VASA) 5.0, 5.1, or 5.5 VMware Center Serer Appliance (VCSA) 5.5 2 IBM Storage Integration Serer
Supported browsers The IBM Storage Integration Serer can be accessed and managed with the following web browsers: Microsoft Internet Explorer 9.0 or later Mozilla Firefox 21.0 or later Google Chrome 27.0 or later The IBM Storage Enhancements for VMware Sphere Web Client can be used on any browser that is supported by VMware Sphere Web Client Serer. For up-to-date information, refer to the Sphere 5 Documentation Center (pubs.mware.com/sphere-50/index.jsp). Change log This section summarizes the changes that were made in different released ersions of the IBM Storage Integration Serer. Version 1.2.2 (June 2014) Version 1.2.2 resoles the following critical issue. Ticket ID HSGSVR-261914 Description Fixed: OpenSSL 1.0.1g includes an additional security ulnerability (CVE-2014-0224, part of the Heartbleed bug) that could hae an impact on the connection to storage arrays. Version 1.2.2 uses OpenSSL ersion 1.0.1h, which resoles this security issue. Attention: To further protect the Red Hat Enterprise Linux serer upon which the IBM Storage Integration Serer is installed, make sure that the operating system uses the updated OpenSSL ersion as well. Version 1.2.1 (May 2014) Version 1.2.1 adds support for Red Hat Enterprise Linux (RHEL) 6.4 and resoles the following critical issue. Ticket ID HSGSVR-261835 Description Fixed: OpenSSL 1.0.1a-f security ulnerability (also known as the Heartbleed bug) could hae an impact on the Integration Serer connection to storage arrays. Version 1.2.1 uses OpenSSL ersion 1.0.1g, which resoles this security issue. Attention: To further protect the Red Hat Enterprise Linux serer upon which the IBM Storage Integration Serer is installed, make sure that the operating system uses the updated OpenSSL ersion as well. Oeriew 3
Version 1.2.0 (March 2014) Version 1.2.0 adds support for newer microcode ersions of the supported IBM storage systems. Additional changes in ersion 1.2.0: Ticket ID VWC-261300 VWC-261635 VWC-261650 HSGSVR-261544 HSGSVR-261657 HSGSVR-261661 HSGSVR-261674 Description Enhancement: Specifying the Integration Serer URL on the Sphere Web Client Serer side is no longer required. The Integration Serer connection through port 8443 is now automatically defined for any Center serer that is registered (added) on the IBM Storage Integration Serer side. Enhancement: The IBM Storage Enhancements for VMware Sphere Web Client are now automatically deployed and enabled for each and eery Center serer that is registered on the IBM Storage Integration Serer side. Manual installation on the Sphere Web Client Serer host is no longer required. This includes support for VMware Center Serer Appliance (VCSA) ersion 5.5, which can be registered on the Integration Serer side like any other Center serer. Enhancement: In the Create New Volume wizard (IBM Storage Enhancements for VMware Sphere Web Client), an option to select the Logical Unit Number (LUN) for the new olume is now aailable. Enhancement: Integration Serer eent logging is now compatible with the Rsyslog application, an open source utility for forwarding log messages oer IP networks (for more information, see the Rsyslog website). Two configuration files, ibmsyslog.conf and ibmsyslog.conf, hae been added to control the way Rsyslog collects and distributes the Integration Serer logs. For more information, refer to the user guide. Enhancement: All integration Serer eents are recorded according to their type (Info, Error, or Warning) in the eents.log file, located in /ar/log/isis/. Enhancement: Improed support for Lightweight Directory Access Protocol (LDAP) Actie Directory access through Transport Layer Security (TLS). Enhancement: Added isis_ldap, a new CLI utility for configuring directory user access to the IBM Storage Integration Serer through LDAP authentication. For more information, refer to the user guide. 4 IBM Storage Integration Serer
Ticket ID HSGSVR-261717 HSGSVR-261470 HSGSVR-261692 VWC-261665 HSGSVR-261549 HSGSVR-261689 HSGSVR-261732 VWC-261541 VWC-261664 Description Enhancement: New information is displayed per storage array in both the GUI (Storage Arrays list) and CLI (isis_storage_array list): Time of the last storage array information update. Any connection error (if and when it occurs). Change: The import_asa115 command has been deprecated. The isis_configuration restore command can now be used for importing ersion 1.1.5 backups. For more information, refer to the user guide. Change: Users are now required to indicate whether the storage admin user (for adding storage arrays) is defined locally on the storage arrays, or on a directory serer. This indication is now displayed in both the GUI and CLI. If the storage admin account is defined on a directory serer, an account lock preention mechanism is applied on the Integration Serer side. For more information, refer to the user guide. Change: The build number is also displayed as part of the IBM Storage Enhancements ersion. Fixed: "Unexpected error" message appears when remoing a storage array and clicking another tab before the operation is completed. Fixed: In some cases, adding arrays with directory-based storage credentials might fail. Fixed: Adding more than one DS8000 storage array to the IBM Storage Integration Serer causes malfunctions. Fixed: DS8000 olumes might be mapped but not attached to an ESXi host. Fixed: Creation of DS8000 olumes that are larger than 16 TB fails (creation through the IBM Storage Enhancements for VMware Sphere Web Client). Version 1.1.0 (October 2013) Version 1.1.0 of the IBM Storage Integration Serer was the first released ersion, supporting a range of IBM storage systems and including the following features and primary components: Web-based access to all Integration Serer management functions using a standard browser. Both the graphical user interface (GUI) and command-line interface (CLI) can be used for management. IBM Storage Proider for VMware VASA Now a part of the IBM Storage Integration Serer 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 Serer user credentials. Oeriew 5
Configuration backups that were made with the preious release (IBM Storage Proider for VMware VASA, ersion 1.1.5) can be easily imported. IBM Storage Enhancements for VMware Sphere Web Client A brand new addition to the VMware Sphere Web Client platform, proiding powerful management features and capabilities, including: Full control oer IBM storage olumes (LUNs), including olume creation, resizing, renaming, migration to a different storage pool, mapping, unmapping, and deletion. Easy and integrated allocation of olumes to VMware datastores, used by irtual machines that run on ESXi hosts, clusters, or datacenters. Storage pools that are attached to Center serers on the IBM Storage Integration Serer side. For more information about the deployment and usage of the IBM Storage Integration Serer and its components, refer to the user guide. Known issues This section details the known issues in ersion 1.2.2 of the IBM Storage Integration Serer and its solution components, along with possible solutions or workarounds (if aailable). Table 1. Known issues in IBM Storage Integration Serer Ticket ID Component Description HSGSVR-261496 HSGSVR-261731 IBM Storage Integration Serer IBM Storage Integration Serer Volumes that were migrated from an XIV storage array (A) to another XIV storage array (B) using Hyper-Scale Mobility (online olume migration) might not be manageable. This specifically occurs if the olumes on the original XIV storage array (A) are deleted from the storage array (A), and then the same olume IDs are reused on that storage array (A). If both XIV systems (A and B) are connected to the same IBM Storage Integration Serer and this situation occurs, it preents the management of these olumes through the Integration Serer. Currently there is no solution or workaround for this limitation (HSGSVR-261496). DS8000 storage array information is not updated on the Integration Serer side after a connectiity break, or if the storage admin user group has been modified on the DS8000 side. To resole this issue, restart the Integration Serer serice: serice ibm_storage_integration_serer restart 6 IBM Storage Integration Serer
Table 1. Known issues in IBM Storage Integration Serer (continued) Ticket ID Component Description HSGSVR-261745 IBM Storage Integration Serer For Storwize V7000 Unified storage arrays, the microcode ersion number, build number, and system ID number are not consistent when appearing in the Integration Serer, Sphere Web Client, and storage system management GUIs. Different ersion numbers and system IDs are displayed on each platform. HSGSVR-261753 HSGSVR-261752 HSGSVR-261763 IBM Storage Integration Serer IBM Storage Integration Serer IBM Storage Integration Serer Currently there is no solution or workaround for this limitation (HSGSVR-261745). The registration of the IBM Storage Integration Serer as a VASA storage proider on the Center Serer side might fail if an expired self-signed SSL certificate is present on the IBM Storage Integration Serer. To resole this issue, replace the self-signed certificate as explained in the user guide. After adding a SAN Volume Controller storage array on the IBM Storage Integration Serer, the IBM Storage Proider for VMware VASA cannot detect SAN Volume Controller eents. To resole this issue, remoe and then add again the SAN Volume Controller storage array. If the Integration Serer fails to update storage information on a particular Center serer due to a connection problem, all other Center serers are not updated as well. To resole this problem, reestablish the connection with the Center serer, or remoe it from the list of Sphere Web Client serers. Oeriew 7
Table 1. Known issues in IBM Storage Integration Serer (continued) Ticket ID Component Description HSGSVR-261771 IBM Storage Integration Serer Wheneer a directory-based storage admin fails to log in (from the Integration Serer side) to any storage array that is in use, the Integration Serer immediately locks the storage admin user account and all storage arrays become inaccessible on the Integration Serer side. This behaior is part of the Integration Serer design, in order to preent repeated login attempt failures after which the directory serer blocks that user account. In such a case, update the storage admin credentials on the storage array with which the login has failed. Alternatiely, you can remoe the that specific storage array from the Integration Serer and then reset the credentials. HSGSVR-261778 IBM Storage Integration Serer You can find the releant storage array by checking the eents.log log file. For example: Mar 26 13:50:01 ronend-isis1 ERROR ID:ISIS-0008 Seerity:ERROR Parameters:reason=Logging in to array 2810-214-MN65025 has failed with the proided credentials.,user_name=ronenu Message:Storage credentials for user ronenu were disabled. Reason: Logging in to array 2810-214-MN65025 has failed with the proided credentials. After an upgrade or reinstallation of the IBM Storage Integration Serer, some DS8000 or SAN Volume Controller storage array identifiers might change, causing the Integration Serer to stop synchronizing with these storage arrays. To resole this issue, use the Integration Serer GUI or CLI to remoe and then add back these storage arrays. 8 IBM Storage Integration Serer
Table 1. Known issues in IBM Storage Integration Serer (continued) Ticket ID Component Description HSGSVR-261905 IBM Storage Integration Serer When replacing the self-signed SSL certificate files on the IBM Storage Integration Serer, changing the default path of these files causes the IBM Storage Enhancements for VMware Sphere Web Client not to work properly. To aoid this problem, always use the default directory and specific filenames (p.key, p.crt) for the SSL certificate files: /opt/ibm/ibm_storage_integration_serer/settings/ ssl_cert/p.key /opt/ibm/ibm_storage_integration_serer/settings/ ssl_cert/p.crt For information about how to replace the self-signed SSL certificate files, refer to the user guide. Table 2. Known issues in IBM Storage Proider for VMware VASA Ticket ID Component Description VASAVP-261222 IBM Storage Proider for VMware VASA Manual storage capability definitions that were made for XIV arrays in ersion 1.1.5 cannot be imported, and are lost when upgrading to the IBM Storage Integration Serer release. This is because storage capabilities in the latest release of the IBM Storage Proider for VMware VASA (now part of the IBM Storage Integration Serer) are automatically created and assigned. Currently there is no solution or workaround for this limitation (VASAVP-261222). Oeriew 9
Table 2. Known issues in IBM Storage Proider for VMware VASA (continued) Ticket ID Component Description VASAVP-261237 IBM Storage Proider for VMware VASA When the IBM Storage Proider for VMware VASA and the IBM Tioli Storage Productiity Center (TPC) storage proider are registered on the same VMware Center serer, while the same storage array is configured for both, Center uses IBM Tioli Storage Productiity Center proider as the only source of information for that array's storage iews on Sphere Client. In such a case, determine whether the IBM Tioli Storage Productiity Center capabilities are sufficient for replacing the IBM Storage Proider for VMware VASA. If the IBM Storage Proider for VMware VASA is still needed, IBM TPC 5.2 (or later) proides a method of excluding storage arrays from a specific storage proider, allowing you to remoe the array association with the IBM TPC proider. VASAVP-261268 IBM Storage Proider for VMware VASA For more information, refer to the IBM Tioli Storage Productiity Center documentation. If spaces are included in the IP interface name (iscsi) of an XIV storage array, that XIV array cannot be monitored by the IBM Storage Proider for VMware VASA, and information of that XIV array is not isible to the releant Center serer. To aoid this issue, do not include spaces in the IP interface name of the XIV storage array. Table 3. Known issues in IBM Storage Enhancements for VMware Sphere Web Client Ticket ID Component Description VWC-261324 IBM Storage Enhancements for VMware Sphere Web Client If a combination of both iscsi and FC initiator port types is defined for an ESXi host, mapping olumes to that ESXi host causes both iscsi and FC to be used for those olumes. To aoid this situation, use the storage system management tools to define only one actie protocol type (iscsi or FC) for the initiators of each ESXi host. 10 IBM Storage Integration Serer
Table 3. Known issues in IBM Storage Enhancements for VMware Sphere Web Client (continued) Ticket ID Component Description VWC-261530 IBM Storage Enhancements for VMware Sphere Web Client When using the storage system management GUI (as opposed to the IBM Storage Enhancements GUI in Sphere Web Client) to map a single olume to more than one ESXi hosts using different LUN IDs, the olume is not properly recognized by Sphere Web Client and cannot be managed by the IBM Storage Enhancements. In addition, multiple errors might occur on the Sphere Web Client during the use or modification of that olume. VWC-261542 VWC-261696 VWC-261713 VWC-261724 IBM Storage Enhancements for VMware Sphere Web Client IBM Storage Enhancements for VMware Sphere Web Client IBM Storage Enhancements for VMware Sphere Web Client IBM Storage Enhancements for VMware Sphere Web Client To aoid this issue, always use the same LUN ID when mapping a olume to multiple ESXi hosts ia the storage system management GUI. The Manage > Host Mapping tab of the IBM Storage Volume object shows incorrect mapping information. Hosts that cannot access the datastore are shown as not being mapped to the LUN. Currently there is no solution or workaround for this limitation (VWC-261542). The IBM Storage Enhancements for Sphere Web Client do not impose a limit on the number of mapped olumes per ESXi host. Howeer, since any ESXi host is limited to 256 LUNs, additional newly created olumes are not recognized and cannot be used with an ESXi host that already uses 256 olumes. To aoid this issue, do not map more than 256 olumes to a single ESXi host. If a olume is mapped to more than one ESXi host while a irtual machine on one of these hosts uses this olume as an RDM LUN, the olume information might not be displayed correctly in Sphere. Currently there is no solution or workaround for this limitation (VWC-261713). If a olume is mapped to two or more ESXi hosts that are managed by more than one Center serer, olume operations fail. To aoid this issue, do not map a specific olume to ESXi hosts that are not managed by the same Center serer. Oeriew 11
Table 3. Known issues in IBM Storage Enhancements for VMware Sphere Web Client (continued) Ticket ID Component Description VWC-261727 IBM Storage Enhancements for VMware Sphere Web Client If a DS8000 olume is mapped using 255 as the LUN ID, the olume cannot be mapped to other ESXi hosts anymore, een to hosts that their LUN 255 slot as aailable. To aoid this issue, do not use LUN 255 when mapping DS8000 olumes. Related information and publications You can find additional information and publications related to the IBM Storage Integration Serer on the following information sources. IBM Storage Host Software Solutions Information Center (publib.boulder.ibm.com/infocenter/strhosts/ic) IBM DS8000 Information Center (publib.boulder.ibm.com/infocenter/dsichelp/ ds8000ic) IBM Flex System Information Center (publib.boulder.ibm.com/infocenter/ flexsys/information) IBM SAN Volume Controller Information Center (publib.boulder.ibm.com/ infocenter/sc/ic) IBM Storwize V3500 Information Center (publib.boulder.ibm.com/infocenter/ storwize/3500_ic) IBM Storwize V3700 Information Center (publib.boulder.ibm.com/infocenter/ storwize/3700_ic) IBM Storwize V5000 Information Center (publib.boulder.ibm.com/infocenter/ storwize/5000_ic) IBM Storwize V7000 Information Center (publib.boulder.ibm.com/infocenter/ storwize/ic) IBM Storwize V7000 Unified Information Center (publib.boulder.ibm.com/ infocenter/storwize/unified_ic) IBM XIV Storage System Information Center (publib.boulder.ibm.com/ infocenter/ibmxi/r2) VMware Documentation (mware.com/support/pubs) VMware Product Support (mware.com/support) VMware Knowledge Base (kb.mware.com) Getting information, help, and serice If you need help, serice, technical assistance, or want more information about IBM products, you can find arious sources to assist you. You can iew the following websites to get information about IBM products and serices and to find the latest technical information and support. IBM website (ibm.com ) IBM Support Portal website (www.ibm.com/storage/support) IBM Directory of Worldwide Contacts website (www.ibm.com/planetwide) 12 IBM Storage Integration Serer
Notices These legal notices pertain to IBM Storage Host Software Solutions product documentation. This information was deeloped for products and serices offered in the U.S.A. IBM may not offer the products, serices, or features discussed in this document in other countries. Consult your local IBM representatie for information on the products and serices currently aailable in your area. Any reference to an IBM product, program, or serice is not intended to state or imply that only that IBM product, program, or serice may be used. Any functionally equialent product, program, or serice that does not infringe any IBM intellectual property right may be used instead. Howeer, it is the user's responsibility to ealuate and erify the operation of any non-ibm product, program, or serice. IBM may hae patents or pending patent applications coering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drie Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd. 1623-14, Shimotsuruma, Yamato-shi Kanagawa 242-8502 Japan The following paragraph does not apply to the United Kingdom or any other country where such proisions are inconsistent with local law: 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 states 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 improements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Copyright IBM Corp. 2013, 2014 13
Any references in this information to non-ibm Web sites are proided for conenience only and do not in any manner sere as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product 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 it beliees appropriate without incurring any obligation to you. Licensees of this program who wish to hae information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Attn: Office of Legal Counsel 650 Harry Road San Jose, CA 95120-6099 U.S.A. Such information may be aailable, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material aailable for it are proided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equialent agreement between us. Any performance data contained herein was determined in a controlled enironment. Therefore, the results obtained in other operating enironments may ary significantly. Some measurements may hae been made on deelopment-leel systems and there is no guarantee that these measurements will be the same on generally aailable systems. Furthermore, some measurements may hae been estimated through extrapolation. Actual results may ary. Users of this document should erify the applicable data for their specific enironment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly aailable sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objecties only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of indiiduals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. 14 IBM Storage Integration Serer
Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and serice names might be trademarks of IBM or other companies. A current list of IBM trademarks is aailable on the Copyright and trademark information website (www.ibm.com/legal/us/en/copytrade.shtml). VMware, ESX, ESXi, Sphere, and Center are trademarks or registered trademarks of VMware Corporation in the United States, other countries, or both. Other product and serice names might be trademarks of IBM or other companies. Notices 15
16 IBM Storage Integration Serer
Printed in USA