Dell PowerPath Management Appliance V2.3 Networking Solution Installation And Configuration Guide PDF

PowerPath Management Appliance Version 2.3 and minor releases

Installation and Configuration Guide 302-004-561

01

Copyright 2013-2018 Dell Inc. or its subsidiaries. All rights reserved.

Published March 2018

Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS-IS. DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND

WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED

IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.

Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners.

Published in the USA.

EMC Corporation Hopkinton, Massachusetts 01748-9103 1-508-435-1000 In North America 1-866-464-7381 www.EMC.com

2 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

Revision history

The following table presents the revision history of this document.

Table 1 Revision history

Revision Date Description

01 March 2018 First release of the product

Revision history 3

Revision history

4 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

Revision history 3

7

Deploying the PowerPath Management Appliance 9 Deploy the PowerPath Management Appliance...........................................10

Deploying the PowerPath Management Appliance (OVA).............. 10 Deploying the PowerPath Management Appliance (TBZ)...............13

Configuring PowerPath Management Appliance 17 Logging into the appliance using SSH (OVA deployment)........................... 18 Changing the PowerPath Management Appliance password.......................18 Port reservation for PowerPath Management Appliance.............................18 Adding a PowerPath host............................................................................18 Adding a VMware vCenter server................................................................19 Edit VMware vCenter user credentials....................................................... 20 Remove a VMware vCenter server............................................................. 20 Change the interval at which to poll the PowerPath/VE hosts....................21 Setting up RabbitMQ messaging over AMQP .............................................21 Registering and enabling a vCenter Plugin..................................................22 Using the self-signed certificate that installs with PowerPath Management Appliance....................................................................................................22 Creating a CSR and self-signed certificate using OpenSSL........................ 22 Installing an SSL certificate on the PowerPath Management Appliance..... 23 ESRS/VE overview.....................................................................................24 PowerPath Management Appliance Integration with ESRS/VE .................25 Enabling or disabling ESRS/VE in PowerPath Management Appliance.......25 Email Alert overview................................................................................... 26 Enabling or disabling Email Alert in PowerPath Management Appliance..... 26

Configuring the Management Component 27 Configuring Management Component on Windows Using GUI................... 28 Configuring Management Component on Linux.......................................... 28 Configuring Management Component on Linux with SNMP daemon..........29 Configuring Management Component on Solaris........................................30 Configuring Management Component on HP-UX........................................31 Configuring Management Component on AIX............................................. 31 Modifying Configuration Parameters on Linux and Unix............................. 32 Troubleshooting emcp_mond on Management Component........................33

Monitoring PowerPath hosts 35 Overview of PowerPath host monitoring....................................................36 PowerPath Monitor views.......................................................................... 36

Managing PowerPath licenses 41 Add a PowerPath/VE license......................................................................42

Tables

Chapter 1

Chapter 2

Chapter 3

Chapter 4

Chapter 5

CONTENTS

PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide 5

Delete a PowerPath/VE license..................................................................42 Setting a PowerPath/VE host to unmanaged state.................................... 43 View the PowerPath/VElicenses................................................................ 43 Export licensed PowerPath and PowerPath/VE host details...................... 43 Export unlicensed PowerPath and PowerPath/VE host details.................. 44 Releasing a served license used by a PowerPath/VE host in unmanaged state........................................................................................................... 44

Upgrading PowerPath Management Appliance 45 Upgrading from PowerPath Management Appliance 2.1 and earlier to 2.3 (script)....................................................................................................... 46 Upgrading from PowerPath Management Appliance 2.1 SP1 or later to 2.3 (OVA)......................................................................................................... 47 Upgrading from PowerPath Management Appliance 2.1 SP1 and earlier to 2.3 (TBZ)................................................................................................... 48

Uninstalling PowerPath Management Appliance 49 Uninstalling PowerPath Management Appliance (OVA deployment).......... 50 Uninstalling PowerPath Management Appliance (TBZ deployment)...........50

Types of licenses and license status 51 Types of PowerPath/VE licenses............................................................... 52

Overdraft.......................................................................................52 License status............................................................................................ 53

Chapter 6

Chapter 7

Appendix A

CONTENTS

6 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

Revision history............................................................................................................ 3 Reserved port numbers and their purposes................................................................. 18 Fields and descriptions............................................................................................... 36 Fields and descriptions............................................................................................... 38 License status............................................................................................................ 53

1 2 3 4 5

TABLES

PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide 7

TABLES

8 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

CHAPTER 1

Deploying the PowerPath Management Appliance

This section contains the following topics:

l Deploy the PowerPath Management Appliance.................................................. 10

Deploying the PowerPath Management Appliance 9

Deploy the PowerPath Management Appliance The software archive packages include the install executables for PowerPath Management Appliance. You can install PowerPath Management Appliance as a full install virtual machine (OVA file) or Docker container image (TBZ file).

Note

Do not use any custom scripts to install, upgrade, or uninstall the PowerPath package.

Proceed to one of the following installation procedures:

l Deploying the PowerPath Management Appliance (OVA)

l Deploying the PowerPath Management Appliance (TBZ)

Deploying the PowerPath Management Appliance (OVA) Deploy the PowerPath Management Appliance from an OVA file using a VMware vSphere client/WebClient.

Before you begin

l Download the PowerPath Management Appliance New Deployment OVA file from EMC Online Support.

Note

Depending on user settings such as browser updates and other factors not related to PowerPath/VE, some internet browsers might not download the PowerPath Management Appliance OVA file correctly. If that occurs, try downloading the OVA file with a different internet browser or check the browser settings.

l Details of the VMware vCenter server where you are installing the virtual appliance.

l Details of the Datastore you can use for installation.

l Details of the local area network (LAN) shared by your VMware vSphere servers, to minimize deployment time. Deployment time should take approximately 5 to 15 minutes. Installation across a WAN could take 2 hours or more.

l For IPv4 and IPv6: Static IP address to assign to your appliance. This should be the same unique IP address specified in the served license file. Fully qualified server name; this should be the same Server name specified in the served license file. Gateway. Netmask (IPv4 only). Prefix length (IPv6 only). DNS servers

l NTP (time) server IP address

l Password you want to assign to the virtual appliance

Procedure

1. Open vSphere client and connect to the vCenter server managing your VMware environment.

2. Navigate to File > Deploy OVF Template.

By design, the vSphere client lists the option of deploying the OVF template. However, the PowerPath Management Appliance deploys an OVA template.

3. In Source, browse to the location of your OVA file.

Deploying the PowerPath Management Appliance

10 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

4. Click Next.

5. Review the details of the loaded OVA file in OVF Details and then click Next.

6. Review the End User License Agreement. Click Accept and then Next to continue.

7. In Name and Location:

a. Type Name: ( PowerPath Management Appliance VM) can be anything, no restrictions.

b. Specify an Inventory Location for the appliance within your VMware environment.

c. Click Next.

8. Select a host or cluster where the appliance will run and then click Next.

9. Select a resource pool associated with the host or cluster where the appliance will run and then click Next.

This step is necessary only if a resource pool has been predefined.

10. Select the virtual disk format, and then click Next.

The Datastore and Available space (GB) fields are automatically populated.

11. In IP Address Allocation:

a. Under Choose the IP allocation policy to use, select Fixed.

b. Select the internet protocol: IPv4 or IPv6.

c. Click Next.

