ibm spectrum control, base editiondownload2.boulder.ibm.com/sar/cma/sda/0560f/0/ibm... · the ibm®...

IBM Spectrum Control, Base editionVersion 2.0.0

Release Notes

��

First Edition (March 2015)

This edition applies to version 2.0.0 of the IBM Spectrum Control – Base edition 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, 2015.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Minimum server hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . 3Supported VMware platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Supported browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4CPU and memory consumption on vCenter Orchestrator . . . . . . . . . . . . . . . . . . . 4

Change log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Version 2.0.0 (March 2015) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Known issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Related information and publications . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Getting information, help, and service . . . . . . . . . . . . . . . . . . . . . . . . . . 14

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

© Copyright IBM Corp. 2013, 2015 iii

iv IBM Spectrum Control, Base edition

Overview

The IBM® Spectrum Control – Base edition is a centralized server system thatconsolidates a range of IBM storage provisioning, automation, and monitoringsolutions through a unified server platform.

The IBM Spectrum Control – Base edition is an improved and enhanced version ofthe IBM Storage Integration Server. It provides a single server backend locationand enables centralized management of IBM storage resources for differentvirtualization and cloud platforms. Version 2.0.0 introduces a new GUI and a rangeof enhancements and fixes.

The following solution components, referred to as applications, are included in thesoftware package:v IBM Storage Provider for VMware VASA – Improves the ability to monitor and

automate storage-related operations on VMware platforms. This includessupport for VASA 2, Virtual Volumes. In addition, it uses Storage Policy BasedManagement (SPBM) technology for optimizing the virtual machine provisioningprocess.

v IBM Storage Enhancements for VMware vSphere Web Client – Integrate into theVMware vSphere Web Client platform and enable VMware administrators toindependently and centrally manage their storage resources on IBM storagesystems.

v IBM Storage Plug-in for VMware vCenter Orchestrator – Allows VMwareadministrators to include IBM XIV® discovery and provisioning in their vCenterOrchestrator automation workflows.

v IBM Storage Management Pack for VMware vCenter Operations Manager –Allows VMware administrators to obtain comprehensive monitoring informationabout the IBM XIV resources that are utilized in their virtualized cloudenvironment.

You can download the IBM Spectrum Control – Base edition software package atany time from the IBM Fix Central website (www.ibm.com/support/fixcentral).

Compatibility and requirementsThis section specifies the compatibility and requirements of version 2.0.0 of theIBM Spectrum Control – Base edition.

Note: For information about the compatibility and requirements of a previousversion, refer to relevant release notes of the IBM Storage Integration Server.

Supported storage systemsThe IBM Spectrum Control – Base edition supports different IBM storage systemsas listed in the following table.

Storage systemMicrocodeversion Compatibility note Supported cloud interface(s)

IBM DS8700 6.3.x v IBM Storage Enhancements forVMware vSphere Web Client

© Copyright IBM Corp. 2013, 2015 1

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

Storage systemMicrocodeversion Compatibility note Supported cloud interface(s)

IBM DS8800 6.3.x v IBM Storage Enhancements forVMware vSphere Web Client

IBM Flex System® V7000 7.1.0, 7.2.0 v IBM Storage Provider forVMware VASA

v IBM Storage Enhancements forVMware vSphere Web Client

IBM Spectrum Virtualize 7.1.0, 7.2.0, 7.3.0,7.4.0

Microcode 7.3.0 PTF(with security fix) isalso supported

v IBM Storage Provider forVMware VASA


IBM Storwize® V3500 7.1.0, 7.2.0, 7.3.0,7.4.0




IBM Storwize V3700 7.1.0, 7.2.0, 7.3.0,7.4.0




IBM Storwize V5000 7.1.0, 7.2.0, 7.3.0,7.4.0




IBM Storwize V7000 7.1.0, 7.2.0, 7.3.0,7.4.0




IBM Storwize V7000 Unified 1.4.2, 1.4.3, 1.5.0,1.5.1

