ibm storage integration server -...

IBM Storage Integration ServerVersion 1.1.0

User Guide

SC27-5999-01

��

NoteBefore using this document and the product it supports, read the information in “Notices” on page 75.

Edition notice

Publication number: SC27-5999-01. This publication applies to version 1.1.0 of the IBM Storage Integration Serverand to all subsequent releases and modifications until otherwise indicated in a newer publication.

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

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixWho should use this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixConventions used in this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixRelated information and publications . . . . . . . . . . . . . . . . . . . . . . . . . . . ixGetting information, help, and service . . . . . . . . . . . . . . . . . . . . . . . . . . . xOrdering publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xSending your comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Included solution components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

IBM Storage Provider for VMware VASA . . . . . . . . . . . . . . . . . . . . . . . . . 1IBM Storage Enhancements for VMware vSphere Web Client . . . . . . . . . . . . . . . . . . 1

Concept diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Compatibility and requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Required vSphere privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Download site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2. Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Extracting and installing the Integration Server software package . . . . . . . . . . . . . . . . . . 5Installing the IBM Storage Enhancements for VMware vSphere Web Client . . . . . . . . . . . . . . 6Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Uninstalling the Integration Server software . . . . . . . . . . . . . . . . . . . . . . . 10Uninstalling the IBM Storage Enhancements for VMware vSphere Web Client . . . . . . . . . . . . 11

Chapter 3. Integration Server operation and management . . . . . . . . . . . . . . 13Required and optional initial tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Configuring LDAP user authentication . . . . . . . . . . . . . . . . . . . . . . . . . . 14Managing the Integration Server from the command-line interface (CLI) . . . . . . . . . . . . . . . 15

CLI – Switching to 'ISIS' user mode . . . . . . . . . . . . . . . . . . . . . . . . . . 15CLI – Adding and managing Integration Server users . . . . . . . . . . . . . . . . . . . . 16CLI – Adding or removing storage array credentials . . . . . . . . . . . . . . . . . . . . . 17CLI – Adding or removing storage arrays . . . . . . . . . . . . . . . . . . . . . . . . 18CLI – Setting the VASA Secret credentials . . . . . . . . . . . . . . . . . . . . . . . . 20CLI – Managing vCenter servers and storage pools for vSphere Web Client . . . . . . . . . . . . . 21CLI – Backing up or restoring an Integration Server configuration . . . . . . . . . . . . . . . . 24

Managing the Integration Server from the graphical user interface (GUI) . . . . . . . . . . . . . . . 25GUI – Logging in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26GUI – Managing storage arrays. . . . . . . . . . . . . . . . . . . . . . . . . . . . 26GUI – Managing Integration Server users . . . . . . . . . . . . . . . . . . . . . . . . 32GUI – Managing and monitoring VASA access . . . . . . . . . . . . . . . . . . . . . . 36GUI – Managing servers and storage pools for vSphere Web Client. . . . . . . . . . . . . . . . 37

Chapter 4. Using the IBM Storage Provider for VMware VASA . . . . . . . . . . . . 45Registering the Integration Server as a storage provider in vCenter Server . . . . . . . . . . . . . . 45

Chapter 5. Using the IBM Storage Enhancements for VMware vSphere Web Client . . . 49Setting the Integration Server web address for vCenter servers . . . . . . . . . . . . . . . . . . 49Populating vCenter server information to the Integration Server . . . . . . . . . . . . . . . . . . 50Viewing the IBM storage resource information. . . . . . . . . . . . . . . . . . . . . . . . 52Creating and mapping a new storage volume (LUN) . . . . . . . . . . . . . . . . . . . . . 56

© Copyright IBM Corp. 2013 iii

Extending a volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Renaming a volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Setting multipath policy enforcement for a volume . . . . . . . . . . . . . . . . . . . . . . 63Moving a volume to another storage pool . . . . . . . . . . . . . . . . . . . . . . . . . 64Unmapping a volume from one or more hosts. . . . . . . . . . . . . . . . . . . . . . . . 65Deleting an unused volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Chapter 6. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Checking and controlling the Integration Server service . . . . . . . . . . . . . . . . . . . . 69Checking the log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Checking and modifying the configuration files . . . . . . . . . . . . . . . . . . . . . . . 71

Chapter 7. Best Practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Handling datastores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Handling ESXi hosts that use XIV volumes . . . . . . . . . . . . . . . . . . . . . . . . . 73Distributing volumes evenly on DS8000 systems . . . . . . . . . . . . . . . . . . . . . . . 73

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

iv IBM Storage Integration Server

Figures

1. Integration of IBM storage systems with a VMware environment . . . . . . . . . . . . . . . . 22. VMware vSphere Web Client – Create Role dialog box . . . . . . . . . . . . . . . . . . . 43. Installation language selection box . . . . . . . . . . . . . . . . . . . . . . . . . . 64. IBM Storage Enhancements for VMware vSphere Web Client – installation wizard . . . . . . . . . . 75. Customer Information panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86. VMware vSphere Web Client on the Windows services list . . . . . . . . . . . . . . . . . . 97. 'Add or Remove Programs' dialog box . . . . . . . . . . . . . . . . . . . . . . . . 128. IBM Storage Integration Server login box in a standard web browser . . . . . . . . . . . . . . 269. Clicking Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

10. Current storage array username (for all storage arrays) . . . . . . . . . . . . . . . . . . . 2811. Change Credentials dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . 2812. Add Array dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2913. List of added storage arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2914. Storage array details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3015. Modify Array icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3016. Modify Array dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3117. Remove Array icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3218. Remove Array confirmation message . . . . . . . . . . . . . . . . . . . . . . . . . 3219. Clicking Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3220. Add User dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3321. List of added Integration Server users (user names) . . . . . . . . . . . . . . . . . . . . 3422. Modify User icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3423. Change Password dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3524. Delete User icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3525. Clicking VASA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3626. Current VASA Secret username . . . . . . . . . . . . . . . . . . . . . . . . . . . 3727. Change Secret dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3728. Clicking vSphere Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3829. Add vCenter Server dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . 3930. List of vCenter servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3931. Update vCenter Server Credentials dialog box . . . . . . . . . . . . . . . . . . . . . . 4032. Remove vCenter Server confirmation message . . . . . . . . . . . . . . . . . . . . . . 4133. Attach Storage Pools dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . 4234. List of attached storage pools per vCenter server . . . . . . . . . . . . . . . . . . . . . 4235. Detach Storage Pool confirmation message . . . . . . . . . . . . . . . . . . . . . . . 4336. vSphere Client – Storage Providers list . . . . . . . . . . . . . . . . . . . . . . . . 4637. Add Vendor Provider dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . 4738. vCenter certificate thumbprint dialog box . . . . . . . . . . . . . . . . . . . . . . . 4739. Supported Vendor list displaying the IBM Storage Integration Server . . . . . . . . . . . . . . 4840. Edit IBM Server Address dialog box . . . . . . . . . . . . . . . . . . . . . . . . . 5041. IBM Storage Integration Server connection details per vCenter server . . . . . . . . . . . . . . 5042. Populate vCenter Information option . . . . . . . . . . . . . . . . . . . . . . . . . 5143. Populate vCenter confirmation message . . . . . . . . . . . . . . . . . . . . . . . . 5144. IBM Storage category in vSphere Web Client . . . . . . . . . . . . . . . . . . . . . . 5245. IBM Storage information per storage array . . . . . . . . . . . . . . . . . . . . . . . 5346. Currently available storage pools per storage array . . . . . . . . . . . . . . . . . . . . 5347. IBM Storage information per vCenter server . . . . . . . . . . . . . . . . . . . . . . 5448. IBM Storage information per datacenter . . . . . . . . . . . . . . . . . . . . . . . . 5449. IBM Storage information per datastore . . . . . . . . . . . . . . . . . . . . . . . . 5450. IBM Storage information per all ESXi hosts of a vCenter server . . . . . . . . . . . . . . . . 5551. IBM Storage information per all VM templates of a vCenter server . . . . . . . . . . . . . . . 5552. IBM Storage information per all vApps of a vCenter server . . . . . . . . . . . . . . . . . 5553. IBM storage array view – Clicking Create New Volume . . . . . . . . . . . . . . . . . . . 5654. Top Level Objects view – Clicking Create New Volume . . . . . . . . . . . . . . . . . . . 5755. Right-clicking the storage array . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

© Copyright IBM Corp. 2013 v

56. Clicking the Create New Volume icon. . . . . . . . . . . . . . . . . . . . . . . . . 5857. Create New Volume wizard (XIV example) . . . . . . . . . . . . . . . . . . . . . . . 5858. Setting the volume size with the graphic space marker . . . . . . . . . . . . . . . . . . . 5959. Creating multiple volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6060. Advanced Host Mapping dialog box . . . . . . . . . . . . . . . . . . . . . . . . . 6161. Clicking Extend on the pop-up menu . . . . . . . . . . . . . . . . . . . . . . . . . 6262. Rename volume option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6363. Rename Volume dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6364. Set Multipath Policy Enforcement option. . . . . . . . . . . . . . . . . . . . . . . . 6465. Change Multipath Policy Enforcement dialog box . . . . . . . . . . . . . . . . . . . . . 6466. Move volume option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6567. Unmap volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6668. Delete volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6769. Integration Server GUI – Collect Logs option . . . . . . . . . . . . . . . . . . . . . . 7070. Integration Server GUI – Saving the logs in a compressed TAR archive . . . . . . . . . . . . . 70

vi IBM Storage Integration Server

Tables

1. Required vSphere privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32. Required tasks in sequential order . . . . . . . . . . . . . . . . . . . . . . . . . . 133. Optional tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144. LDAP configuration parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . 155. Arguments for isis_users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176. Arguments for isis_storage_credentials . . . . . . . . . . . . . . . . . . . . . . . 187. Arguments for isis_storage_array . . . . . . . . . . . . . . . . . . . . . . . . . 198. Arguments for vasa_admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209. Arguments for vwc_vcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

10. Arguments for vwc_pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2311. Arguments for vwc_host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2312. Arguments for isis_configuration . . . . . . . . . . . . . . . . . . . . . . . . . 2513. Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

© Copyright IBM Corp. 2013 vii

viii IBM Storage Integration Server

About this guide

This guide describes how to install, configure, and use the IBM® StorageIntegration Server and its solution components.

Who should use this guideThis guide is intended for system administrators who are familiar with theVMware vCenter and vSphere environments, and with the specific IBM storagesystem that is in use.

Conventions used in this guideThese notices are used in this guide to highlight key information.

Note: These notices provide important tips, guidance, or advice.

Important: These notices provide information or advice that might help you avoidinconvenient or difficult situations.

Attention: These notices indicate possible damage to programs, devices, or data.An attention notice appears before the instruction or situation in which damagecan occur.

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 Flex System™ Information Center (publib.boulder.ibm.com/infocenter/

flexsys/information)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 System Storage® SAN Volume Controller Information Center

