IBM Storage Integration Serverdelivery04.dhe.ibm.com/sar/CMA/SDA/04lmz/0/IBM_Storage...IBM Storage...

IBM Storage Integration ServerVersion 1.2.0

User Guide

SC27-5999-03

��

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

Edition notice

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

© Copyright IBM Corporation 2013, 2014.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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Upgrading an existing installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Extracting and installing the Integration Server software package . . . . . . . . . . . . . . . . . . 8

Replacing the self-signed SSL certificate . . . . . . . . . . . . . . . . . . . . . . . . . 8Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Uninstalling the Integration Server software . . . . . . . . . . . . . . . . . . . . . . . 10Uninstalling version 1.1.0 of the IBM Storage Enhancements for VMware vSphere Web Client . . . . . . . 10

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

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

Managing the Integration Server from the graphical user interface (GUI) . . . . . . . . . . . . . . . 30GUI – Logging in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31GUI – Managing storage arrays. . . . . . . . . . . . . . . . . . . . . . . . . . . . 31GUI – Managing Integration Server users . . . . . . . . . . . . . . . . . . . . . . . . 37GUI – Managing and monitoring VASA access . . . . . . . . . . . . . . . . . . . . . . 41GUI – Managing servers and storage pools for vSphere Web Client. . . . . . . . . . . . . . . . 43

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

Chapter 5. Using the IBM Storage Enhancements for VMware vSphere Web Client . . . 55Populating vCenter server information to the Integration Server . . . . . . . . . . . . . . . . . . 55Viewing the IBM storage resource information. . . . . . . . . . . . . . . . . . . . . . . . 57Creating and mapping a new storage volume (LUN) . . . . . . . . . . . . . . . . . . . . . 61

© Copyright IBM Corp. 2013, 2014 iii

Extending a volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Renaming a volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Setting multipath policy enforcement for a volume . . . . . . . . . . . . . . . . . . . . . . 69Moving a volume to another storage pool . . . . . . . . . . . . . . . . . . . . . . . . . 70Unmapping a volume from one or more hosts. . . . . . . . . . . . . . . . . . . . . . . . 71Deleting an unused volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Chapter 6. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Checking and controlling the Integration Server service . . . . . . . . . . . . . . . . . . . . 75Checking the log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Checking and modifying the configuration files . . . . . . . . . . . . . . . . . . . . . . . 77

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

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

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. IBM Storage Integration Server version number . . . . . . . . . . . . . . . . . . . . . . 64. vSphere Web Client – Client Plug-Ins . . . . . . . . . . . . . . . . . . . . . . . . . 75. IBM Storage Extension in the vCenter Plug-in Manager . . . . . . . . . . . . . . . . . . . 76. VMware vSphere Web Client on the Windows services list . . . . . . . . . . . . . . . . . . 117. 'Add or Remove Programs' dialog box . . . . . . . . . . . . . . . . . . . . . . . . 128. IBM Storage Integration Server login box in a standard web browser . . . . . . . . . . . . . . 319. Clicking Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

10. Current storage array username (for all storage arrays) . . . . . . . . . . . . . . . . . . . 3311. Change Credentials dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . 3312. Add Array dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3413. List of added storage arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3514. Storage array details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3515. Modify Array icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3616. Modify Array dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3617. Remove Array icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3718. Remove Array confirmation message . . . . . . . . . . . . . . . . . . . . . . . . . 3719. Clicking Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3820. Add User dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3921. List of added Integration Server users (user names) . . . . . . . . . . . . . . . . . . . . 3922. Modify User icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4023. Change Password dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4024. Delete User icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4125. Clicking VASA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4126. Current VASA Secret username . . . . . . . . . . . . . . . . . . . . . . . . . . . 4227. Change Secret dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4228. Clicking vSphere Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4329. Add vCenter Server dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . 4430. List of vCenter servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4431. Update vCenter Server Credentials dialog box . . . . . . . . . . . . . . . . . . . . . . 4532. vSphere Web Client – vCenter Servers – Remove button . . . . . . . . . . . . . . . . . . 4633. Remove vCenter Server confirmation message . . . . . . . . . . . . . . . . . . . . . . 4634. Attach Storage Pools dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . 4735. List of attached storage pools per vCenter server . . . . . . . . . . . . . . . . . . . . . 4836. Detach Storage Pool confirmation message . . . . . . . . . . . . . . . . . . . . . . . 4937. vSphere Client – Storage Providers list . . . . . . . . . . . . . . . . . . . . . . . . 5238. Add Vendor Provider dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . 5339. vCenter certificate thumbprint dialog box . . . . . . . . . . . . . . . . . . . . . . . 5340. Supported Vendor list displaying the IBM Storage Integration Server . . . . . . . . . . . . . . 5441. Populate vCenter Information option . . . . . . . . . . . . . . . . . . . . . . . . . 5642. Populate vCenter confirmation message . . . . . . . . . . . . . . . . . . . . . . . . 5643. IBM Storage category in vSphere Web Client . . . . . . . . . . . . . . . . . . . . . . 5744. IBM Storage information per storage array . . . . . . . . . . . . . . . . . . . . . . . 5845. Currently available storage pools per storage array . . . . . . . . . . . . . . . . . . . . 5846. IBM Storage information per vCenter server . . . . . . . . . . . . . . . . . . . . . . 5947. IBM Storage information per datacenter . . . . . . . . . . . . . . . . . . . . . . . . 5948. IBM Storage information per datastore . . . . . . . . . . . . . . . . . . . . . . . . 5949. IBM Storage information per all ESXi hosts of a vCenter server . . . . . . . . . . . . . . . . 6050. IBM Storage information per all VM templates of a vCenter server . . . . . . . . . . . . . . . 6051. IBM Storage information per all vApps of a vCenter server . . . . . . . . . . . . . . . . . 6052. IBM storage array view – Clicking Create New Volume . . . . . . . . . . . . . . . . . . . 6153. Top Level Objects view – Clicking Create New Volume . . . . . . . . . . . . . . . . . . . 6254. Right-clicking the storage array . . . . . . . . . . . . . . . . . . . . . . . . . . . 6255. Clicking the Create New Volume icon. . . . . . . . . . . . . . . . . . . . . . . . . 63