Only block storage issupported. File sharesand file systems arenot supported.



IBM XIV Storage System 10.2.4.x

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

VMware VASA 2(VVOL) is supportedby version 11.5.1 andabove.



v IBM Storage Plug-in for VMwarevCenter Orchestrator

v IBM Storage Management Packfor VMware vCenter OperationsManager

IBM Spectrum Accelerate 11.5.0.b v IBM Storage Enhancements forVMware vSphere Web Client

v IBM Storage Plug-in for VMwarevCenter Orchestrator

IBM FlashSystem 840 1.2.0 v IBM Storage Provider forVMware VASA

2 IBM Spectrum Control, Base edition

Note: Newer microcode versions may also be compatible. When a newermicrocode version becomes available, contact IBM Support to inquire whether thenew microcode version is compatible with version 2.0.0 of the IBM SpectrumControl – Base edition. Alternatively, check for a newer version of the IBMSpectrum Control – Base edition.

Supported operating systemsThe IBM Spectrum Control – Base edition software can be installed on thefollowing Linux versions.

Operating system Architecture

Red Hat Enterprise Linux (RHEL) 6.3 – 6.5 x64

Minimum server hardware requirementsThe Linux server upon which the IBM Spectrum Control – Base edition is installedshould meet the following minimum hardware requirements:v 64-bit dual-core CPUv At least 4 GB of RAMv At least 16 GB of free disk space

The same requirements apply if a virtual machine is used instead of a physicalserver.

Note:

v For best performance, use a dedicated server.v The minimum requirements are for supporting up to 20 storage arrays and up to

1000 objects (storage pools, volumes, hosts, mappings, snapshots, mirroringgroups, consistency groups).

Supported VMware platformsVersion 2.0.0 of the IBM Spectrum Control – Base edition supports the followingVMware platforms and frameworks.

VMware platform or framework Version

vSphere Web Client Server 5.1, 5.5.x, 6.0

vSphere APIs for Storage Awareness (VASA) 5.0, 5.1, 5.5.x, 6.0

vCenter Server Appliance (VCSA) 5.5.x, 6.0

vCenter Operations Manager (vCOps) 5.8.x

vCenter Orchestrator (vCO) 5.1.x, 5.5.x

vCloud Automation Center (vCAC) 5.x

Overview 3

Note:

v The IBM Storage Enhancements for VMware vSphere Web Client areautomatically deployed and enabled by registering vCenter servers on the IBMSpectrum Control – Base edition.

v The IBM Storage Plug-in for VMware vCenter Orchestrator is deployed byinstalling its plug-in package on the vCenter Orchestrator server.

v The IBM Storage Management Pack for VMware vCenter Operations Manager isdeployed by installing its PAK file on the vCenter Operations Manager server.

For more information, refer to the user guide.

Supported browsersThe IBM pectrum Control – Base edition can be accessed and managed with thefollowing web browsers:v Microsoft Internet Explorer 10.0 or later.v Mozilla Firefox 21.0 or later.v Google Chrome 39.0 or later.

The required screen resolution for GUI management is 1024×768 or higher.

CPU and memory consumption on vCenter OrchestratorWhen the IBM Storage Plug-in for VMware vCenter Orchestrator is used, the CPUand memory consumption impact on the vCenter Orchestrator server is minimal:approximately 2% CPU usage at peak, and less than 1% memory usage.

The server environment on which the IBM Storage Plug-in for VMware vCenterOrchestrator was tested included:v CPU: 2 vCPU, Intel Xeon X5650 @ 2.67GHzv Memory: 3088 MB

Change logThis section summarizes the changes that were made in different released versionsof the IBM Spectrum Control – Base edition.

Version 2.0.0 (March 2015)Version 2.0.0 of the IBM Spectrum Control – Base edition was the first releasedversion, supporting a range of IBM storage systems and including the followingfeatures and primary components:v Newly designed, powerful and intuitive web management interface with