12. In Properties:

a. Set the fully qualified host name of the appliance.

For example,

myHost.emc.com

You cannot change the hostname of the appliance after deployment. If you have to change the hostname, delete the appliance and redeploy it with the new hostname. If you need to change the hostname for a longer running appliance, the preferred method is to set up an alias in your domain name server (DNS) to resolve the appliance hostname.

b. (Optional) Set a space-separated list of domains used in the network.

For example,

emc.com myhostname.emc.com

c. Set the name or IP address of an NTP server to use for synchronizing the appliance date and time.

For example,

pool.ntp.org

d. Set the time zone of the appliance. For example, US/Eastern.

Deploying the PowerPath Management Appliance

Deploying the PowerPath Management Appliance (OVA) 11

e. Set appliance Linux root password to the password for the root user of the appliance.

This password is used to log into the console in the vSphere Client or to SSH into the appliance. This password is stored in clear text.

f. For IPv4 and IPv6, set a static IP address for the appliance, netmask applied to IP addresses (IPv4 only), prefix length (IPv6 only), gateway IP address for hosts in the network, and set a comma-separated list of domain name servers (DNS) available in the network.

The static IP address for the appliance should be the unique IP address specified in the served license file. To change the IP address of the appliance after deployment, re-deploy the appliance.

An example of a comma-separated list of domain name servers (DNS) is as follows.

192.168.0.1, 192.168.0.2

You must independently register the hostname for your appliance with your domain name servers (DNS). The appliance does not validate hostnames. Hostnames not registered with the corresponding DNS may prevent normal operation.

g. Click Next.

13. In Ready to Complete, verify the list of properties for the appliance and the click Power On after Deployment.

14. Click Finish.

A status bar appears in the VMware vSphere client/WebClient showing the deployment progress.

15. After deployment is complete, click Close.

After you finish

Use one of the following methods to verify if the deployment is successfully completed.

l Launch a browser and point to https://host_name, where host_name is the FQDN of the Appliance Virtual Machine or its IP address.

l Log into the appliance. Check if the Tomcat server is running.

service tomcat status

Reconfigure the PowerPath Management Appliance You can use vCenter to reconfigure the appliance properties.

This procedure does not change the PowerPath Management Appliance instance password. Navigate to Security > Change Password to change the password.

Procedure

1. Open vSphere client, and connect to the vCenter server managing your VMware environment.

2. Right-click the appliance name and then select Power Off.

Deploying the PowerPath Management Appliance

12 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

3. Right-click the appliance and then select Edit Settings.

4. In Virtual Machine Properties, select the Options tab.

5. Select Properties.

6. Change the properties in the right-hand side of the window and then click OK.

7. Right-click the appliance name and then select Power On.

Starting the appliance Start the appliance using vSphere client after deployment. The appliance may take few minutes to start for the first time depending on the environment. You can monitor the progress on the vSphere console.

Procedure

1. In the vSphere Client, right-click the appliance name.

2. Select Power > Power On.

The status appears in the Recent Tasks bar.

Verifying the appliance deployment After deploying the appliance, verify that it is working.

Procedure

1. In the vSphere client, navigate to the VMs and Templates view.

2. From the configured resource pool, find the resource pool you selected for the appliance.

The new appliance is listed under the resource pool.

3. In the console, log in to the appliance with the credentials you defined during the deployment.

4. Verify the services.

Deploying the PowerPath Management Appliance (TBZ) Deploy the PowerPath Management Appliance as a Dockerized container from a TBZ file.

Before you begin

Download the PowerPath Management Appliance New Deployment Docker file from EMC Online Support.

Note

Depending on user settings such as browser updates and other factors not related to PowerPath/VE, some internet browsers might not download the PowerPath Management Appliance TBZ file correctly. If that occurs, try downloading the file with a different internet browser or check the browser settings.

Procedure

1. Import the container image.

l cat <package> | docker import - <container_image_name> For example,

cat EMCPower.PPMA-<version>-<build>.tbz | docker import - powerpath

Deploying the PowerPath Management Appliance

Deploying the PowerPath Management Appliance (TBZ) 13

d478a9ce81504ebb533b9dfb5c07914aea6778e493ab5a4e5d796c8967ac 4b

2. Start the container.

There are two methods to start the container. Perform one of the following steps:

l Use the docker run command. Use this method if you do not have the Docker Compose tool.

docker run -it --cap-add=NET_ADMIN -e docker_host_ip=<docker host -ip> -e docker_hostname=<docker host name> -h=" <docker-name>" -v <database export location>:/var/lib/pgsql/data/ -v <License files export location>:/etc/emc -v <Logs export location>:/var/log/ tomcat/ -v <Logs export location> : /var/log/datacollector/- p 443:443 -p 27010:27010 -p 9083:9083 <container Image> /bin/bash -c "startup"

Where:

n Docker host-ip: IP address of the host/VM where the container will be deployed.

n Docker host name: Fully Qualified Domain Name (FQDN) of the Host/VM where container will be deployed.

n Database export location: Location on the docker host where the database files will be exported for persistence.

n License files export location: Location on the docker host where the License files will be exported for persistence.

n Logs export location: Location on the docker host where the various logs files will be exported for persistence.

n Port 443 can be mapped to a different port in the docker host, however the docker host mapped port number must be used to access the PowerPath Management Appliance web console.

n Ports 20710 and 9083 must be mapped to the same port number in the docker host.

n Container Image: container image for PowerPath Management Appliance.

Press ctrl-p+ctrl-q to turn interactive mode to daemon mode. This allows you to exit out of the container after running the docker run command.

Run exit to stop the container.

Run sudo service docker restart ; sleep 10; if the iptables issue is seen after running the docker run command.

l With the Docker Compose tool. The Docker Compose tool must be installed on the Docker host. Supported on docker-compose-1.2.0-2.1.noarch

a. Download the docker-compose.yml file from the PowerPath Management Appliance package to the Docker host.

b. Open docker-compose.yml with a text editor and provide values for the below mentioned properties.

n hostname : FQDN of the docker host.

Deploying the PowerPath Management Appliance

14 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

n docker_hostname : FQDN of the docker host.

n docker_host_ip : IP of the docker host.

n pathToPersistLicense : Location on the docker host where the License files will be exported for persistence

n pathToPersistTomcatLogs : Location on the docker host where Tomcat logs files will be exported for persistence

n pathToPersistdatacollectorLogs : Location on the docker host where Datacollector logs files will be exported for persistence

n pathToPersistdatabase : Location on the docker host where the database files will be exported for persistence

c. Run the file.

docker-compose up -d

This runs the container in detach mode.

d. In order to access the CLI console of PowerPath Management Appliance, attach to the container.

docker attach <container id>

After you finish

Use one of the following methods to verify if the deployment is successfully completed.

l Launch a browser and point to https://docker_hostname:<port_number>, where is the FQDN of the Appliance Virtual Machine or its IP address.

l Log into the PowerPath Management Appliance web console.

Docker container deployment If the PowerPath Management Appliance docker container deployment parameters are changed (such as, IP/host name), stop/remove the existing container and then bring up a new container from the PowerPath Management Appliance container image. This image was previously imported by the user.

Deploying the PowerPath Management Appliance

Deploying the PowerPath Management Appliance (TBZ) 15

Deploying the PowerPath Management Appliance

16 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

CHAPTER 2

Configuring PowerPath Management Appliance