© Copyright IBM Corp. 2013, 2014 v

56. Create New Volume wizard (XIV example) . . . . . . . . . . . . . . . . . . . . . . . 6357. Setting the volume size with the graphic space marker . . . . . . . . . . . . . . . . . . . 6458. Creating multiple volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6559. Creating multiple volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6660. Advanced Host Mapping dialog box . . . . . . . . . . . . . . . . . . . . . . . . . 6761. Clicking Extend on the pop-up menu . . . . . . . . . . . . . . . . . . . . . . . . . 6862. Rename volume option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6963. Rename Volume dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6964. Set Multipath Policy Enforcement option. . . . . . . . . . . . . . . . . . . . . . . . 7065. Change Multipath Policy Enforcement dialog box . . . . . . . . . . . . . . . . . . . . . 7066. Move volume option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7167. Unmap volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7268. Delete volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7369. Integration Server GUI – Collect Logs option . . . . . . . . . . . . . . . . . . . . . . 7770. Integration Server GUI – Saving the logs in a compressed TAR archive . . . . . . . . . . . . . 77

vi IBM Storage Integration Server

Tables

1. Required vSphere privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32. Required tasks in sequential order . . . . . . . . . . . . . . . . . . . . . . . . . . 133. Optional tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144. Arguments for isis_ldap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155. ldap.ini configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 186. Arguments for isis_users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207. Arguments for isis_storage_credentials . . . . . . . . . . . . . . . . . . . . . . . 228. Arguments for isis_storage_array . . . . . . . . . . . . . . . . . . . . . . . . . 249. Arguments for vasa_admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

10. Arguments for vwc_vcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2711. Arguments for vwc_pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2812. Arguments for vwc_host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2813. Arguments for isis_configuration . . . . . . . . . . . . . . . . . . . . . . . . . 3014. Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

© Copyright IBM Corp. 2013, 2014 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, 2014 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 VMwarevSphere APIs for 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 the VMware vSphere APIs for Storage Awareness (VASA). It deliversinformation about IBM storage topology, capabilities, and state, together withstorage events and alerts 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, 2014 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 automaticallydeployed and enabled for each and every vCenter server that is registered forvSphere Web Client services on the connected 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 page43)

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 55)

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 “Upgrading an existing installation”v “Extracting and installing the Integration Server software package” on page 8v “Replacing the self-signed SSL certificate” on page 8

Upgrading an existing installationIf you are already using a previous version of the IBM Storage Integration Server,you can upgrade to the newer version without having to uninstall the previousversion.

Note: For the first-time installation procedure, see “Extracting and installing theIntegration Server software package” on page 8.

To upgrade to the newer Integration Server version:1. On the vSphere Web Client Server side: if you were using version 1.1.0 of the

IBM Storage Enhancements for vSphere Web Client, perform the manualuninstallation procedure as described in “Uninstalling version 1.1.0 of the IBMStorage Enhancements for VMware vSphere Web Client” on page 10.

2. On the IBM Storage Integration Server side: download the newer installationpackage (see “Download site” on page 4).

3. Extract the downloaded package (see steps 1–2 in “Extracting and installing theIntegration Server software package” on page 8).

4. Go to the extracted directory and then use the rpm -U *.* command (asopposed to rpm -vi *.* that is used in first-time installations).

5. Log out of the Integration Server GUI and then log in (see “GUI – Logging in”on page 31). Verify that the Integration Server version number has beenupdated on the bottom left corner on the GUI window.


6. To avoid issues with the VASA Provider functionality, replace the self-signedSSL certificate as described in “Replacing the self-signed SSL certificate” onpage 8.

The IBM Storage Enhancements for vSphere Web Client are automatically updatedon each and every registered vCenter server (previously added to the IntegrationServer; see 'List of vCenter servers' in “GUI – Adding a vCenter server” on page43). Accordingly:1. On the vSphere Web Client side: log off from then log on.2. Go to Home > Administration > Client Plug-Ins and verify that the latest

version of the IBM Storage Enhancements is enabled for each relevant vCenterserver.

Figure 3. IBM Storage Integration Server version number


If you are managing a vCenter server through vSphere Client, you can verify thatthe IBM Storage Extension plug-in has been updated by checking the vCenterPlug-in Manager.

Figure 4. vSphere Web Client – Client Plug-Ins

Figure 5. IBM Storage Extension in the vCenter Plug-in Manager

Chapter 2. Installation 7

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.2.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.2.0-*.rpm – product RPMv ibm_storage_integration_server_java_runtime_extension-1.2.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.2.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.2.0-*.rpm last.