improved usability and superb user experience.v IBM Storage Provider for VMware VASA, improving ability to monitor and

automate storage-related operations on VMware platforms. This includessupport for VMware virtual volumes (VVOLs), with XIV v11.5.1, and for StoragePolicy Based Management (SPBM).

v IBM Storage Enhancements for VMware vSphere Web Client, allowingVMware administrators to self-provision volumes (LUNs) in selected storagepools that were predefined by the storage administrators. The volumes aremapped to ESXi hosts, clusters, or datacenters as logical drives that can be usedfor storing VMware datastores (virtual machine data containers).


v IBM Storage Plug-in for VMware vCenter Orchestrator, allowing VMwareadministrators to include IBM storage discovery and provisioning in theirvCenter Orchestrator (vCO) automation workflows.

v IBM Storage Management Pack for VMware vCenter Operations Manager,allowing Operations Manager users to obtain comprehensive monitoringinformation about the IBM storage resources that are utilized in their virtualizedenvironment.

For more information about the deployment and usage of the IBM SpectrumControl – Base edition and its components, refer to the user guide.

Known issuesThis section details the known issues in version 2.0.0 of the IBM Spectrum Control– Base edition and its solution components, along with possible solutions orworkarounds (if available).

Note: In this section, the IBM Spectrum Control – Base edition also referred to ascloud integrator.

Table 1. Known issues in IBM Spectrum Control – Base edition

Ticket ID Component Description

HSGSVR-261496 IBM Spectrum Control – Baseedition

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 Spectrum Control – Base edition and thissituation occurs, it prevents the management of thesevolumes through the cloud integrator.

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


DS8000® storage array information is not updated onthe cloud integrator side after a connectivity break, orif the storage admin user group has been modified onthe DS8000 side.

To resolve this issue, restart the cloud integratorservice:service ibm_spectrum_control restart

Overview 5