(publib.boulder.ibm.com/infocenter/svc/ic)v IBM System Storage DS8000® Information Center (publib.boulder.ibm.com/

infocenter/dsichelp/ds8000ic)v IBM XIV® Storage System Information Center (publib.boulder.ibm.com/

infocenter/ibmxiv/r2)

© Copyright IBM Corp. 2013 ix

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

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

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/svc/ic

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

http://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)

Ordering publicationsThe IBM Publications Center is a worldwide central repository for IBM productpublications and marketing material.

The IBM Publications Center website (www.ibm.com/shop/publications/order/)offers customized search functions to help you find the publications that you need.Some publications are available for you to view or download at no charge. You canalso order publications. The publications center displays prices in your localcurrency.

Sending your commentsYour feedback is important in helping to provide the most accurate and highestquality information.

Procedure

To submit any comments about this guide or any other IBM Storage Host Softwaredocumentation:v Go to the online feedback form (http://pic.dhe.ibm.com/infocenter/strhosts/ic/

topic/com.ibm.help.strghosts.doc/icfeedback.htm). You can use this form toenter and submit comments.

v You can send your comments by email to [email protected]. Be sure toinclude the following information:– Exact publication title and version– Publication form number (for example: GC00-1111-22)– Page, table, or illustration numbers that you are commenting on– A detailed description of any information that should be changed

Note: When you send information to IBM, you grant IBM a nonexclusive rightto use or distribute the information in any way it believes appropriate withoutincurring any obligation to you.

x IBM Storage Integration Server

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

http://www.ibm.com/shop/publications/order/

http://pic.dhe.ibm.com/infocenter/strhosts/ic/topic/com.ibm.help.strghosts.doc/icfeedback.htm

mailto:[email protected]?subject=IBM Storage Host Software Solutions publications

Chapter 1. Introduction

The IBM Storage Integration Server is a centralized server system that consolidatesa range of IBM storage provisioning, automation, and monitoring solutionsthrough 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 VMware APIsfor Storage Awareness (VASA).

Through its user credential, storage system, and storage pool management options,the IBM Storage Integration Server facilitates the integration of IBM storage systemresources with the supported ISV platforms and frameworks, while providing thefoundation for integration with future IBM systems and ISV solutions.

The IBM Storage Integration Server can be managed through a standard webbrowser and a graphical user interface (GUI), or through terminal and acommand-line interface (CLI).

Included solution componentsThe following solution components are included in the IBM Storage IntegrationServer software package:v IBM Storage Provider for VMware VASAv IBM Storage Enhancements for VMware vSphere Web Client

IBM Storage Provider for VMware VASAThe IBM Storage Provider for VMware VASA improves the ability to monitor andautomate storage-related operations on VMware platforms.

From its IBM Storage Integration Server host, the IBM Storage Provider forVMware VASA provides a standard interface for any connected VMware vCenterServer using VMware APIs for Storage Awareness (VASA), delivering informationabout IBM storage topology, capabilities and state, as well as storage events andalerts to vCenter Server in real time.

IBM Storage Enhancements for VMware vSphere Web ClientThe 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.

Depending on the IBM storage system in use, VMware administrators canself-provision volumes (LUNs) in selected storage pools that were predefined bythe storage administrators. The volumes are mapped to ESX hosts, clusters, ordatacenters as logical drives that can be used for storing VMware datastores(virtual machine data containers).

As opposed to the IBM Storage Management Console for VMware vCenter, whichis individually installed on each vCenter server, the IBM Storage Enhancements for

© Copyright IBM Corp. 2013 1

vSphere Web Client are installed only on the vSphere Web Client Server, allowingmultiple vCenter servers to utilize IBM storage resources. In addition, storage poolattachment and detachment operations are performed on the IBM StorageIntegration Server side, rather than on the vSphere Client side.

The IBM Storage Enhancements for VMware vSphere Web Client are provided in asoftware package that is installed separately on the VMware vSphere Web ClientServer, and then communicates with the IBM Storage Integration Server.

Concept diagramThe following concept diagram illustrates how IBM storage systems are accessedand utilized from the VMware environment through the IBM Storage IntegrationServer.

The storage administrator uses the IBM Storage Integration Server to control whichIBM storage systems (arrays) and what storage pools should be available for use inthe VMware environment, and control which specific vCenter servers can utilizethe IBM storage resources. This control, as well as other administrative options, arereferred to in the diagram as Integration Server operation and management.

On the VMware vSphere Web Client side, administrators can create, map, and fullycontrol storage volumes on the available storage systems and storage pools(defined by the storage administrator). In parallel, the IBM Storage IntegrationServer allows registered VMware vCenter servers to connect to it and utilize itsVASA functions, which can be monitored on the vSphere Client station.

Figure 1. Integration of IBM storage systems with a VMware environment

2 IBM Storage Integration Server

Note: The IBM Storage Integration Server can use only predefined storage pools.New storage pools cannot be created from the Integration Server or from VMwarevSphere Web Client, and must be created through the dedicated storage systemmanagement tools.

Compatibility and requirementsFor the complete and up-to-date information about the compatibility andrequirements of the IBM Storage Integration Server, refer to the latest release notes.

You can find the latest release notes on the IBM Storage Host Software SolutionsInformation Center (publib.boulder.ibm.com/infocenter/strhosts/ic) or on the IBMFix Central (www.ibm.com/support/fixcentral).

Note: Refer to the relevant VMware documentation for information about how toinstall the compatible versions of vSphere Web Client Server. You should also referto the latest installation and configuration instructions for ESXi and vCenterservers.

Required vSphere privilegesTo operate the IBM Storage Integration Server functions that relate to the IBMStorage Enhancements for VMware vSphere Web Client, you must have theminimum required privileges defined in your vSphere user role.

Use the Role Manager extension in vSphere Web Client to define the requiredprivileges for your user role as detailed in the following table.

Table 1. Required vSphere privileges

Task Required vSphere user privilege

Adding a vCenter server to the IBM StorageIntegration Server

(see “GUI – Adding a vCenter server” on page38)

v Extension – In this category, select Register extension,Unregister extension, and Update extension.

v Global – In this category, select Log event and Cancel task.

v Tasks – In this category, select Create task and Update task.

v Sessions – In this category, select Impersonate user.

v Host – In this category, select Configuration > Storage partitionconfiguration.

Storage provisioning (volume creation andmanagement) from vSphere Web Client

(see Chapter 5, “Using the IBM StorageEnhancements for VMware vSphere WebClient,” on page 49)

Chapter 1. Introduction 3



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


For more detailed information about how to set the vSphere Web Client privilegetypes, refer to the VMware vSphere 5.1 Documentation Center(pubs.vmware.com/vsphere-51/index.jsp ).

Download siteThe IBM Storage Integration Server is available as a free software solution.

You can download the latest version at any time from the IBM Fix Central(ibm.com/support/fixcentral).

Figure 2. VMware vSphere Web Client – Create Role dialog box


http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.security.doc%2FGUID-93B962A7-93FA-4E96-B68F-AE66D3D6C663.html


Chapter 2. Installation

After downloading the IBM Storage Integration Server software package, you canbegin the installation as described in the following sections.v “Extracting and installing the Integration Server software package”v “Installing the IBM Storage Enhancements for VMware vSphere Web Client” on

page 6

Extracting and installing the Integration Server software packageYou can install the IBM Storage Integration Server software on a compatibleversion of Red Hat Enterprise Linux (RHEL). For more information, refer to therelease notes.

Procedure

Perform the following procedure to install the IBM Storage Integration Server:1. Copy the installation package file to a local folder on the Linux host that will

be used as the IBM Storage Integration Server.2. Extract the installation package file ('* ' represents for the build number) :

# tar xvf ibm_storage_integration_server-1.1.0-*.tar.gz

The following RPM files are extracted:v nginx-1.4.1-1.el6.ngx.x86_64.rpm

v postgresql92-9.2.2-1PGDG.rhel6.x86_64.rpm

v postgresql92-contrib-9.2.2-1PGDG.rhel6.x86_64.rpm

v postgresql92-libs-9.2.2-1PGDG.rhel6.x86_64.rpm

v postgresql92-server-9.2.2-1PGDG.rhel6.x86_64.rpm

v uuid-1.6.1-10.el6.x86_64.rpm

v ibm_storage_integration_server-1.1.0-*.rpm – product RPMv ibm_storage_integration_server_java_runtime_extension-1.1.0-*.rpm –

Required if DS8000 is used; should be installed last.3. Go to the extracted directory and then use the rpm -vi *.* command to run

and install all the complementary RPM files and product RPM file.

Important:

v If you choose to install each package separately without using the *.* option, donot install the ibm_storage_integration_server-1.1.0-*.rpm file before all thecomplementary RPM files have been installed, except the one for DS8000.

v If DS8000 is to be used, installibm_storage_integration_server_java_runtime_extension-1.1.0-*.rpm last.

v Issue the service ibm_storage_integration_server stop|start|restartcommand to manage the Red Hat service.

The IBM Storage Provider service starts automatically after the installation, anda new Linux user named isis is created so that you can use it for managementoperations.


Installing the IBM Storage Enhancements for VMware vSphere WebClient

The software package of IBM Storage Enhancements for VMware vSphere WebClient is installed separately on the vSphere Web Client Server.

About this task

This separate Windows-based installation is required in addition to theLinux-based installation of the IBM Storage Integration Server (see “Extracting andinstalling the Integration Server software package” on page 5).

Run this installation on the vSphere Web Client Server to which all vSphere WebClient stations connect. The compatible version of VMware vSphere Web ClientServer must already be installed on the Windows Server host.

Procedure1. Run the installation package file: VMware_vSphere_Web_Client-1.1.0-*-x64.exe2. From the appearing language selection box, select the language that you want

to use in the installation wizard, and then click OK.

Note: The language selection affects only the text that is displayed on theinstallation wizard, including the language used in the IBM license agreement. Itdoes not affect the graphic user interface of the IBM Storage Enhancements forVMware vSphere Web Client, which are available in English only.

After a short preparation, the installation wizard of the IBM StorageEnhancements for VMware vSphere Web Client starts.

Figure 3. Installation language selection box


3. Click Next. The License Agreement panel is displayed.4. Read the IBM License Agreement and then select I accept the terms in the

license agreement.5. Click Next. The Customer Information panel is displayed.

Figure 4. IBM Storage Enhancements for VMware vSphere Web Client – installation wizard

Chapter 2. Installation 7

6. Enter your name and your organization name, and then click Next. The 'Readyto Install the Program' panel is displayed.

7. Click Install to begin the installation.

Note: During the installation, the IBM Storage Enhancements files are copied tofolders in the directory where VMware vSphere Web Client Server is installed.

8. After the files are installed, the Post-Installation Requirement panel isdisplayed, notifying you that you must restart the vSphere Web Client service(Windows service). Click Next and then click Finish.