The IBM Storage Provider service starts automatically after the installation (formore information, see “Checking and controlling the Integration Server service”on page 75), and a new Linux user named isis is created so that you can use itfor Integration Server management operations.

Replacing the self-signed SSL certificateDuring the installation, a self-signed Secure Sockets Layer (SSL) certificate isgenerated to create a secure communication channel for servers and clients. If youalready have a trusted certificate that you want to use, you can replace theself-signed certificate with the trusted certificate.

About this task

A self-signed certificate file, vp.crt, is stored in the following directory:/opt/ibm/ibm_storage_integration_server/settings/ssl_cert.


Procedure

To replace the self-signed certificate with a trusted certificate, complete thefollowing steps:1. Place a copy of the ssl_certificate file and ssl_certificate_key file in the

/opt/ibm/ibm_storage_integration_server/settings/ssl_cert directory.The ssl_certificate is your primary certificate that is combined with theintermediate certificate (your_domain_name.crt). The ssl_certificate_key is thekey file that is generated when you created the certificate signing request.

2. Edit the isis_nginx.conf file in the opt/ibm/ibm_storage_integration_server/conf.d/nginx directory by changing the following names to your file names:

ssl_certificate ssl_cert/vp.crt

ssl_certificate_key ssl_cert/vp.key

Note: You can also override the content of the existing files.

3. Issue the service nginx restart command to restart nginx.

What to do next

The format of your key file can be PK12, or a combination of CRT or PEM and KEY.v To convert the certificates bundle file from PK12 format to PEM, run the

following command:openssl pkcs12 -nokeys -in server-cert-key-bundle.p12-out server-ca-cert-bundle.pem

v To convert the server key file from PK12 format to KEY, run the followingcommand:openssl pkcs12 -nocerts -nodes -in server-cert-key-bundle.p12-out server.key

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 29.

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.


The following sections describe how to uninstall each individual software package.v “Uninstalling version 1.1.0 of the IBM Storage Enhancements for VMware

vSphere Web Client”v “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 29.