This section contains the following topics:

l Logging into the appliance using SSH (OVA deployment)...................................18 l Changing the PowerPath Management Appliance password.............................. 18 l Port reservation for PowerPath Management Appliance.................................... 18 l Adding a PowerPath host................................................................................... 18 l Adding a VMware vCenter server....................................................................... 19 l Edit VMware vCenter user credentials...............................................................20 l Remove a VMware vCenter server.....................................................................20 l Change the interval at which to poll the PowerPath/VE hosts........................... 21 l Setting up RabbitMQ messaging over AMQP .................................................... 21 l Registering and enabling a vCenter Plugin......................................................... 22 l Using the self-signed certificate that installs with PowerPath Management

Appliance........................................................................................................... 22 l Creating a CSR and self-signed certificate using OpenSSL................................22 l Installing an SSL certificate on the PowerPath Management Appliance.............23 l ESRS/VE overview............................................................................................ 24 l PowerPath Management Appliance Integration with ESRS/VE ........................ 25 l Enabling or disabling ESRS/VE in PowerPath Management Appliance.............. 25 l Email Alert overview...........................................................................................26 l Enabling or disabling Email Alert in PowerPath Management Appliance.............26

Configuring PowerPath Management Appliance 17

Logging into the appliance using SSH (OVA deployment) Access the appliance from your local machine using SSH to view and manage the applications, such as RTOOLS and the PowerPath/VE Electronic License Manager System (ELMS), that are automatically deployed using the virtual appliance.

This procedure applies only to OVA deployments of PowerPath Management Appliance.

Procedure

1. From your local machine, connect through SSH to the virtual machine that you have deployed.

2. Log into SSH as root.

3. Type the username and password that you set up when you created the virtual appliance.

Changing the PowerPath Management Appliance password For security reasons, you should change the default password after you first deploy the appliance. Make note of the new password. The default password for the Docker container deployment is password.

Procedure

l In the PowerPath Management Appliance web console, navigate to Security > Change Password.

Port reservation for PowerPath Management Appliance Reserve the following port numbers for PowerPath Management Appliance:

Table 2 Reserved port numbers and their purposes

Port number Purpose

9083 The PowerPath Management port for non-ESX host communication.

5989 The CIM port for CIM communication by VMWare.

27010 The port used by the Licensing server (ELMS).

443 The port used for vCenter Communication and to access the PowerPath Management Appliance web console.

Adding a PowerPath host Add a PowerPath for AIX, HP-UX, Linux, Solaris, or Windows host to PowerPath Management Appliance for license reporting and PowerPath host monitoring.

PowerPath hosts can be also added from PowerPath Monitor tab. For more information refer to Monitor PowerPath hosts.

Configuring PowerPath Management Appliance

18 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

Note

PowerPath Management Appliance requires that the Management Component feature is enabled on all of the PowerPath hosts.

Procedure

1. Navigate to Inventory > PowerPath Hosts.

2. Click Add Host.

3. Perform one of the following steps:

l Discover the host by hostname or IP address.

l Discover the host by an IP range.

l Import PowerPath Viewer connections list.

4. Click OK.

Adding a VMware vCenter server Add a VMware vCenter server to PowerPath Management Appliance for license deployment and PowerPath monitoring.

Before you begin

In order to discover vCenter, your vCenter user must contain the following privileges. The user should have the privileges from the vCenter level to the corresponding managed hosts.

Note

You can also use the PowerPath Monitor context menu to add a VMware vCenter server.

In the vCenter UI, perform either of the following steps:

Note

If the privileges were set after adding the vCenter to PowerPath Management Appliance then wait for the next vCenter poll interval or remove the vCenter from PowerPath Management Appliance and then add it back.

1. Grant Administrator privilege to the requested user.

2. Add a new role with below privileges to the requested user:

l Validate session found under Sessions

l View and stop sessions found under Sessions

l CIM interaction found under Host > CIM

l Change settings found under Host > Configuration

Procedure

1. HostNavigate to Inventory > vCenter Servers.

2. Click Add vCenter.

3. Type the host name or IP address of the VMware vCenter server.

4. Type the port to the VMware vCenter server or use the default port of 443.

Configuring PowerPath Management Appliance

Adding a VMware vCenter server 19

5. Type a username and password of the user with the above-mentioned privileges, and then click OK.

6. Select the Register plug-in checkbox to register PowerPath Management Appliance vCenter plug-in.

Refer to Registering and enabling a vCenter Plugin.

Edit VMware vCenter user credentials If VMware vCenter user credentials changed, update the credentials with the following procedure.

Note

You can also use the PowerPath Monitor context menu to edit VMware vCenter user credentials.

Procedure

1. Navigate to Inventory > vCenter Servers.

2. Select the VMware vCenter for which you want to change the credentials.

3. Click Edit Credentials.

4. Change the username or password, or both, and then click OK.

5. Select the Register plugin checkbox to register the PowerPath Management Appliance vCenter plugin.

Refer to Registering and enabling a vCenter plugin for more information.

6. Click OK.

Remove a VMware vCenter server Remove a disconnected VMware vCenter server.

Procedure

1. Navigate to Inventory > vCenter Servers.

2. Select the VMware vCenter server that you want to remove and then select Remove.

3. Click OK.

Results

The PowerPath/VE hosts are removed from the PowerPath Management Appliance but remain licensed.

Note

When a VMware vCenter server is removed from the virtual appliance, the PowerPath/VE licenses for the ESXi hosts managed by that VMware vCenter server are not removed. The trial licenses applied to any of PowerPath/VE hosts remain continue to be valid. However, the number is reflected in PowerPath Licenses >

Summary.

Configuring PowerPath Management Appliance

20 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

Note

You can also use the PowerPath Monitor context menu to remove a VMware vCenter server.

Change the interval at which to poll the PowerPath/VE hosts

Use this procedure to change the interval at which PowerPath Management Appliance polls the ESXi hosts for changes.

This procedure applies to PowerPath/VE for VMware vSphere ESXi hosts only.

Note

If more than 100 PowerPath hosts are added to PowerPath Management Appliance, you should increase default polling interval. For a large configuration, polling interval should be set to 4 hours.

Procedure

1. Navigate to System > Settings.

2. Use the slider to change the poll interval.

You can select from 10 minutes to 4 hours. The default is 30 minutes.

Setting up RabbitMQ messaging over AMQP Use the following procedure to setup RabbitMQ messaging over AMQP.

PowerPath Management Appliance collects events from PowerPath hosts and sends them to the message queue provided by RabbitMQ. RabbitMQ is enabled by default in PowerPath Management Appliance.

Note

Third party AMQP clients have to either run from within PowerPath Management Appliance or implement mechanisms to proxy the AMQP traffic.

Procedure

1. In the PowerPath Management Appliance web console, navigate to Security > RabbitMQ to add the credentials for the RabbitMQ queue.

You can test the RabbitMQ connection with the new user by adding a message and clicking Send.

2. Subscribe to the RabbitMQ queue.

The subscription requires a RabbitMQ client.

Configuring PowerPath Management Appliance

Change the interval at which to poll the PowerPath/VE hosts 21

Registering and enabling a vCenter Plugin The vCenter plugin provides a minimal view of the PowerPath Management Appliance web console. Only the details of ESXi hosts belonging to the current instance of a vCenter server are displayed.

