IBM Storage Integration Server Version User Guide SC

Transcription

1 IBM Storage Integration Serer Version User Guide SC

2 Note Before using this document and the product it supports, read the information in Notices on page 75. Edition notice Publication number: SC This publication applies to ersion of the IBM Storage Integration Serer and to all subsequent releases and modifications until otherwise indicated in a newer publication. Copyright IBM Corporation US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents Figures Tables ii About this guide ix Who should use this guide ix Conentions used in this guide ix Related information and publications ix Getting information, help, and serice x Ordering publications x Sending your comments x Chapter 1. Introduction Included solution components IBM Storage Proider for VMware VASA IBM Storage Enhancements for VMware Sphere Web Client Concept diagram Compatibility and requirements Required Sphere priileges Download site Chapter 2. Installation Extracting and installing the Integration Serer software package Installing the IBM Storage Enhancements for VMware Sphere Web Client Uninstallation Uninstalling the Integration Serer software Uninstalling the IBM Storage Enhancements for VMware Sphere Web Client Chapter 3. Integration Serer operation and management Required and optional initial tasks Configuring LDAP user authentication Managing the Integration Serer from the command-line interface (CLI) CLI Switching to 'ISIS' user mode CLI Adding and managing Integration Serer users CLI Adding or remoing storage array credentials CLI Adding or remoing storage arrays CLI Setting the VASA Secret credentials CLI Managing Center serers and storage pools for Sphere Web Client CLI Backing up or restoring an Integration Serer configuration Managing the Integration Serer from the graphical user interface (GUI) GUI Logging in GUI Managing storage arrays GUI Managing Integration Serer users GUI Managing and monitoring VASA access GUI Managing serers and storage pools for Sphere Web Client Chapter 4. Using the IBM Storage Proider for VMware VASA Registering the Integration Serer as a storage proider in Center Serer Chapter 5. Using the IBM Storage Enhancements for VMware Sphere Web Client Setting the Integration Serer web address for Center serers Populating Center serer information to the Integration Serer Viewing the IBM storage resource information Creating and mapping a new storage olume (LUN) Copyright IBM Corp iii

4 Extending a olume Renaming a olume Setting multipath policy enforcement for a olume Moing a olume to another storage pool Unmapping a olume from one or more hosts Deleting an unused olume Chapter 6. Troubleshooting Checking and controlling the Integration Serer serice Checking the log files Checking and modifying the configuration files Chapter 7. Best Practices Handling datastores Handling ESXi hosts that use XIV olumes Distributing olumes eenly on DS8000 systems Notices Trademarks Index i IBM Storage Integration Serer

5 Figures 1. Integration of IBM storage systems with a VMware enironment VMware Sphere Web Client Create Role dialog box Installation language selection box IBM Storage Enhancements for VMware Sphere Web Client installation wizard Customer Information panel VMware Sphere Web Client on the Windows serices list 'Add or Remoe Programs' dialog box IBM Storage Integration Serer login box in a standard web browser Clicking Arrays Current storage array username (for all storage arrays) Change Credentials dialog box Add Array dialog box List of added storage arrays Storage array details Modify Array icon Modify Array dialog box Remoe Array icon Remoe Array confirmation message Clicking Users Add User dialog box List of added Integration Serer users (user names) Modify User icon Change Password dialog box Delete User icon Clicking VASA Current VASA Secret username Change Secret dialog box Clicking Sphere Web Client Add Center Serer dialog box List of Center serers Update Center Serer Credentials dialog box Remoe Center Serer confirmation message Attach Storage Pools dialog box List of attached storage pools per Center serer Detach Storage Pool confirmation message Sphere Client Storage Proiders list Add Vendor Proider dialog box Center certificate thumbprint dialog box Supported Vendor list displaying the IBM Storage Integration Serer Edit IBM Serer Address dialog box IBM Storage Integration Serer connection details per Center serer Populate Center Information option Populate Center confirmation message IBM Storage category in Sphere Web Client IBM Storage information per storage array Currently aailable storage pools per storage array IBM Storage information per Center serer IBM Storage information per datacenter IBM Storage information per datastore IBM Storage information per all ESXi hosts of a Center serer IBM Storage information per all VM templates of a Center serer IBM Storage information per all Apps of a Center serer IBM storage array iew Clicking Create New Volume Top Leel Objects iew Clicking Create New Volume Right-clicking the storage array Copyright IBM Corp. 2013

6 56. Clicking the Create New Volume icon Create New Volume wizard (XIV example) Setting the olume size with the graphic space marker Creating multiple olumes Adanced Host Mapping dialog box Clicking Extend on the pop-up menu Rename olume option Rename Volume dialog box Set Multipath Policy Enforcement option Change Multipath Policy Enforcement dialog box Moe olume option Unmap olume Delete olume Integration Serer GUI Collect Logs option Integration Serer GUI Saing the logs in a compressed TAR archie i IBM Storage Integration Serer

7 Tables 1. Required Sphere priileges Required tasks in sequential order Optional tasks LDAP configuration parameters Arguments for isis_users Arguments for isis_storage_credentials Arguments for isis_storage_array Arguments for asa_admin Arguments for wc_center Arguments for wc_pool Arguments for wc_host Arguments for isis_configuration Configuration files Copyright IBM Corp ii

8 iii IBM Storage Integration Serer

9 About this guide Who should use this guide This guide describes how to install, configure, and use the IBM Storage Integration Serer and its solution components. This guide is intended for system administrators who are familiar with the VMware Center and Sphere enironments, and with the specific IBM storage system that is in use. Conentions used in this guide These notices are used in this guide to highlight key information. Note: These notices proide important tips, guidance, or adice. Important: These notices proide information or adice that might help you aoid inconenient or difficult situations. Attention: These notices indicate possible damage to programs, deices, or data. An attention notice appears before the instruction or situation in which damage can occur. Related information and publications You can find additional information and publications related to the IBM Storage Integration Serer on the following information sources. IBM Storage Host Software Solutions Information Center (publib.boulder.ibm.com/infocenter/strhosts/ic) IBM Flex System Information Center (publib.boulder.ibm.com/infocenter/ flexsys/information) IBM Storwize V3500 Information Center (publib.boulder.ibm.com/infocenter/ storwize/3500_ic) IBM Storwize V3700 Information Center (publib.boulder.ibm.com/infocenter/ storwize/3700_ic) IBM Storwize V5000 Information Center (publib.boulder.ibm.com/infocenter/ storwize/5000_ic) IBM Storwize V7000 Information Center (publib.boulder.ibm.com/infocenter/ storwize/ic) IBM Storwize V7000 Unified Information Center (publib.boulder.ibm.com/ infocenter/storwize/unified_ic) IBM System Storage SAN Volume Controller Information Center (publib.boulder.ibm.com/infocenter/sc/ic) IBM System Storage DS8000 Information Center (publib.boulder.ibm.com/ infocenter/dsichelp/ds8000ic) IBM XIV Storage System Information Center (publib.boulder.ibm.com/ infocenter/ibmxi/r2) Copyright IBM Corp ix