Important: Before removing the IBM Storage Integration Server software, removeall vCenter servers that were registered for vSphere Web Client, as explained in“GUI – Removing a vCenter server” on page 45. If any vCenter server is notremoved prior to the uninstallation, the IBM Storage Enhancements will remainvisible but not functional for that vCenter server.

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 75.3. Run the standard Linux uninstallation command for each installed package (as

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

Uninstalling version 1.1.0 of the IBM Storage Enhancementsfor VMware vSphere Web Client

If you have been using version 1.1.0 of the IBM Storage Integration Server, youneed to manually uninstall the previous version of the IBM Storage Enhancementsfor VMware vSphere Web Client.

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.


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.

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


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 “Configuring directory user access” on page 14v “Managing the Integration Server from the command-line interface (CLI)” on

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

page 30

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 19

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

GUI v “GUI – Logging in” on page 31

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

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

CLI orGUI

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

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

4. Add the storage arrays to be used CLI orGUI

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

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

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 25

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

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 26

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

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

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


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 26

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

Table 3. Optional tasks

Optional task Interface Refer to

Configure LDAP-based directory user access tothe Integration Server

CLI v “Configuring directory user access”

Manage the Integration Server users CLI orGUI

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

v “GUI – Managing Integration Server users” onpage 37

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 29

Configuring directory user accessYou can allow external directory users to connect to the IBM Storage IntegrationServer and manage it without having a locally-defined user account.

The connection to the directory server is established through Lightweight DirectoryAccess Protocol (LDAP) authentication. When directory server access is enabled,any login attempt (attempt to log in to the Integration Server) is authenticatedagainst both the local database of Integration Server users, and against the defineddirectory server.

Use the isis_ldap CLI command to configure LDAP-based directory user access toIBM Storage Integration Server. Use the required argument after the command, asspecified in the following table.

Note:

v When directory user access is enabled and configured through isis_ldap, thedirectory users can access and manage only the Integration Server. A separateand unrelated authentication system may be used on the storage system side fordirectory-based management of the storage system. For more information, referto “CLI – Adding or removing storage array credentials” on page 21 and to yourstorage system documentation.

v Once the connection is established, all users that are defined on the directoryserver can access and manage the IBM Storage Information Server.


Table 4. Arguments for isis_ldap

Argument Use after isis_ldap to:

configure -e -a

-s <server URI>

-t <directory server type>

-r <user search DN>

-k <user search key>

-g <user group DN>

-o <user group object class

-n <user group authentication DN>

or

configure --enable --anonymous

--server_uri <server URI>

--server_type <directory server type>

--user_search_dn <user search DN>

--user_search_key <user search key>

--group_search_dn <user group DN>

--group_object_class <user group object class

--authentication_group_dn <user groupauthentication DN>

Enable directory access and establish a connection to a directoryserver as an anonymous user with the following parametersspecified after the -a argument on the command line:

v Server URI (-s; --server_uri) – Uniform resource identifier(URI) of the directory server. This parameter determineswhich directory server should be accessed and used fordirectory user management of the Integration Server.

v Server type (-t; --server_type) – Type of the directory server.One of the following types can be specified:

– Active Directory (active_directory)

– Open LDAP (open_ldap)

– Custom (custom)

v User search DN (-r; --user_search_dn) – Distinguished name(DN) to be used for the user search.

v User search key (-k; --user_search_key) – Search key of thedirectory user. Valid only if the specified server type (-t;--server_type) is 'custom'.

v Group search DN (-g; --group_search_dn) – Distinguishedname (DN) of the user group for search purposes.

v Group object class (-o; --group_object_class) – Object classof the user group. Valid only if the specified server type (-t;--server_type) is 'custom'.

v Authentication group DN (-n; --authentication_group_dn) –Distinguished name (DN) used for the user groupauthentication.

When prompted to enter a password, press Enter withoutentering any password:

Please enter the BIND_DN password (password not shown):

The following changes were applied to the LDAP configuration:ENABLEDPlease restart the IBM Storage Integration Server to applythe new configuration.

After enabling the directory access, you can test the directoryconnection by using the test option (see below). Then, restartthe IBM Storage Integration Server service as explained in“Checking and controlling the Integration Server service” onpage 75.

Chapter 3. Integration Server operation and management 15

Table 4. Arguments for isis_ldap (continued)


configure -e -u <Bind DN username>

-p <Bind DN password>

-s <server URI>

-t <directory server type>

-r <user search DN>

-k <user search key>

-g <user group DN>

-o <user group object class

-n <user group authentication DN>

or

configure --enable

--bind_dn <Bind DN username>

--bind_passowrd <Bind DN password>

--server_uri <server URI>

--server_type <directory server type>

--user_search_dn <user search DN>

--user_search_key <user search key>

--group_search_dn <user group DN>

--group_object_class <user group object class

--authentication_group_dn <user groupauthentication DN>

Enable directory access and establish a connection to a directoryserver by using the Bind DN user account that was predefinedon the directory server (predefined by the directory serveradministrator). For this command, specify the followingparameters on the command line:

v Bind DN username (-u; --bind_dn) – Username of the BindDN user through which access to the directory server isestablished. The IBM Storage Integration Server uses thisusername to log in to the directory server and establish theconnection with it.

v Bind DN password (-p; --bind_password) – Password of theBind DN username.

v Server URI (-s; --server_uri) – Uniform resource identifier(URI) of the directory server. This parameter determineswhich directory server should be accessed and used fordirectory user management of the Integration Server.

v Server type (-t; --server_type) – Type of the directory server.One of the following types can be specified:

– Active Directory (active_directory)

– Open LDAP (open_ldap)

– Custom (custom)

v User search DN (-r; --user_search_dn) – Distinguished name(DN) to be used for the user search.

v User search key (-k; --user_search_key) – Search key of thedirectory user. Valid only if the specified server type (-t;--server_type) is 'custom'.

v Group search DN (-g; --group_search_dn) – Distinguishedname (DN) of the user group for search purposes.

v Group object class (-o; --group_object_class) – Object classof the user group. Valid only if the specified server type (-t;--server_type) is 'custom'.

v Authentication group DN (-n; --authentication_group_dn) –Distinguished name (DN) used for the user groupauthentication.

When prompted to enter a password, enter the directory server'sBind DN user password:

Please enter the BIND_DN password (password not shown): ******

The following changes were applied to the LDAP configuration:ENABLEDPlease restart the IBM Storage Integration Server to applythe new configuration.

After enabling the directory access, you can test the directoryconnection by using the test option (see below). Then, restartthe IBM Storage Integration Server service as explained in“Checking and controlling the Integration Server service” onpage 75.


Table 4. Arguments for isis_ldap (continued)


configure -d

or

configure --disable

Disable directory user access.

After disabling the directory access, restart the IBM StorageIntegration Server service as explained in “Checking andcontrolling the Integration Server service” on page 75.

list Display the current directory server configuration status (on theIBM Storage Integration Server) and Bind DN username.

test -u <directory username> -p <password> Test a directory user account by specifying the username andpassword of that account. You can test any user account that isdefined on the directory server (the test is not for the Bind DNuser account, but for an actual directory account).

For example:

isis_ldap test -u john221 -p ********

-h

or --help

Display help information that is relevant to isis_ldap.

You can also display help for the configure, list, or testargument if it is typed on the command line as well.

Adding a directory server certificate

If the directory server uses Transport Layer Security (TLS), you must edit theldap.conf file and specify the trusted certificate directory location and filename onthe IBM Storage Integration Server. Complete the following steps to update theIBM Storage Integration Server:1. Log in to the directory server and issue the following command: certutil

-ca.cert client.crt. This command generates the server certificate.2. Go to the /etc/openldap/ directory and edit the ldap.conf file by setting the

value for the TLS_CACERT parameter. The following example shows the contentsof the ldap.conf file:#LDAP Defaults##BASE dc=example,dc=com#URI ldap://ldap.example.com ldap://ldap-master.example.com:port##SIZELIMIT 12#TIMELIMIT 15#DEREF neverTLS_CACERT /etc/openldap/certs/trusted_ldap.pem

Make sure that the TLS_CACERT parameter has the directory and file name of thenew certificate that you generated. After editing the ldap.conf file, theldap.ini file is automatically updated.

Editing the ldap.ini configuration file

You can edit the ldap.ini configuration file to manually change the directory useraccess settings.

Attention: Do not edit the ldap.ini file if you are not familiar with directorysetting conventions.


The following example shows the editable parameters and their values specifiedafter the '=' sign:enable_ldap = Trueserver_uri = ldap://servername.domainname:389server_type = OPEN_LDAPuser_search_dn = ou=users,dc=dcname,dc=comuser_search_key =group_search_dn = dc=dcname,dc=comgroup_object_class =authentication_group_dn = cn=authenticating-group,dc=dcname,dc=combind_dn =bind_password = <enctypted password>=bind_pwd_verification = <encrypted key>=

The following table summarizes the parameters and their indication.

Table 5. ldap.ini configuration parameters

Parameter Indication

enable_ldap True or False.

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

server_uri Uniform resource identifier (URI) of the directoryserver.

server_type Type of the directory server:

v Active Directory

v Open LDAP

v Custom

user_search_dn Distinguished name (DN) to be used for usersearch.

user_search_key Search tag for obtaining a unique relativedistinguished name (RDN).

Commonly used values: uid, preferredId

group_search_dn Distinguished name (DN) to be used for usergroup search.

group_object_class Type of the user group.

Commonly used values: GroupOfNames,NestedGroupOfNames, GroupOfUniqueNames,NestedGroupOfUniqueNames, ActiveDirectoryGroup,NestedActiveDirectoryGroup

authentication_group_dn Distinguished name (DN) of the authenticationuser group.

bind_dn Username of the Bind DN user through whichaccess to the directory server is established.

bind_password Password of the Bind DN username. Thepassword is displayed in its encrypted form.

bind_pwd_verification Verification string for the Bind DN password. Thestring is displayed in its encrypted form.


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. You can remove this parameter from the ldap.ini file to disablegroup authentication.

v When server_type type is Active Directory, the following parameters are usedby default:user search key = sAMAccountNameuser group object class = ActiveDirectoryGroup

v When server_type type is Open LDAP, the following parameters are used bydefault:user search key = uiduser group object class = GroupOfUniqueNames

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 20v “CLI – Adding or removing storage array credentials” on page 21v “CLI – Adding or removing storage arrays” on page 23v “CLI – Setting the VASA Secret credentials” on page 25v “CLI – Managing vCenter servers and storage pools for vSphere Web Client” on

page 26v “CLI – Backing up or restoring an Integration Server configuration” on page 29

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.

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 37.v The isis_users utility cannot define or affect external directory users. For more

information about how to configure directory user access, see “Configuringdirectory user access” on page 14.

Table 6. 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 ********


Table 6. Arguments for isis_users (continued)

Argument Use after isis_users to:

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 listUser list:john_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 An identical storage admin user account with identical credentials (the sameusername and password) must already be predefined on all the IBM storagearrays that you intend to use. The IBM Storage Integration Server can use only asingle array management account for accessing all the different storage arraysthat you use. For more information about how to define a storage adminaccount on your IBM storage arrays, refer to the relevant storage systemmanagement tools documentation.

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 32.

Table 7. Arguments for isis_storage_credentials

Argument Use after isis_storage_credentials to:

set -u <array username>

-p <array password>

-f

-a <user type>

or

set --user <array username>

--password <array password>

--force

--user_account <user type>

Set the username and password for accessing all the relevant IBMstorage systems, and specify whether the storage admin user islocally-defined on the storage system or on a directory server.

For example, if the storage admin user is locally defined on thestorage system, enter:

isis_storage_credentials set -u john21 -p ******** -a local

And if the storage admin user is defined on a directory server,enter:

isis_storage_credentials set -u john21 -p ******** -a directory

Attention: During regular operation, whenever a directory-basedstorage admin fails to log in (from the Integration Server side) toany storage array that is in use, the Integration Server immediatelylocks the storage admin user account and all storage arraysbecome inaccessible on the Integration Server side. This is toprevent repeated login attempt failures after which the directoryserver blocks that user account. In such a case, use the -f or--force argument on the command line to unlock the storageadmin account on the Integration Server side, with either the samecredentials or with updated credentials. For example:

isis_storage_credentials set -u john21 -p ******** -f -a directory

The equivalent action in the Integration Server GUI is to updatethe account credentials, as described in “GUI – Entering thestorage array credentials” on page 32.

remove Delete the existing storage array user account definition from theserver.

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.


Table 7. Arguments for isis_storage_credentials (continued)

Argument Use after isis_storage_credentials to:

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

The following example shows the command output when thestorage admin user account is defined locally on the storagesystem:

isis_storage_credentials listUsername: john21, User Account: local

The following example shows the command output when thestorage admin user account is defined on a directory server:

isis_storage_credentials listUsername: john21, User Account: directory

-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 21.

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 31.


Table 8. 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

list List the names and details of all the IBM storage arrays that arecurrently added (and were not removed). The displayedinformation includes:

v Array alias

v Array identifier

v Management IP address

v Elapsed time since last update

v Connected

v Notes

See the example after this table.

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

The following example shows the displayed information and format of theisis_storage_array list command output.


isis_storage_array list

Array Array Management Elapsed timeAlias Identifier IP Addresses since last update Connected Notes---------- ---------------- ------------- ------------------ ---------- ---------------------------------array1000 2810-114-MN65026 9.100.150.155 16 minutes False Failed to log in to array 2810

with the provided credentials.

array2000 2810-114-MN65027 9.200.155.155 27 minutes True

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 vSphere 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 51. 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 41.

Table 9. Arguments for vasa_admin

Argument Use after vasa_admin to:

set_secret -n <username> -p <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

-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 23.

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 12 on page 28), the same