Important: After the installation, stop the vSphere Web Client service (Windowsservice) and then start it again to make the IBM Storage Enhancements functional.

Figure 5. Customer Information panel


Figure 6. VMware vSphere Web Client on the Windows services list


UninstallationYou can uninstall the IBM Storage Integration Server software packages in twoseparate uninstallation procedures.

Attention:

v To avoid loss of user accounts, credentials, storage array configurations, storagepool attachments, and vCenter server associations – always back up the IBMStorage Integration Server configuration before any uninstallation. For moreinformation, see “CLI – Backing up or restoring an Integration Serverconfiguration” on page 24.

v Uninstalling the software on the IBM Storage Integration Server side causes thefollowing features to cease functioning:– All CLI and GUI management options on the IBM Storage Integration Server

side.– IBM Storage Enhancements on the vSphere Web Client side.– VASA-related operations on the vCenter server side.

However, existing volumes are not affected and continue to function and bemanageable from the standard storage system management tools.

v Uninstalling only the IBM Storage Enhancements for VMware vSphere WebClient on the vSphere Web Client Server side does not affect any existingvolume associations with datastores, nor does it affect the VASA-relatedoperations on the IBM Storage Integration Server side. It only disables the abilityto manage volumes from vSphere Web Client.

The following sections describe how to uninstall each individual software package.v “Uninstalling the IBM Storage Enhancements for VMware vSphere Web Client”

on page 11v “Uninstalling the Integration Server software”

Uninstalling the Integration Server softwareIf you want to completely remove the IBM Storage Integration Server softwarefrom the Linux host upon which it is installed, follow the steps in the followingprocedure.

Before you begin

To avoid loss of user accounts, credentials, storage array configurations, storagepool attachments, and vCenter server associations – always back up the IBMStorage Integration Server configuration before any uninstallation. For moreinformation, see “CLI – Backing up or restoring an Integration Serverconfiguration” on page 24.

Before removing the IBM Storage Integration Server:v Uninstall the IBM Storage Enhancements for VMware vSphere Web Client (and

restart the Web Client service).v Remove the vCenter server definitions by using the IBM Storage Integration

Server User Interface.v Unregister any VASA providers that are registered to this IBM Storage

Integration Server (From the vSphere client).


Procedure

To uninstall the Integration Server software from the Linux host:1. Log on to the Linux command prompt environment as a root user.2. Stop the Integration Server service, as explained in “Checking and controlling

the Integration Server service” on page 69.3. Run the standard Linux uninstallation command for each installed package (as

detailed in “Extracting and installing the Integration Server software package”on page 5).

Uninstalling the IBM Storage Enhancements for VMwarevSphere Web Client

If you want to remove the IBM Storage Enhancements for VMware vSphere WebClient, perform the following procedure.

Before you begin

If there are IBM storage volumes that are currently in use by VMware datastores, itis recommended that these volumes remain monitored by the storage administratoron the IBM storage system side. All volume management functions will bedisabled on the vSphere Web Client side until the IBM Storage Enhancements arereinstalled.

Procedure1. Stop the VMware vSphere Web Client Server service (Windows service; see the

last step in “Installing the IBM Storage Enhancements for VMware vSphereWeb Client” on page 6).

2. From the Windows Control Panel, go to Programs > Programs and Features >Change or Remove Programs, select IBM Storage Enhancements for VMwarevSphere Client on the list of installed programs, and then click Remove.


The uninstallation wizard guides you through the remaining uninstallationsteps.

3. Resume the VMware vSphere Web Client Server service.

Figure 7. 'Add or Remove Programs' dialog box


Chapter 3. Integration Server operation and management

This chapter describes the initial operation tasks, as well as the full range ofmanagement options that are available on the IBM Storage Integration Server.v “Required and optional initial tasks”v “Managing the Integration Server from the command-line interface (CLI)” on

page 15v “Managing the Integration Server from the graphical user interface (GUI)” on

page 25

Required and optional initial tasksAfter the IBM Storage Integration Server is installed, different tasks are requiredbefore the server can become fully operational.

Refer to the following tables for information about the required and optional andmanagement tasks.

Note: Unless specified otherwise in the 'Interface' column, you can perform tasksfrom either the command-line interface (CLI) or graphical user interface (GUI).

Table 2. Required tasks in sequential order

Step Required task Interface Refer to

1. Set a password for the 'isis' user ifnecessary (a Linux root user action), andthen switch to the 'isis' user.

CLI v “CLI – Switching to 'ISIS' user mode” on page 15

2. Log in to the GUI and then change thepassword of the initial admin user.

GUI v “GUI – Logging in” on page 26

v “GUI – Changing the password of an IntegrationServer user” on page 34

3. Add the storage array (storage system)access credentials

CLI orGUI

v “CLI – Adding or removing storage arraycredentials” on page 17

v “GUI – Entering the storage array credentials” onpage 27

4. Add the storage arrays to be used CLI orGUI

v “CLI – Adding or removing storage arrays” onpage 18

v “GUI – Adding a storage array” on page 28

5. Set the VASA access credentials ("VASASecret") to allow connection of vCenterservers that require VASA functions.Note: Not applicable to DS8000 systems.

CLI orGUI

v “CLI – Setting the VASA Secret credentials” onpage 20

v “GUI – Setting the VASA Secret credentials” onpage 36

6. Add vCenter servers for which you want toutilize the IBM Storage Enhancements forVMware vSphere Web Client.

CLI orGUI

v “CLI – Managing vCenter servers and storagepools for vSphere Web Client” on page 21

v “GUI – Adding a vCenter server” on page 38

7. For DS8000 systems only: specify the ESXhost details.

CLI v “CLI – Managing vCenter servers and storagepools for vSphere Web Client” on page 21


Table 2. Required tasks in sequential order (continued)

Step Required task Interface Refer to

8. Attach storage pools to any specific vCenterserver that was added.

CLI orGUI

v “CLI – Managing vCenter servers and storagepools for vSphere Web Client” on page 21

v “GUI – Attaching a storage pool to a vCenterserver” on page 41

Table 3. Optional tasks

Optional task Interface Refer to

Manage the Integration Server users CLI orGUI

v “CLI – Adding and managing Integration Serverusers” on page 16

v “GUI – Managing Integration Server users” onpage 32

Back up or restore an Integration Serverconfiguration, including the data of all existinguser accounts, credentials, storage arrays, andstorage pools.

CLI v “CLI – Backing up or restoring an IntegrationServer configuration” on page 24

Configuring LDAP user authenticationThe IBM Storage Integration Server can authenticate users using LightweightDirectory Access Protocol (LDAP) services.

When LDAP authentication is configured, any login attempt is authenticated bothagainst the local database of Integration Server users, and against the LDAP server.

Note: LDAP is not used when vCenter servers connect to the IBM StorageIntegration Server in order to use VASA services (see “Registering the IntegrationServer as a storage provider in vCenter Server” on page 45).

Use the ldap.ini configuration file (located in ../opt/ibm/ibm_storage_integration_server/conf.d/) to configure LDAP user connectivity toIBM Storage Integration Server.

For example:

# Change to True in order to work with ldapenable_ldap=False server_uri=ldap://servername.domainname:389user_search_dn=ou=users,dc=dcname,dc=com# next is the user search key (uid, preferredId, etc.)user_search_key=uidgroup_search_dn=dc=dcname,dc=com# supported classes: GroupOfNames, NestedGroupOfNames, GroupOfUniqueNames# NestedGroupOfUniqueNames, ActiveDirectoryGroup, NestedActiveDirectoryGroupgroup_object_class=GroupOfUniqueNames# comment out authentication_group_dn if every LDAP authenticated user is allowedauthentication_group_dn=cn=authenticating-group,dc=dcname,dc=com

The following table summarizes the possible LDAP authentication parameters.


Table 4. LDAP configuration parameters

Parameter Indication

enable_ldap True or False.

When True and enabled, the login attempt isauthenticated against the LDAP server.

server_uri LDAP server URL

user_search_dn The DN (Distinguished Name) to be used for usersearch.

user_search_key The search tag for getting a unique RDN (RelativeDistinguished Name)

group_search_dn The DN to be used for group search.

group_object_class The group type that should match the groupsearch.

authentication_group_dn A DN that results in a unique group.

Note:

v user_search_key and user_search_dn return unique results. For example:user_search_key=uiduser_search_dn=ou=users,dc=dcname,dc=com

In this case, if the user name is "John", the resulting DN for matching the userover LDAP would be: uid=John,ou=users,dc=dcname,dc=com

v If authentication_group_dn is set, only users that belong to that group areauthenticated on IBM Storage Integration Server. You can comment it out todisable group authentication.

Managing the Integration Server from the command-line interface (CLI)You can access and control the Integration Server by using its command-lineinterface (CLI) functions locally from the Linux command prompt environment, orfrom a remote terminal connection.

The following sections describe all the CLI configuration and managementfunctions:v “CLI – Switching to 'ISIS' user mode”v “CLI – Adding and managing Integration Server users” on page 16v “CLI – Adding or removing storage array credentials” on page 17v “CLI – Adding or removing storage arrays” on page 18v “CLI – Setting the VASA Secret credentials” on page 20v “CLI – Managing vCenter servers and storage pools for vSphere Web Client” on

page 21v “CLI – Backing up or restoring an Integration Server configuration” on page 24

CLI – Switching to 'ISIS' user modeTo start configuring the IBM Storage Integration Server, you must be logged in asthe isis user in the Linux command prompt environment.

Chapter 3. Integration Server operation and management 15

About this task

isis is a user account that is automatically created after the installation, allowingyou to carry out the Integration Server CLI-based configuration and managementoperations.

If needed, you can set the password for accessing the isis user account externally(for example, from a remote computer over SSH), as described in the followingprocedure.

Procedure

To set a password for the isis user:1. Log in to the Linux command prompt environment as a root user.2. Enter passwd isis and then enter the password for the user account:

[root]# passwd isisChanging password for user isis.New password: **********Retype new password: **********passwd: all authentication tokens updated successfully.[root]#

What to do next

To switch to the ISIS user, enter the su - isis command:

[root]# su - isis

CLI – Adding and managing Integration Server usersAll user accounts that can be used to access the IBM Storage Integration Servermust be individually defined.

You can either define (add) a single Integration Server user account, or definemultiple user accounts to be used separately.

Use the isis_users CLI command to add, delete, or display user accounts, andalso to change the password of any specific account. Use the required argumentafter the command, as specified in the following table.

Note:

v All CLI command arguments are case-sensitive.v The same operations are available from the GUI as well, as explained in “GUI –

Managing Integration Server users” on page 32.


Table 5. Arguments for isis_users

Argument Use after isis_users to:

add -n <username> -p <password>

or:

add --user_name <username> --user_password<password>

Add the username and password of the user that may accessthe IBM Storage Integration Server. You can add more than oneuser.