The Web client plugin can be registered on the vCenter server in two ways. Select one of the following options:

l Register the plugin while adding or editing the vCenter properties in the PowerPath Management Appliance. Browse to the Inventory > vCenter Servers tab, select the Register Plugin checkbox in the Add vCenter dialog box, and then click OK.

l After adding a vCenter to the PowerPath Management Appliance, browse to the Inventory > vCenter Servers page, and click the Register vCenter Plugin button on the bottom of the page.

Results

Access the plugin after registering. Use the short-cut, EMC PowerPath, located in the vCenter Web client.

Note

If you use the default self-signed certificate of PowerPath Management Appliance, open the PowerPath Management Appliance web console in a new tab in order to accept the certificate before accessing plugin through the vCenter web client.

Using the self-signed certificate that installs with PowerPath Management Appliance

PowerPath Management Appliance ships with a 2048-bit SSL certificate issued by EMC Corporation which is used to generate or regenerate a host-based SSL certificate and key using the customer's host name at PowerPath Management Appliance boot time.

This certificate expires 1100 days after PowerPath Management Appliance installation.

Creating a CSR and self-signed certificate using OpenSSL Use this procedure to create a certificate signing request (CSR) and a self-signed certificate using OpenSSL.

The PowerPath Management Appliance employs the SLES 12 Operating System and to assist with the steps in this procedure, ships with the secure shell and openssl utilities, and the vi and vim editors installed.

Consult your companies' information security department for assistance with SSL certificate and key generation.

Procedure

1. Generate a Private Key.

Configuring PowerPath Management Appliance

22 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

This example creates a 2048-bit RSA key using Triple-DES.

openssl genrsa -des3 -out server.key 2048

The OpenSSL documentation provides more information on the command syntax.

2. Generate a CSR.

openssl req -new -key server.key -out server.csr

Fill in the prompts for your organization, such as country name, state or province, locality name, and other attributes of the certificate.

3. Remove the passphrase from the key to avoid entering it each time the web server is started.

If you are getting a certificate signed by a third-party certificate authority (CA) then this is your final step.

cp server.key server.key.org openssl rsa -in server.key.org -out server.key

The newly created server.key file does not include the passphrase in the key.

4. Generate a self-signed certificate.

openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt -sha256

A temporary certificate good for 365 days is generated.

After you finish

Install an SSL certificate on the PowerPath Management Appliance

Installing an SSL certificate on the PowerPath Management Appliance

Use this procedure to install an SSL certificate on the PowerPath Management Appliance host.

Before you begin

Ensure that you have created a self-signed certificate or obtained a certificate signed by a third-party certificate authority (CA) or by an in-house CA for the PowerPath Management Appliance host. Create a CSR and self-signed certificate using OpenSSL provides more information.

Procedure

1. Using a terminal emulator program, log into the PowerPath Management Appliance as root using secure shell.

l On OVA deployment:

ssh -l root hostname

Configuring PowerPath Management Appliance

Installing an SSL certificate on the PowerPath Management Appliance 23

l On TBZ (Docker container) deployment, attach to the console of Management Appliance Container.

2. Place the generated certificate and key files in the directories listed below.

Directory

Certificate /etc/apache2/ssl.crt Key file /etc/apache2/ssl.key Certificate chain /etc/apache2/ssl.crt

For certificate chain, either put all of the certificates in the directory as separate files or create a single PEM file from all of the certificates by concatenating the certificate PEM files together. All of the certificates in the CA chain must be in PEM format before concatenating them into a single file. Their key will be the bottom most key in the certification chain (this is called the key for the leaf certificate).

3. Edit the PowerPath Management Appliance /etc/apache2/httpd- EMCPower.conf file to point to the certificate and key files.

l For the certificate and key file, modify the SSLCertificateFile and SSLCertificateKeyFile lines.

SSLCertificateFile /etc/apache2/ssl.crt/ customers_crt_file.crt SSLCertificateKeyFile /etc/apache2/ssl.key/ customers_key_file.key

l If the CA certificate chain is in separate files, modify the SSLCACertificatePath line.

SSLCACertificatePath /etc/apache2/ssl.crt

l If there is only a single CA certificate or if a chain of CA certificate PEM files have been concatenated together into a single file, modify the SSLCACertificateFile line.

SSLCACertificateFile /etc/apache2/ssl.crt/ca_cert_filename

4. Change permissions of the certificate file.

chmod 644 /etc/apache2/ssl.crt/customers_crt_file.crt 5. Restart the VM/container.

6. (optional) Connect to the PowerPath Management Appliance with a web browser to verify the certificate.

https://hostname_or_ip_address/LicenseReportingApplication/

ESRS/VE overview Secure Remote Services/Virtual Edition (ESRS/VE) can provide connectivity and remote serviceability solutions for automated Connect Home and Remote Service activities.

The service is available through an IP-based solution enhanced by a comprehensive security system.

Configuring PowerPath Management Appliance

24 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

PowerPath Management Appliance supports the Usage Intelligence feature of ESRS/VE when deployed into the ESRS Virtual Edition Gateway. Usage Intelligence (UI) is available for the collection, transfer, analysis, and reporting of usage data for EMC customers.

The PowerPath Management Appliance Release Notes provides the versions of ESRS/VE qualified with PowerPath Management Appliance.

PowerPath Management Appliance Integration with ESRS/VE

PowerPath Management Appliance integrates with the ESRS RESTful services providing Usage Intelligence (UI).

Usage Intelligence provides collection, transfer, analysis, and reporting of your usage data to EMC. It allows the PowerPath Management Appliance to send UI XML files to Secure Remote Services/Virtual Edition.

With ESRS Virtual Edition, PowerPath Management Appliance can add itself as a device to ESRS/VE, and send license usage reports to ESRS/VE, every 24 hours, as well as: update the device IP, delete the device, and keep live messages every 60 seconds.

Enabling or disabling ESRS/VE in PowerPath Management Appliance

After successful installation of PowerPath Management Appliance, follow this procedure to enable or disable the Secure Remote Services/Virtual Edition (ESRS/VE) component in PowerPath Management Appliance.

Procedure

1. Browse to System > Settings > ESRS Gateway Settings.

ESRS/VE is enabled by default.

Note

To disable ESRS/VE, click Disable.

2. Type the ESRS/VE gateway information, username, and password.

3. Click Update.

Results

The procedure adds PowerPath Management Appliance as a device to ESRS/VE, and reporting served licenses usage begins.

Note

You must have a PowerPath UI-enabled served license in order to receive license usage reports.

If ESRS/VE gateway details change, update the details in PowerPath Management Appliance.

Configuring PowerPath Management Appliance

PowerPath Management Appliance Integration with ESRS/VE 25

For additional information on ESRS/VE, refer to the ESRS/VE EMC Online Support product page.

Email Alert overview The email alert feature, when enabled, triggers a host-based alert to the recipients' email ids when there is a change in volume, path, and bus.

Based on the SMTP server and recipient email id details defined on the Settings screen, a host-based email alert is sent to the customers when there is a change in volume, path, or bus. The host-based email alert triggers from ppma_alert@emc.com and it displays the host state with date and time, host name, status, LUN state, Path/Bus state, PowerPath version, and license state.

Enabling or disabling Email Alert in PowerPath Management Appliance

After successful installation of PowerPath Management Appliance, follow this procedure to enable or disable the email alert component in PowerPath Management Appliance.