operations are available from the GUI as well, as explained in “GUI – Managingservers and storage pools for vSphere Web Client” on page 43.


Table 10. Arguments for vwc_vcenter

Argument Use after vwc_vcenter to:

add -u <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 -u 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 11 on page 28).

modify -u <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 -u 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 11. 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 10 on page 27) 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 12. 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 12. 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 75. 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 13. 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

restore -f ./vasa115exported.db Restore an existing Integration Server configuration that wasmade with IBM Storage Provider for VMware VASA version1.1.5 (applicable only to XIV systems).

For this restore operation, you do not need to provide anencryption key:

isis_configuration restore -f ./vasa115exported.db

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 31v “GUI – Managing storage arrays” on page 31v “GUI – Managing Integration Server users” on page 37v “GUI – Managing and monitoring VASA access” on page 41


v “GUI – Managing servers and storage pools for vSphere Web Client” on page 43

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.

Attention:

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 37).

v If the Integration Server service is stopped on the Linux host (see “Checking andcontrolling the Integration Server service” on page 75), 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.

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


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 thefollowing sections.

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

v “GUI – Entering the storage array credentials”v “GUI – Adding a storage array” on page 34v “GUI – Modifying the IP address or hostname of a storage array” on page 35v “GUI – Removing a storage array” on page 36

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 An identical storage admin user account with identical credentials (the sameusername and password) must already be predefined on all the IBM storagearrays that you intend to use. The IBM Storage Integration Server can use only asingle array management account for accessing all the different storage arraysthat you use. For more information about how to define a storage adminaccount on your IBM storage arrays, refer to the relevant storage systemmanagement tools documentation.

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 21.

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. Next to the username, in parentheses, one of the followingindications is displayed:v (local) – The storage admin user account is locally defined on the storage