For example:

isis_users add -n johnvc -p ********

change_password -n <username> -p <newpassword>

or:

change_password --user_name <username>--user_password <password>

Change the password of a user account that was alreadyadded. The password that you type for the specified usernameis set as the new password.

For example:

isis_users change_password -n johnvc -p **********

delete -n <username>

or:

delete --user_name <username>

Delete a user account from the server.

For example:

isis_users delete -n johnvc

list Display the names of currently defined user accounts.

For example:

isis_users listjohn_vczivkal_vclihit_vc

-h

or --help

Display help information that is relevant to isis_users.

You can also display help for the add_user, change_password, ordelete_user argument if it is typed on the command line aswell.

CLI – Adding or removing storage array credentialsThis section explains how to set the credentials that will be used to connect to theIBM storage system, or systems, that your VMware platforms use for storageprovisioning.

Important:

v The same credentials (the same username and password) must already bepredefined on all the IBM storage arrays that you intend to use. The IBMStorage Integration Server cannot use more than a single array managementaccount. For more information about how to define a user account on the IBMstorage systems, refer to the relevant storage system management toolsdocumentation.

v Setting the storage credentials on the IBM Storage Integration Server allows youto add the IBM storage arrays on the next step.


Use the isis_storage_credentials CLI command to set (add), remove, or displaythe current storage array access credentials that the Integration Server uses in orderto access all the IBM storage arrays. Use the required argument after the command,as specified in the following table.

Note:


Entering the storage array credentials” on page 27.

Table 6. Arguments for isis_storage_credentials

Argument Use after isis_storage_credentials to:

set -u <array username> -p <array password>

or:

set --user <array username> --password <arraypassword>

Set the username and password for accessing all the relevantIBM storage systems.

For example:

isis_storage_credentials set -u johnxiv -p ***********

remove Delete the existing storage array user account definition fromthe server.

For example:

isis_storage_credentials remove

Attention: If you already added storage systems to the server,deleting the user account disconnects all these storage systems.

list Display the username of the existing storage array user accountdefinition.

For example:

isis_storage_credentials listjohnxiv

-h

or --help

Display help information that is relevant toisis_storage_credentials.

You can also display help for the set argument if it is typed onthe command line as well.

CLI – Adding or removing storage arraysAll IBM storage systems that provide storage resources to your VMware platformsmust be defined as storage arrays on the IBM Storage Integration Server.

Use the isis_storage_array CLI command to add, remove, or list these IBMstorage systems (referred to as storage arrays). Use the required argument after thecommand, as specified in the following table.


Important:

v IBM storage arrays can be added only after the storage credentials are set, asexplained in “CLI – Adding or removing storage array credentials” on page 17.

v If you want to remove existing storage arrays:– A removed storage array, along with its storage pools and volumes, can no

longer be managed by the included solution components (see “Includedsolution components” on page 1).

– If the removed storage array contains working storage pools and volumes, theinformation of these storage pools and volumes is no longer displayed invSphere Web Client. However, vSphere data access and service level forthese storage pools and volumes is not affected. In addition, the removedarray and its storage pools and volumes can be managed from the standardIBM storage system management tools.

– After the removal, you can add the storage array back again to fully restoreits management.

Note:


Managing storage arrays” on page 26.

Table 7. Arguments for isis_storage_array

Argument Use after isis_storage_array to:

add -i <management IP address> -t <array type>

or

add --mgmt_ip <management IP address> --type<array type>

Add a storage array (IBM storage system) specified by an IPaddress or DNS, and the type of the array.

For the -t (array type) argument, specify xiv for XIV, svc forSAN Volume Controller, Storwize, and Flex System, or ds8k forDS8000.

For example:

isis_storage_array add -i 10.100.155.200 -t xiv

Optional: you can define an alias name for the added XIVsystem, by adding -a <alias name> or --alias <alias name> tothe command.

For example:

isis_storage_array add -i 10.100.155.200 -t xiv -a mystorage1

Note: If you choose not to define an alias, the alias name thatis already defined (if one was defined) on the IBM storagesystem side is automatically assigned as the alias name.

remove -a <system alias name>

or

remove --alias <system alias name>

Remove a storage array specified by its alias name (alias thatwas given by you or was automatically assigned).

For example:

isis_storage_array remove -a mystorage1


Table 7. Arguments for isis_storage_array (continued)

Argument Use after isis_storage_array to:

list List the names of all the IBM storage arrays that are currentlyadded (and were not removed).

For example:

isis_storage_array listmystorage1mystorage2

-h

or --help

Display help information that is relevant toisis_storage_array.

You can also display help for the add or remove argument if it istyped on the command line as well.

CLI – Setting the VASA Secret credentialsThe VASA Secret credentials comprise a user name and a password that VMwarevCenter servers can use to connect to the IBM Storage Integration Server andemploy VMware APIs for Storage Awareness (VASA) functions.

Use the vasa_admin CLI command to set or display the VASA Secret credentials.vCenter servers can then use these credentials to connect to the Integration Serverand utilize VASA functions, as explained in “Registering the Integration Server as astorage provider in vCenter Server” on page 45. Use the required argument afterthe command, as specified in the following table.

Note:

v Only one set of a username and a password can be used for the VASA Secret,which applies to all vCenter servers that require VASA functions.


Setting the VASA Secret credentials” on page 36.

Table 8. Arguments for vasa_admin

Argument Use after vasa_admin to:

set_secret -n <username> -<password>

or:

set_secret --user_name <username>--user_password <password>

Set the username and password for that the VASA Secretshould comprise.

For example:

vasa_admin set_secret -n johnvasa -p ********The secret key for the VASA Provider has been setsuccessfully.

list_secret Display the username of the currently defined VASA Secret.

For example:

vasa_admin list_secretSecret key username for the VASA Provider:johnvasa


Table 8. Arguments for vasa_admin (continued)

Argument Use after vasa_admin to:

-h

or --help

Display help information that is relevant to vasa_admin.

You can also display help for the set_secret argument if it istyped on the command line as well.

CLI – Managing vCenter servers and storage pools forvSphere Web Client

Before you can use the IBM Storage Enhancements for VMware vSphere WebClient on the web client side, you need to define on the IBM Storage IntegrationServer side the vCenter servers for which you want to provide storage resources.Then, you can the attach storage pools that you want to make available to eachvCenter server.

The storage pools that you attach on the Integration Server side become visible onthe vSphere Web Client side, and can be used for volume creation by using theIBM Storage Enhancements on the vSphere Web Client side.

Use the vwc_vcenter and vwc_poolCLI commands to add, modify, remove, or listvCenter servers, and also to attach or detach storage pools that were predefined onthe IBM storage systems you have added. The vwc_host command is required forESXi host definition on DS8000 arrays.

Use the required argument after each command, as specified in the followingtables.

Important:

v Storage pools can be attached to vCenter servers only after the relevant storagearrays have been added, as explained in “CLI – Adding or removing storagearrays” on page 18.

v If you want to detach storage pools or remove vCenter servers:– A detached storage pool, along with its volumes, can no longer be managed

by the included solution components (see “Included solution components” onpage 1).

– If the detached storage pool contains working volumes, the information ofthese volumes is no longer displayed in vSphere Web Client. However,vSphere data access and service level for these volumes is not affected. Inaddition, the removed storage pool (and its volumes) can still be managedfrom the standard IBM storage system management tools.

– After the detachment, you can attach the storage pool again to fully restore itsmanagement.

– A removed vCenter server can no longer be managed through the IntegrationServer, but it continues to be managed from the vSphere environment. Youcan add it again to restore management through the Integration Server.

Note:

v All CLI command arguments are case-sensitive.v Apart from DS8000 host definition (see Table 11 on page 23), the same operations

are available from the GUI as well, as explained in “GUI – Managing serversand storage pools for vSphere Web Client” on page 37.


Table 9. Arguments for vwc_vcenter

Argument Use after vwc_vcenter to:

add -n <username> -i <IP or hostname> -p<password>

or

add --user_name <username> --host_name<hostname> --user_password <password>

Add a vCenter server connection by specifying:

v The username for accessing the vCenter server.

v The hostname or IP address of the vCenter server.

v The user password.

For example:

vwc_vcenter add -n john1 -i myvcenter -p ********

Note: After a vCenter connection is added, you can attachstorage pools to that vCenter server using the vwc_poolcommand (see Table 10 on page 23).

modify -n <username> -i <IP or hostname> -p<password> -g <vCenter GUID>

or

modify --user_name <username> --host_name <IPor hostname> --user_password <password> --guid<vCenter GUID>

Modify a vCenter server connection by specifying:

v The username for accessing the vCenter server.

v The hostname or IP address of the vCenter server.

v The user password.

v The GUID of the vCenter server. You can use the listcommand argument (see below) to obtain the GUID.

For example:

vwc_vcenter modify -n john1 -i myvcenter -p ********-g 11EC2020

list List all vCenter server connections and GUID of each vCenterserver.

For example:

vwc_vcenter list

vCenter host vCenter user vCenter GUID Last updated------------------------------------------------------------10.200.250.11 john11 11EC2020 01-OCT-2013

remove -g <vCenter GUID>

or

remove --guid <vCenter GUID>

Remove a vCenter server connection by specifying its GUID.

For example:

vwc_vcenter remove -g 11EC2020

-h

or --help

Display help information that is relevant to vwc_vcenter.

You can also display help for the add, modify, or removeargument if it is typed on the command line as well.


Table 10. Arguments for vwc_pool

Argument Use after vwc_pool to:

attach -g <vCenter GUID> -a <array alias> -pn<storage pool name>

or

attach --guid <vCenter GUID> --array_alias<array alias> --pool_name <storage pool name>

Attach a storage pool to a vCenter server by specifying:

v The GUID of the vCenter server. You can use thevwc_vcenter list command (see Table 9 on page 22) toobtain the GUID.

v The defined alias name of a storage array.

v The storage pool name.

For example:

vwc_pool attach -g 11EC2020 -a myarray -pn mypool

detach -g <vCenter GUID> -a <array alias> -pn<storage pool name>

or

detach --guid <vCenter GUID> --array_alias<array alias> --pool_name <storage pool name>

Detach a storage pool from a vCenter server by specifying:


v The defined alias name of a storage array.

v The storage pool name.

For example:

vwc_pool detach -g 11EC2020 -a myarray -pn mypool

list -g <vCenter GUID>

or

list --guid <vCenter GUID>

List the storage pools that are attached to a vCenter server, byspecifying the vCenter GUID.

For example:

vwc_pool list -g 11EC2020

-h

or --help

Display help information that is relevant to vwc_pool.

You can also display help for the attach or detach argument ifit is typed on the command line as well.

Table 11. Arguments for vwc_host

Argument Use after vwc_host to:

list -g <vCenter GUID> -e <ESX host name>

or

list --guid <vCenter GUID> --esx_host <ESXhost name>