10 VMware Documentation (mware.com/support/pubs) VMware Product Support (mware.com/support) VMware Knowledge Base (kb.mware.com) Getting information, help, and serice Ordering publications Sending your comments If you need help, serice, technical assistance, or want more information about IBM products, you can find arious sources to assist you. You can iew the following websites to get information about IBM products and serices and to find the latest technical information and support. IBM website (ibm.com ) IBM Support Portal website ( IBM Directory of Worldwide Contacts website ( The IBM Publications Center is a worldwide central repository for IBM product publications and marketing material. The IBM Publications Center website ( offers customized search functions to help you find the publications that you need. Some publications are aailable for you to iew or download at no charge. You can also order publications. The publications center displays prices in your local currency. Your feedback is important in helping to proide the most accurate and highest quality information. Procedure To submit any comments about this guide or any other IBM Storage Host Software documentation: Go to the online feedback form ( topic/com.ibm.help.strghosts.doc/icfeedback.htm). You can use this form to enter and submit comments. You can send your comments by to starpubs@us.ibm.com. Be sure to include the following information: Exact publication title and ersion Publication form number (for example: GC ) 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 nonexclusie right to use or distribute the information in any way it beliees appropriate without incurring any obligation to you. x IBM Storage Integration Serer

11 Chapter 1. Introduction The IBM Storage Integration Serer is a centralized serer system that consolidates a range of IBM storage proisioning, automation, and monitoring solutions through a unified serer platform. The IBM Storage Integration Serer proides a single serer back-end location and enables centralized management of IBM storage resources for the use of Independent Software Vendor (ISV) platforms and frameworks, which currently include VMware Center Serer, VMware Sphere Web Client, and VMware APIs for Storage Awareness (VASA). Through its user credential, storage system, and storage pool management options, the IBM Storage Integration Serer facilitates the integration of IBM storage system resources with the supported ISV platforms and frameworks, while proiding the foundation for integration with future IBM systems and ISV solutions. The IBM Storage Integration Serer can be managed through a standard web browser and a graphical user interface (GUI), or through terminal and a command-line interface (CLI). Included solution components The following solution components are included in the IBM Storage Integration Serer software package: IBM Storage Proider for VMware VASA IBM Storage Enhancements for VMware Sphere Web Client IBM Storage Proider for VMware VASA The IBM Storage Proider for VMware VASA improes the ability to monitor and automate storage-related operations on VMware platforms. From its IBM Storage Integration Serer host, the IBM Storage Proider for VMware VASA proides a standard interface for any connected VMware Center Serer using VMware APIs for Storage Awareness (VASA), deliering information about IBM storage topology, capabilities and state, as well as storage eents and alerts to Center Serer in real time. IBM Storage Enhancements for VMware Sphere Web Client The IBM Storage Enhancements for VMware Sphere Web Client integrate into the VMware Sphere Web Client platform and enable VMware administrators to independently and centrally manage their storage resources on IBM storage systems. Depending on the IBM storage system in use, VMware administrators can self-proision olumes (LUNs) in selected storage pools that were predefined by the storage administrators. The olumes are mapped to ESX hosts, clusters, or datacenters as logical dries that can be used for storing VMware datastores (irtual machine data containers). As opposed to the IBM Storage Management Console for VMware Center, which is indiidually installed on each Center serer, the IBM Storage Enhancements for Copyright IBM Corp

12 Concept diagram Sphere Web Client are installed only on the Sphere Web Client Serer, allowing multiple Center serers to utilize IBM storage resources. In addition, storage pool attachment and detachment operations are performed on the IBM Storage Integration Serer side, rather than on the Sphere Client side. The IBM Storage Enhancements for VMware Sphere Web Client are proided in a software package that is installed separately on the VMware Sphere Web Client Serer, and then communicates with the IBM Storage Integration Serer. The following concept diagram illustrates how IBM storage systems are accessed and utilized from the VMware enironment through the IBM Storage Integration Serer. The storage administrator uses the IBM Storage Integration Serer to control which IBM storage systems (arrays) and what storage pools should be aailable for use in the VMware enironment, and control which specific Center serers can utilize the IBM storage resources. This control, as well as other administratie options, are referred to in the diagram as Integration Serer operation and management. On the VMware Sphere Web Client side, administrators can create, map, and fully control storage olumes on the aailable storage systems and storage pools (defined by the storage administrator). In parallel, the IBM Storage Integration Serer allows registered VMware Center serers to connect to it and utilize its VASA functions, which can be monitored on the Sphere Client station. Figure 1. Integration of IBM storage systems with a VMware enironment 2 IBM Storage Integration Serer

13 Note: The IBM Storage Integration Serer can use only predefined storage pools. New storage pools cannot be created from the Integration Serer or from VMware Sphere Web Client, and must be created through the dedicated storage system management tools. Compatibility and requirements For the complete and up-to-date information about the compatibility and requirements of the IBM Storage Integration Serer, refer to the latest release notes. You can find the latest release notes on the IBM Storage Host Software Solutions Information Center (publib.boulder.ibm.com/infocenter/strhosts/ic) or on the IBM Fix Central ( Note: Refer to the releant VMware documentation for information about how to install the compatible ersions of Sphere Web Client Serer. You should also refer to the latest installation and configuration instructions for ESXi and Center serers. Required Sphere priileges To operate the IBM Storage Integration Serer functions that relate to the IBM Storage Enhancements for VMware Sphere Web Client, you must hae the minimum required priileges defined in your Sphere user role. Use the Role Manager extension in Sphere Web Client to define the required priileges for your user role as detailed in the following table. Table 1. Required Sphere priileges Task Adding a Center serer to the IBM Storage Integration Serer (see GUI Adding a Center serer on page 38) Storage proisioning (olume creation and management) from Sphere Web Client (see Chapter 5, Using the IBM Storage Enhancements for VMware Sphere Web Client, on page 49) Required Sphere user priilege Extension In this category, select Register extension, Unregister extension, and Update extension. Global In this category, select Log eent and Cancel task. Tasks In this category, select Create task and Update task. Sessions In this category, select Impersonate user. Host In this category, select Configuration > Storage partition configuration. Chapter 1. Introduction 3

14 Figure 2. VMware Sphere Web Client Create Role dialog box For more detailed information about how to set the Sphere Web Client priilege types, refer to the VMware Sphere 5.1 Documentation Center (pubs.mware.com/sphere-51/index.jsp ). Download site The IBM Storage Integration Serer is aailable as a free software solution. You can download the latest ersion at any time from the IBM Fix Central (ibm.com/support/fixcentral). 4 IBM Storage Integration Serer

15 Chapter 2. Installation After downloading the IBM Storage Integration Serer software package, you can begin the installation as described in the following sections. Extracting and installing the Integration Serer software package Installing the IBM Storage Enhancements for VMware Sphere Web Client on page 6 Extracting and installing the Integration Serer software package You can install the IBM Storage Integration Serer software on a compatible ersion of Red Hat Enterprise Linux (RHEL). For more information, refer to the release notes. Procedure Perform the following procedure to install the IBM Storage Integration Serer: 1. Copy the installation package file to a local folder on the Linux host that will be used as the IBM Storage Integration Serer. 2. Extract the installation package file ('* ' represents for the build number) : # tar xf ibm_storage_integration_serer *.tar.gz The following RPM files are extracted: nginx el6.ngx.x86_64.rpm postgresql pgdg.rhel6.x86_64.rpm postgresql92-contrib pgdg.rhel6.x86_64.rpm postgresql92-libs pgdg.rhel6.x86_64.rpm postgresql92-serer pgdg.rhel6.x86_64.rpm uuid el6.x86_64.rpm ibm_storage_integration_serer *.rpm product RPM ibm_storage_integration_serer_jaa_runtime_extension *.rpm Required if DS8000 is used; should be installed last. 3. Go to the extracted directory and then use the rpm -i *.* command to run and install all the complementary RPM files and product RPM file. Important: If you choose to install each package separately without using the *.* option, do not install the ibm_storage_integration_serer *.rpm file before all the complementary RPM files hae been installed, except the one for DS8000. If DS8000 is to be used, install ibm_storage_integration_serer_jaa_runtime_extension *.rpm last. Issue the serice ibm_storage_integration_serer stop start restart command to manage the Red Hat serice. The IBM Storage Proider serice starts automatically after the installation, and a new Linux user named isis is created so that you can use it for management operations. Copyright IBM Corp

16 Installing the IBM Storage Enhancements for VMware Sphere Web Client The software package of IBM Storage Enhancements for VMware Sphere Web Client is installed separately on the Sphere Web Client Serer. About this task This separate Windows-based installation is required in addition to the Linux-based installation of the IBM Storage Integration Serer (see Extracting and installing the Integration Serer software package on page 5). Run this installation on the Sphere Web Client Serer to which all Sphere Web Client stations connect. The compatible ersion of VMware Sphere Web Client Serer must already be installed on the Windows Serer host. Procedure 1. Run the installation package file: VMware_Sphere_Web_Client *-x64.exe 2. From the appearing language selection box, select the language that you want to use in the installation wizard, and then click OK. Figure 3. Installation language selection box Note: The language selection affects only the text that is displayed on the installation wizard, including the language used in the IBM license agreement. It does not affect the graphic user interface of the IBM Storage Enhancements for VMware Sphere Web Client, which are aailable in English only. After a short preparation, the installation wizard of the IBM Storage Enhancements for VMware Sphere Web Client starts. 6 IBM Storage Integration Serer

17 Figure 4. IBM Storage Enhancements for VMware Sphere Web Client installation wizard 3. Click Next. The License Agreement panel is displayed. 4. Read the IBM License Agreement and then select I accept the terms in the license agreement. 5. Click Next. The Customer Information panel is displayed. Chapter 2. Installation 7

18 Figure 5. Customer Information panel 6. Enter your name and your organization name, and then click Next. The 'Ready to Install the Program' panel is displayed. 7. Click Install to begin the installation. Note: During the installation, the IBM Storage Enhancements files are copied to folders in the directory where VMware Sphere Web Client Serer is installed. 8. After the files are installed, the Post-Installation Requirement panel is displayed, notifying you that you must restart the Sphere Web Client serice (Windows serice). Click Next and then click Finish. Important: After the installation, stop the Sphere Web Client serice (Windows serice) and then start it again to make the IBM Storage Enhancements functional. 8 IBM Storage Integration Serer

19 Figure 6. VMware Sphere Web Client on the Windows serices list Chapter 2. Installation 9

20 Uninstallation You can uninstall the IBM Storage Integration Serer software packages in two separate uninstallation procedures. Attention: To aoid loss of user accounts, credentials, storage array configurations, storage pool attachments, and Center serer associations always back up the IBM Storage Integration Serer configuration before any uninstallation. For more information, see CLI Backing up or restoring an Integration Serer configuration on page 24. Uninstalling the software on the IBM Storage Integration Serer side causes the following features to cease functioning: All CLI and GUI management options on the IBM Storage Integration Serer side. IBM Storage Enhancements on the Sphere Web Client side. VASA-related operations on the Center serer side. Howeer, existing olumes are not affected and continue to function and be manageable from the standard storage system management tools. Uninstalling only the IBM Storage Enhancements for VMware Sphere Web Client on the Sphere Web Client Serer side does not affect any existing olume associations with datastores, nor does it affect the VASA-related operations on the IBM Storage Integration Serer side. It only disables the ability to manage olumes from Sphere Web Client. The following sections describe how to uninstall each indiidual software package. Uninstalling the IBM Storage Enhancements for VMware Sphere Web Client on page 11 Uninstalling the Integration Serer software Uninstalling the Integration Serer software If you want to completely remoe the IBM Storage Integration Serer software from the Linux host upon which it is installed, follow the steps in the following procedure. 10 IBM Storage Integration Serer Before you begin To aoid loss of user accounts, credentials, storage array configurations, storage pool attachments, and Center serer associations always back up the IBM Storage Integration Serer configuration before any uninstallation. For more information, see CLI Backing up or restoring an Integration Serer configuration on page 24. Before remoing the IBM Storage Integration Serer: Uninstall the IBM Storage Enhancements for VMware Sphere Web Client (and restart the Web Client serice). Remoe the Center serer definitions by using the IBM Storage Integration Serer User Interface. Unregister any VASA proiders that are registered to this IBM Storage Integration Serer (From the Sphere client).

21 Procedure To uninstall the Integration Serer software from the Linux host: 1. Log on to the Linux command prompt enironment as a root user. 2. Stop the Integration Serer serice, as explained in Checking and controlling the Integration Serer serice on page Run the standard Linux uninstallation command for each installed package (as detailed in Extracting and installing the Integration Serer software package on page 5). Uninstalling the IBM Storage Enhancements for VMware Sphere Web Client If you want to remoe the IBM Storage Enhancements for VMware Sphere Web Client, perform the following procedure. Before you begin If there are IBM storage olumes that are currently in use by VMware datastores, it is recommended that these olumes remain monitored by the storage administrator on the IBM storage system side. All olume management functions will be disabled on the Sphere Web Client side until the IBM Storage Enhancements are reinstalled. Procedure 1. Stop the VMware Sphere Web Client Serer serice (Windows serice; see the last step in Installing the IBM Storage Enhancements for VMware Sphere Web Client on page 6). 2. From the Windows Control Panel, go to Programs > Programs and Features > Change or Remoe Programs, select IBM Storage Enhancements for VMware Sphere Client on the list of installed programs, and then click Remoe. Chapter 2. Installation 11

22 Figure 7. 'Add or Remoe Programs' dialog box The uninstallation wizard guides you through the remaining uninstallation steps. 3. Resume the VMware Sphere Web Client Serer serice. 12 IBM Storage Integration Serer

23 Chapter 3. Integration Serer operation and management This chapter describes the initial operation tasks, as well as the full range of management options that are aailable on the IBM Storage Integration Serer. Required and optional initial tasks Managing the Integration Serer from the command-line interface (CLI) on page 15 Managing the Integration Serer from the graphical user interface (GUI) on page 25 Required and optional initial tasks After the IBM Storage Integration Serer is installed, different tasks are required before the serer can become fully operational. Refer to the following tables for information about the required and optional and management tasks. Note: Unless specified otherwise in the 'Interface' column, you can perform tasks from 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 if necessary (a Linux root user action), and then switch to the 'isis' user. CLI CLI Switching to 'ISIS' user mode on page Log in to the GUI and then change the password of the initial admin user. 3. Add the storage array (storage system) access credentials GUI GUI Logging in on page 26 GUI Changing the password of an Integration Serer user on page 34 CLI or GUI 4. Add the storage arrays to be used CLI or GUI 5. Set the VASA access credentials ("VASA Secret") to allow connection of Center serers that require VASA functions. Note: Not applicable to DS8000 systems. 6. Add Center serers for which you want to utilize the IBM Storage Enhancements for VMware Sphere Web Client. 7. For DS8000 systems only: specify the ESX host details. CLI or GUI CLI or GUI CLI Adding or remoing storage array credentials on page 17 GUI Entering the storage array credentials on page 27 CLI Adding or remoing storage arrays on page 18 GUI Adding a storage array on page 28 CLI Setting the VASA Secret credentials on page 20 GUI Setting the VASA Secret credentials on page 36 CLI Managing Center serers and storage pools for Sphere Web Client on page 21 GUI Adding a Center serer on page 38 CLI CLI Managing Center serers and storage pools for Sphere Web Client on page 21 Copyright IBM Corp

24 Table 2. Required tasks in sequential order (continued) Step Required task Interface Refer to 8. Attach storage pools to any specific Center serer that was added. CLI or GUI CLI Managing Center serers and storage pools for Sphere Web Client on page 21 GUI Attaching a storage pool to a Center serer on page 41 Table 3. Optional tasks Optional task Interface Refer to Manage the Integration Serer users CLI or CLI Adding and managing Integration Serer GUI users on page 16 Back up or restore an Integration Serer configuration, including the data of all existing user accounts, credentials, storage arrays, and storage pools. GUI Managing Integration Serer users on page 32 CLI CLI Backing up or restoring an Integration Serer configuration on page 24 Configuring LDAP user authentication The IBM Storage Integration Serer can authenticate users using Lightweight Directory Access Protocol (LDAP) serices. When LDAP authentication is configured, any login attempt is authenticated both against the local database of Integration Serer users, and against the LDAP serer. Note: LDAP is not used when Center serers connect to the IBM Storage Integration Serer in order to use VASA serices (see Registering the Integration Serer as a storage proider in Center Serer on page 45). Use the ldap.ini configuration file (located in../opt/ibm/ ibm_storage_integration_serer/conf.d/) to configure LDAP user connectiity to IBM Storage Integration Serer. For example: # Change to True in order to work with ldap enable_ldap=false serer_uri=ldap://serername.domainname:389 user_search_dn=ou=users,dc=dcname,dc=com # next is the user search key (uid, preferredid, etc.) user_search_key=uid group_search_dn=dc=dcname,dc=com # supported classes: GroupOfNames, NestedGroupOfNames, GroupOfUniqueNames # NestedGroupOfUniqueNames, ActieDirectoryGroup, NestedActieDirectoryGroup group_object_class=groupofuniquenames # comment out authentication_group_dn if eery LDAP authenticated user is allowed authentication_group_dn=cn=authenticating-group,dc=dcname,dc=com The following table summarizes the possible LDAP authentication parameters. 14 IBM Storage Integration Serer

25 Table 4. LDAP configuration parameters Parameter enable_ldap Indication True or False. When True and enabled, the login attempt is authenticated against the LDAP serer. serer_uri user_search_dn user_search_key group_search_dn group_object_class authentication_group_dn LDAP serer URL The DN (Distinguished Name) to be used for user search. The search tag for getting a unique RDN (Relatie Distinguished Name) The DN to be used for group search. The group type that should match the group search. A DN that results in a unique group. Note: user_search_key and user_search_dn return unique results. For example: user_search_key=uid user_search_dn=ou=users,dc=dcname,dc=com In this case, if the user name is "John", the resulting DN for matching the user oer LDAP would be: uid=john,ou=users,dc=dcname,dc=com If authentication_group_dn is set, only users that belong to that group are authenticated on IBM Storage Integration Serer. You can comment it out to disable group authentication. Managing the Integration Serer from the command-line interface (CLI) You can access and control the Integration Serer by using its command-line interface (CLI) functions locally from the Linux command prompt enironment, or from a remote terminal connection. The following sections describe all the CLI configuration and management functions: CLI Switching to 'ISIS' user mode CLI Adding and managing Integration Serer users on page 16 CLI Adding or remoing storage array credentials on page 17 CLI Adding or remoing storage arrays on page 18 CLI Setting the VASA Secret credentials on page 20 CLI Managing Center serers and storage pools for Sphere Web Client on page 21 CLI Backing up or restoring an Integration Serer configuration on page 24 CLI Switching to 'ISIS' user mode To start configuring the IBM Storage Integration Serer, you must be logged in as the isis user in the Linux command prompt enironment. Chapter 3. Integration Serer operation and management 15

26 About this task isis is a user account that is automatically created after the installation, allowing you to carry out the Integration Serer CLI-based configuration and management operations. If needed, you can set the password for accessing the isis user account externally (for example, from a remote computer oer SSH), as described in the following procedure. Procedure To set a password for the isis user: 1. Log in to the Linux command prompt enironment as a root user. 2. Enter passwd isis and then enter the password for the user account: [root]# passwd isis Changing 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 Serer users All user accounts that can be used to access the IBM Storage Integration Serer must be indiidually defined. You can either define (add) a single Integration Serer user account, or define multiple user accounts to be used separately. Use the isis_users CLI command to add, delete, or display user accounts, and also to change the password of any specific account. Use the required argument after the command, as specified in the following table. Note: All CLI command arguments are case-sensitie. The same operations are aailable from the GUI as well, as explained in GUI Managing Integration Serer users on page IBM Storage Integration Serer

27 Table 5. Arguments for isis_users Argument add -n <username> -p <password> or: add --user_name <username> --user_password <password> Use after isis_users to: Add the username and password of the user that may access the IBM Storage Integration Serer. You can add more than one user. For example: isis_users add -n johnc -p ******** change_password -n <username> -p <new password> or: change_password --user_name <username> --user_password <password> Change the password of a user account that was already added. The password that you type for the specified username is set as the new password. For example: isis_users change_password -n johnc -p ********** delete -n <username> or: delete --user_name <username> Delete a user account from the serer. For example: isis_users delete -n johnc list Display the names of currently defined user accounts. For example: isis_users list john_c zikal_c lihit_c -h or --help Display help information that is releant to isis_users. You can also display help for the add_user, change_password, or delete_user argument if it is typed on the command line as well. CLI Adding or remoing storage array credentials This section explains how to set the credentials that will be used to connect to the IBM storage system, or systems, that your VMware platforms use for storage proisioning. Important: The same credentials (the same username and password) must already be predefined on all the IBM storage arrays that you intend to use. The IBM Storage Integration Serer cannot use more than a single array management account. For more information about how to define a user account on the IBM storage systems, refer to the releant storage system management tools documentation. Setting the storage credentials on the IBM Storage Integration Serer allows you to add the IBM storage arrays on the next step. Chapter 3. Integration Serer operation and management 17

28 Use the isis_storage_credentials CLI command to set (add), remoe, or display the current storage array access credentials that the Integration Serer uses in order to access all the IBM storage arrays. Use the required argument after the command, as specified in the following table. Note: All CLI command arguments are case-sensitie. The same operations are aailable from the GUI as well, as explained in GUI Entering the storage array credentials on page 27. Table 6. Arguments for isis_storage_credentials Argument set -u <array username> -p <array password> or: set --user <array username> --password <array password> Use after isis_storage_credentials to: Set the username and password for accessing all the releant IBM storage systems. For example: isis_storage_credentials set -u johnxi -p *********** remoe Delete the existing storage array user account definition from the serer. For example: isis_storage_credentials remoe list Attention: If you already added storage systems to the serer, deleting the user account disconnects all these storage systems. Display the username of the existing storage array user account definition. For example: isis_storage_credentials list johnxi -h or --help Display help information that is releant to isis_storage_credentials. You can also display help for the set argument if it is typed on the command line as well. CLI Adding or remoing storage arrays All IBM storage systems that proide storage resources to your VMware platforms must be defined as storage arrays on the IBM Storage Integration Serer. Use the isis_storage_array CLI command to add, remoe, or list these IBM storage systems (referred to as storage arrays). Use the required argument after the command, as specified in the following table. 18 IBM Storage Integration Serer

29 Important: IBM storage arrays can be added only after the storage credentials are set, as explained in CLI Adding or remoing storage array credentials on page 17. If you want to remoe existing storage arrays: A remoed storage array, along with its storage pools and olumes, can no longer be managed by the included solution components (see Included solution components on page 1). If the remoed storage array contains working storage pools and olumes, the information of these storage pools and olumes is no longer displayed in Sphere Web Client. Howeer, Sphere data access and serice leel for these storage pools and olumes is not affected. In addition, the remoed array and its storage pools and olumes can be managed from the standard IBM storage system management tools. After the remoal, you can add the storage array back again to fully restore its management. Note: All CLI command arguments are case-sensitie. The same operations are aailable from the GUI as well, as explained in GUI Managing storage arrays on page 26. Table 7. Arguments for isis_storage_array Argument add -i <management IP address> -t <array type> or add --mgmt_ip <management IP address> --type <array type> Use after isis_storage_array to: Add a storage array (IBM storage system) specified by an IP address or DNS, and the type of the array. For the -t (array type) argument, specify xi for XIV, sc for SAN Volume Controller, Storwize, and Flex System, or ds8k for DS8000. For example: isis_storage_array add -i t xi Optional: you can define an alias name for the added XIV system, by adding -a <alias name> or --alias <alias name> to the command. For example: isis_storage_array add -i t xi -a mystorage1 Note: If you choose not to define an alias, the alias name that is already defined (if one was defined) on the IBM storage system side is automatically assigned as the alias name. remoe -a <system alias name> or remoe --alias <system alias name> Remoe a storage array specified by its alias name (alias that was gien by you or was automatically assigned). For example: isis_storage_array remoe -a mystorage1 Chapter 3. Integration Serer operation and management 19

30 Table 7. Arguments for isis_storage_array (continued) Argument list Use after isis_storage_array to: List the names of all the IBM storage arrays that are currently added (and were not remoed). For example: isis_storage_array list mystorage1 mystorage2 -h or --help Display help information that is releant to isis_storage_array. You can also display help for the add or remoe argument if it is typed on the command line as well. CLI Setting the VASA Secret credentials The VASA Secret credentials comprise a user name and a password that VMware Center serers can use to connect to the IBM Storage Integration Serer and employ VMware APIs for Storage Awareness (VASA) functions. Use the asa_admin CLI command to set or display the VASA Secret credentials. Center serers can then use these credentials to connect to the Integration Serer and utilize VASA functions, as explained in Registering the Integration Serer as a storage proider in Center Serer on page 45. Use the required argument after the command, as specified in the following table. Note: Only one set of a username and a password can be used for the VASA Secret, which applies to all Center serers that require VASA functions. All CLI command arguments are case-sensitie. The same operations are aailable from the GUI as well, as explained in GUI Setting the VASA Secret credentials on page 36. Table 8. Arguments for asa_admin Argument set_secret -n <username> -<password> or: set_secret --user_name <username> --user_password <password> Use after asa_admin to: Set the username and password for that the VASA Secret should comprise. For example: asa_admin set_secret -n johnasa -p ******** The secret key for the VASA Proider has been set successfully. list_secret Display the username of the currently defined VASA Secret. For example: asa_admin list_secret Secret key username for the VASA Proider: johnasa 20 IBM Storage Integration Serer

31 Table 8. Arguments for asa_admin (continued) Argument -h or --help Use after asa_admin to: Display help information that is releant to asa_admin. You can also display help for the set_secret argument if it is typed on the command line as well. CLI Managing Center serers and storage pools for Sphere Web Client Before you can use the IBM Storage Enhancements for VMware Sphere Web Client on the web client side, you need to define on the IBM Storage Integration Serer side the Center serers for which you want to proide storage resources. Then, you can the attach storage pools that you want to make aailable to each Center serer. The storage pools that you attach on the Integration Serer side become isible on the Sphere Web Client side, and can be used for olume creation by using the IBM Storage Enhancements on the Sphere Web Client side. Use the wc_center and wc_poolcli commands to add, modify, remoe, or list Center serers, and also to attach or detach storage pools that were predefined on the IBM storage systems you hae added. The wc_host command is required for ESXi host definition on DS8000 arrays. Use the required argument after each command, as specified in the following tables. Important: Storage pools can be attached to Center serers only after the releant storage arrays hae been added, as explained in CLI Adding or remoing storage arrays on page 18. If you want to detach storage pools or remoe Center serers: A detached storage pool, along with its olumes, can no longer be managed by the included solution components (see Included solution components on page 1). If the detached storage pool contains working olumes, the information of these olumes is no longer displayed in Sphere Web Client. Howeer, Sphere data access and serice leel for these olumes is not affected. In addition, the remoed storage pool (and its olumes) can still be managed from the standard IBM storage system management tools. After the detachment, you can attach the storage pool again to fully restore its management. A remoed Center serer can no longer be managed through the Integration Serer, but it continues to be managed from the Sphere enironment. You can add it again to restore management through the Integration Serer. Note: All CLI command arguments are case-sensitie. Apart from DS8000 host definition (see Table 11 on page 23), the same operations are aailable from the GUI as well, as explained in GUI Managing serers and storage pools for Sphere Web Client on page 37. Chapter 3. Integration Serer operation and management 21

32 Table 9. Arguments for wc_center Argument add -n <username> -i <IP or hostname> -p <password> or add --user_name <username> --host_name <hostname> --user_password <password> Use after wc_center to: Add a Center serer connection by specifying: The username for accessing the Center serer. The hostname or IP address of the Center serer. The user password. For example: wc_center add -n john1 -i mycenter -p ******** modify -n <username> -i <IP or hostname> -p <password> -g <Center GUID> or modify --user_name <username> --host_name <IP or hostname> --user_password <password> --guid <Center GUID> Note: After a Center connection is added, you can attach storage pools to that Center serer using the wc_pool command (see Table 10 on page 23). Modify a Center serer connection by specifying: The username for accessing the Center serer. The hostname or IP address of the Center serer. The user password. The GUID of the Center serer. You can use the list command argument (see below) to obtain the GUID. For example: wc_center modify -n john1 -i mycenter -p ******** -g 11EC2020 list List all Center serer connections and GUID of each Center serer. For example: wc_center list Center host Center user Center GUID Last updated john11 11EC OCT-2013 remoe -g <Center GUID> or remoe --guid <Center GUID> Remoe a Center serer connection by specifying its GUID. For example: wc_center remoe -g 11EC2020 -h or --help Display help information that is releant to wc_center. You can also display help for the add, modify, or remoe argument if it is typed on the command line as well. 22 IBM Storage Integration Serer

33 Table 10. Arguments for wc_pool Argument attach -g <Center GUID> -a <array alias> -pn <storage pool name> or attach --guid <Center GUID> --array_alias <array alias> --pool_name <storage pool name> Use after wc_pool to: Attach a storage pool to a Center serer by specifying: The GUID of the Center serer. You can use the wc_center list command (see Table 9 on page 22) to obtain the GUID. The defined alias name of a storage array. The storage pool name. For example: wc_pool attach -g 11EC2020 -a myarray -pn mypool detach -g <Center GUID> -a <array alias> -pn <storage pool name> or detach --guid <Center GUID> --array_alias <array alias> --pool_name <storage pool name> Detach a storage pool from a Center serer by specifying: The GUID of the Center serer. You can use the wc_center list command (see Table 9 on page 22) to obtain the GUID. The defined alias name of a storage array. The storage pool name. For example: wc_pool detach -g 11EC2020 -a myarray -pn mypool list -g <Center GUID> or list --guid <Center GUID> List the storage pools that are attached to a Center serer, by specifying the Center GUID. For example: wc_pool list -g 11EC2020 -h or --help Display help information that is releant to wc_pool. You can also display help for the attach or detach argument if it is typed on the command line as well. Table 11. Arguments for wc_host Argument list -g <Center GUID> -e <ESX host name> or list --guid <Center GUID> --esx_host <ESX host name> Use after wc_host to: List all known ESXi host ports and their storage host names by specifying: The GUID of the Center serer. You can use the wc_center list command (see Table 9 on page 22) to obtain the GUID. The name of the ESX host. For example: wc_host list -g 11EC2020 -e mymhost Chapter 3. Integration Serer operation and management 23

34 Table 11. Arguments for wc_host (continued) Argument define -a <DS8000 array alias> -n <storage host 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 <port type> Use after wc_host to: Define an ESXi host on a DS8000 storage array (not applicable to other storage arrays) by specifying: The defined alias name of the DS8000 storage array. The name of the ESXi host to be defined on the DS8000 side. The name of the ESX host. The connectiity type (between the ESXi host and the DS8000 array): fc for Fibre Channel (FC) or iscsi for iscsi. If not specified, the default is FC. For example: wc_host define -a myds8k -n hostname -e myhost -pt iscsi -h or --help Display help information that is releant to wc_host. You can also display help for the define argument if it is typed on the command line as well. CLI Backing up or restoring an Integration Serer configuration At any point, you can back up the current IBM Storage Integration Serer configuration and sae it to a file, or load a preiously saed configuration to restore a configuration. The configuration includes storage credentials, storage arrays, Center credentials, and storage pools attachment. Use the isis_configuration CLI command to sae the existing configuration, or load a saed configuration that will replace the existing one. Use the required argument after the command, as specified in the following table. Note: All CLI command arguments are case-sensitie. The backup and restore operations are not aailable on the Integration Serer GUI. Attention: Before using the restore option, the IBM VASA Proider serice must be stopped as explained in Checking and controlling the Integration Serer serice on page 69. Start the serice again after the configuration has been loaded. The restore should be used only with a freshly installed IBM Storage Integration Serer that has not yet been configured. 24 IBM Storage Integration Serer

35 Table 12. Arguments for isis_configuration Argument backup -f <file name> -k <16 characters> or: backup --file <file name> --key <16 characters> Use after isis_configuration to: Sae the current IBM Storage Proider configuration to the specified file using an AES-128 encryption key that comprises 16 characters. For example: isis_configuration backup -f confbackup -k abcdefghijklmnop restore -f <file name> -k <16 characters> or: restore --file <file name> --key <16 characters> Important: You will need to proide this key in any restore operation (see below). Load a configuration from a specified file by proiding the file name and the encryption key that was used in the creation of the file. Attention: For example: See the notes aboe this table. isis_configuration restore -f confgbackup -k abcdefghijklmnop import_asa115 -f <file name> or: import_asa115 --file <file name> Import an existing Integration Serer configuration that was made with IBM Storage Proider for VMware VASA ersion (applicable only to XIV systems). For example: isis_configuration import_asa115 -f 115backup -h or --help Attention: The storage capability definitions made in ersion cannot be imported because storage capabilities are automatically created and assigned on the Integration Serer. Display help information that is releant to isis_configuration. You can also display help for the backup or restore argument if it is typed on the command line as well. Managing the Integration Serer from the graphical user interface (GUI) You can log in to the Integration Serer through a web browser and use the configuration and management options that are aailable from the web-based graphical user interface (GUI). The following sections describe all the GUI configuration and management functions: GUI Logging in on page 26 GUI Managing storage arrays on page 26 GUI Managing Integration Serer users on page 32 GUI Managing and monitoring VASA access on page 36 GUI Managing serers and storage pools for Sphere Web Client on page 37 Chapter 3. Integration Serer operation and management 25

36 GUI Logging in To log in to the Integration Serer from a browser, you need to enter the web address (URL) of the Linux host upon which the IBM Storage Integration Serer is installed. The secure IP connection to the Integration Serer is established though port number Accordingly, the web address should be entered in the browser address bar in the following format: Serer IP address]:8443 After entering the address, the IBM Storage Integration Serer login page is loaded and you can log in by entering your Integration Serer username and password. Figure 8. IBM Storage Integration Serer login box in a standard web browser Important: After the instillation, the initial username is admin and the initial password is adminadmin. To aoid unauthorized access to the Integration Serer, it is strongly recommended to change this password as soon as possible, or create a new user account and then delete the admin account (see GUI Managing Integration Serer users on page 32). If the Integration Serer serice is stopped on the Linux host (see Checking and controlling the Integration Serer serice on page 69), it is not possible to log in or perform any GUI operation. GUI Managing storage arrays All IBM storage systems that proide storage resources to your VMware platforms must be defined as storage arrays on the IBM Storage Integration Serer. To access the storage array management options, click Arrays on the top GUI panel. You can then iew, add, and manage the storage arrays as explained in the 26 IBM Storage Integration Serer

37 following sections. Figure 9. Clicking Arrays Note: The same operations are aailable from the CLI as well, as explained CLI Adding or remoing storage array credentials on page 17 and in CLI Adding or remoing storage arrays on page 18. GUI Entering the storage array credentials GUI Adding a storage array on page 28 GUI Modifying the IP address or hostname of a storage array on page 30 GUI Remoing a storage array on page 31 GUI Entering the storage array credentials The storage array credentials are used to connect to the IBM storage system or systems, which your VMware platforms use for storage proisioning. About this task From the Integration Serer GUI you can set or change the current storage array access credentials that are used for accessing all the IBM storage arrays. Important: The same credentials (the same username and password) must already be predefined on all the IBM storage arrays that you intend to use. The IBM Storage Integration Serer cannot use more than a single array management account. For more information about how to define a user account on the IBM storage systems, refer to the releant storage system management tools documentation. Setting the storage credentials on the IBM Storage Integration Serer allows you to add the IBM storage arrays on the next step. Note: The same operations are aailable from the CLI as well, as explained in CLI Adding or remoing storage array credentials on page 17. Procedure 1. 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 Change Credentials button. Chapter 3. Integration Serer operation and management 27

38 Figure 10. Current storage array username (for all storage arrays) 2. Click Change Credentials. The Change Credentials dialog box appears. 3. Enter the username and password of the storage admin user that was defined on the IBM storage arrays, and then click Apply. Figure 11. Change Credentials dialog box What to do next You can now start adding storage arrays. The IBM Storage Integration Serer will use the credentials that you hae set in order to connect to the storage arrays that you add. GUI Adding a storage array After the storage array credentials are set, you can start adding storage arrays to the Integration Serer. About this task The storage arrays that you add can be used by the solution components that are included in the IBM Storage Integration Serer package (see Included solution 28 IBM Storage Integration Serer

39 components on page 1). You can add each indiidual storage array separately, as described in the following procedure. Procedure 1. 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. Figure 12. Add Array dialog box 3. Select the storage array type (XIV, SAN Volume Controller, Storwize, or DS8000) and then enter its management IP address or hostname. 4. Click Add. If the credentials are correct (as preiously defined; see GUI Entering the storage array credentials on page 27) and the IP connection is established, the storage array is added to the Storage Arrays table. Figure 13. List of added storage arrays You can click the row of a storage array to iew its details on the Storage Array Details pane. Chapter 3. Integration Serer operation and management 29

40 Figure 14. Storage array details GUI Modifying the IP address or hostname of a storage array At any time, you can modify the IP address or hostname of an added storage array. About this task If the management IP address or hostname of a storage array changes, you can update this change on the Integration Serer without haing to remoe or re-add the storage array. Procedure 1. Click Arrays on the top GUI panel. The Storage Arrays table is displayed and lists the currently added storage arrays. 2. Click the row of the storage array that you want to update, and then click the Modify Array icon. The Modify Array dialog box appears. Figure 15. Modify Array icon 30 IBM Storage Integration Serer

41 Figure 16. Modify Array dialog box 3. Enter the new management IP address or hostname of the storage array, and then click Modify. GUI Remoing a storage array If a storage array is no longer needed, you can remoe and disconnect it from the Integration Serer. About this task A remoed storage array, along with its storage pools and olumes, can no longer be managed by the included solution components (see Included solution components on page 1). If the remoed storage array contains working storage pools and olumes, the information of these storage pools and olumes is no longer displayed in Sphere Web Client. Howeer, Sphere data access and serice leel for these storage pools and olumes is not affected. In addition, the remoed array and its storage pools and olumes can be managed from the standard IBM storage system management tools. After the remoal, you can add the storage array back again to fully restore its management. Procedure 1. Click Arrays on the top GUI panel. The Storage Arrays table is displayed and lists the currently added storage arrays. 2. Click the row of the storage array that you want to update, and then click the Remoe Array icon. Chapter 3. Integration Serer operation and management 31

42 Figure 17. Remoe Array icon A confirmation message appears. Figure 18. Remoe Array confirmation message 3. Click Yes to remoe the array, or No to cancel the operation. GUI Managing Integration Serer users At any time, you can add new Integration Serer user accounts, change user account passwords, or delete existing user accounts. To access the storage array management options, click Users on the top GUI panel. You can then iew, add, and manage the Integration Serer users as explained in the following sections. Figure 19. Clicking Users Note: The same operations are aailable from the CLI as well, as explained in CLI Adding and managing Integration Serer users on page 16. GUI Adding an Integration Serer user on page 33 GUI Changing the password of an Integration Serer user on page 34 GUI Deleting an Integration Serer user on page IBM Storage Integration Serer

43 GUI Adding an Integration Serer user You can add a user account for any authorized user that requires access to the IBM Storage Integration Serer. About this task Each added user is able to indiidually log into the IBM Storage Integration Serer and perform GUI or CLI management actions. Note: All Integration Serer users hae the same permission leel on the Integration Serer, and can undo any setting or action made by another user. Procedure 1. 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 20. Add User dialog box 3. Enter the username and password for the account that you want to create, and then click Add. The username of the created account is added to the Users table. Chapter 3. Integration Serer operation and management 33

44 Figure 21. List of added Integration Serer users (user names) GUI Changing the password of an Integration Serer user At any time, you can change the password of an Integration Serer user account. About this task You can modify a user account only by changing its password. Periodic password change is recommended on a regular basis. Note: Integration Serer user names cannot be changed. Instead, you can delete a user account (see GUI Deleting an Integration Serer user on page 35) and then create a new one (see GUI Adding an Integration Serer user on page 33). Procedure 1. Click Users on the top GUI panel. The Users table is displayed and lists the currently added users. 2. Click the row of the storage array that you want to update, and then click the Modify User icon. The Change Password dialog box is displayed. Figure 22. Modify User icon 34 IBM Storage Integration Serer

45 Figure 23. Change Password dialog box 3. Enter the current password of the user account, and then the new password twice as required. Then, click Change. GUI Deleting an Integration Serer user When necessary, you can delete any Integration Serer user account. About this task After you delete an Integration Serer user account from the GUI, the specific user can no longer log in to the integration serer from either the GUI or the CLI. Although the user deletion is a non-reersible operation, you can redefine the same username as explained in GUI Adding an Integration Serer user on page 33. Note: Deleting an Integration Serer user does not affect the storage credentials or VASA Secret credentials, which both remain defined. Procedure 1. Click Users on the top GUI panel. The Users table is displayed and lists the currently added users. 2. Click the row of the user account that you want to update, and then click the Delete User icon. Figure 24. Delete User icon A confirmation message appears. Chapter 3. Integration Serer operation and management 35

46 3. Click Yes to delete the user, or No to cancel the operation. GUI Managing and monitoring VASA access You can control and monitor the utilization of the IBM Storage Proider for VMware VASA, which is part of the IBM Storage Integration Serer solution Note: This functionality is not applicable to DS8000 systems, which are not supported by the IBM Storage Proider for VMware VASA. To access the VASA management options, click VASA on the top GUI panel. You can then display a list (read-only) of all Center serers that are currently registered and are utilizing VASA functions. Figure 25. Clicking VASA Before any Center serer can be registered and start utilizing the IBM Storage Proider, you must first set the 'VASA Secret' credentials, as explained in the following section. GUI Setting the VASA Secret credentials The 'VASA Secret' credentials comprise a username and a password that is set separately from the Integration Serer user accounts, and separately from the storage array credentials. About this task VMware Center serers can use the VASA Secret credentials to connect to the IBM Storage Integration Serer and utilize VASA functions, as explained in Registering the Integration Serer as a storage proider in Center Serer on page 45. From the Integration Serer GUI you can set, change, or display these VASA Secret credentials at any time. Note: Only one set of a username and a password can be used for the VASA Secret, which applies to all Center serers that require VASA functions and connect to the IBM Storage Integration Serer. The same operations are aailable from the CLI as well, as explained in CLI Setting the VASA Secret credentials on page 20. Procedure 1. Click VASA on the top GUI panel. The Registered Center Serers table is displayed, and the currently defined VASA Secret username is displayed next to the Change Secret button. At the initial use after the installation, the installation-default user name is displayed. 36 IBM Storage Integration Serer

47 Figure 26. Current VASA Secret username 2. Click Change Secret. The Change Secret dialog box is displayed. Figure 27. Change Secret dialog box 3. Enter the required username and password of the VASA Secret that you want to set, and then click Update. GUI Managing serers and storage pools for Sphere Web Client Before you can use the IBM Storage Enhancements for VMware Sphere Web Client on the web client side, you need to define on the IBM Storage Integration Serer side the Center serers for which want to proide storage resources. Then, you can the attach storage pools that you want to make aailable to each Center serer. The storage pools that you attach on the Integration Serer side become isible on the Sphere Web Client side, and can be used for olume creation by using the IBM Storage Enhancements on the web client side. To access these options, click Sphere Web Client on the top GUI panel. You can then manage serers and storage pools as explained in the following sections. Chapter 3. Integration Serer operation and management 37

48 Figure 28. Clicking Sphere Web Client Note: The same operations can be performed from the CLI as well, as explained in CLI Managing Center serers and storage pools for Sphere Web Client on page 21. GUI Adding a Center serer GUI Updating the credentials of a Center serer on page 39 GUI Remoing a Center serer on page 40 GUI Attaching a storage pool to a Center serer on page 41 GUI Detaching a storage pool from a Center serer on page 43 GUI Adding a Center serer Add the VMware Center serers for which want to proide storage resources through the IBM Storage Integration Serer. About this task You need to connect to and add the Center serers for which you can later attach storage pools that would be isible and accessible on the Sphere Web Client side. You can add a single Center serer at a time, as described in the following procedure. Procedure 1. Click Sphere Web Client on the top GUI panel. The Center Serers table is displayed and lists the currently added Center serers. 2. Click Add. The Add Center Serer dialog box is displayed. 38 IBM Storage Integration Serer

49 Figure 29. Add Center Serer dialog box 3. Enter the IP address or hostname of the Center serer, as well as the username and password for logging into that Center serer. Then, click Sae. If the proided IP address and credentials are accepted by the Center serer, it is added to the list of Center serers. Figure 30. List of Center serers GUI Updating the credentials of a Center serer At any time, you can update the credentials that are used to access a Center serer. About this task Wheneer the credentials on the Center serer side change, you can update these credentials on the Integration Serer side to allow continued management of storage resources on the Sphere Web Client side. Procedure 1. Click Sphere Web Client on the top GUI panel. The Center Serers table is displayed and lists the currently added Center serers. Chapter 3. Integration Serer operation and management 39

50 2. Click the row of the Center serer for which you want to update the credentials, and then click Edit. The update Center Serer Credentials dialog box is displayed. Figure 31. Update Center Serer Credentials dialog box 3. Enter the new username and password for accessing the Center serer. Then, click Sae. GUI Remoing a Center serer When a Center serer is no longer needed, you can disconnect it from the Integration Serer by remoing it from the list of Center serers. About this task A remoed Center serer, along the storage pools attached to it, can no longer be managed by the included solution components (see Included solution components on page 1). If the remoed Center serer is attached to working storage pools, the information of these storage pools, as well as the olumes on these pools is no longer displayed in Sphere Web Client. Howeer, Sphere data access and serice leel for these storage pools and olumes is not affected. After the remoal, you can add the Center serer again to fully restore its management. Procedure 1. Click Sphere Web Client on the top GUI panel. The Center Serers table is displayed and lists the currently added Center serers. 2. Click the row of the Center serer that you want to remoe, and then click Remoe. A confirmation message is displayed. 40 IBM Storage Integration Serer

51 Figure 32. Remoe Center Serer confirmation message 3. Click Remoe to remoe the Center serer, or Cancel to cancel the operation. GUI Attaching a storage pool to a Center serer You must attach to the Center serer any predefined storage pool (predefined by the storage administrator) that you want to use for olume management operations on the Sphere Web Client side. Before you begin Storage pools can be attached only with Admin, Storage Admin, System Admin, or Security Admin storage credentials (see GUI Entering the storage array credentials on page 27). When working with DS8000, storage pools can be attached only with Admin or Logical Operator storage credentials. Any other type of storage credentials (read-only, application admin) cannot perform storage pool attachment. If your credentials are not sufficient, contact your storage administrator for assistance. About this task The storage pool attachment is done on the Integration Serer side, proiding more control to storage administrators as opposed to the VMware administrators on the Sphere enironment side. After the attachment, the storage pools become isible and manageable on the Sphere Web Client side (by using the IBM Storage Enhancements). You can select and attach one or more storage pools in one attachment operation, as described in the following procedure. Procedure 1. Click Sphere Web Client on the top GUI panel. The Center Serers table is displayed and lists the Center serers to which you can attach storage pools. 2. Click the row of the Center serer to which you want to attach one or more storage pools, and then click Attach. The Attach Storage Pools dialog box is Chapter 3. Integration Serer operation and management 41

52 displayed. Figure 33. Attach Storage Pools dialog box 3. From the drop-down list, select the storage array from which you want to choose storage pools. The aailable predefined storage pools that reside on the selected storage array are immediately displayed. 4. Select the storage pools that you want to attach to the Center serer (specified in the dialog box), and then click Attach. The list of attached storage pools per Center serer is updated accordingly. Figure 34. List of attached storage pools per Center serer 42 IBM Storage Integration Serer

53 GUI Detaching a storage pool from a Center serer When required, you can detach a storage pool from the Center serer to which it is attached. About this task A detached storage pool, along with its olumes, can no longer be managed by the included solution components (see Included solution components on page 1). If the detached storage pool contains working olumes, the information of these olumes is no longer displayed in Sphere Web Client. Howeer, Sphere data access and serice leel for these olumes is not affected. In addition, the remoed storage pool (including its olumes) can be managed from the standard IBM storage system management tools. After the detachment, you can attach the storage pool again to fully restore its management. Procedure 1. Click Sphere Web Client on the top GUI panel. The Center Serers table is displayed on the left and lists the Center serers to which you can attach storage pools. 2. Click the row of the Center serer from which you want to detach one or more storage pools. The list of storage pools that are currently attached to the Center serer is displayed on the right. 3. Click the row of the storage pool that you want to detach, and then click Detach. A confirmation message appears. Figure 35. Detach Storage Pool confirmation message 4. Click Detach to delete the user, or Cancel to cancel the operation. Chapter 3. Integration Serer operation and management 43

54 44 IBM Storage Integration Serer

55 Chapter 4. Using the IBM Storage Proider for VMware VASA This chapter focuses on how to use the IBM Storage Proider for VMware VASA after the required configuration on the IBM Storage Integration Serer has been completed. Note: IBM System Storage DS8000 systems are not supported by the IBM Storage Proider for VMware VASA. After the IBM storage systems hae been added to the Integration Serer, and after the VASA access credentials were set (see Required and optional initial tasks on page 13), you can start using the IBM Storage Proider for VMware VASA by registering the Integration Serer in the releant Center serer or serers. Checking and controlling the Integration Serer serice on page 69 Registering the Integration Serer as a storage proider in Center Serer Registering the Integration Serer as a storage proider in Center Serer To use the IBM Storage Proider for VMware VASA solution component, you need to register the IBM Storage Integration Serer as a storage proider in VMware Center Serer. Before you begin When the IBM Storage Proider for VMware VASA and the IBM Tioli Storage Productiity Center (TPC) storage proider are registered on the same VMware Center serer, while the same storage array is configured for both, Center uses IBM Tioli Storage Productiity Center proider as the only source of information for that array's storage iews on Sphere Client. In such a case, determine whether the IBM Tioli Storage Productiity Center capabilities are sufficient for replacing the IBM Storage Proider for VMware VASA. If the IBM Storage Proider for VMware VASA is still needed, IBM TPC 5.2 (or later) proides a method of excluding storage arrays from a specific storage proider, allowing you to remoe the array association with the IBM TPC proider. About this task The following procedure describes how to register the Integration Serer on a single Center serer by using Sphere Client. You can, howeer, register the Integration Serer on multiple Center serers by using Sphere Web Client, as explained in Setting the Integration Serer web address for Center serers on page 49. Procedure To register the IBM Storage Integration Serer in VMware Center Serer, complete the following steps. 1. In Sphere Client, go to Administration > Storage Proiders. Copyright IBM Corp

56 2. Click Add. Figure 36. Sphere Client Storage Proiders list The Add Vendor Proider dialog box is displayed. 3. Enter the name, URL, and pre-configured username and password (VASA Secret) for accessing the IBM Storage Integration Serer (the VASA Secret is predefined as explained in GUI Setting the VASA Secret credentials on page 36). The URL should be entered in the ip:port format, specifying the releant IP address and port number of the IBM Storage Integration Serer: Serer IP address]:8443/serices/asa1 Note: In this example, "Integration Serer IP address" stands for the IP address or domain namespace of the IBM Storage Integration Serer. 46 IBM Storage Integration Serer

57 Figure 37. Add Vendor Proider dialog box 4. Click OK. A security alert dialog box is displayed. Figure 38. Center certificate thumbprint dialog box 5. Click Yes to accept the certificate. The IBM Storage Integration Serer is added to Center Serer. Note: The certificate proides improed security by adding serer authentication. Chapter 4. Using the IBM Storage Proider for VMware VASA 47

58 Figure 39. Supported Vendor list displaying the IBM Storage Integration Serer 48 IBM Storage Integration Serer

59 Chapter 5. Using the IBM Storage Enhancements for VMware Sphere Web Client With supported IBM storage systems that are managed by the IBM Storage Integration Serer, the separately installed IBM Storage Enhancements enable the following management features on Sphere Web Client side: Full control oer storage olumes, including olume creation, resizing, renaming, migration to a different storage pool, mapping, unmapping, multipath policy enforcement, and deletion. Easy and integrated allocation of olumes to VMware datastores, used by irtual machines that run on ESXi hosts, clusters, or datacenters. Note: To enable these features, the IBM Storage Enhancements must be installed on the VMware Sphere Web Client Serer, as described in Installing the IBM Storage Enhancements for VMware Sphere Web Client on page 6. See the following sections for more information: Setting the Integration Serer web address for Center serers Populating Center serer information to the Integration Serer on page 50 Viewing the IBM storage resource information on page 52 Creating and mapping a new storage olume (LUN) on page 56 Extending a olume on page 61 Renaming a olume on page 62 Setting multipath policy enforcement for a olume on page 63 Moing a olume to another storage pool on page 64 Unmapping a olume from one or more hosts on page 65 Deleting an unused olume on page 66 Setting the Integration Serer web address for Center serers To allow interoperation between the Center serers that are in use and the IBM Storage Integration Serer, you must specify the Integration Serer web address (URL) for each Center serer. About this task Specifying the Integration Serer web address for a Center serer establishes a connection between that Center seer and that specific Integration Serer host, and actiates the IBM storage proisioning and control features for that Center serer. You can specify the Integration Serer web address for one or more Center serers, as described in the following procedure. Important: In addition to this procedure, the releant Center serer must be added on the IBM Storage Integration Serer, as explained in GUI Adding a Center serer on page 38. Copyright IBM Corp

60 Procedure 1. In Sphere Web Client, naigate to the releant Center serer and then click the Manage tab. 2. Click Settings > IBM Serer > Edit, and then enter the Integration Serer web address in the displayed dialog box. Important: The secure IP-based connection to Integration Serer must be made through port 8443, which must be specified with a colon (":8334") at end the web address (URL) in the following format: Serer IP address]:8443 Figure 40. Edit IBM Serer Address dialog box 3. Click OK. If the connection is established, the Connectiity indicator shows a green icon with the status 'Connected'. Figure 41. IBM Storage Integration Serer connection details per Center serer Populating Center serer information to the Integration Serer At any time and wheneer needed, you can manually update the Center serer information on the IBM Storage Integration Serer side. About this task By default, the Center serer information is automatically updated on the IBM Storage Integration Serer eery 30 minutes (as defined in wc_config.ini, see 50 IBM Storage Integration Serer

61 Checking and modifying the configuration files on page 71). If you want to run the update earlier without haing to wait for the next automatic update, perform the following procedure. Important: Before you can use this option, the releant Center serer must already be: Added on the IBM Storage Integration Serer, as explained in GUI Adding a Center serer on page 38. Pointed to the IBM Storage Integration Serer web address, as explained in Setting the Integration Serer web address for Center serers on page 49. Procedure 1. In Sphere Web Client, focus on the releant Center serer. 2. From the Actions menu, select All IBM Storage Actions > Populate Center Information A confirmation message appears. Figure 42. Populate Center Information option Figure 43. Populate Center confirmation message 3. Click Yes to send the specified Center information to the IBM Storage Integration Serer. Chapter 5. Using the IBM Storage Enhancements for VMware Sphere Web Client 51

62 Viewing the IBM storage resource information After the IBM Storage Enhancements for VMware Sphere Client are properly installed, the IBM Storage category is shown under the standard Sphere Web Client categories for each Center serer, as shown in the following figure. Figure 44. IBM Storage category in Sphere Web Client For each Center serer, the IBM Storage category shows how many IBM storage arrays are aailable for that Center serer. The number and type of aailable IBM storage arrays is determined on the IBM Storage Integration Serer side, as explained in GUI Managing storage arrays on page 26 and GUI Managing serers and storage pools for Sphere Web Client on page 37. You can click and open the IBM Storage category, and then click an IBM storage array to iew the currently aailable storage olumes on that particular storage array, and also to check which VMware entities are currently using storage resources on that storage array. 52 IBM Storage Integration Serer

63 Figure 45. IBM Storage information per storage array Figure 46. Currently aailable storage pools per storage array In addition, IBM Storage information and functions are aailable per Center serer in the different category iews on the Related Objects tab, as shown in the following figures. Chapter 5. Using the IBM Storage Enhancements for VMware Sphere Web Client 53

64 Figure 47. IBM Storage information per Center serer Figure 48. IBM Storage information per datacenter Figure 49. IBM Storage information per datastore 54 IBM Storage Integration Serer

65 Figure 50. IBM Storage information per all ESXi hosts of a Center serer Figure 51. IBM Storage information per all VM templates of a Center serer Figure 52. IBM Storage information per all Apps of a Center serer Chapter 5. Using the IBM Storage Enhancements for VMware Sphere Web Client 55

66 And so on, click the other information categories that are aailable in Sphere to iew the releant IBM Storage information in these categories as well. Creating and mapping a new storage olume (LUN) The IBM Storage Enhancements for VMware Sphere Web Client allow you to create new olumes (LUNs) directly from the Sphere Web Client interface. These olumes can be used as storage deices in the Sphere enironment. About this task Any created olume is mapped to either ESXi hosts, clusters, or datacenters, so that the irtual machines on these hosts, clusters, or datacenters would be able to sae datastore information on that olume. In addition to single olume creation, you can create multiple olumes simultaneously. If you choose this option, the created olumes are appended with differently numbered suffixes that are automatically generated by the system in consecutie order. Important: You can create olumes only on storage pools that hae been attached to the releant Center serer on the IBM Storage Integration Serer side. For more information, see GUI Managing serers and storage pools for Sphere Web Client on page 37 The ESXi hosts and clusters to which you map the created olumes must be predefined on the storage system side. For more information, refer to your IBM storage system documentation. Procedure 1. In Sphere Web Client, naigate to the releant Center serer and then to the specific IBM storage array on which you want to create the new olume. The IBM storage array and the releant storage pools should already be associated with the Center serer (see Viewing the IBM storage resource information on page 52). 2. Click Actions > Create New Volume. Alternatiely, from the Top Leel Objects iew on the releant Center serer, click Actions > All IBM Storage Actions > Create New Volume. Figure 53. IBM storage array iew Clicking Create New Volume 56 IBM Storage Integration Serer

67 Figure 54. Top Leel Objects iew Clicking Create New Volume You can also right-click the storage array or click the dedicated icon in order to inoke the Create New Volume option. Figure 55. Right-clicking the storage array Chapter 5. Using the IBM Storage Enhancements for VMware Sphere Web Client 57

68 Figure 56. Clicking the Create New Volume icon The Create New Volume dialog box is displayed. Figure 57. Create New Volume wizard (XIV example) 3. In the Volume Size text box, enter the size for the new olume. Alternatiely, place the mouse pointer on the graphic image of the storage pool, and then click and slide the space marker rightward to set the new olume size. The numerical alue in Volume Size is automatically updated accordingly. 58 IBM Storage Integration Serer

69 Figure 58. Setting the olume size with the graphic space marker Note: It is recommended to define the size of an XIV olume in a multiple of 17 GB. The Volume Size box appears with a yellow rectangle around it if the size alue is not a multiple of 17 GB. The XIV Recommended Volume Size (GB) information is displayed below. The largest aailable 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 the new olume. 5. If you want to create multiple olumes simultaneously (otherwise, go to step 6 on page 60): In the Number of Volumes text box, enter the number of olumes that you want to create simultaneously. The text box next to the Volume Name entry displays olumename_{1} in this example. The {1} represents the suffix alue. You can enter the olume name and moe the suffix alue to the middle or kept at the end of the olume name (see Figure 59 on page 60). Chapter 5. Using the IBM Storage Enhancements for VMware Sphere Web Client 59

70 Figure 59. Creating multiple olumes 6. If you want to change the automatically selected storage pool (otherwise, skip to next step), select a different storage pool from the Storage Array/Pool list box. 7. Only if you are creating the olume on an IBM Flex System, DS8000, SAN Volume Controller, or Storwize storage system (otherwise, skip to the next step): Select the I/O Group to which the olume should belong. Not applicable to DS8000. Optional: Select Enable Thin Proisioning if you want the olume to be defined as thin proisioned and not as a fixed hard disk allocation. When this option is selected, the aailable capacity and total capacity are displayed based on the requested olume size. For DS8000, the oer-proision ratio information is also displayed. Optional: Select Enable Data Compression if you use data compression on SAN Volume Controller or Storwize V7000, on Storwize V3500 or Storwize V3700, or on Storwize V7000 Unified. Not applicable to DS8000. Optional: Select Enable Vdisk Mirroring if you want to use irtual disk mirroring for the olume or olumes that you create. Not applicable to DS8000. If selected, a list of storage pools appears and you must select the secondary storage pool on which you want the mirrored olume or olumes to be created. Notes: XIV olumes are not associated with I/O groups and are thin-proisioned if created in a thin-proisioned storage pool. Compressed olumes SAN Volume Controller or Storwize storage systems (if supported by the microcode) are always thin-proisioned. 60 IBM Storage Integration Serer

71 8. From Host Mapping, select the host(s), cluster(s), or datacenter(s) to which you want to map the new olume. You can click Custom to specify a custom mapping in the Adanced Host Mapping dialog box. If you select a datacenter, its member clusters and hosts are automatically selected. Figure 60. Adanced Host Mapping dialog box Note: All ESXi hosts are aailable to be selected. If there is a connectiity problem, the help text indicates that. Hosts that are not connected to the array are marked. Important: You must map the olume to at least one ESXi host, cluster, or datacenter in order to enable Sphere management of the created olume. Extending a olume 9. Reiew the details of the new olume that is about to be created, and then click OK to confirm its creation as detailed. If enough free space is aailable on the releant storage pool, you can extend the size of an existing olume. Procedure Perform the following procedure to extend the size of a olume. 1. In Sphere Web Client, naigate to the row of the olume that you want to extend. 2. Right-click the olume row and choose Extend or use the Actions menu to select Extend. Chapter 5. Using the IBM Storage Enhancements for VMware Sphere Web Client 61

72 Figure 61. Clicking Extend on the pop-up menu The Extend Volume dialog box is displayed. 3. In the Volume Size text box, enter the new size for the olume. Alternatiely, place the mouse pointer on the graphic image of the storage pool, and then click and slide the space marker rightward to set the new olume size. The numerical alue in Volume Size is automatically updated accordingly. 4. Click Extend. Important: Extending the size of a olume does not automatically increase the datastore capacity. Renaming a olume Wheneer required, you can rename any existing olume by performing the following procedure. About this task Renaming a olume is a logical action that does not hae any physical effect on the olume or its logical connections. Renaming a olume also changes its displayed name in the Sphere enironment. Procedure 1. In Sphere Web Client, naigate to and then click the row of the olume that you want to rename, and then choose the Rename option by right-clicking the olume row or using the Actions menu. 62 IBM Storage Integration Serer

73 Figure 62. Rename olume option The Rename Volume dialog box is displayed. Figure 63. Rename Volume dialog box 2. Enter the new name that you want to assign to the olume, and then click OK. Setting multipath policy enforcement for a olume This section describes how to set multipath policy enforcement for a single olume. About this task By default, the Round Robin multipath policy is enforced on olumes. You can disable or change this enforcement for a specific olume if needed. Procedure 1. In Sphere Web Client, naigate to and then click the row of the olume for which you want to change the enforcement, and then choose the Set Multipath Policy Enforcement option by right-clicking the olume row or using the Actions menu. Chapter 5. Using the IBM Storage Enhancements for VMware Sphere Web Client 63

74 Figure 64. Set Multipath Policy Enforcement option The Change Multipath Policy Enforcement dialog box is displayed. Figure 65. Change Multipath Policy Enforcement dialog box 2. Select the required option and then click OK. Important: After the policy is set, it is enforced by oerriding any existing policy for this olume. Moing a olume to another storage pool You can moe a olume to a different storage pool, for example, when the current storage pool has run out of space. 64 IBM Storage Integration Serer

75 About this task Attention: On XIV storage systems, moing a olume to another storage pool is a logical action. No data is actually moed on physical disks as a result. On DS8000, Storwize, and SAN Volume Controller storage systems, moing a olume to another storage pool is a physical action that causes data to moe to a different physical disk. This may cause some performance oerhead. On DS8000, Storwize, and SAN Volume Controller storage systems, moing a olume to another storage pool is an asynchronous action. The capacity of the source and target storage pools may not be updated after the task is completed in Center. When using mirrored olumes on SAN Volume Controller systems, only the primary copy olumes can be moed. In addition, these olumes can be moed only to the primary storage pool copy (not to the secondary copy). Procedure 1. In Sphere Web Client, naigate to and then click the row of the olume that you want to moe, and then choose the Moe option by right-clicking the olume row or using the Actions menu. Figure 66. Moe olume option The Moe Volume dialog box is displayed. 2. Select the storage pool to which you want to moe the olume, and then click OK. Unmapping a olume from one or more hosts When olumes or ESXi hosts are no longer needed, or if new ones are to replace the current ones, you can unmap olumes from the hosts. Chapter 5. Using the IBM Storage Enhancements for VMware Sphere Web Client 65

76 About this task Important: A olume (LUN) must remain mapped to at least one host. Otherwise, you cannot iew the olume or perform any actions on it from Sphere Web Client. Procedure 1. In Sphere Web Client, naigate to and then click the row of the olume that you want to unmap, and then choose the Unmap option by right-clicking the olume row or using the Actions menu. Figure 67. Unmap olume Deleting an unused olume The Unmap Volume dialog box is displayed. 2. Select the hosts or clusters from which you want to unmap the olume, and then click OK. When a storage olume is unused and no longer required, you can delete it. Before you begin Important: You cannot delete olumes that are currently used by datastores or as a raw mapped LUN. Procedure 1. In Sphere Web Client, naigate to and then click the row of the olume that you want to delete, and then choose the Delete option by right-clicking the olume row or using the Actions menu. 66 IBM Storage Integration Serer

77 Figure 68. Delete olume The Delete Volume confirmation message is displayed. 2. Click OK to confirm the deletion, or Cancel to exit without deleting the olume. Chapter 5. Using the IBM Storage Enhancements for VMware Sphere Web Client 67

78 68 IBM Storage Integration Serer

79 Chapter 6. Troubleshooting This chapter can help you detect and sole problems that you might encounter when using the IBM Storage Integration Serer. Note: For up-to-date information about known issues and possible workarounds, refer to the latest release notes. Checking and controlling the Integration Serer serice At any time, you can check whether the IBM Storage Integration Serer serice runs properly on the Linux host. You can also stop and then start the serice if needed. Procedure 1. Log on to the Linux command prompt enironment as a root user. Important: Only root users can perform serice operations. 2. Enter the following command: serice ibm_storage_integration_serer status. The status of the Celery and Django serices is displayed. [root@isis]# serice ibm_storage_integration_serer status Celery serices are running... Django serice is running... What to do next If you want to stop the IBM Storage Proider serice, use the stop command: [root@isis]# serice ibm_storage_integration_serer stop Stopping Django serice: [ OK ] Stopping celery serices: [ OK ] To start the serice again, use the start command: [root@isis]# serice ibm_storage_integration_serer start Starting celery serices: [ OK ] Starting Django serice: [ OK ] Checking the log files The IBM Storage Integration Serer maintains six log files that record different types of eents. You can find the following log files in the opt/ibm/ ibm_storage_integration_serer/log/ directory: isis.log Records eents regarding the Integration Serer functionality. hsgsr.log Records eents regarding the collection of information from the monitored storage systems. Copyright IBM Corp

80 asa1.log Records eents regarding the communication between the Integration Serer and the connected Center serers that utilize VASA functions. wc.log Records eents regarding the communication between the Integration Serer and the Sphere Web Client Serer on which the IBM Storage Enhancements are installed. celery.log Records eents regarding the Celery serices on the Linux host on which the Integration Serer is installed. isis_django.log Records eents regarding the Django serice on the Linux host on which the Integration Serer is installed. You can retriee and sae the current log files in a compressed TAR archie file by using the Collect Logs option on the Integration Serer GUI. This option allows you to sae different instances of the log files at different times. Figure 69. Integration Serer GUI Collect Logs option Figure 70. Integration Serer GUI Saing the logs in a compressed TAR archie 70 IBM Storage Integration Serer