system.v (directory) – The storage admin user account is defined on a directory server.

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.4. If the storage admin user account is defined on a directory server, select the

This is a directory account check box. Otherwise, if the storage admin useraccount is locally-defined on the storage system, clear the check box.

5. 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.

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

Figure 11. Change Credentials dialog box


Attention: During regular operation, whenever a directory-based storage adminfails to log in (from the Integration Server side) to any storage array that is in use,the Integration Server immediately locks the storage admin user account and allstorage arrays become inaccessible on the Integration Server side. This is toprevent repeated login attempt failures after which the directory server blocks thatuser account. In such a case, use the Change Credentials option again to unlockthe storage admin account on the Integration Server side, with either the samecredentials or with updated credentials. The equivalent action in the IntegrationServer CLI is to use the force credentials options, as described in “CLI – Adding orremoving storage array credentials” on page 21.

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 solutioncomponents” 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 32) and the IP connection isestablished, the storage array is added to the Storage Arrays table.

Figure 12. Add Array dialog box


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

Note: If the connection between the storage array and the Integration Server islost, a Note is also displayed under Storage Array Details to notify you about theconnection loss.

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.

Figure 13. List of added storage arrays

Figure 14. Storage array details



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.

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 these

Figure 15. Modify Array icon

Figure 16. Modify Array dialog box


storage 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.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 in

Figure 17. Remove Array icon

Figure 18. Remove Array confirmation message


the 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 20.

v “GUI – Adding an Integration Server user”v “GUI – Changing the password of an Integration Server user” on page 39v “GUI – Deleting an Integration Server user” on page 40

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.

Figure 19. Clicking Users


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.

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 40) andthen create a new one (see “GUI – Adding an Integration Server user” on page 38).

Figure 20. Add User dialog box

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



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.

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 38.

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

Figure 22. Modify User icon

Figure 23. Change Password dialog box



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.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 51.

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

Figure 24. Delete User icon

Figure 25. Clicking VASA


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 25.

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.

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.

Figure 26. Current VASA Secret username

Figure 27. Change Secret dialog box


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.

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 26.

v “GUI – Adding a vCenter server”v “GUI – Updating the credentials of a vCenter server” on page 44v “GUI – Removing a vCenter server” on page 45v “GUI – Attaching a storage pool to a vCenter server” on page 46v “GUI – Detaching a storage pool from a vCenter server” on page 48

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.

Note: For any vCenter server that you add, the IBM Storage Enhancements forVMware vSphere Web Client (see Chapter 5, “Using the IBM StorageEnhancements for VMware vSphere Web Client,” on page 55) are automaticallydeployed and enabled on the vSphere Web Client Server side.

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.

Figure 29. Add vCenter Server dialog box

Figure 30. List of vCenter servers



displayed and lists the currently added vCenter servers.2. Click the row of the vCenter server for which you want to update the

credentials, 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 with the storage pools attached to it, can no

longer be managed by the IBM Storage Enhancements for VMware vSphere WebClient. Following the removal, the IBM Storage Enhancements become disabledfor that vCenter on the vSphere Web Client Server side.

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.

Figure 31. Update vCenter Server Credentials dialog box


2. Click the row of the vCenter server that you want to remove, and then clickRemove.A confirmation message is displayed.

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 32).

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

Figure 32. vSphere Web Client – vCenter Servers – Remove button

Figure 33. Remove vCenter Server confirmation message


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 isdisplayed.

Figure 34. Attach Storage Pools dialog box


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.

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.

Figure 35. List of attached storage pools per vCenter server


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

Figure 36. 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 DS8000 systems are not supported by the IBM Storage Provider forVMware 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.

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.

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 page41). 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 37. 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 38. Add Vendor Provider dialog box

Figure 39. vCenter certificate thumbprint dialog box

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

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


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