List all known ESXi host ports and their storage host names byspecifying:


v The name of the ESX host.

For example:

vwc_host list -g 11EC2020 -e myvmhost


Table 11. Arguments for vwc_host (continued)

Argument Use after vwc_host to:

define -a <DS8000 array alias> -n <storagehost name> -e <ESX host name> -pt <port type>

or

define --array_alias <DS8000 array alias>--storage_host_name <storage host name>--esx_host <ESX host name> --port_type <porttype>

Define an ESXi host on a DS8000 storage array (not applicableto other storage arrays) by specifying:

v The defined alias name of the DS8000 storage array.

v The name of the ESXi host to be defined on the DS8000 side.

v The name of the ESX host.

v The connectivity type (between the ESXi host and the DS8000array): fc for Fibre Channel (FC) or iscsi for iSCSI. If notspecified, the default is FC.

For example:

vwc_host define -a myds8k -n hostname -e myhost -pt iscsi

-h

or --help

Display help information that is relevant to vwc_host.

You can also display help for the define argument if it is typedon the command line as well.

CLI – Backing up or restoring an Integration Serverconfiguration

At any point, you can back up the current IBM Storage Integration Serverconfiguration and save it to a file, or load a previously saved configuration torestore a configuration.

The configuration includes storage credentials, storage arrays, vCenter credentials,and storage pools attachment.

Use the isis_configuration CLI command to save the existing configuration, orload a saved configuration that will replace the existing one. Use the requiredargument after the command, as specified in the following table.

Note:

v All CLI command arguments are case-sensitive.v The backup and restore operations are not available on the Integration Server

GUI.

Attention:

v Before using the restore option, the IBM VASA Provider service must bestopped as explained in “Checking and controlling the Integration Serverservice” on page 69. Start the service again after the configuration has beenloaded.

v The restore should be used only with a freshly installed IBM StorageIntegration Server that has not yet been configured.


Table 12. Arguments for isis_configuration

Argument Use after isis_configuration to:

backup -f <file name> -k <16 characters>

or:

backup --file <file name> --key <16characters>

Save the current IBM Storage Provider configuration to thespecified file using an AES-128 encryption key that comprises16 characters.

For example:

isis_configuration backup -f confbackup -k abcdefghijklmnop

Important: You will need to provide this key in any restoreoperation (see below).

restore -f <file name> -k <16 characters>

or:

restore --file <file name> --key <16characters>

Load a configuration from a specified file by providing the filename and the encryption key that was used in the creation ofthe file.

Attention: See the notes above this table.

For example:

isis_configuration restore -f confgbackup -k abcdefghijklmnop

import_vasa115 -f <file name>

or:

import_vasa115 --file <file name>

Import an existing Integration Server configuration that wasmade with IBM Storage Provider for VMware VASA version1.1.5 (applicable only to XIV systems).

For example:

isis_configuration import_vasa115 -f 115backup

Attention: The storage capability definitions made in version1.1.5 cannot be imported because storage capabilities areautomatically created and assigned on the Integration Server.

-h

or --help

Display help information that is relevant toisis_configuration.

You can also display help for the backup or restore argument ifit is typed on the command line as well.

Managing the Integration Server from the graphical user interface(GUI)

You can log in to the Integration Server through a web browser and use theconfiguration and management options that are available from the web-basedgraphical user interface (GUI).

The following sections describe all the GUI configuration and managementfunctions:v “GUI – Logging in” on page 26v “GUI – Managing storage arrays” on page 26v “GUI – Managing Integration Server users” on page 32v “GUI – Managing and monitoring VASA access” on page 36v “GUI – Managing servers and storage pools for vSphere Web Client” on page 37


GUI – Logging inTo log in to the Integration Server from a browser, you need to enter the webaddress (URL) of the Linux host upon which the IBM Storage Integration Server isinstalled.

The secure IP connection to the Integration Server is established though portnumber 8443. Accordingly, the web address should be entered in the browseraddress bar in the following format:

https://[Integration Server IP address]:8443

After entering the address, the IBM Storage Integration Server login page is loadedand you can log in by entering your Integration Server username and password.

Important:

v After the instillation, the initial username is admin and the initial password isadminadmin. To avoid unauthorized access to the Integration Server, it is stronglyrecommended to change this password as soon as possible, or create a new useraccount and then delete the admin account (see “GUI – Managing IntegrationServer users” on page 32).

v If the Integration Server service is stopped on the Linux host (see “Checking andcontrolling the Integration Server service” on page 69), it is not possible to log inor perform any GUI operation.

GUI – Managing storage arraysAll IBM storage systems that provide storage resources to your VMware platformsmust be defined as storage arrays on the IBM Storage Integration Server.

To access the storage array management options, click Arrays on the top GUIpanel. You can then view, add, and manage the storage arrays as explained in the

Figure 8. IBM Storage Integration Server login box in a standard web browser


following sections.

Note: The same operations are available from the CLI as well, as explained “CLI –Adding or removing storage array credentials” on page 17 and in “CLI – Addingor removing storage arrays” on page 18.

v “GUI – Entering the storage array credentials”v “GUI – Adding a storage array” on page 28v “GUI – Modifying the IP address or hostname of a storage array” on page 30v “GUI – Removing a storage array” on page 31

GUI – Entering the storage array credentialsThe storage array credentials are used to connect to the IBM storage system orsystems, which your VMware platforms use for storage provisioning.

About this task

From the Integration Server GUI you can set or change the current storage arrayaccess credentials that are used for accessing all the IBM storage arrays.

Important:

v The same credentials (the same username and password) must already bepredefined on all the IBM storage arrays that you intend to use. The IBMStorage Integration Server cannot use more than a single array managementaccount. For more information about how to define a user account on the IBMstorage systems, refer to the relevant storage system management toolsdocumentation.

v Setting the storage credentials on the IBM Storage Integration Server allows youto add the IBM storage arrays on the next step.

Note: The same operations are available from the CLI as well, as explained in“CLI – Adding or removing storage array credentials” on page 17.

Procedure1. Click Arrays on the top GUI panel. The Storage Arrays table is displayed, and

the currently defined storage array username is displayed next to the ChangeCredentials button.

Figure 9. Clicking Arrays


2. Click Change Credentials. The Change Credentials dialog box appears.3. Enter the username and password of the storage admin user that was defined

on the IBM storage arrays, and then click Apply.

What to do next

You can now start adding storage arrays. The IBM Storage Integration Server willuse the credentials that you have set in order to connect to the storage arrays thatyou add.

GUI – Adding a storage arrayAfter the storage array credentials are set, you can start adding storage arrays tothe Integration Server.

About this task

The storage arrays that you add can be used by the solution components that areincluded in the IBM Storage Integration Server package (see “Included solution

Figure 10. Current® storage array username (for all storage arrays)

Figure 11. Change Credentials dialog box


components” on page 1). You can add each individual storage array separately, asdescribed in the following procedure.

Procedure1. Click Arrays on the top GUI panel. The Storage Arrays table is displayed and

lists the currently added storage arrays.2. Click Add. The Add Array dialog box is displayed.

3. Select the storage array type (XIV, SAN Volume Controller, Storwize, orDS8000) and then enter its management IP address or hostname.

4. Click Add. If the credentials are correct (as previously defined; see “GUI –Entering the storage array credentials” on page 27) and the IP connection isestablished, the storage array is added to the Storage Arrays table.

You can click the row of a storage array to view its details on the Storage ArrayDetails pane.

Figure 12. Add Array dialog box

Figure 13. List of added storage arrays


GUI – Modifying the IP address or hostname of a storage arrayAt any time, you can modify the IP address or hostname of an added storagearray.

About this task

If the management IP address or hostname of a storage array changes, you canupdate this change on the Integration Server without having to remove or re-addthe storage array.


lists the currently added storage arrays.2. Click the row of the storage array that you want to update, and then click the

Modify Array icon.The Modify Array dialog box appears.

Figure 14. Storage array details

Figure 15. Modify Array icon


3. Enter the new management IP address or hostname of the storage array, andthen click Modify.

GUI – Removing a storage arrayIf a storage array is no longer needed, you can remove and disconnect it from theIntegration Server.

About this taskv A removed storage array, along with its storage pools and volumes, can no

longer be managed by the included solution components (see “Included solutioncomponents” on page 1).

v If the removed storage array contains working storage pools and volumes, theinformation of these storage pools and volumes is no longer displayed invSphere Web Client. However, vSphere data access and service level for thesestorage pools and volumes is not affected. In addition, the removed array andits storage pools and volumes can be managed from the standard IBM storagesystem management tools.

v After the removal, you can add the storage array back again to fully restore itsmanagement.


lists the currently added storage arrays.2. Click the row of the storage array that you want to update, and then click the

Remove Array icon.

Figure 16. Modify Array dialog box


A confirmation message appears.

3. Click Yes to remove the array, or No to cancel the operation.

GUI – Managing Integration Server usersAt any time, you can add new Integration Server user accounts, change useraccount passwords, or delete existing user accounts.

To access the storage array management options, click Users on the top GUI panel.You can then view, add, and manage the Integration Server users as explained inthe following sections.

Note: The same operations are available from the CLI as well, as explained in“CLI – Adding and managing Integration Server users” on page 16.

v “GUI – Adding an Integration Server user” on page 33v “GUI – Changing the password of an Integration Server user” on page 34v “GUI – Deleting an Integration Server user” on page 35

Figure 17. Remove Array icon

Figure 18. Remove Array confirmation message

Figure 19. Clicking Users


GUI – Adding an Integration Server userYou can add a user account for any authorized user that requires access to the IBMStorage Integration Server.

About this task

Each added user is able to individually log into the IBM Storage Integration Serverand perform GUI or CLI management actions.

Note: All Integration Server users have the same permission level on theIntegration Server, and can undo any setting or action made by another user.

Procedure1. Click Users on the top GUI panel. The Users table is displayed and lists the

currently added users.2. Click Add. The Add User dialog box appears.

3. Enter the username and password for the account that you want to create, andthen click Add. The username of the created account is added to the Userstable.

Figure 20. Add User dialog box


GUI – Changing the password of an Integration Server userAt any time, you can change the password of an Integration Server user account.

About this task

You can modify a user account only by changing its password. Periodic passwordchange is recommended on a regular basis.

Note: Integration Server user names cannot be changed. Instead, you can delete auser account (see “GUI – Deleting an Integration Server user” on page 35) andthen create a new one (see “GUI – Adding an Integration Server user” on page 33).


currently added users.2. Click the row of the storage array that you want to update, and then click the

Modify User icon.The Change Password dialog box is displayed.

Figure 21. List of added Integration Server users (user names)

Figure 22. Modify User icon


3. Enter the current password of the user account, and then the new passwordtwice as required. Then, click Change.

GUI – Deleting an Integration Server userWhen necessary, you can delete any Integration Server user account.

About this task

