EMC PowerPath/VE Installation and Administration Guide

Transcription

1 EMC PowerPath/VE Installation and Administration Gide Version 5.9 and Minor Releases for VMware vsphere P/N REV 03

2 Copyright All rights reserved. Pblished in USA. EMC believes the information in this pblication is accrate as of its pblication date. The information is sbject to change withot notice. The information in this pblication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this pblication, and specifically disclaims implied warranties of merchantability or fitness for a particlar prpose. Use, copying, and distribtion of any EMC software described in this pblication reqires an applicable software license. EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other contries. All other trademarks sed herein are the property of their respective owners. For the most p-to-date reglatory docment for yor prodct line, go to EMC Online Spport ( For docmentation on EMC Data Domain prodcts, go to the EMC Data Domain Spport Portal ( EMC Corporation Hopkinton, Massachsetts In North America EMC PowerPath/VE Installation and Administration Gide 5.9 and Minor Releases for VMware vsphere

3 CONTENTS Chapter 1 Installing PowerPath/VE with served licenses 7 Installation components and workflow for served licenses... 8 Obtaining served licenses... 9 Sggested license file locations Migrating to EMC PowerPath Virtal Appliance Migrating physical PPVE ELMS to PowerPath Virtal Appliance with existing served license file...10 Migrating physical PPVE ELMS to PowerPath Virtal Appliance with new served license file...11 Install PPVE ELMS...11 Install PPVE ELMS on Windows hosts Installing PPVE ELMS on Windows sing Interactive Installer Install PPVE ELMS on Windows sing CLI silent installation Upgrade PPVE ELMS on Windows sing Interactive Installer Install PPVE ELMS on Linx hosts Installing PPVE ELMS on Linx sing interactive installation script...14 Installing PPVE ELMS on Linx sing non-interactive installation script Upgrading PPVE ELMS on Linx sing interactive script Upgrading PPVE ELMS on Linx sing non-interactive installation script...15 Using PowerELMS script Installing PowerPath/VE Configre served license configration files on the rpowermt server Setting non-defalt directories...18 Make non-defalt directories persistent across reboots on Linx Making non-defalt directories persistent across reboots on Windows PowerPath/VE served licenses post-installation tasks Chapter 2 Administering served licenses 21 Migrate physical PPVE ELMS to virtal appliance PPVE ELMS Obtaining additional served licenses Using mltiple served license files on Windows PPVE ELMS...23 Verify license server and license stats Verifying license server sing lmtil tility...23 Verifying license server lmtools tility for Windows only Set served license file path Set served license file path sing lmtil tility...24 Setting served license file path sing lmtools tility Rereading served license files Register served license for vsphere host License cont change after re-imaging the vsphere host Unregistering served license from vsphere host Re-installing and configring after converting license types Moving served licenses Chapter 3 Installing PowerPath/VE with nserved licenses 27 EMC PowerPath/VE Installation and Administration Gide 5.9 and Minor Releases for VMware vsphere 3

4 CONTENTS Installation components and workflow for nserved licenses Installing PowerPath/VE Install PowerPath remote CLI Finding ESX niqe system ID Obtaining nserved licenses Sggested nserved license file locations...30 Configring nserved license configration files on the rpowermt server Setting non-defalt directories...31 Make non-defalt directories persistent across reboots on Linx Making non-defalt directories persistent across reboots on Windows PowerPath/VE nserved licenses post-installation and configration tasks...32 Chapter 4 Administering nserved licenses 33 Unregistering nserved licenses...34 Moving nserved licenses Chapter 5 Installing PowerPath/VE 37 Install PowerPath/VE for VMware vsphere Spported PowerPath-VE installation scenarios PowerPath/VE installation prereqisites...38 Installing sing VMware Update Manager...39 Installing sing remote vcli...42 Installing sing remote vcli and offline package locally available on vsphere host...42 Installing sing remote vcli and VIB packages remotely available on http server Install PowerPath/VE sing Ato Deploy Chapter 6 Installing PowerPath/VE remote CLI (rpowermt) 47 Install PowerPath/VE remote CLI (rpowermt)...48 PowerPath/VE rpowermt installation reqirements...48 Pre-reqisites for installing PowerPath/VE remote CLI Installing PowerPath/VE remote CLI (rpowermt) on Linx...49 Installing PowerPath/VE remote CLI (rpowermt) on Windows...49 Chapter 7 Post-PowerPath/VE Installation and Configration 51 Manally registering the vsphere hosts PowerPath/VE post-installation and configration tasks...53 Pre-configration tasks Adding hosts to rpowermt lockbox Changing load-balancing policy Enabling path latency monitoring...55 Verifying PowerPath/VE configration rpowermt server lockbox Creating lockbox Updating host sername and password in the lockbox...56 Defalt lockbox location...57 Change lockbox name and location...57 Disabling lockbox Bypass lockbox EMC PowerPath/VE Installation and Administration Gide 5.9 and Minor Releases for VMware vsphere

5 CONTENTS Creating CIM Ticket Athentication...58 Set rpowermt CST libraries environment variable...58 Chapter 8 Upgrading PowerPath/VE remote CLI (rpowermt) 61 RTOOLS pgrade paths...62 Upgrading PowerPath/VE remote CLI (rpowermt) on Linx Upgrading PowerPath-VE remote CLI (rpowermt) on Windows Chapter 9 Removing PowerPath/VE 65 Removing PowerPath/VE sing vcli...66 Chapter 10 Remove Virtal Appliance 67 Uninstalling the appliance...68 Chapter 11 Removing PowerPath/VE remote CLI (rpowermt) 69 Remove PowerPath/VE rpowermt Removing PowerPath/VE rpowermt from Linx...70 Remove PowerPath/VE rpowermt from Windows Chapter 12 Managing PowerPath/VE 71 Claim rles in PowerPath/VE environment...72 PowerPath/VE assigned claim rles Claim rles and definitions List claim rles...74 Adding claim rles Example: Claim a LUN for NMP with 2 HBAs and Symmetrix array with 2 storage ports...75 Example: Claim a LUN for NMP with 2 HBAs and CLARiiON array with 4 storage ports...77 Reclaiming devices by NMP...79 Renmbering claim rles...80 Configration changes in PowerPath/VE...81 Adding new paths to PowerPath/VE logical device Add new logical devices to a configration...83 Remove paths or logical devices from PowerPath/VE configration Removing HBA Removing logical device Alternate procedre to remove logical device Configring path latency monitoring...85 Manage PowerPath/VE sing rpowermt Workaronds for non-existent powermt commands...85 Chapter 13 Remove PPVE ELMS 87 Remove PPVE ELMS on Windows Removing PPVE ELMS sing interactive ninstallation Removing PPVE ELMS sing Add/Remove Programs Removing PPVE ELMS sing CLI ninstallation...88 Removing PPVE ELMS on Linx EMC PowerPath/VE Installation and Administration Gide 5.9 and Minor Releases for VMware vsphere 5

6 CONTENTS Chapter 14 Trobleshooting PowerPath/VE Installation 91 Served license file errors Resolving PPVE ELMS TCP port conflicts Modifying vendor daemon port nmber...93 Modifying vendor daemon search path rpowermt lockbox errors...93 PowerPath/VE installation error...94 Collecting logs from vcenter server or vsphere client...94 Log file location...95 Stop license server...95 Using lmtil tility to stop the license server Using lmtools tility to stop the licence server...96 Start license server manager Starting license server on Linx host Starting license server manager on Windows hosts Report a problem PPVE ELMS v01 Installer FAQ Appendix A Files Installed and Modified by PowerPath/VE 99 Files installed and modified by the PowerPath/VE installation Appendix B PowerPath/VE Messages 101 Error log messages VM kernel errors PowerPath/VE error messages rpowermt error and warning messages Appendix C PowerPath/VE Overview 115 PowerPath/VE for VMware vsphere platform Native LAM spport for XtremIO Spport for NetApp array PowerPath Mltipathing Plgin Technical differences Components of a PowerPath/VE configration PowerPath/VE mltipathing software Remote PowerPath CLI (rpowermt) server PPVE ELMS PowerPath/VE featres Dynamic path failover Proactive path testing and atomatic path recovery Dynamic mltipath load balancing Storage system types PowerPath/VE and NMP coexistence PowerPath/VE licensing Spported license types Permanent and expiring licenses License files License athorization code Licensing Service Center Served licensing Served license file contents Unserved licensing EMC PowerPath/VE Installation and Administration Gide 5.9 and Minor Releases for VMware vsphere

7 CHAPTER 1 Installing PowerPath/VE with served licenses This chapter covers the following topics: Installation components and workflow for served licenses... 8 Obtaining served licenses... 9 Migrating to EMC PowerPath Virtal Appliance Install PPVE ELMS...11 Using PowerELMS script Installing PowerPath/VE Configre served license configration files on the rpowermt server PowerPath/VE served licenses post-installation tasks Installing PowerPath/VE with served licenses 7

8 Installing PowerPath/VE with served licenses Installation components and workflow for served licenses Installation components for served licenses Refer the following to identify the reqired components for a PowerPath/VE environment that ses served licenses. Reqired PowerPath/VE components: Component: RTOOLS Virtal Appliance that contains PPVE ELMS and RTOOLS packages pre-installed Software type: Windows Linx SLES virtal machine Host compatibility: Windows Linx vsphere Software location: PowerPath/VE and RTOOLS RHEL and Windows software contained in the PowerPath/VE software distribtion on EMC Online Spport Reqired VMware components: Component: VMware vsphere CLI (vcli) Software type: Linx, Windows VMware vcenter Update Manager (VUM) VUM server vsphere Client VUM plgin vcenter Server Software type: Windows, all physical host, or VM Ato Deploy vcenter Server Ato Deploy application Software type: Windows Software location: Software located on the VMware website Reqired electronics served license components Component: Electronic License Management server (ELMS) Software type: Physical host, virtal machine PPVE Electronic License Management server (PPVE ELMS) 8 EMC PowerPath/VE Installation and Administration Gide 5.9 and Minor Releases for VMware vsphere

9 Installing PowerPath/VE with served licenses Virtal Appliance that contains PPVE ELMS and RTOOLS packages preinstalled Software type: Linx, Windows Host compatibility: Windows Linx Software location: Software contained in a separate download on EMC Online Spport. PPVE ELMS is a compressed file (.zip) Installation workflow for served licenses The following table lists the steps in configring a served licensing environment for PowerPath/VE: Table 1 PowerPath/VE served licensing workflow Task Action on Windows Action on RHEL Action on SLES Virtal Appliance Obtaining served licenses on page 9 Obtaining served licenses on page 9 Obtaining served licenses on page 9 2. Save served license files. See Sggested license file locations on page 10 Save served license files. See Sggested license file locations on page 10 Save served license files. See Sggested license file locations on page Install PPVE ELMS on page 11 Install PPVE ELMS on page 11 Using PowerELMS script on page Installing PowerPath/VE on page 16 Installing PowerPath/VE on page 16 Deploy EMC PowerPath Virtal Appliance. Refer EMC PowerPath Virtal Appliance 1.2 Installation and Configration Gide on instrctions to deploy the Virtal Appliance. Using PowerELMS script on page Install PowerPath remote CLI on page Configre served license configration files on the rpowermt server on page 16 Install PowerPath remote CLI on page 29 Configre served license configration files on the rpowermt server on page 16 Installing PowerPath/VE on page 16 Configre served license configration files on the rpowermt server on page 16 Obtaining served licenses Before yo begin Ensre that yo know yor LAC. Ensre that yo know the IP address of the PPVE ELMS. On a Linx host, se the ifconfig -a command to determine the IP address. On a Windows host, se the ipconfig command to determine the IP address. Ensre that yo know the host name of the PPVE ELMS. Procedre: On a Linx host, se the hostname or name -a command to determine the host name. Obtaining served licenses 9

10 Installing PowerPath/VE with served licenses On a Windows host, se the hostname command. Alternatively: 1. Navigate to the Windows Control Panel. 2. Under System, locate the compter's fll compter name. License files are not inclded with the PowerPath/VE software package. When yo prchase PowerPath/VE, EMC sends yo an that contains the License Athorization Code (LAC). Use the LAC that contains yor PowerPath/VE entitlements to obtain the served license file at the Licensing Service Center on EMC Online Spport. After receiving yor served license file, save the license server distribtion file for yor platform to an installation directory on the license server. Procedre Sggested license file locations 1. Login to sing yor sername and password. 2. Click Activate Licenses and follow the on screen instrctions. Use the following locations as installation directories on PPVE ELMS. Linx For Linx hosts, copy the license files to the /etc/emc/licenses directory. Windows For Windows hosts, copy the license files to the c:\program Files\emc \License Server directory. Migrating to EMC PowerPath Virtal Appliance This section provides information on migrating PPVE ELMS to EMC PowerPath Virtal Appliance to with existing served license and with new served license file. Refer the following EMC PowerPath Virtal Appliance 1.2 docments for detailed instrctions on deploying and sing the Virtal Appliance: PowerPath Virtal Appliance version 1.2 Release Notes PowerPath Virtal Appliance version 1.2 Installation and Configration Gide EMC PowerPath Virtal Appliance version 1.2 Administration Gide Migrating physical PPVE ELMS to PowerPath Virtal Appliance with existing served license file Use this procedre if yo crrently have the physical PPVE ELMS version and want to migrate to the Virtal Appliance PPVE ELMS at the same IP address sing the same served license file. Served licenses are tied to the IP address of the PPVE ELMS. Therefore, if yo deploy the Virtal Appliance at the IP address as the PPVE ELMS that yo are replacing, yo can se the existing served license file. Procedre 1. Stop the existing PPVE ELMS. Stop license server on page 95 provides more information. 2. Save the existing served license file to a location that is accessible after stopping the PPVE ELMS in step Deploy the Virtal Appliance at the same IP address as the PPVE ELMS that was removed in step EMC PowerPath/VE Installation and Administration Gide 5.9 and Minor Releases for VMware vsphere

11 Installing PowerPath/VE with served licenses EMC PowerPath 1.2 Installation Configration Gide provides more information. 4. Configre and start the PPVE ELMS. Using PowerELMS script on page 16 provides information on that procedre. After yo finish Note If yo want to migrate the PPVE ELMS to a new IP address, yo mst reqest a new served license file. Migrating physical PPVE ELMS to PowerPath Virtal Appliance with new served license file on page 11 provides more information. Migrating physical PPVE ELMS to PowerPath Virtal Appliance with new served license file Install PPVE ELMS Use this procedre if yo crrently have the physical PPVE ELMS version and want to migrate to the PowerPath Virtal Appliance PPVE ELMS at a different IP address from the existing PPVE ELMS sing the new served license file. Served licenses are tied to the IP address of the PPVE ELMS. Therefore, if yo deploy the Virtal Appliance at a different IP address as the PPVE ELMS that yo are replacing, yo mst move (rehost) the served licenses to the new PPVE ELMS in the Virtal Appliance with the new IP address. Procedre 1. Login to sing yor sername and password. 2. Click Move Licenses and follow the onscreen instrctions. The activation certificate is atomatically sent to the registered ser for this transaction. 3. Deploy the Virtal Appliance with a different IP address as the PPVE ELMS that crrently exists. Refer theemc PowerPath 1.2 Installation Configration Gide for information on deploying the EMC PowerPath Virtal Appliance. 4. Configre and start the PPVE ELMS. Using PowerELMS script on page 16 provides more information. 5. Stop the physical PPVE ELMS. Stop license server on page 95 provides more information. 6. Remove the physical PPVE ELMS. Remove PPVE ELMS on Windows on page 88 and Removing PPVE ELMS on Linx on page 89 provide more information. Before yo begin Use this procedre only if yo are not deploying the virtal appliance. PowerPath/VE for VMware vsphere license is not tied to a prodct version nmber. For PowerPath/VE, the license file indicates 5.4 license. Select a machine to be the PPVE ELMS. The PowerPath/VE 5.9 and Minor Releases for VMware vsphere Release Notes provides information on spported PPVE ELMS operating systems and versions. Have the served license file located and ready to reference dring the PPVE ELMS installation. If yo have a valid PowerPath/VE 5.4 and service packs license for VMware vsphere, the 5.4 version license is valid for 5.9 and 5.9 SP1. Migrating physical PPVE ELMS to PowerPath Virtal Appliance with new served license file 11

12 Installing PowerPath/VE with served licenses On a Linx host, ensre that the /etc/hosts file has an entry like the following for the license server: # Do not remove the following line, or varios programs # reqire network fnctionality will fail. lsca2147 casco.iss.emc.com casco Verify that the machines selected as rpowermt servers have access to the license server throgh the TCP/IP connection. Install PPVE ELMS on Windows hosts This section incldes procedres for: Interactive installation CLI silent installation Upgrade Installing PPVE ELMS on Windows sing Interactive Installer Before yo begin Yo mst have administrative privileges to rn the Interactive Installer. Procedre 1. Navigate to and log in sing yor sername and password. 2. From the EMC Online Spport home page, go to Downloads. In the Find a Prodct type PowerPath/VE for VMware. 3. Download the spported EMC Virtal Appliance package from EMC Online Spport. The PPVE ELMS package is inclded in the PowerPath/VE Appliance bndle ZIP. 4. Unzip the PPVE ELMS package. 5. Unzip the PPVE ELMS for Windows package. For example, EMCPower.ELMS.Windows v01.x86_32.zip 6. Place the PPVE ELMS exectable for Windows in the c:\ drive. 7. Doble-click the PPVE ELMS exectable to rn it. 8. In the DestinationFolder window, choose the location for the PPVE ELMS to be installed. By defalt, PPVE ELMS is installed and configred at c:\program Files\emc \ELMS. 9. In the InstallProgress window, yo are prompted to inpt the absolte path to the license file. Type the absolte path to the served license file. Failre to inpt license file path information reslts in sccessfl PPVE ELMS configration bt not sccessfl start of the PPVE ELMS service. If yo do not enter license file information, re-rn the installer with the Repair option to inpt the license file. After yo finish The InstallComplete page indicates sccess or failre. In case of installation failre, refer Trobleshooting PowerPath/VE Installation on page EMC PowerPath/VE Installation and Administration Gide 5.9 and Minor Releases for VMware vsphere

13 Installing PowerPath/VE with served licenses Install PPVE ELMS on Windows sing CLI silent installation This procedre applies to fresh installation only. Procedre 1. Complete steps 1 to 6 of Installing PPVE ELMS on Windows sing Interactive Installer on page Type the following command: <setp.exe> /s /v"/q /l*v <Path to log file> INSTALLDIR=<path to destination folder> PATHTOFILE=<path to license file>" Where <setp.exe> is the name of the PPVE ELMS package. <path to log file> is the absolte cstomized path where the installation log file is created. INSTALLDIR=<path to destination folder> is the location to install or pdate the PPVE ELMS. By defalt, the package is installed in c:\program files\emc\elms. <path to license file> is the absolte path to the license file. 3. Verify installation. From command prompt, provide the path to the folder where the license server exectables are installed. Type: C:\program files\emc\elms \lmtil.exe lmstat -a -c <path to license_file_list> The otpt indicates whether the license server and vendor daemon are rnning, the total nmber of licenses available on the license server, and the nmber of licenses that have been allocated. Alternatively: a. Navigate to the directory where the license server exectables are installed and click lmtools.exe. a. On the Server Stats tab, click Perform Stats Enqiry. After yo finish In case of installation failre, refer Trobleshooting PowerPath/VE Installation on page 91. Upgrade PPVE ELMS on Windows sing Interactive Installer Before yo begin Yo mst have administrative privileges to rn the Interactive Installer. Procedre 1. Complete steps 1 to 6 of Installing PPVE ELMS on Windows sing Interactive Installer on page In the DestinationFolder window, choose the location where the existing Flexera ELM server for PowerPath/VE is configred. The PPVE ELMS files will be pdated to the same location. The InstallComplete page indicates installation sccess or failre. Install PPVE ELMS on Windows sing CLI silent installation 13

14 Installing PowerPath/VE with served licenses After yo finish Install PPVE ELMS on Linx hosts In case of installation failre, refer Trobleshooting PowerPath/VE Installation on page 91. PPVE ELMS for Linx can be started by root and non-root sers. If the service is started by a root ser then, it can be stopped only by a root ser. PPVE ELMS for Linx fails if a nonroot ser tries to stop the service started by a root ser. This section incldes procedres for: Installation sing interactive script Installation sing non-interactive script with installation parameters Upgrade sing interactive script Upgrade sing non-interactive script Installing PPVE ELMS on Linx sing interactive installation script Procedre 1. Navigate to log in sing yor sername and password. 2. From the EMC Online Spport home page, go to Downloads. In the Find a Prodct type PowerPath/VE for VMware. 3. Download the PowerPath Virtal Appliance 1.2 P02 (New Deployment).zip from EMC Online Spport. The PPVE ELMS package is inclded in the PowerPath/VE Appliance bndle ZIP. 4. Unzip the PPVE ELMS package. 5. Untar the PPVE ELMS package for Linx. For example, type: tar -xzf EMCPower.ELMS.LINUX v01.RHEL.x86_64.tar.gz 6. Rn the elms_install.sh in the ELMS_LINUX folder and follow the onscreen instrctions. 7. When prompted to pgrade, press N and contine the installation. 8. Provide the license file to be sed. The license server service starts after installation sing the license file indicated. The service starts by defalt. 9. Verify installation. Type: /etc/emc/elms/lmtil lmstat -a -c <path to license_file> The otpt indicates whether the license server and vendor daemon are rnning, the total nmber of licenses available on this license server, and how many licenses have been allocated. After yo finish In case of installation failre, refer Trobleshooting PowerPath/VE Installation on page EMC PowerPath/VE Installation and Administration Gide 5.9 and Minor Releases for VMware vsphere

15 Installing PowerPath/VE with served licenses Installing PPVE ELMS on Linx sing non-interactive installation script Procedre 1. Complete steps 1 to 6 of Installing PPVE ELMS on Linx sing interactive installation script on page Provide parameters to the elms_install.sh. Type: elms_install.sh -s Or Type: elms_install.sh -s -c absolte path to the license file" The service starts by defalt. 3. Verify installation. Type: /etc/emc/elms/lmtil lmstat -a -c <path to license_file> The otpt indicates whether the license server and vendor daemon are rnning, the total nmber of licenses available on this license server, and the nmber of licenses that have been allocated. After yo finish In case of installation failre, refer Trobleshooting PowerPath/VE Installation on page 91. Upgrading PPVE ELMS on Linx sing interactive script Use this procedre to pgrade PPVE ELMS on Linx sing an interactive script. Procedre 1. Complete steps 1 to 5 of Installing PPVE ELMS on Linx sing interactive installation script on page Rn the elms_install.sh in the ELMS_LINUX folder and follow the onscreen instrctions. Provide the location of the previos Flexera ELMS software installation and absolte path to the license file when prompted. The service starts by defalt. 3. Verify installation. Type: /etc/emc/elms/lmtil lmstat -a -c <path to license_file> The otpt indicates whether the license server and vendor daemon are rnning, the total nmber of licenses available on this license server, and how many licenses have been allocated. After yo finish In case of installation failre, refer Trobleshooting PowerPath/VE Installation on page 91. Upgrading PPVE ELMS on Linx sing non-interactive installation script Procedre 1. Complete steps 1 to 6 of Installing PPVE ELMS on Linx sing interactive installation script on page Provide the location of the previos installation and the license file as parameters to the elms_install.sh. Type: elms_install.sh -s -d "location of the old installation" -c "absolte path to the license file" Installing PPVE ELMS on Linx sing non-interactive installation script 15

16 Installing PowerPath/VE with served licenses The service starts by defalt. 3. Verify installation. Type: /etc/emc/elms/lmtil lmstat -a -c <path to license_file> The otpt indicates whether the license server and vendor daemon are rnning, the total nmber of licenses available on this license server, and the nmber of licenses that have been allocated. After yo finish Using PowerELMS script In case of installation failre, refer Trobleshooting PowerPath/VE Installation on page 91. The PowerELMS script atomates configration of and starting the PPVE ELMS. This task applies to sing the Linx RHEL PPVE ELMS and the Linx SLES virtal appliance. This task also applies to spporting mltiple served license files on the Linx SLES virtal appliance. Before yo begin Before carrying ot this step, ensre that yo have obtained and saved the served license file. Obtaining served licenses on page 9 and Sggested license file locations on page 10 provide more information. Procedre Installing PowerPath/VE 1. Type: /etc/init.d/powerelms start -l <license search path> For single license, the license search path mst contain the flly qalified path(s) to the license file. For mltiple license, the license search path mst contain the flly qalified path(s) to the directories containing the files. Mltiple search paths shold be separated by colons. For example, if license files exist in /licenses and /etc/licenses, a search path might be /licenses:/etc/licenses to locate any of the license files or / licenses/pplicense.lic:/etc/licenses to specify one specific license file and any others located in /etc/licenses. Install the PowerPath/VE mltipathing software on the ESX hosts in yor PowerPath/VE environment. Install PowerPath/VE for VMware vsphere on page 38 provides installation procedres. Configre served license configration files on the rpowermt server Before yo begin Ensre that yo have generated and obtained a license (.lic) file for the PPVE ELMS at the Licensing Service Center on EMC Online Spport. Obtaining served licenses on page 9 provides information. 16 EMC PowerPath/VE Installation and Administration Gide 5.9 and Minor Releases for VMware vsphere

17 Installing PowerPath/VE with served licenses Ensre that yo have stored the license file with.lic extension in the PPVE ELMS directory. Ensre that the PPVE ELMS is started and rnning. Use the following procedre to create a license configration file that identifies the PPVE ELMS to the rpowermt application. Note Ensre that the rpowermt server and PPVE ELMS are synchronized within 48 hors of one another. If there is a clock skew of more than 48 hors between the rpowermt server and PPVE ELMS, rpowermt register will report license registration errors. Procedre 1. On the rpowermt server, configre a license configration (.lic) file that identifies the license server to the rpowermt application. a. Save the license file downloaded from Licensing Service Center on EMC Online Spport as a text file with the file extension.lic. This is the license configration file. Ensre that the following fields on both files match exactly, if yo modified them on the license file downloaded from Licensing Service Center on EMC Online Spport: SERVER [host] INTERNET=[IP address] VENDOR EMCLM USE_SERVER where host is the name of the license server to be sed IP address is the IP address of the license server is the TCP port nmber (by defalt, 27010). Served license file errors on page 92 provides information if yo receive errors. Save the file with the.lic extension. For example, powerpath_vmware_served.lic If yo are working on a Windows host, ensre that a sffix is not atomatically added to the file name; for example.txt. 2. Place the license server configration file in a directory that is part of the defalt search path on an rpowermt server. Ensre that the license configration file is saved with the.lic extension. On a Linx host, the directories in the defalt search path are: /etc/emc /etc/emc/licenses /opt/emcpower /opt/emcpower/licenses On Windows, the directories in the defalt search path are: %USERPROFILE% \MyDocments\EMC\PowerPath\rpowermt %ALLUSRSPROFILE% \MyDocments\EMC\PowerPath\rpowermt Configre served license configration files on the rpowermt server 17

18 Installing PowerPath/VE with served licenses Setting non-defalt directories Setting non-defalt directories on page 18 provides se cases and procedres for setting non-defalt license server configration file directories. 3. Rn an rpowermt command valid for ato registration to register the vsphere hosts with the license server. For example, rn the rpowermt display command. If yo do not want to se atomatic registration, proceed to Upgrading PowerPath/VE remote CLI (rpowermt) on page 61. Upon entering the rpowermt command, yo are prompted to create an rpowermt lockbox. Enter lockbox passphrase: Confirm passphrase: Enter server sername: root Enter server password: The passphrase mst meet the following reqirements: Be eight or more characters in length. Contain at least one nmeric, one ppercase, one lowercase character, and one non-alphanmeric character (sch as # or!). Yo will need this passphrase if the lockbox is moved to a different rpowermt server. The PowerPath/VE 5.9 and Minor Releases for VMware vsphere Remote CLI Gide provides information on setting the rpowermt lockbox. Place the license server configration file in a non-defalt directory and point the PPMT_LIC_PATH environment variable to that directory. Yo can keep licenses segregated into different folders or directories, for example: separate served and nserved license configration files separate PowerPath/VE and other prodct licenses separate license server instances Yo se a non-defalt path if yo want to point to a single license file instead of a general directory. To change directory that is part of the defalt search path, set the PPMT_LIC_PATH environment variable to point to the desired directory. To set the environment variable PPMT_LIC_PATH : Procedre 1. Set non-defalt directories on Linx by typing one of the following: # setenv PPMT_LIC_PATH <license file directory> # export PPMT_LIC_PATH=<license file directory> 2. Set non-defalt directories on Windows by typing the following: C:\> set PPMT_LIC_PATH=<license file directory> Make non-defalt directories persistent across reboots on Linx Add the environment variable to the shell configration file (for example, the.profile file). 18 EMC PowerPath/VE Installation and Administration Gide 5.9 and Minor Releases for VMware vsphere

19 Installing PowerPath/VE with served licenses Making non-defalt directories persistent across reboots on Windows Procedre 1. Add the environment variable to the Environment Variables table. 2. From My Compter, select System Properties > Environment Variables. PowerPath/VE served licenses post-installation tasks Complete the post-installation tasks provided in PowerPath/VE post-installation and configration tasks on page 53. Making non-defalt directories persistent across reboots on Windows 19

20

21 CHAPTER 2 Administering served licenses This chapter contains the following topics: Migrate physical PPVE ELMS to virtal appliance PPVE ELMS Obtaining additional served licenses...22 Using mltiple served license files on Windows PPVE ELMS...23 Verify license server and license stats Set served license file path Rereading served license files Register served license for vsphere host Unregistering served license from vsphere host Re-installing and configring after converting license types Moving served licenses Administering served licenses 21

22 Administering served licenses Migrate physical PPVE ELMS to virtal appliance PPVE ELMS If yo have the physical PPVE ELMS version and want to migrate to the virtal appliance PPVE ELMS, the following procedres provide information: Migrating physical PPVE ELMS to PowerPath Virtal Appliance with existing served license file on page 10 Use this procedre if yo want to deploy the virtal appliance PPVE ELMS at the same IP address as the existing physical PPVE ELMS and the existing served license file. Migrating physical PPVE ELMS to PowerPath Virtal Appliance with new served license file on page 11 Use this procedre if yo want to deploy the virtal appliance PPVE ELMS at a different IP address as the existing physical PPVE ELMS and need a new served license file. Obtaining additional served licenses When yo first obtain a served license at the Licensing Service Center on EMC Online Spport, yo can obtain all licenses available for that served license, or a sbset of available licenses. If yo initially choose to obtain a sbset of available served licenses, yo can obtain the remaining served licenses at a later time. Procedre 1. Login to EMC Powerlink Licensing website ( sing yor sername and password. 2. Click Activate Licenses. 3. Follow the onscreen instrctions. If yo experience isses dring the regeneration process, open a service reqest on EMC Online Spport contact or EMC Spport Center at the following nmbers: Inside the United States: (800) (SVC-4EMC) In Canada: (800) (543-4SVC) Worldwide otside the United States and Canada: +1 (508) option 4, and option 4 again, for assistance opening a service reqest. 4. Install the new served license file on the PPVE ELMS. Place the served license file in the same directory where yo installed the initial served license file. PPVE spports mltiple served license files. They mst be stored in the same directory. To spport additional served license files on the Windows manal installation PPVE ELMS, follow the procedre provided in Using mltiple served license files on Windows PPVE ELMS on page 23. To spport additional served license files on the RHEL manal installation PPVE ELMS or the SLES virtal appliance PPVE ELMS, follow the procedre provided in Using PowerELMS script on page Set the license path. In lmtools select Config Services > Path to the license file. Browse to the permanent served license file location and select, and then click Save Service. 6. Stop and restart the PPVE ELMS. In lmtools: a. Select: Start/Stop/Reread > Stop Ensre that the Force Server Shtdown box is checked. The progress bar at the bottom of the pane indicates when the service is stopped. 22 EMC PowerPath/VE Installation and Administration Gide 5.9 and Minor Releases for VMware vsphere

23 Administering served licenses b. Select: Start/Stop/Reread > Start The progress bar at the bottom of the pane indicates when the service is started 7. Install the PowerPath/VE mltipathing software on the vsphere hosts for which yo obtained the additional licenses. Installing PowerPath/VE, on page 16 provides detailed information. 8. From the rpowermt server, rn an rpowermt command valid for ato-registration to register the vsphere hosts with the license server. Rn an rpowermt command for each vsphere for which yo obtained an additional served license. Using mltiple served license files on Windows PPVE ELMS Use this procedre if yo are sing the manal installation of PPVE ELMS and yo want to se mltiple served license files. Before yo begin Ensre that yo have obtained the additional served license file for Y nmber of licenses. Obtaining additional served licenses on page 22 provides information. Procedre 1. Place the original existing served license file for X nmber of licenses and the newly obtained served license file for Y nmber of licenses in the same folder. 2. Stop the PPVE ELMS in the Start/Stop/Reread tab. 3. In the Config Services tab, manally enter the path to the directory where all the licenses are placed in the Path to license file field, and then click Save service. 4. Start the PPVE ELMS from the Start/Stop/Reread tab. 5. Verify that the PPVE ELMS shows the total nmber (X + Y nmber) of served licenses. Go to Server Stats > Perform Stats Enqiry. To spport mltiple served license files on the SLES virtal appliance PPVE ELMS, see Using PowerELMS script on page 16. Verify license server and license stats Use the following procedres to verify license server and license stats: Verifying license server sing lmtil tility on page 23 Verifying license server lmtools tility for Windows only on page 24 Verifying license server sing lmtil tility Procedre On a Linx host, type: # lmtil lmstat -a -c <path to license_file_list> On a Windows host, type: lmtil.exe Using mltiple served license files on Windows PPVE ELMS 23

24 Administering served licenses The otpt indicates whether the license server and vendor daemon are rnning, the total nmber of licenses available on this license server, and how many licenses have been allocated. Verifying license server lmtools tility for Windows only Procedre 1. Navigate to the directory where the license server exectables are installed and click lmtools.exe. 2. On the Server Stats tab, click Perform Stats Enqiry. 3. Scroll down to see the information. Set served license file path Use the following procedres to set served license file path: Set served license file path sing lmtil tility on page 24 Setting served license file path sing lmtools tility on page 24 Set served license file path sing lmtil tility Use the lmtil lmpath command to: add a directory to the path (the -add argment) override the path (the -override argment) Setting served license file path sing lmtools tility Procedre Rereading served license files 1. Navigate to the directory where the license server exectables are installed and click lmtools.exe. 2. On the Config Services tab, se the Path to the license file field to view or set the path. Reread the served license files whenever a new or changed license file is added to the license server. Rereading the served license files enables the license manager and EMC vendor daemon to contine rnning while pdating the internal cache of license featres. Procedre 1. Navigate to the directory where the license server exectables are installed and click lmtools.exe. 2. On the Start/Stop/Reread tab, click ReRead License File. The following message appears: Reread Server License File Completed Alternatively, se the lmtil lmreread command to force the EMC vendor daemon to reread a new or changed served license file. Type: # lmtil lmreread -vendor 24 EMC PowerPath/VE Installation and Administration Gide 5.9 and Minor Releases for VMware vsphere

25 Administering served licenses Register served license for vsphere host Rn an rpowermt command valid for ato-registration to register the vsphere hosts. Alternatively, se the rpowermt register command to register a served license manally on a vsphere host. The PowerPath/VE 5.9 and Minor Releases for VMware vsphere Remote CLI Gide provides more information on the rpowermt register command. License cont change after re-imaging the vsphere host The license-in-se cont increases by one when yo re-register the vsphere host after reimaging the vsphere host. This pertains only to served licenses. This is an expected behavior. To correct this change in license cont: Before re-imaging the vsphere host, nregister the PowerPath/VE served license from the vsphere host. Follow the procedre provided in Unregister served license from vsphere host on page 25 Alternatively, take no action and wait 45 days, after which the license cont decreases by one. This pertains to isse Unregistering served license from vsphere host Procedre 1. Rn the rpowermt nregister command to nregister a served license on an vsphere host. The PowerPath/VE 5.9 and Minor Releases for VMware vsphere Remote CLI Gide provides more information on the rpowermt nregister command. 2. Remove the.lic file from the rpowermt server. 3. (Optional) Restart the vsphere host, if desired. If yo do not restart the vsphere host after nregistering a PowerPath/VE license, PowerPath mltipathing fnctionality contines to be provided to any storage device previosly claimed by PowerPath/VE. Note For served licenses, occasionally if the PPVE ELMS cannot be contacted dring the nregister process, the nregister scceeds althogh the license available cont does not get incremented. This is a known isse. Re-installing and configring after converting license types Complete the following procedre to: convert from nserved license to served license convert from served license to nserved license convert yor ELM license server configration Register served license for vsphere host 25

26 Administering served licenses Procedre Moving served licenses 1. Work with yor EMC Cstomer Spport Representative to convert yor license type. 2. For the original license for which yo are converting, complete the procedre for Unregister served license from vsphere host on page 25 or Unregister nserved licenses on page For the new license for which yo are converting, complete the procedre explained in: converting to served licenses: Installation components and workflow for served licenses on page 127 or converting to nserved licenses: Installation components and workflow for nserved licenses on page 130 Before yo begin Moving a served license file to a new host machine in a PowerPath/VE environment is called rehosting. Moving a license on page 133 provides information on the reasons and circmstances nder which yo might rehost. Install the license sever software on the host to which yo will rehost the served license file. Note the IP address and host name of the host to which yo are rehosting the served license file. Procedre 1. Login to EMC Powerlink Licensing website sing yor sername and password. 2. Click Move Licenses and follow the steps otlined on Licensing Service Center. The activation certificate is atomatically sent to the registered ser for this transaction. 3. Install the new served license file on the new PPVE ELMS. For example, place the served license file in the same directory where yo installed the license server exectables. 4. Start and configre the license server manager on the new PPVE ELMS Using PowerELMS script on page 16 provides information. 5. Edit the license server configration file on the rpowermt servers to point to the new PPVE ELMS. Update the IP address of the license server and the TCP/IP port nmber sed by the license server. Configre served license configration files on the rpowermt server on page 16 provides more information. 26 EMC PowerPath/VE Installation and Administration Gide 5.9 and Minor Releases for VMware vsphere

27 CHAPTER 3 Installing PowerPath/VE with nserved licenses This chapter covers the following topics: Installation components and workflow for nserved licenses Installing PowerPath/VE Install PowerPath remote CLI Finding ESX niqe system ID...29 Obtaining nserved licenses Configring nserved license configration files on the rpowermt server PowerPath/VE nserved licenses post-installation and configration tasks...32 Installing PowerPath/VE with nserved licenses 27

28 Installing PowerPath/VE with nserved licenses Installation components and workflow for nserved licenses Installation components for nserved licenses The following table identifies the reqired components for a PowerPath/VE environment that ses nserved licenses. Table 2 PowerPath/VE and VMware vsphere nserved licensing components Reqired PowerPath/VE components Reqired VMware components Component Type Component Type Components PowerPath/VE Software VMware vsphere CLI (vcli) Software: Linx or Windows OR RTOOLS Software VMware vcenter Update manager (VUM) rpowermt server Physical host or VM VUM server OR vsphere Client VUM plgin packages pre-installed. vcenter Server Virtal appliance that Software contains RTOOLS SLES Virtal Machine Software : Windows All can be physical host or VM Host compatibility Software location Windows and Linx available. PowerPath/VE installs on vsphere host. Software contained in the PowerPath/VE software distribtion on EMC Online Spport. Virtal appliance is an OVF file available as a separate download on EMC Online Spport. See Type colmn. Software located on the VMware website. Go to Task Action Installing PowerPath/VE on page 16 Installation workflow for nserved licenses The following table provides a high-level workflow of the installation process for nserved licenses: Table 3 PowerPath/VE for VMware vsphere Installation workflow nserved licenses 2. Install PowerPath remote CLI on page 29 or Deploy EMC PowerPath Virtal Appliance. Refer EMC PowerPath Virtal Appliance 1.2 Installation and Configration Gide on instrctions to deploy the Virtal Appliance. 3. Finding ESX niqe system ID on page Obtaining nserved licenses on page Configring nserved license configration files on the rpowermt server on page EMC PowerPath/VE Installation and Administration Gide 5.9 and Minor Releases for VMware vsphere

29 Installing PowerPath/VE with nserved licenses Installing PowerPath/VE Install PowerPath remote CLI Finding ESX niqe system ID Install the PowerPath/VE mltipathing software on the ESX hosts in yor PowerPath/VE environment. Install PowerPath/VE for VMware vsphere on page 38 provides installation procedres. Install the rpowermt CLI on the Windows and Linx hosts designated as rpowermt servers. Use this procedre only if yo are not deploying the virtal appliance. This topic describes how to install the rpowermt package on a Linx or Windows host. PowerPath/VE ses the ESX niqe system ID to identify each vsphere host in an nserved licensing environment. Before yo obtain an nserved license for a vsphere host, find its ESX niqe system ID. Procedre 1. Use the esxcli command to obtain the ESX niqe system ID. Type: # esxcli -s <vsphere server IP address or hostname> system id get For example: # esxcli -s lcla111 system id get Otpt sch as the following appears: 4d5e4241-6b3c-132e-44f a This is the ESX niqe system ID. Obtaining nserved licenses 2. Alternatively, se the rpowermt check_registration command to find the ESX niqe system ID of a vsphere host for which yo need to obtain an nserved license. The PowerPath/VE for VMware vsphere Remote CLI Gide provides more information on the rpowermt check_registration command. Before yo begin Ensre that yo know yor License Athorization Code (LAC). When yo prchase PowerPath/VE, EMC sends yo an that contains the LAC. Use the LAC to obtain PowerPath/VE licenses. Procedre 1. Log in to EMC Online Spport sing yor sername and password. 2. From the EMC Online Spport home page, navigate to Service Center Prodct Registration and Licenses, and click PowerPath. 3. Click Activate Licenses and follow the steps otlined on EMC Online Spport Licensing Service Center. Online help throgh context-sensitive help is provided if yo reqire assistance. Installing PowerPath/VE 29

30 Installing PowerPath/VE with nserved licenses After yo finish After receiving yor nserved license file, save the license file for yor platform to an installation directory. Sggested nserved license file locations Use the following locations as installation directories for nserved license files. Linx For RHEL rpowermt hosts and the SLES virtal appliance VM, copy the license file in the one of following directory locations: /etc/emc /etc/emc/licenses /opt/emcpower /opt/emcpower/licenses Windows For Windows rpowermt hosts, copy the license file in the one of following directories:. %USERPROFILE%\MyDocments\EMC\PowerPath\rpowermt %ALLUSRSPROFILE%\MyDocments\EMC\PowerPath\rpowermt Configring nserved license configration files on the rpowermt server Before yo begin Note Ensre that the rpowermt server and the ESX host are synchronized within 48 hors of one another. If there is a clock skew of more than 48 hors between the rpowermt server and the ESX host, rpowermt register reports license registration errors. Procedre 1. On the rpowermt server, configre a license configration (.lic) file that identifies the ESX host to the rpowermt application. Save the license file downloaded from Licensing Service Center on EMC Online Spport as a text file with the file extension.lic. This is the license configration file. 2. Place the license configration file in a directory that is part of the defalt search path on an rpowermt server. 3. Save the file with the.lic extension. For example, powerpath_vmware_nserved.lic If yo are working on a Windows host, ensre that a sffix is not atomatically added to the file name; for example.txt. On a Linx host, the directories in the defalt search path are: /etc/emc /etc/emc/licenses /opt/emcpower 30 EMC PowerPath/VE Installation and Administration Gide 5.9 and Minor Releases for VMware vsphere