Together with supported IBM storage systems that are managed by the IBMStorage Integration Server, the deployed IBM Storage Enhancements enable thefollowing management features on vSphere Web Client side for registered vCenterservers: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.

Note: The IBM Storage Enhancements are automatically deployed and madeavailable for the vCenter servers that were registered (added) on the IBM StorageIntegration Server (see “GUI – Adding a vCenter server” on page 43).

See the following sections for more information:v “Populating vCenter server information to the Integration Server”v “Viewing the IBM storage resource information” on page 57v “Creating and mapping a new storage volume (LUN)” on page 61v “Extending a volume” on page 67v “Renaming a volume” on page 68v “Setting multipath policy enforcement for a volume” on page 69v “Moving a volume to another storage pool” on page 70v “Unmapping a volume from one or more hosts” on page 71v “Deleting an unused volume” on page 72

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“Checking and modifying the configuration files” on page 77). 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 added on the IBM Storage Integration Server, as explained in “GUI –Adding a vCenter server” on page 43.

Procedure1. In vSphere Web Client, focus on the relevant vCenter server.


2. From the Actions menu, select All IBM Storage Enhancements for... > RefreshStorage Integration ServerA confirmation message appears.

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

Figure 41. Populate vCenter Information option

Figure 42. Populate vCenter confirmation message


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 31 and “GUI – Managingservers and storage pools for vSphere Web Client” on page 43.

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 43. IBM Storage category in vSphere Web Client

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

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 44. IBM Storage information per storage array

Figure 45. Currently available storage pools per storage array


Figure 46. IBM Storage information per vCenter server

Figure 47. IBM Storage information per datacenter

Figure 48. IBM Storage information per datastore


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

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

Figure 51. 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 43

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 57).

2. Click Actions > Create New Volume. Alternatively, from the Top LevelObjects view on the relevant vCenter server, click Actions > All IBM StorageActions > Create New Volume.

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


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

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

Figure 54. Right-clicking the storage array


The Create New Volume dialog box is displayed.

Note: When you create a single volume, a LUN ID is created for that volume,which you can later modify. If you create multiple volumes, LUN IDs areautomatically assigned to those volumes but cannot be modified.

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 55. Clicking the Create New Volume icon

Figure 56. 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 step6 on page 65): In the Number of Volumes text box, enter the number ofvolumes that you want to create simultaneously. The text box next to theVolume Name entry displays vol_{1} by default. The {1} represents the suffixvalue, and it must be kept as part of the volume name. You edit the volumename and also move the suffix value within the name (the {1} suffix does nothave to be at the end of the volume name).

Figure 57. 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. If you are creating a single volume, you can select the LUN that shouldrepresent the new volume on the storage system, or keep the automaticallyselected LUN. The LUNs are automatically selected when creating multiplevolumes.

Figure 58. Creating multiple volumes


Note: After the volume is created, the specific LUN association cannot be changed,and the same number cannot be assigned to a different volume. The specific LUNcan become available for reassignment only after its associated volume is deleted.

8. 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 aredisplayed based on the requested volume size. For DS8000, theover-provision ratio information 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 orvolumes to be created.

Figure 59. Creating multiple volumes


Note:

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.

9. From Host Mapping, select the host(s), cluster(s), or datacenter(s) to whichyou want to map the new volume. You can click Custom to specify a custommapping in the Advanced Host Mapping dialog box.

Note: Any ESXi host that is connected to the storage array can be selected. Hoststhat are not connected to the storage array are marked and a message notifies youabout any connectivity problem. If you select a datacenter, its member clusters andhosts are automatically selected under it.

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

10. Review the details of the new volume that is about to be created, and thenclick OK 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.

Figure 60. Advanced Host Mapping dialog box


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.

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 the

Figure 61. Clicking Extend on the pop-up menu


volume row or using the Actions 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 ]

If you want to stop and then start the IBM Storage Provider service in onecommand, use the restart command:

[root@isis]# service ibm_storage_integration_server restartStopping Django service ... [ OK ]Stopping Celery services ... [ OK ]Starting 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 /var/log/isis/ directory:v events.log – Records Integration Server events according to their type: Info,

Error, or Warning. Event logging is now compatible with the Rsyslogapplication, an open source utility for forwarding log messages over IP networks(for more information, see the Rsyslog website). The following example showsdifferent events that might be recorded:

ISIS-0001, INFO, "User {user_name} has logged in."ISIS-0002, INFO, "User {user_name} has logged out."ISIS-0003, WARNING, "User {user_name} login attempt failed."ISIS-0004, INFO, "IBM Storage Integration Server local user account {user_name} was created."ISIS-0005, INFO, "IBM Storage Integration Server local user account {user_name} was deleted."ISIS-0006, INFO, "IBM Storage Integration Server local user account {user_name} password was reset."ISIS-0007, INFO, "Storage credentials were set for user {user_name}."ISIS-0008, ERROR, "Storage credentials for user {user_name} were disabled. Reason: {reason}."ISIS-0009, INFO, "Storage array identified as {identifier} with IP address {ip_address} has been added."ISIS-0010, WARNING, "Storage array {identifier} was removed."ISIS-0011, WARNING, "Storage array {identifier} was modified. Its new IP address is {ip_address}."ISIS-0014, INFO, "vCenter server with IP address {ip_address} was added by user {user_name}."ISIS-0015, WARNING, "vCenter server with IP address {ip_address} was removed."ISIS-0016, WARNING, "Credentials for vCenter server with IP address {ip_address} were updated by user {user_name}."ISIS-0017, INFO, "Storage pool {pool_name} on storage array {identifier} was attached to vCenter server with IP address {ip_address}."ISIS-0018, WARNING, "Storage pool {pool_name} on storage array {identifier} was detached from vCenter server with IP address {ip_address}."ISIS-0019, ERROR, "Failed to connect to storage array {identifier}. Reason: {reason}."ISIS-0020, INFO, "Information retrieval from storage array {identifier} was completed."ISIS-0021, ERROR, "Failed to retrieve information from storage array {identifier}. Reason: {reason}."ISIS-0022, INFO, "LDAP authentication was enabled."ISIS-0023, INFO, "LDAP authentication was disabled."ISIS-0024, INFO, "Completed the vSphere Web Client extension task {task_name} with the following parameters: {parameter_list}."ISIS-0025, ERROR, "Failed to complete the vSphere Web Client extension task {task_name} with the following parameters {parameter_list}.Reason: {reason}."