After you delete an Integration Server user account from the GUI, the specific usercan no longer log in to the integration server from either the GUI or the CLI.Although the user deletion is a non-reversible operation, you can redefine the sameusername as explained in “GUI – Adding an Integration Server user” on page 33.

Note: Deleting an Integration Server user does not affect the storage credentials orVASA Secret credentials, which both remain defined.


currently added users.2. Click the row of the user account that you want to update, and then click the

Delete User icon.

A confirmation message appears.

Figure 23. Change Password dialog box

Figure 24. Delete User icon


3. Click Yes to delete the user, or No to cancel the operation.

GUI – Managing and monitoring VASA accessYou can control and monitor the utilization of the IBM Storage Provider forVMware VASA, which is part of the IBM Storage Integration Server solution

Note: This functionality is not applicable to DS8000 systems, which are notsupported by the IBM Storage Provider for VMware VASA.

To access the VASA management options, click VASA on the top GUI panel. Youcan then display a list (read-only) of all vCenter servers that are currentlyregistered and are utilizing VASA functions.

Before any vCenter server can be registered and start utilizing the IBM StorageProvider, you must first set the 'VASA Secret' credentials, as explained in thefollowing section.

GUI – Setting the VASA Secret credentialsThe 'VASA Secret' credentials comprise a username and a password that is setseparately from the Integration Server user accounts, and separately from thestorage array credentials.

About this task

VMware vCenter servers can use the VASA Secret credentials to connect to the IBMStorage Integration Server and utilize VASA functions, as explained in “Registeringthe Integration Server as a storage provider in vCenter Server” on page 45.

From the Integration Server GUI you can set, change, or display these VASA Secretcredentials at any time.

Note:

v Only one set of a username and a password can be used for the VASA Secret,which applies to all vCenter servers that require VASA functions and connect tothe IBM Storage Integration Server.

v The same operations are available from the CLI as well, as explained in “CLI –Setting the VASA Secret credentials” on page 20.

Procedure1. Click VASA on the top GUI panel. The Registered vCenter Servers table is

displayed, and the currently defined VASA Secret username is displayed nextto the Change Secret button. At the initial use after the installation, theinstallation-default user name is displayed.

Figure 25. Clicking VASA


2. Click Change Secret. The Change Secret dialog box is displayed.

3. Enter the required username and password of the VASA Secret that you wantto set, and then click Update.

GUI – Managing servers and storage pools for vSphere WebClient

Before you can use the IBM Storage Enhancements for VMware vSphere WebClient on the web client side, you need to define on the IBM Storage IntegrationServer side the vCenter servers for which want to provide storage resources. Then,you can the attach storage pools that you want to make available to each vCenterserver.

The storage pools that you attach on the Integration Server side become visible onthe vSphere Web Client side, and can be used for volume creation by using theIBM Storage Enhancements on the web client side.

To access these options, click vSphere Web Client on the top GUI panel. You canthen manage servers and storage pools as explained in the following sections.

Figure 26. Current VASA Secret username

Figure 27. Change Secret dialog box


Note: The same operations can be performed from the CLI as well, as explained in“CLI – Managing vCenter servers and storage pools for vSphere Web Client” onpage 21.

v “GUI – Adding a vCenter server”v “GUI – Updating the credentials of a vCenter server” on page 39v “GUI – Removing a vCenter server” on page 40v “GUI – Attaching a storage pool to a vCenter server” on page 41v “GUI – Detaching a storage pool from a vCenter server” on page 43

GUI – Adding a vCenter serverAdd the VMware vCenter servers for which want to provide storage resourcesthrough the IBM Storage Integration Server.

About this task

You need to connect to and add the vCenter servers for which you can later attachstorage pools that would be visible and accessible on the vSphere Web Client side.You can add a single vCenter server at a time, as described in the followingprocedure.

Procedure1. Click vSphere Web Client on the top GUI panel. The vCenter Servers table is

displayed and lists the currently added vCenter servers.2. Click Add. The Add vCenter Server dialog box is displayed.

Figure 28. Clicking vSphere Web Client


3. Enter the IP address or hostname of the vCenter server, as well as theusername and password for logging into that vCenter server. Then, click Save.If the provided IP address and credentials are accepted by the vCenter server, itis added to the list of vCenter servers.

GUI – Updating the credentials of a vCenter serverAt any time, you can update the credentials that are used to access a vCenterserver.

About this task

Whenever the credentials on the vCenter server side change, you can update thesecredentials on the Integration Server side to allow continued management ofstorage resources on the vSphere Web Client side.


displayed and lists the currently added vCenter servers.

Figure 29. Add vCenter Server dialog box

Figure 30. List of vCenter servers


2. Click the row of the vCenter server for which you want to update thecredentials, and then click Edit. The update vCenter Server Credentials dialogbox is displayed.

3. Enter the new username and password for accessing the vCenter server. Then,click Save.

GUI – Removing a vCenter serverWhen a vCenter server is no longer needed, you can disconnect it from theIntegration Server by removing it from the list of vCenter servers.

About this taskv A removed vCenter server, along the storage pools attached to it, can no longer

be managed by the included solution components (see “Included solutioncomponents” on page 1).

v If the removed vCenter server is attached to working storage pools, theinformation of these storage pools, as well as the volumes on these pools is nolonger displayed in vSphere Web Client. However, vSphere data access andservice level for these storage pools and volumes is not affected.

v After the removal, you can add the vCenter server again to fully restore itsmanagement.


displayed and lists the currently added vCenter servers.2. Click the row of the vCenter server that you want to remove, and then click

Remove. A confirmation message is displayed.

Figure 31. Update vCenter Server Credentials dialog box


3. Click Remove to remove the vCenter server, or Cancel to cancel the operation.

GUI – Attaching a storage pool to a vCenter serverYou must attach to the vCenter server any predefined storage pool (predefined bythe storage administrator) that you want to use for volume managementoperations on the vSphere Web Client side.

Before you beginv Storage pools can be attached only with Admin, Storage Admin, System Admin, or

Security Admin storage credentials (see “GUI – Entering the storage arraycredentials” on page 27).

v When working with DS8000, storage pools can be attached only with Admin orLogical Operator storage credentials.

Any other type of storage credentials (read-only, application admin) cannotperform storage pool attachment. If your credentials are not sufficient, contact yourstorage administrator for assistance.

About this task

The storage pool attachment is done on the Integration Server side, providing morecontrol to storage administrators as opposed to the VMware administrators on thevSphere environment side. After the attachment, the storage pools become visibleand manageable on the vSphere Web Client side (by using the IBM StorageEnhancements).

You can select and attach one or more storage pools in one attachment operation,as described in the following procedure.


displayed and lists the vCenter servers to which you can attach storage pools.2. Click the row of the vCenter server to which you want to attach one or more

storage pools, and then click Attach. The Attach Storage Pools dialog box is

Figure 32. Remove vCenter Server confirmation message


displayed.

3. From the drop-down list, select the storage array from which you want tochoose storage pools. The available predefined storage pools that reside on theselected storage array are immediately displayed.

4. Select the storage pools that you want to attach to the vCenter server (specifiedin the dialog box), and then click Attach. The list of attached storage pools pervCenter server is updated accordingly.

Figure 33. Attach Storage Pools dialog box

Figure 34. List of attached storage pools per vCenter server


GUI – Detaching a storage pool from a vCenter serverWhen required, you can detach a storage pool from the vCenter server to which itis attached.

About this taskv A detached storage pool, along with its volumes, can no longer be managed by

the included solution components (see “Included solution components” on page1).

v If the detached storage pool contains working volumes, the information of thesevolumes is no longer displayed in vSphere Web Client. However, vSphere dataaccess and service level for these volumes is not affected. In addition, theremoved storage pool (including its volumes) can be managed from the standardIBM storage system management tools.

v After the detachment, you can attach the storage pool again to fully restore itsmanagement.


displayed on the left and lists the vCenter servers to which you can attachstorage pools.

2. Click the row of the vCenter server from which you want to detach one ormore storage pools. The list of storage pools that are currently attached to thevCenter server is displayed on the right.

3. Click the row of the storage pool that you want to detach, and then clickDetach. A confirmation message appears.

4. Click Detach to delete the user, or Cancel to cancel the operation.

Figure 35. Detach Storage Pool confirmation message


Chapter 4. Using the IBM Storage Provider for VMware VASA

This chapter focuses on how to use the IBM Storage Provider for VMware VASAafter the required configuration on the IBM Storage Integration Server has beencompleted.

Note: IBM System Storage DS8000 systems are not supported by the IBM StorageProvider for VMware VASA.

After the IBM storage systems have been added to the Integration Server, and afterthe VASA access credentials were set (see “Required and optional initial tasks” onpage 13), you can start using the IBM Storage Provider for VMware VASA byregistering the Integration Server in the relevant vCenter server or servers.v “Checking and controlling the Integration Server service” on page 69v “Registering the Integration Server as a storage provider in vCenter Server”

Registering the Integration Server as a storage provider in vCenterServer

To use the IBM Storage Provider for VMware VASA solution component, you needto register the IBM Storage Integration Server as a storage provider in VMwarevCenter Server.

Before you begin

When the IBM Storage Provider for VMware VASA and the IBM Tivoli® StorageProductivity Center (TPC) storage provider are registered on the same VMwarevCenter server, while the same storage array is configured for both, vCenter usesIBM Tivoli Storage Productivity Center provider as the only source of informationfor that array's storage views on vSphere Client.

In such a case, determine whether the IBM Tivoli Storage Productivity Centercapabilities are sufficient for replacing the IBM Storage Provider for VMwareVASA. If the IBM Storage Provider for VMware VASA is still needed, IBM TPC 5.2(or later) provides a method of excluding storage arrays from a specific storageprovider, allowing you to remove the array association with the IBM TPC provider.

About this task

The following procedure describes how to register the Integration Server on asingle vCenter server by using vSphere Client. You can, however, register theIntegration Server on multiple vCenter servers by using vSphere Web Client, asexplained in “Setting the Integration Server web address for vCenter servers” onpage 49.

Procedure

To register the IBM Storage Integration Server in VMware vCenter Server, completethe following steps.1. In vSphere Client, go to Administration > Storage Providers.


2. Click Add.

The Add Vendor Provider dialog box is displayed.3. Enter the name, URL, and pre-configured username and password (VASA

Secret) for accessing the IBM Storage Integration Server (the VASA Secret ispredefined as explained in “GUI – Setting the VASA Secret credentials” on page36). The URL should be entered in the ip:port format, specifying the relevant IPaddress and port number of the IBM Storage Integration Server:https://[Integration Server IP address]:8443/services/vasa1

Note: In this example, "Integration Server IP address" stands for the IP addressor domain namespace of the IBM Storage Integration Server.

Figure 36. vSphere Client – Storage Providers list


4. Click OK. A security alert dialog box is displayed.

5. Click Yes to accept the certificate. The IBM Storage Integration Server is addedto vCenter Server.