Table 1. Known issues in IBM Spectrum Control – Base edition (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.



The registration of the IBM Spectrum Control – Baseedition as a VASA storage provider on the vCenterServer side might fail if an expired self-signed SSLcertificate is present on the IBM Spectrum Control –Base edition.

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


Whenever a directory-based storage admin fails to login (from the cloud integrator side) to any storagearray that is in use, cloud integrator immediatelylocks the storage admin user account and all storagearrays become inaccessible on the cloud integratorside.

This is to prevent repeated login attempt failures afterwhich the directory server blocks that user account.

In such a case, update the storage admin credentialson the storage array with which the login has failed.Alternatively, you can remove that specific storagearray from cloud integrator and then reset thecredentials.

You can find the relevant storage array by checkingthe events.log log file. For example:Mar 26 13:50:01 ronend-sc1 ERROR ID:SC-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 IBMSpectrum Control – Base edition, some DS8000 orSAN Volume Controller storage array identifiersmight change, causing cloud integrator to stopsynchronizing with these storage arrays.

To resolve this issue, use the cloud integrator GUI orCLI to remove and then add back these storagearrays.





The Collect Log GUI option does not work onMicrosoft Internet Explorer 10 or 11.

To resolve this issue, disable the Internet ExplorerEnhanced Security Configuration option.


If the IP address of a storage array changes, thesc_storage_array CLI command is unable to updatethe IP address of the storage array.

In such a case, use the cloud integrator GUI to editand update the IP address of the storage array (In theArrays pane, move the mouse pointer over an arraythat you want to update, and then click the Editbutton).


In some cases, the Celery service might hang when itis stopped.

To resolve this issue, terminate the Celerybackground process by using the Linux kill -9command.


When the XIV storage credentials are of an XIVdomain administrator (supported by XIV microcodeversion 11.5 or later), volume mapping might returnthe 'LUN already in use' error message.

This occurs if the LUN number is already associatedwith a volume outside of the XIV domain.



When an XIV array configuration includes a clusterwith no hosts (empty cluster), a volume created fromvSphere Web Client or vCenter Orchestrator ismapped to that cluster in addition to any specifiedhost mapping.

As a result, volumes that were mapped to an emptycluster must be manually unmapped.

To avoid this issue: before mapping volumes to anXIV array, delete all empty cluster configurations onthat array, or add at least one host to each emptycluster.

Overview 7




The DS8000 proxy service fails to stop duringuninstallation or upgrade.

Stopping Django service ... [OK]Stopping Celery services ... [OK]Stopping DS8K proxy.....[FAILED]

To resolve this issue, terminate all the Java™

background processes and then restart the cloudintegrator service.


Cloud integrator fails to lock out a storage adminuser account with LDAP credentials after anunsuccessful login attempt.



Backup and restore operations are not available.



RESTful API may not display the correct number ofstorage array IP interfaces.



A long-running RESTful API task, such as phase-in,phase-out, etc, may not update its current state, ifcloud integrator service has been restarted during itsoperation.



If a vCenter server is disconnected from cloudintegrator during the upgrade, the vWC extensionappears with the previous version, when the vCenterserver is activated.

To resolve this issue, remove and reattach the vCenterserver on cloud integrator.


IBM Spectrum Control – Base edition fails to pullupdates from the storage array, if the internal clock ofits server is set back.

To avoid this issue, set the cloud integrator serverclock to the correct time before the installation.





XIV hosts appear in vWC as disconnected because ofa mismatch between the XIV domain policy and thehost domain settings. When a host without a domainadded to the XIV in the open domain policy mode, itbecomes inaccessible, if the XIV domain access policyis changed to Closed.

To resolve this issue, delete all hosts defined withoutdomain, and add these hosts again with valid domainsettings.


IBM Spectrum Control – Base edition cannot use IPv6addresses for management connection to the XIVstorage systems.

To resolve this issue, use IPv4 addressing, whenconfiguring storage arrays.


Disconnected storage array disappear from the cloudintegrator web interface after the upgrade.

To avoid this issue, before performing upgrade, verifythat all storage arrays are connected to cloudintegrator properly.

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


VVOLVP-261037 IBM Storage Provider forVMware VASA

VASA 2 fails to connect to a storage array if onlymanagement port 1 is down and the rest of themanagement ports are available.

Currently there is no solution or workaround for thislimitation (VVOLVP-261037).

Overview 9

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


VASAVP-261237 IBM Storage Provider forVMware VASA

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.

VASAVP-261268 IBM Storage Provider forVMware VASA

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.


A storage space with a VVOL-enabled service deletedfrom a primary cloud integrator in an HA group, stillexists in the standby cloud integrator.

To resolve this issue, delete the space and the servicefrom the standby cloud integrator manually.


If an array is removed and added to cloud integratorafter its storage resource was added to aVVOL-enabled service, its previous configuration isnot preserved after the addition. This occurs if cloudintegrator is not registered as a VASA provider.

To avoid this issue, verify that cloud integrator isregistered as a VASA provider before adding thearray after its removal. In addition, after the array isadded, it is recommended to check the vCenter logwhether cloud integrator was identified as an activeVASA provider.

HSGSVR-262638 IBM Storage Provider forVMware VASA

User cannot revoke VASA 1 trusted certificates, usingthe cloud integrator web interface.

To resolve this issue, unregister cloud integrator as astorage provider on the vCenter server.


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


HSGSVR-262750 IBM Storage Provider forVMware VASA

Cloud integrator does not generate an error message,when a storage service with a certain capability isattached to a storage array, which does not supportthe required capability.

To avoid this issue, verify that both service andstorage array have matching capabilities before theattachment.

HSGSVR-262815 A storage resource can be created on a manageddomain and non-VVOL-enabled service.

To avoid this issue, do not create a storage resourceon a managed domain and non-VVOL-enabledservice.

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 volumes tothat ESXi host causes both iSCSI and FC to be used forthose 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.


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 IBM StorageVolume object shows incorrect mapping information.Hosts that cannot access the datastore are shown asnot being mapped to the LUN.

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

Overview 11

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



If a volume is mapped to more than one ESXi hostwhile a virtual machine on one of these hosts uses thisvolume as an RDM LUN, the volume informationmight not be displayed correctly in vSphere.



If a volume is mapped to two or more ESXi hosts thatare 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.


Error message 'Could not connect to vSphere WebClient server' appears if the IBM Spectrum Control –Base edition software is upgraded without firstlogging out from vSphere Web Client.

To avoid this error on the cloud integrator side, logout of vSphere Web Client before upgrading the cloudintegrator software.


If the host_rescan_timeout parameter value ischanged to 1 in the vwc_config.ini configuration file(on the cloud integrator), volume creation andmapping operations might fail.

To avoid this issue, keep the default value of 300 orkeep the value higher than 1.


When deleting a volume that is mapped to a host, themapping is removed but the volume is not deleted.No indication is given on vSphere Web Client that thevolume still exists.

To avoid this issue, unmap the volume before deletingit.


DS8000 volume creation might fail when mappingmultiple volume groups to one ESXi host.

If you encounter this problem, configure only onevolume group for one ESXi host when creating andmapping a volume.


A volume cannot be moved to or from a child storagepool on IBM Spectrum Virtualize (7.4), using vSphereWeb Client.



Table 4. Known issues in IBM Storage Plug-in for VMware vCenter Orchestrator


VCOPLUGIN-133 IBM Storage Plug-in forVMware vCenterOrchestrator

Due to a known issue in VMware vCenterOrchestrator, title texts are displayed improperly afterclicking the IBM Storage tab.

Currently there is no solution or workaround for thislimitation (VCOPLUGIN-133).

VCOPLUGIN-162 IBM Storage Plug-in forVMware vCenterOrchestrator

If the Map workflow uses initiators that are notconfigured on the storage array, the workflowsucceeds even though the initiators are silentlyignored.

Currently there is no solution or workaround for thislimitation (VCOPLUGIN-162).

Table 5. Known issues in IBM Storage Management Pack for VMware vCenter Operations Manager


HSGSVR-262168 IBM Storage ManagementPack for VMware vCenterOperations Manager

Not all XIV informational-level severity events arereported by the IBM Spectrum Control – Base editionto vCenter Operations Manager.Note: All other XIV severity events (Warning, Minor,Major, Critical) are reported.


VCOP-244615 IBM Storage ManagementPack for VMware vCenterOperations Manager

The thresholds reported to the vCOps server aretailored for XIV microcode version 11.2 or later, butnot for earlier XIV microcode versions.

To resolve this issue, manually update to thethresholds in vCOps to match the XIV microcode thatyou are using.


If a storage object name contains spaces, it isdisplayed in the vCOps custom view with underlinesinstead of spaces.

Currently there is no solution or workaround for thislimitation (VCOP-244666).


Duplicate thresholds might be appear in vCOps if avCOps server was removed from the IBM SpectrumControl – Base edition and then re-added.

To resolve this issue, delete the duplicate thresholds.


If the vCOps server becomes unreachable while theIBM Spectrum Control – Base edition is still reportingto it, the reporting ceases when the vCOps serverbecomes reachable again.

To resolve this issue, restart the IBM SpectrumControl – Base edition service.

Overview 13

Related information and publicationsYou can find additional information and publications related to the IBM SpectrumControl – Base edition on the following information sources.v IBM Knowledge Centerv 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://www.ibm.com/support/knowledgecenter

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, 2015 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.

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, vCenter, and vCloud are trademarks or registeredtrademarks of VMware Corporation in the United States, other countries, or both.

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

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

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

��

Printed in USA

ibm spectrum control, base editiondownload2.boulder.ibm.com/sar/cma/sda/0560f/0/ibm... · the ibm®...

Documents