v hsgsvr.log – Records events regarding the collection of information from themonitored 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.

v ds8k_proxy.log – Records ESS network interface (ESSNI) proxy operations forDS8000.

v ds8k_jsvc_error.log – Records startup failures of the ESSNI proxy for DS8000.v ds8k_jsvc.log – Records Apache Jsvc operations for DS8000.

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


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

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 75.

Figure 69. Integration Server GUI – Collect Logs option

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

Chapter 6. Troubleshooting 77

Table 14. Configuration files

File name Directory location Purpose or relevant parameters

ibmsyslog.conf opt/ibm/ibm_storage_integration_server/conf.d/

Defines the logging standard per application,as well as the target of the log messages.

ibmlogs-rotate opt/ibm/ibm_storage_integration_server/conf.d/

Controls the archive and renewal timingattributes of the log files. For the list of logfiles, see “Checking the log files” on page 76.

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

See “Configuring directory user access” onpage 14.

ldap.conf /etc/openldap/ See “Configuring directory user access” onpage 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.

essni_proxy.properties/opt/ibm/ibm_storage_integration_server/conf.d/ds8k_proxy

ESS network interface (ESSNI) proxyconfiguration file.


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 83

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

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


Index

Aaccess to array 21add

storage array 23storage provider 51user 20vCenter server 26

admin commands 20array credentials 21attach pools 26

Bbackup 29best practices

datastores 79distributing DS8000 volumes 79ESXi hosts 79

Ccertificate

replacing 8change password 20check service 75CLI commands 19collect logs 76command-line interface

add or remove storage arraycredentials 21

add or remove storage arrays 23adding users 20backup or restore server

configuration 29configure directory server access 14manage vSphere web client 26managing the integration server 19set VASA credentials 25switch to ISIS user mode 19tasks 13

compatibility 3concept diagram 2configuration backup 29configuration files

modify 77creating or mapping

LUN 61

Ddatastores

best practices 79debug mode 77detach pools 26detect problems 76directory users 14download site 4DS8000 volumes

best practices 79

FFix Central 4

GGUI

adding server users 38adding storage array 34adding vCenter server 43attach storage pool to vCenter

server 46change user password 39deleting server users 40detach storage pool from vCenter

server 48enter storage array credentials 32logging in 31manage storage arrays 32manage the server 30manage the users 37manage VASA access 41manage vSphere web client 43modify IP address or hostname 35remove storage array 36remove vCenter server 45setting VASA credentials 41tasks 13update vCenter server credentials 44

Hhsgsvr_config.ini 77

Iibmsyslog.conf 77installation

Integration Server 8upgrade 5

Integration Servercontrolling the service 75

interval 77isis username 8

LLDAP 14ldap.conf 14ldap.ini 14, 77list

storage array 23users 20

log files 76LUN

create 61

Mmanagement 13multipath policy enforcement 69

Ooptional tasks 13

Ppopulate vCenter

update the Integration Server 55

Rregister

integration server 51release notes 3remove

storage array 23storage credentials 21user 20vCenter server 26

required tasks 13requirements 3resolve issues 75restart service 10restore 29rpm package 8

Ssave configuration 29server users 20service status 75start service 75stop service 10, 75storage array commands 23storage credentials

display 21remove 21set 21

storage enhancementsvSphere Web Client 55

storage poolsattach or detach 26

storage resource informationviewing 57

storage volumecreate 61

supported storage systems 3

Ttar.gz file 8tasks 13time interval 77troubleshoot 75


Uuninstall

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

vSphere Web Client 10upgrade 5user

privileges 3roles 3

user authentication 14

VVASA credentials 25VASA Provider server 51vasa_config.ini 77vCenter Server 51vendor providers 51VMware VASA

using storage provider 51volume

deleting unused 72extending 68move to another storage pool 71multipath policy enforcement 69rename 68unmapping from host 72

vSphere Client 51vSphere privileges 3vSphere Web Client

storage enhancements 1vSphere Web Client enhancements 55vwc_config.ini 77

Wwhat to do first 13


��

Printed in USA

SC27-5999-03

Date post:	17-May-2018
Category:	Documents
Upload:	habao
View:	217 times
Download:	1 times

IBM Storage Integration Serverdelivery04.dhe.ibm.com/sar/CMA/SDA/04lmz/0/IBM_Storage...IBM Storage...

Documents