Note: The certificate provides improved security by adding server authentication.

Figure 37. Add Vendor Provider dialog box

Figure 38. vCenter certificate thumbprint dialog box

Chapter 4. Using the IBM Storage Provider for VMware VASA 47

Figure 39. Supported Vendor list displaying the IBM Storage Integration Server


Chapter 5. Using the IBM Storage Enhancements for VMwarevSphere Web Client

With supported IBM storage systems that are managed by the IBM StorageIntegration Server, the separately installed IBM Storage Enhancements enable thefollowing management features on vSphere Web Client side:v Full control over storage volumes, including volume creation, resizing,

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

v Easy and integrated allocation of volumes to VMware datastores, used by virtualmachines that run on ESXi hosts, clusters, or datacenters.

v

Note: To enable these features, the IBM Storage Enhancements must be installedon the VMware vSphere Web Client Server, as described in “Installing the IBMStorage Enhancements for VMware vSphere Web Client” on page 6.

See the following sections for more information:v “Setting the Integration Server web address for vCenter servers”v “Populating vCenter server information to the Integration Server” on page 50v “Viewing the IBM storage resource information” on page 52v “Creating and mapping a new storage volume (LUN)” on page 56v “Extending a volume” on page 61v “Renaming a volume” on page 62v “Setting multipath policy enforcement for a volume” on page 63v “Moving a volume to another storage pool” on page 64v “Unmapping a volume from one or more hosts” on page 65v “Deleting an unused volume” on page 66

Setting the Integration Server web address for vCenter serversTo allow interoperation between the vCenter servers that are in use and the IBMStorage Integration Server, you must specify the Integration Server web address(URL) for each vCenter server.

About this task

Specifying the Integration Server web address for a vCenter server establishes aconnection between that vCenter sever and that specific Integration Server host,and activates the IBM storage provisioning and control features for that vCenterserver. You can specify the Integration Server web address for one or more vCenterservers, as described in the following procedure.

Important: In addition to this procedure, the relevant vCenter server must beadded on the IBM Storage Integration Server, as explained in “GUI – Adding avCenter server” on page 38.


Procedure1. In vSphere Web Client, navigate to the relevant vCenter server and then click

the Manage tab.2. Click Settings > IBM Server > Edit, and then enter the Integration Server web

address in the displayed dialog box.

Important: The secure IP-based connection to Integration Server must be madethrough port 8443, which must be specified with a colon (":8334") at end the webaddress (URL) in the following format: https://[Integration Server IPaddress]:8443

3. Click OK. If the connection is established, the Connectivity indicator shows agreen icon with the status 'Connected'.

Populating vCenter server information to the Integration ServerAt any time and whenever needed, you can manually update the vCenter serverinformation on the IBM Storage Integration Server side.

About this task

By default, the vCenter server information is automatically updated on the IBMStorage Integration Server every 30 minutes (as defined in vwc_config.ini, see

Figure 40. Edit IBM Server Address dialog box

Figure 41. IBM Storage Integration Server connection details per vCenter server


“Checking and modifying the configuration files” on page 71). If you want to runthe update earlier without having to wait for the next automatic update, performthe following procedure.

Important: Before you can use this option, the relevant vCenter server mustalready be:

v Added on the IBM Storage Integration Server, as explained in “GUI – Adding avCenter server” on page 38.

v Pointed to the IBM Storage Integration Server web address, as explained in“Setting the Integration Server web address for vCenter servers” on page 49.

Procedure1. In vSphere Web Client, focus on the relevant vCenter server.2. From the Actions menu, select All IBM Storage Actions > Populate vCenter

InformationA confirmation message appears.

3. Click Yes to send the specified vCenter information to the IBM StorageIntegration Server.

Figure 42. Populate vCenter Information option

Figure 43. Populate vCenter confirmation message

Chapter 5. Using the IBM Storage Enhancements for VMware vSphere Web Client 51

Viewing the IBM storage resource informationAfter the IBM Storage Enhancements for VMware vSphere Client are properlyinstalled, the IBM Storage category is shown under the standard vSphere WebClient categories for each vCenter server, as shown in the following figure.

For each vCenter server, the IBM Storage category shows how many IBM storagearrays are available for that vCenter server. The number and type of available IBMstorage arrays is determined on the IBM Storage Integration Server side, asexplained in “GUI – Managing storage arrays” on page 26 and “GUI – Managingservers and storage pools for vSphere Web Client” on page 37.

You can click and open the IBM Storage category, and then click an IBM storagearray to view the currently available storage volumes on that particular storagearray, and also to check which VMware entities are currently using storageresources on that storage array.

Figure 44. IBM Storage category in vSphere Web Client


In addition, IBM Storage information and functions are available per vCenterserver in the different category views on the Related Objects tab, as shown in thefollowing figures.

Figure 45. IBM Storage information per storage array

Figure 46. Currently available storage pools per storage array


Figure 47. IBM Storage information per vCenter server

Figure 48. IBM Storage information per datacenter

Figure 49. IBM Storage information per datastore


Figure 50. IBM Storage information per all ESXi hosts of a vCenter server

Figure 51. IBM Storage information per all VM templates of a vCenter server

Figure 52. IBM Storage information per all vApps of a vCenter server


And so on, click the other information categories that are available in vSphere toview the relevant IBM Storage information in these categories as well.

Creating and mapping a new storage volume (LUN)The IBM Storage Enhancements for VMware vSphere Web Client allow you tocreate new volumes (LUNs) directly from the vSphere Web Client interface. Thesevolumes can be used as storage devices in the vSphere environment.

About this task

Any created volume is mapped to either ESXi hosts, clusters, or datacenters, sothat the virtual machines on these hosts, clusters, or datacenters would be able tosave datastore information on that volume.

In addition to single volume creation, you can create multiple volumessimultaneously. If you choose this option, the created volumes are appended withdifferently numbered suffixes that are automatically generated by the system inconsecutive order.

Important:

v You can create volumes only on storage pools that have been attached to therelevant vCenter server on the IBM Storage Integration Server side. For moreinformation, see “GUI – Managing servers and storage pools for vSphere WebClient” on page 37

v The ESXi hosts and clusters to which you map the created volumes must bepredefined on the storage system side. For more information, refer to your IBMstorage system documentation.

Procedure1. In vSphere Web Client, navigate to the relevant vCenter server and then to the

specific IBM storage array on which you want to create the new volume. TheIBM storage array and the relevant storage pools should already be associatedwith the vCenter server (see “Viewing the IBM storage resource information”on page 52).

2. Click Actions > Create New Volume. Alternatively, from the Top Level Objectsview on the relevant vCenter server, click Actions > All IBM Storage Actions> Create New Volume.

Figure 53. IBM storage array view – Clicking Create New Volume


You can also right-click the storage array or click the dedicated icon in order toinvoke the Create New Volume option.

Figure 54. Top Level Objects view – Clicking Create New Volume

Figure 55. Right-clicking the storage array


The Create New Volume dialog box is displayed.

3. In the Volume Size text box, enter the size for the new volume. Alternatively,place the mouse pointer on the graphic image of the storage pool, and thenclick and slide the space marker rightward to set the new volume size. Thenumerical value in Volume Size is automatically updated accordingly.

Figure 56. Clicking the Create New Volume icon

Figure 57. Create New Volume wizard (XIV example)


Note:

v It is recommended to define the size of an XIV volume in a multiple of 17 GB.The Volume Size box appears with a yellow rectangle around it if the size valueis not a multiple of 17 GB. The XIV Recommended Volume Size (GB)information is displayed below.

v The largest available storage pool on the storage array is automatically selected.

4. In the Volume Name text box, enter the name that you want to assign to thenew volume.

5. If you want to create multiple volumes simultaneously (otherwise, go to step 6on page 60): In the Number of Volumes text box, enter the number of volumesthat you want to create simultaneously. The text box next to the Volume Nameentry displays volumename_{1} in this example. The {1} represents the suffixvalue. You can enter the volume name and move the suffix value to the middleor kept at the end of the volume name (see Figure 59 on page 60).

Figure 58. Setting the volume size with the graphic space marker


6. If you want to change the automatically selected storage pool (otherwise, skipto next step), select a different storage pool from the Storage Array/Pool listbox.

7. Only if you are creating the volume on an IBM Flex System, DS8000, SANVolume Controller, or Storwize storage system (otherwise, skip to the nextstep):v Select the I/O Group to which the volume should belong. Not applicable to

DS8000.v Optional: Select Enable Thin Provisioning if you want the volume to be

defined as thin provisioned and not as a fixed hard disk allocation. Whenthis option is selected, the available capacity and total capacity are displayedbased on the requested volume size. For DS8000, the over-provision ratioinformation is also displayed.

v Optional: Select Enable Data Compression if you use data compression onSAN Volume Controller or Storwize V7000, on Storwize V3500 or StorwizeV3700, or on Storwize V7000 Unified. Not applicable to DS8000.

v Optional: Select Enable Vdisk Mirroring if you want to use virtual diskmirroring for the volume or volumes that you create. Not applicable toDS8000. If selected, a list of storage pools appears and you must select thesecondary storage pool on which you want the mirrored volume or volumesto be created.

Notes:

v XIV volumes are not associated with I/O groups and are thin-provisioned ifcreated in a thin-provisioned storage pool.

v Compressed volumes SAN Volume Controller or Storwize storage systems (ifsupported by the microcode) are always thin-provisioned.

Figure 59. Creating multiple volumes


8. From Host Mapping, select the host(s), cluster(s), or datacenter(s) to which youwant to map the new volume. You can click Custom to specify a custommapping in the Advanced Host Mapping dialog box. If you select a datacenter,its member clusters and hosts are automatically selected.

Note: All ESXi hosts are available to be selected. If there is a connectivity problem,the help text indicates that. Hosts that are not connected to the array are marked.

Important: You must map the volume to at least one ESXi host, cluster, ordatacenter in order to enable vSphere management of the created volume.

9. Review the details of the new volume that is about to be created, and then clickOK to confirm its creation as detailed.

Extending a volumeIf enough free space is available on the relevant storage pool, you can extend thesize of an existing volume.

Procedure

Perform the following procedure to extend the size of a volume.1. In vSphere Web Client, navigate to the row of the volume that you want to

extend.2. Right-click the volume row and choose Extend or use the Actions menu to

select Extend.

Figure 60. Advanced Host Mapping dialog box


The Extend Volume dialog box is displayed.3. In the Volume Size text box, enter the new size for the volume. Alternatively,

place the mouse pointer on the graphic image of the storage pool, and thenclick and slide the space marker rightward to set the new volume size. Thenumerical value in Volume Size is automatically updated accordingly.

4. Click Extend.

Important: Extending the size of a volume does not automatically increase thedatastore capacity.

Renaming a volumeWhenever required, you can rename any existing volume by performing thefollowing procedure.

About this task

Renaming a volume is a logical action that does not have any physical effect onthe volume or its logical connections. Renaming a volume also changes itsdisplayed name in the vSphere environment.