Procedure

1. Browse to System > Settings > Email Alert.

The email alert functionality is disabled by default.

2. Click Enable to enable to the email alert functionality.

3. Type the SMTP Server information.

4. Type the Recipient Email Id information.

In case of multiple recipients, enter comma separated email Ids.

5. Click Test Email Setup.

6. Click Update.

A pop-up window appears for confirmation.

7. Click OK.

8. Click Udate.

Results

The procedure enables email alert functionality to the PowerPath Management Appliance and the customer starts receiving host-based email alerts when there is a change in volume, path, and bus.

Note

For the email alert functionality to enable or disable, you must click Update followed by OK.

Configuring PowerPath Management Appliance

26 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

CHAPTER 3

Configuring the Management Component

This chapter contains the following topics:

l Configuring Management Component on Windows Using GUI........................... 28 l Configuring Management Component on Linux..................................................28 l Configuring Management Component on Linux with SNMP daemon................. 29 l Configuring Management Component on Solaris............................................... 30 l Configuring Management Component on HP-UX............................................... 31 l Configuring Management Component on AIX..................................................... 31 l Modifying Configuration Parameters on Linux and Unix..................................... 32 l Troubleshooting emcp_mond on Management Component............................... 33

Configuring the Management Component 27

Configuring Management Component on Windows Using GUI

The Management Component is included in the PowerPath package. Separate installation is not required. This procedure describes how to configure the Management Component.

In the Configure PowerPath Management Component window, follow these steps to configure the Management Component:

Procedure

1. In the Enable Management Component checkbox, ensure that Enable is selected. It should be selected by default.

2. In the Port Number field, do one of the following:

l Maintain the default port value of 9083. This value is the recommended setting and indicated as Registered under the Port Number field.

l Change the port value if required. For example, if another application is using the default port. The valid, alternate port range is 4915265535 and indicated as Alternatives under the Port Number field.

3. In the Heartbeat Interval field, do one of the following:

l Maintain the default value of 10. This value is in minutes.

l Change the heartbeat interval value. The valid heartbeat interval value is 1 60. EMC recommends that the heartbeat interval be based on the number of managed hosts.

4. In the Disable Single Path Symmetrix gatekeeper Setup Warning checkbox, do one of the following:

l Maintain the default setting if you do not want Setup error reports for Symmetrix gatekeeper devices that are configured with a single path.

l Change the setting if Symmetrix gatekeeper devices are multipathed in the data center.

PowerPath supports both single-path and multipath configured Symmetrix gatekeepers. Consult the network administrator for more information about the Symmetrix gatekeeper configuration.

5. Click finish.

Configuring Management Component on Linux The Management Component is included in the PowerPath package. Separate installation is not required. This procedure describes how to configure the Management Component.

Procedure

1. Enable the Management Component. Type:

> /sbin/emcp_mond_edit

a. Start the editor. Note that if the emcp_mond.conf file does not exist on the machine, the editor will read the sample configuration.

Configuring the Management Component

28 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

b. The Management Component is disabled by default. To enable the Management Component service using default configuration parameter values, type 1 and 13 to confirm and save. Then type the number option to exit, save, and restart the Management Component.

EMC recommends using default configuration parameters. To modify the configuration parameters, go to Modifying Configuration Parameters on Linux and Unix.

2. Verify that emcp_mond is running and that PowerPath Management Component is started. Type:

> pgrep -xl emcp_mond Alternatively, verify the messages log for successful Management Component installation and start. Type:> tail /var/log/ messages The message log contains the messages such as the following:

PowerPath: Management Component: Info: Attempting to start. Version: 5.3.SP1-b044. PowerPath: Management Component: Info: Config parameters valid. Config: port#=9083, heartbeat interval=10 mins, singlePathGkOk=1 PowerPath: Management Component: Info: Service started.

3. Verify that the Management Component is installed correctly on the hosts where you have installed PowerPath Management Component. Type:

# rpm -qa | grep EMC Output such as the following appears:

EMCpower.MgmtComponent.LINUX-5.3.2.00.00-046 EMCpower.LINUX-5.3.1.02.00-007

The output shows the Management Component package is installed.

Configuring Management Component on Linux with SNMP daemon

The Management Component is included in the PowerPath package. Separate installation is not required. This procedure describes how to configure the Management Component.

Use this procedure if the system runs SNMP daemon.

Procedure

1. To enable SNMP trap processing, perform one of these steps:

l Run emcp_mond_edit

a. Select line 5 to enable SNMP trap processing.

b. Select line 13 to write the emcp_mond configuration file and exit the program.

l In the file, emcp_mond,conf uncomment the line: ## MgmtComponentEnable=TRUE

Configuring the Management Component

Configuring Management Component on Linux with SNMP daemon 29

2. Start the SNMP service.

svcadm enable -s system/emcpower/emcp_mond

3. Restart the PowerPath monitoring daemon (emcp_mond)from the script.

/etc/init.d/emcp_mond.sh start

Configuring Management Component on Solaris The Management Component is included in the PowerPathpackage. Separate installation is not required. This procedure describes how to configure the Management Component.

Before you begin

To access the Management Component, go to Inventory > PowerPath Hosts and select Mgmt Component.

Procedure

1. Enable the Management Component.

> /etc/emc/bin/emcp_mond_edit

a. Note that if the emcp_mond.conf file does not exist on the machine, the editor will read the sample configuration file.

b. The Management Component is disabled by default. To enable the Management Component service using default configuration parameter values, type 1 and 13 to confirm the changes and save. Then type the number option to exit, save, and restart the Management Component.

EMC recommends using default configuration parameters. To modify the configuration parameters, go to Modifying Configuration Parameters on Linux and Unix

2. Verify that emcp_mond is running on the system.

> pgrep -xl emcp_mond

3. Verify that the message log contains the following messages:

> tail /var/adm/messages PowerPath: Management Component: Info: Attempting to start. Version: 5.3-b006. PowerPath: Management Component: Info: Config parameters valid. Config: port#=9083, heartbeat interval=10 mins, singlePathGkOk=1 PowerPath: Management Component: Info: Service started.

To stop and start the emcp_mond service, go to Troubleshooting emcp_mond on Management Component

Configuring the Management Component

30 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

Configuring Management Component on HP-UX The Management Component is included in the PowerPath package. Separate installation is not required. This procedure describes how to configure the Management Component.

Before you begin

To access the Management Component, go to Inventory > PowerPathHosts and select Mgmt Component.

Procedure

1. Enable the Management Component.

/etc/emc/bin/emcp_mond_edit

a. Start the editor. Note that if the emcp_mond.conf file does not exist on the machine, the editor will read the sample configuration file.

b. The Management Component is disabled by default. To enable the Management Component service using default configuration parameter values, type 1 and 6 to confirm the changes and save. Then type the number option to exit, save, and restart the Management Component.

EMC recommends using default configuration parameters. To modify the configuration parameters, go to Modifying Configuration Parameters on Linux and Unix.

2. To verify that the Management Component is installed and started, check that the system log contains the following messages:

PowerPath: Management Component: Info: Attempting to start. Version: 5.1.SP2-b001. PowerPath: Management Component: Info: Config parameters valid. Config: port#=9083, heartbeat interval=10 mins, singlePathGkOk=1. PowerPath: Management Component: Info: Service

If you need to stop and start the emcp_mond, go to Troubleshooting emcp_mond on Management Component for more information.

Configuring Management Component on AIX The Management Component is included in the PowerPath package. Separate installation is not required. This procedure describes how to configure the Management Component.

Procedure

1. Enable the Management Component on AIX.

/etc/emc/bin/emcp_mond_edit

a. Start the editor. Note that if the emcp_mond.conf file does not exist on the machine, the editor will read the sample configuration file.

Configuring the Management Component

Configuring Management Component on HP-UX 31

b. The Management Component is disabled by default. To enable the Management Component service using default configuration parameter values, type 1 and 13 to confirm the changes and save. Then type the number option to exit, save, and restart the Management Component.

EMC recommends using default configuration parameters. To modify the configuration parameters, go to Modifying Configuration Parameters on Linux and Unix

2. Verify that emcp_mond is running.

> ps -ef | egrep emcp_mond

3. Verify that the message log contains messages similar to the following:

>tail /usr/safe.log

:info PowerPath: Management Component: Info: Attempting to start. Version: 5.3-b001. :info PowerPath: Management Component: Info: Service started. :info PowerPath: Management Component: Info: Config parameters valid. Config: port#=9083, heartbeat interval=10 mins, singlePathGkOk=1

Modifying Configuration Parameters on Linux and Unix To modify the configuration parameters on Linux and Unix, perform the following procedures:

Procedure

1. Log in as root.

2. Go to emcp_mond_edit in/etc/emc/bin to start the Management Component editor.

3. To modify the heartbeat interval:

l Type 2

l Type the number of the desired heartbeat interval. The valid range in minutes is 1-60.

4. To modify the port number:

l Type 3

l Type the number of the desired port. Ensure that the port is not already in use by another application. Note that the Management Component defaults to port 9083 if the port number entered is already in use. The default and recommended port number is 9083. The valid range is 49152-65535.

5. To disable Single Path Symmetrix Gatekeeper warnings:

l Type 4

Note that options 5 through 11 apply to modification of SNMP features. The PowerPath release notes for your platform provide information on SNMP support.

Configuring the Management Component

32 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

6. Type the number option depending on your platform to confirm emcp_mond.conf and save. Then type the number option to exit, save, and restart the Management Component.

Troubleshooting emcp_mond on Management Component To troubleshoot the emcp_mond on Management Component, follow these procedures:

Start and stop the emcp_mond Service on Solaris To stop the emcp_mond Service, run:

svcadm disable system/emcpower/emcp_mond To start the emcp_mond Service, run:

svcadm enable -s system/emcpower/emcp_mond To get the state of the emcp_mond Service, run:

svcs system/emcpower/emc_mond Start and stop emcp_mond daemon on HP-UX To stop the emcp_mond daemon, run:

/sbin/init.d/emcpmond stop To start the emcp_mond daemon, run:

/sbin/init.d/emcpmond start

Configuring the Management Component

Troubleshooting emcp_mond on Management Component 33

Configuring the Management Component

34 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

CHAPTER 4

Monitoring PowerPath hosts

This chapter includes the following topics:

l Overview of PowerPath host monitoring........................................................... 36 l PowerPath Monitor views..................................................................................36

Monitoring PowerPath hosts 35

Overview of PowerPath host monitoring The PowerPath Monitor, available in versions 2.0 SP1 and later, provides host monitoring capabilities including device/path monitoring. The monitor displays PowerPath volume, path, and bus details.

Monitoring is provided for the following PowerPath-supported platforms:

l ESXi

l AIX

l HP-UX

l Linux

l Solaris

l Windows

The tree view on the left side of the PowerPath Monitor view block displays non-ESXi and ESXi hosts. Non-ESXi PowerPath hosts are organized under their corresponding user-defined host groups (created from the inventory tab). ESXi hosts are grouped under corresponding vCenter to which they belong. Entries in the host tree view are highlighted with an icon to indicate the state.

PowerPath Monitor views The PowerPath Monitor displays tabs for the Host Group Tree view, Summary view, LUN view, BUS view, and Serviceability Data view.

Summary view

When you select a host, the Host Summary view launches with information on the status of the devices and paths of the host, with configured PowerPath options, current host state, and LUN and Path summary details display. Host state warnings are highlighted at the top and bottom of Summary view.

Table 3 Fields and descriptions

Fields Description

Host details Host State as of The last time stamp when the host information was retrieved by the PowerPath Virtual/Management Appliance.

IP IP of the host

Host Name FQDN of host as known to PowerPath Management Appliance (via DNS)

PowerPath Version Version of PowerPath running on the host

Status PowerPath Management Appliance connection status to the management component on the host

License License is valid or host is unlicensed

Monitoring PowerPath hosts

36 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

Table 3 Fields and descriptions (continued)

Fields Description

Platform OS platform (AIX, HPUX, LINUX, ESXi, SOLARIS, WINDOWS)

OS Version OS Version of the selected PowerPath host. This is displayed only from PowerPath versions later than PowerPath 6.0 for all platforms except Linux which needs PowerPath version later than 6.0 SP1.

Path and LUN state

LUN State Total number of dead/alive volumes

Path State Total number of dead/alive paths

PowerPath Options Auto Host Registration If Auto host registration is enabled or disabled (PowerPath 6.0 and later)

Autostandby: Proximity (prox)

Autostandby (prox) state and threshold for specified storage class.

Auto Standby IOPF If auto standby IOPF is enabled or disabled

IOPF Aging Period IOPF aging period in days

IOPF Limit IOPF limit

Path Latency Monitor If Path latency monitoring is enabled or disabled

Path Latency Monitoring Threshold

Path Latency Monitoring Threshold (displayed only if path latency monitoring is enabled)

Performance Monitor If PMI is enabled or disabled

Performance Monitor Interval PMI interval in seconds (displayed only if PMI is enabled)

Persist Path Information If Path information persistence is enabled or disabled

Summary tab also displays following warning/errors:

l Connection related warnings

n Connection failure.

n Maximum allowed number of connections exceeded (Non-ESXi hosts only).

l Host unlicensed

l Volume related warnings

n Number of volumes with a single path alive.

n Number of degraded volumes. This includes dead paths as well as volumes with unlicensed policy.

LUN view LUN view provides details of LUNs and paths of the selected host. Right-click on table header to select columns that you want to view. This selection is not persistent across multiple sessions.

Monitoring PowerPath hosts

PowerPath Monitor views 37

Table 4 Fields and descriptions

Fields Description

Volume details Name Name of the Volume

Array Type Type of array to which the Volume belongs

Alive/Total Paths Ratio of live to total paths

Array Name(s) Name of arrays to which a volume is connected.

Policy Multipathing policy for the device

Device ID Logical device ID of the volume

Storage Group Storage group to which the volume belongs

LUN Name Name of the LUN from array side

Queued IOs Number of IOs queued for the volume

Standard UID For ESXi only

Path details Queued IOs Number of IOs queued for the path

HBA Port HBA port

Array Port Array port that is part of the path

Mode Mode of the path

State Live/dead state of the path

ALUA State ALUA state of the device

BUS view BUS view shows the association between HBA Ports > HBA IP > Array Name > Array Ports along with the IOs queued for the bus.

Icon State in both LUN view and BUS view:

l Green Normal: All the paths to the volume/BUS are live

l YellowDegraded: A few path to the volume/BUS are dead

l RedError: All paths to the volume/BUS are dead