Procedure1. In vSphere Web Client, navigate to and then click the row of the volume that

you want to rename, and then choose the Rename option by right-clicking thevolume row or using the Actions menu.

Figure 61. Clicking Extend on the pop-up menu


The Rename Volume dialog box is displayed.

2. Enter the new name that you want to assign to the volume, and then click OK.

Setting multipath policy enforcement for a volumeThis section describes how to set multipath policy enforcement for a singlevolume.

About this task

By default, the Round Robin multipath policy is enforced on volumes. You candisable or change this enforcement for a specific volume if needed.

Procedure1. In vSphere Web Client, navigate to and then click the row of the volume for

which you want to change the enforcement, and then choose the Set MultipathPolicy Enforcement option by right-clicking the volume row or using theActions menu.

Figure 62. Rename volume option

Figure 63. Rename Volume dialog box


The Change Multipath Policy Enforcement dialog box is displayed.

2. Select the required option and then click OK.

Important: After the policy is set, it is enforced by overriding any existing policyfor this volume.

Moving a volume to another storage poolYou can move a volume to a different storage pool, for example, when the currentstorage pool has run out of space.

Figure 64. Set Multipath Policy Enforcement option

Figure 65. Change Multipath Policy Enforcement dialog box


About this task

Attention:

v On XIV storage systems, moving a volume to another storage pool is a logicalaction. No data is actually moved on physical disks as a result.

v On DS8000, Storwize, and SAN Volume Controller storage systems, moving avolume to another storage pool is a physical action that causes data to move toa different physical disk. This may cause some performance overhead.

v On DS8000, Storwize, and SAN Volume Controller storage systems, moving avolume to another storage pool is an asynchronous action. The capacity of thesource and target storage pools may not be updated after the task is completedin vCenter.

v When using mirrored volumes on SAN Volume Controller systems, only theprimary copy volumes can be moved. In addition, these volumes can be movedonly to the primary storage pool copy (not to the secondary copy).


you want to move, and then choose the Move option by right-clicking thevolume row or using the Actions menu.

The Move Volume dialog box is displayed.2. Select the storage pool to which you want to move the volume, and then click

OK.

Unmapping a volume from one or more hostsWhen volumes or ESXi hosts are no longer needed, or if new ones are to replacethe current ones, you can unmap volumes from the hosts.

Figure 66. Move volume option


About this task

Important: A volume (LUN) must remain mapped to at least one host. Otherwise,you cannot view the volume or perform any actions on it from vSphere WebClient.


you want to unmap, and then choose the Unmap option by right-clicking thevolume row or using the Actions menu.

The Unmap Volume dialog box is displayed.2. Select the hosts or clusters from which you want to unmap the volume, and

then click OK.

Deleting an unused volumeWhen a storage volume is unused and no longer required, you can delete it.

Before you begin

Important: You cannot delete volumes that are currently used by datastores or as araw mapped LUN.


you want to delete, and then choose the Delete option by right-clicking thevolume row or using the Actions menu.

Figure 67. Unmap volume


The Delete Volume confirmation message is displayed.2. Click OK to confirm the deletion, or Cancel to exit without deleting the

volume.

Figure 68. Delete volume


Chapter 6. Troubleshooting

This chapter can help you detect and solve problems that you might encounterwhen using the IBM Storage Integration Server.

Note: For up-to-date information about known issues and possible workarounds,refer to the latest release notes.

Checking and controlling the Integration Server serviceAt any time, you can check whether the IBM Storage Integration Server serviceruns properly on the Linux host. You can also stop and then start the service ifneeded.

Procedure1. Log on to the Linux command prompt environment as a root user.

Important: Only root users can perform service operations.

2. Enter the following command: service ibm_storage_integration_serverstatus. The status of the Celery and Django services is displayed.

[root@isis]# service ibm_storage_integration_server statusCelery services are running...Django service is running...

What to do next

If you want to stop the IBM Storage Provider service, use the stop command:

[root@isis]# service ibm_storage_integration_server stopStopping Django service: [ OK ]Stopping celery services: [ OK ]

To start the service again, use the start command:

[root@isis]# service ibm_storage_integration_server startStarting celery services: [ OK ]Starting Django service: [ OK ]

Checking the log filesThe IBM Storage Integration Server maintains six log files that record differenttypes of events.

You can find the following log files in the opt/ibm/ibm_storage_integration_server/log/ directory:v isis.log – Records events regarding the Integration Server functionality.v hsgsvr.log – Records events regarding the collection of information from the

monitored storage systems.


v vasa1.log – Records events regarding the communication between theIntegration Server and the connected vCenter servers that utilize VASAfunctions.

v vwc.log – Records events regarding the communication between the IntegrationServer and the vSphere Web Client Server on which the IBM StorageEnhancements are installed.

v celery.log – Records events regarding the Celery services on the Linux host onwhich the Integration Server is installed.

v isis_django.log – Records events regarding the Django service on the Linuxhost on which the Integration Server is installed.

You can retrieve and save the current log files in a compressed TAR archive file byusing the Collect Logs option on the Integration Server GUI. This option allowsyou to save different instances of the log files at different times.

Figure 69. Integration Server GUI – Collect Logs option

Figure 70. Integration Server GUI – Saving the logs in a compressed TAR archive


Checking and modifying the configuration filesThe IBM Storage Integration Server has four configuration files that storeconfiguration settings that you can change manually if needed.

You can view and modify the contents of each file with any standard text editor,according to the purpose and contents of each file.

After modifying a configuration file, you must restart the Integration Server serviceby running the following CLI command on the Linux host:

service ibm_storage_integration_server restart

For more information about this service, see “Checking and controlling theIntegration Server service” on page 69.

Table 13. Configuration files

File name Directory location Parameters

ldap.ini opt/ibm/ibm_storage_integration_server/conf.d/

For information about the LDAP userauthentication option, see “Configuring LDAPuser authentication” on page 14.

vasa_config.ini opt/ibm/ibm_storage_integration_server/conf.d/vasa1/

v populate_vasa_events_and_alarms – Thetime interval in minutes between eachoperation of filtering relevant events foreach connected vCenter server. The defaultvalue is 2.

vwc_config.ini opt/ibm/ibm_storage_integration_server/conf.d/vwc/

v populate_all_vmware_objects – The timeinterval in minutes between each operationof refreshing of all vCenter serverinformation on the Integration Server. Thedefault value is 30. When using a largenumber of vCenter servers, the value mightneed to be higher.

hsgsvr_config.ini opt/ibm/ibm_storage_integration_server/conf.d/hsgsvr/

v populate_arrays_and_events – The timeinterval in minutes between each update ofinformation (changes and events) receivedfrom each monitored storage system. Thedefault value is 10. When using a largenumber of storage array, the value mightneed to be higher than 10.

Chapter 6. Troubleshooting 71

Chapter 7. Best Practices

Refer to the general guidance and best practices that are described in the followingsections.v “Handling datastores”v “Handling ESXi hosts that use XIV volumes”v “Distributing volumes evenly on DS8000 systems”

Handling datastoresFor best performance of VMware datastores:v Create each datastore on a separate storage volume.v If you use snapshots/mirroring for volumes, place all Datastore Extents volumes

(the building block LUNs of a datastore) in a consistency group (defined byusing the storage system GUI or CLI).

Handling ESXi hosts that use XIV volumesFor the best performance of ESXi hosts that use XIV volumes, define all ESXi hostswithin a cluster as cluster hosts on the XIV storage system as well.

Following this practice prevents situations in which a storage volume is mapped todifferent ESXi hosts in a cluster using different LUN numbers, thus making thisLUN unusable.

Distributing volumes evenly on DS8000 systemsDS8000 storage systems have two rank groups, 0 and 1, each managed by a singleserver. In addition, each DS8000 extent pool is based on one rank group.

Accordingly, it is recommended to spread volumes evenly across the DS8000systems. Spreading the volumes equally on the extent pools of rank groups 0 and 1balances the workload across the DS8000 system.


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.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, 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.


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 of theInternational 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, the VMware logo, ESX, ESXi, vSphere, and vCenter are trademarks orregistered trademarks 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.

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

Notices 77

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

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

Index

Aaccess to array 17add

storage array 18storage provider 45user 16vCenter server 21

admin commands 16array credentials 17attach pools 21

Bbackup 24best practices

datastores 73distributing DS8000 volumes 73ESXi hosts 73

Cchange password 16check service 69collect logs 69command-line interface

add or remove storage arraycredentials 17

add or remove storage arrays 18adding users 16backup or restore server

configuration 24manage vSphere web client 21managing the integration server 15set VASA credentials 20switch to ISIS user mode 16tasks 13

compatibility 3concept diagram 2config.ini 71configuration backup 24configuration files

modify 71creating or mapping

LUN 56

Ddatastores

best practices 73debug mode 71detach pools 21detect problems 69download site 4DS8000 volumes

best practices 73

FFix Central 4

GGUI

adding server users 33adding storage array 28adding vCenter server 38attach storage pool to vCenter

server 41change user password 34deleting server users 35detach storage pool from vCenter

server 43enter storage array credentials 27logging in 26manage storage arrays 26manage the server 25manage the users 32manage VASA access 36manage vSphere web client 37modify IP address or hostname 30remove storage array 31remove vCenter server 40setting VASA credentials 36tasks 13update vCenter server credentials 39

Iinstallation

Integration Server 5vSphere Web Client 6

Integration Servercontrolling the service 69vCenter server web address 49

interval 71isis username 5

LLDAP

user authentication 14list

storage array 18users 16

log files 69LUN

create 56

Mmanagement 13manual configuration 71multipath policy enforcement 63

Ooptional tasks 13

Ppopulate vCenter

update the Integration Server 50

Rregister

integration server 45release notes 3remove

storage array 18storage credentials 17user 16vCenter server 21

required tasks 13requirements 3resolve issues 69restart service 8restore 24rpm package 5

Ssave configuration 24server users 16service status 69start service 69stop service 8, 69storage array commands 18storage credentials

display 17remove 17set 17

storage enhancementsvSphere Web Client 49

storage poolsattach or detach 21

storage resource informationviewing 52

storage volumecreate 56

supported storage systems 3

Ttar.gz file 5tasks 13time interval 71troubleshoot 69

Uuninstall

IBM Storage Integration Server 10Integration Server software 10storage enhancements for VMware

vSphere web client 11user

privileges 3


user (continued)roles 3

VVASA credentials 20VASA Provider server 45vCenter Server 45vendor providers 45VMware VASA

using storage provider 45volume

deleting unused 66extending 61move to another storage pool 65multipath policy enforcement 63rename 62unmapping from host 66

vSphere Client 45vSphere privileges 3vSphere Web Client

storage enhancements 1

Wwhat to do first 13Windows installation 6


��

Printed in USA

SC27-5999-01

ibm storage integration server -...

Documents