Serviceability Data view Serviceability Data view provides details of some host-level parameters and a subset of Serviceability feature of PowerPath Management Appliance parameters.

The parameters include:

l PowerPath Version

l PowerPath License

l PowerPath Policy

l Machine Architecture

l Full OS Name

l SYMAPI Version

l SYMM Microcode Version

Monitoring PowerPath hosts

38 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

l Native Multipathing

l CLARiiON FLARE Version

l CLARiiON Failover Mode

l HBA Information

Context Menu Options The following context menu options are available, based on the node that you selected:

l Repoll

l Repoll non-ESXi hosts

l Repoll Group

l Add Host

l Create New Group

l Edit Host

l Add vCenter

l Edit vCenter

l Remove vCenter

l Repoll ESXi Hosts

l Edit Group

l Remove Host

l Remove Group

Monitoring PowerPath hosts

PowerPath Monitor views 39

Monitoring PowerPath hosts

40 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

CHAPTER 5

Managing PowerPath licenses

This section contains the following topics:

l Add a PowerPath/VE license............................................................................. 42 l Delete a PowerPath/VE license......................................................................... 42 l Setting a PowerPath/VE host to unmanaged state............................................43 l View the PowerPath/VElicenses........................................................................43 l Export licensed PowerPath and PowerPath/VE host details..............................43 l Export unlicensed PowerPath and PowerPath/VE host details..........................44 l Releasing a served license used by a PowerPath/VE host in unmanaged state.. 44

Managing PowerPath licenses 41

Add a PowerPath/VE license Add PowerPath/VE for VMware vSphere licenses to the PowerPath Management Appliance.

Before you begin

If you are uploading the license key from your local machine, download the license key to your local machine.

This procedure applies to PowerPath/VE for VMware vSphere hosts only. To add licenses on PowerPath for AIX, HP-UX, Linux, Solaris, or Windows hosts, use the emcpreg command or Windows PowerPath Administrator GUI.

Note

You can also add a PowerPath/VE license from the PowerPath Management Appliance vCenter plugin.

Procedure

1. Navigate to PowerPath Licenses > PowerPath/VE License.

2. Click Add License.

3. Perform one of the following steps:

l Paste the license key in the Add License dialog box.

l Upload the license key.

a. Click Browse.

b. Navigate to the license key location on your local computer and then select the license key.

c. Click OK.

4. Click OK.

Delete a PowerPath/VE license Delete PowerPath/VE for VMware vSphere licenses from the PowerPath Management Appliance.

This procedure applies to PowerPath/VE for VMware vSphere hosts only. This operation cannot be undone. To delete licenses on PowerPath for AIX, HP-UX, Linux, Solaris, or Windows hosts, use the emcpreg command or Windows PowerPath Administrator GUI.

Note

You can also delete a PowerPath/VE license from the PowerPath Management Appliance vCenter plugin.

Procedure

1. Navigate to PowerPath Licenses > PowerPath/VE License.

2. Select the license to be deleted, and then click Delete License.

3. Click Yes on the confirmation page.

Managing PowerPath licenses

42 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

Setting a PowerPath/VE host to unmanaged state This procedure enables you to set a PowerPath/VE host to unmanaged state.

Procedure

1. Identify vCenter details of the host which needs to be set to unmanaged state.

2. Remove the concerned ESXi host from the vCenter server.

Removes the link between the host and PowerPath Management Appliance.

3. Navigate to PowerPath Licenses > Licensed Hosts.

4. Check under the Host Group/Hosts column to ensure that the ESXi host is listed as unmanaged host.

Note

Only an unmanaged host license can be released using the release action button. Refer to Releasing a served license used by a PowerPath/VE host in unmanaged state on page 44 for more information.

View the PowerPath/VElicenses View thePowerPath/VE licenses added or present in the PowerPath Management Appliance.

Note

You can also view the PowerPath/VE licenses from the PowerPath Management Appliance vCenter plugin.

Procedure

l Navigate to PowerPath Licenses > PowerPath/VE License.

Results

A list of all PowerPath/VE licenses added or present in the PowerPath Management Appliance is displayed.

Export licensed PowerPath and PowerPath/VE host details Export license details for licensed PowerPath and PowerPath/VE hosts.

Procedure

1. Browse to PowerPath Licenses > Licensed Hosts.

2. Click Export.

Results

The license details are exported to a CSV (Comma Separated Value) file.

Managing PowerPath licenses

Setting a PowerPath/VE host to unmanaged state 43

Export unlicensed PowerPath and PowerPath/VE host details

Export license details for unlicensed PowerPath and PowerPath/VE hosts.

Procedure

1. Browse to PowerPath Licenses > Unlicensed Hosts.

2. Click Export.

Results

The license details are exported to a CSV (Comma Separated Value) file.

Releasing a served license used by a PowerPath/VE host in unmanaged state

This procedure only applies for PowerPath/VE hosts that are shown as unmanaged in PowerPath Licenses > Licensed Hosts

Procedure

1. Navigate to PowerPath Licenses > Licensed Hosts.

2. Select the required unmanaged host from the table.

3. Click Release License.

Managing PowerPath licenses

44 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

CHAPTER 6

Upgrading PowerPath Management Appliance

This section contains the following topic:

l Upgrading from PowerPath Management Appliance 2.1 and earlier to 2.3 (script) ...........................................................................................................................46

l Upgrading from PowerPath Management Appliance 2.1 SP1 or later to 2.3 (OVA) ........................................................................................................................... 47

l Upgrading from PowerPath Management Appliance 2.1 SP1 and earlier to 2.3 (TBZ)................................................................................................................. 48

Upgrading PowerPath Management Appliance 45

Upgrading from PowerPath Management Appliance 2.1 and earlier to 2.3 (script)

You can upgrade from PowerPath Management Appliance Version 2.1 and earlier to 2.3 using the export_ppma_config script.

Before you begin

l Download the PowerPath Management Appliance package from EMC Online Support. This package contains the upgrade script required to upgrade the PowerPath Management Appliance.

l The CST Standalone Lockbox passphrase is required after an upgrade from earlier versions of PowerPath Management Appliance to the current version . You will be prompted to re-enter the passphrase when you attempt to run the first rpowermt command on the appliance.

If the passphrase is lost, recreate the lockbox and re-enter the PowerPath/VE host information and credentials in order to perform rpowermt commands, or supply the host username and password on the rpowermt command line.

The upgrade to PowerPath Management Appliance Version 2.3 from PowerPath Virtual Appliance 2.x is supported only by using the upgrade script. You must have root privileges to carry out the upgrade.

For script-based upgrade from PowerPath Virtual Appliance 1.2 to PowerPath Management Appliance 2.0, refer to the video on the PowerPath EMC Community Network for a demonstration on upgrading PowerPath Management Appliance: https://community.emc.com/videos/26034

Procedure

1. Unzip the export_ppma_config script and then copy it to the PowerPath Management Appliance 2.x VM.

2. SSH into the PowerPath Virtual Appliance 2.x VM and then run the script to export the PowerPath Virtual Appliance 2.x configuration.

chmod +x export_ppma_config

./export_ppma_config

3. Copy the resulting PowerPath_management_appliance.zip file to the local desktop or a remote location.

4. Take note of the PowerPath Management Appliance deployment parameter details.

PowerPath Management Appliance Deployment Parameters ======================================= Host name : <> Search Domain : <> IP : <> Subnet mask : <> Gateway : <> DNS Server : <> NTP Server : <>

5. Power down the PowerPath Virtual Appliance 2.x VM.

Upgrading PowerPath Management Appliance

46 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

Note

Do not delete the PowerPath Virtual Appliance 2.x VM until after successful PowerPath Management Appliance import.

6. Deploy PowerPath Management Appliance 2.3 with the same PowerPath Management Appliance Deployment Parameters as PowerPath Virtual Appliance 2.x.

7. Power up the PowerPath Management Appliance 2.3 VM.

8. In the 2.3 PowerPath Management Appliance web console, navigate to System > Settings > Import Config ZIP and then import the PowerPath_management_appliance.zip file.

After you finish

After successful import, PowerPath Virtual Appliance 2.x can be deleted.

Upgrading from PowerPath Management Appliance 2.1 SP1 or later to 2.3 (OVA)

Before you begin

l Download the PowerPath Management Appliance upgrade package (Zip file) from EMC Online Support. Copy to the PowerPath Management Appliance.

l The CST Standalone Lockbox passphrase is required after an upgrade from earlier versions of PowerPath Management Appliance to the current version. You are prompted to re-enter the passphrase when you try to run the first rpowermt command on the appliance.

If the passphrase is lost, recreate the lockbox and re-enter thePowerPath/VE host information and credentials to perform rpowermt commands, or supply the host username and password on the rpowermt command line.

Procedure

1. SSH into the PowerPath Management Appliance.

2. Change to the directory in which the upgrade only package is copied.

cd <upgrade_package_directory>

3. Unzip the upgrade only package.

unzip <upgrade_package>

4. Unzip the PowerPath Management Appliance Update package.

unzip EMCPower.PPMA-update-x.x.x.xx.xx-xx.zip

5. Change to the PowerPath Management Appliance update folder.

cd update

6. Change access to the applianceUpdate.

chmod 777 applianceUpdate

7. Run just "./applianceUpdate".

Wait for the update to finish. This might take some time.

Upgrading PowerPath Management Appliance

Upgrading from PowerPath Management Appliance 2.1 SP1 or later to 2.3 (OVA) 47

8. Restart PowerPath Management Appliance.

Upgrading from PowerPath Management Appliance 2.1 SP1 and earlier to 2.3 (TBZ)

Direct upgrade is not supported with PowerPath Management Appliance container images. Perform the following procedure to upgrade from 2.1 SP1 and earlier to 2.3.

Before you begin

l Download the PowerPath Management Appliance New Deployment file from EMC Online Support. This package contains the TBZ file.

l The CST Standalone Lockbox passphrase is required after an upgrade from earlier versions of PowerPath Management Appliance to the current version . You will be prompted to re-enter the passphrase when you attempt to run the first rpowermt command on the appliance.

If the passphrase is lost, recreate the lockbox and re-enter the PowerPath/VE host information and credentials in order to perform rpowermt commands, or supply the host username and password on the rpowermt command line.

Procedure

1. If the PowerPath Management Appliance 2.1 container data is not persisted outside of the container, in the PowerPath Management Appliance web console, navigate to Help > Export Config ZIP and save the resulting PowerPath_Management_Appliance.zip file to the local desktop or a remote location.

2. Stop the running container.

docker stop <container_ID>

3. Import the PowerPath Management Appliance 2.3 docker image.

cat <package> | docker import - <container_image_name>

4. Bring up a new container with same parameters of previous container.

5. If the PowerPath Management Appliance 2.1 container data is not persisted outside of the container, navigate to System > Settings > Import Config ZIP and then import the PowerPath_management_appliance.zip file.

6. Remove the previous container and image.

docker rmi <container_ID>

docker rmi container_image_name>

Upgrading PowerPath Management Appliance

48 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

CHAPTER 7

Uninstalling PowerPath Management Appliance

This section contains the following topics:

l Uninstalling PowerPath Management Appliance (OVA deployment)..................50 l Uninstalling PowerPath Management Appliance (TBZ deployment).................. 50

Uninstalling PowerPath Management Appliance 49

Uninstalling PowerPath Management Appliance (OVA deployment)

Using your vSphere client, you can shut down and remove PowerPath Management Appliance from your VMware inventory.

This procedure applies only to OVA deployments of PowerPath Management Appliance.

Procedure

1. Open the vSphere Client and connect to the vCenter server managing your appliance.

2. Right-click the appliance in the left pane of the Inventory > VMs and Templates window for the vSphere Client and then select Power > Shut Down Guest.

3. Right-click the appliance and then select Delete from Disk.

Uninstalling PowerPath Management Appliance (TBZ deployment)

This procedure applies only to TBZ (Docker container) deployments of PowerPath Management Appliance.

The Docker documentation provides more information on the Docker CLI.

Procedure

1. Stop the container.

docker stop <container_ID>

2. Remove the container.

docker rm <container_ID>

3. Remove the image.

docker rmi <container_image_name>

Uninstalling PowerPath Management Appliance

50 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

APPENDIX A

Types of licenses and license status

This section contains the following topics:

l Types of PowerPath/VE licenses.......................................................................52 l License status.................................................................................................... 53

Types of licenses and license status 51

Types of PowerPath/VE licenses Explains the types of license supported by PowerPath/VE for VMware vSphere.

Served license

The Served licensing model uses a license server to store, distribute and manage PowerPath/VE licenses. In this model, the Electronic License Manager System (ELMS) distributes the PowerPath/VE licenses to vSphere hosts. You install the license configuration file on the PowerPath/VE ELMS and it manages the licenses for all the PowerPath/VE hosts for which the license was generated.

Unserved license

The Unserved licensing model binds PowerPath/VE to a specific vSphere host. More accurately, to a vSphere unique system ID. An Unserved license is only valid for the specific vSphere host for which it was generated. An Unserved license is static; it cannot be used on another vSphere host.

It does not use a license server. Rather, the PowerPath/VE license is stored on the remote (rpowermt) PowerPath server. This type of license is also known as the Node Locked license.

FX license

FX licensing is applicable for the host connected to PowerMax FX enabled arrays. For more information on FX licenses, refer PowerMax documentation.

Master Key license

The Master Key license is a special case of Unserved license. This license model is available to customers with an Enterprise License Agreement only. A Master Key license is locked to a domain subnet, for example *.abc.def.com. In this case, it must contain the Virtual/Management Appliance's subnet. It allows rpowermt commands to be run against any PowerPath/VE host regardless of the host's address or domain.

Trial license

The PowerPath Management Appliance comes with a 45-day trial license period for an unlimited number of PowerPath/VE version hosts. The addition of Permanent or Temporary license keys to the PowerPath/VE hosts that are using Trial licenses will transition respective licenses that are added.

The Trial licenses are automatically pushed to all unlicensed PowerPath/VE hosts.

Overdraft Served licenses contain an overdraft count which provides a temporary buffer of 10% above the count of licenses purchased.

The overdraft feature provides a temporary buffer license when the number of PowerPath/VE hosts exceed the number of PowerPath/VE licenses. The overdraft count applies to the Served licenses only.

Types of licenses and license status

52 PowerPath Management Appliance 2.3 and minor releases Installation and Configuration Guide

License status The following table provides a list of license status indicators and descriptions.

Table 5 License status

Indicator Description

License that is due to expire or the license is valid but is unused

Valid licen