appliance dell emc powerpath management · 2020-03-04 · dell emc powerpath management appliance...

Dell EMC PowerPath ManagementApplianceVersion 2.4 and minor releases

Installation and Configuration Guide302-005-248

01

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

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

Dell EMCHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381www.DellEMC.com

2 Dell EMC PowerPath Management Appliance 2.4 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 October 2018 First release of the product

Revision history 3

Revision history


Revision history 3

7

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

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

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

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

Tables

Chapter 1

Chapter 2

Chapter 3

CONTENTS

Dell EMC PowerPath Management Appliance 2.4 and minor releases Installation and Configuration Guide 5

Monitoring PowerPath hosts 37Overview of PowerPath host monitoring....................................................38PowerPath Monitor views.......................................................................... 38

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

Upgrading Dell EMC PowerPath Management Appliance 47Upgrading from Dell EMC PowerPath Management Appliance 2.1 and earlierto 2.4 (script).............................................................................................48Upgrading from Dell EMC PowerPath Management Appliance 2.1 SP1 orlater to 2.4 (OVA).......................................................................................49Upgrading from Dell EMC PowerPath Management Appliance 2.1 SP1 andearlier to 2.4 (TBZ).................................................................................... 50

Uninstalling Dell EMC PowerPath Management Appliance 51Uninstalling Dell EMC PowerPath Management Appliance (OVAdeployment)............................................................................................... 52Uninstalling Dell EMC PowerPath Management Appliance (TBZdeployment)............................................................................................... 52

Types of licenses and license status 53Types of PowerPath/VE licenses............................................................... 54

Overdraft.......................................................................................54License status............................................................................................ 55

Chapter 4

Chapter 5

Chapter 6

Chapter 7

Appendix A

CONTENTS


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

12345

TABLES

Dell EMC PowerPath Management Appliance 2.4 and minor releases Installation and Configuration Guide 7

TABLES


CHAPTER 1

Deploying the Dell EMC PowerPathManagement Appliance

This section contains the following topics:

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

Deploying the Dell EMC PowerPath Management Appliance 9

Deploy the Dell EMC PowerPath Management ApplianceThe Dell EMC PowerPath Management Appliance packages available for downloadfrom Dell EMC Online Support.

There are two software archive packages available for download:

1. Dell EMC PowerPath Management Appliance as a full install virtual machine (OVAfile) containing config export script file, and

2. Dell EMC PowerPath Management Appliance Docker container image (TBZ file)containing config export script file and Docker compose file.

Proceed to one of the following installation procedures:

l Deploying the Dell EMC PowerPath Management Appliance (OVA)

l Deploying the Dell EMC PowerPath Management Appliance (TBZ)

Deploying the Dell EMC PowerPath Management Appliance (OVA)Deploy the Dell EMC PowerPath Management Appliance from an OVA file using aVMware vSphere client/WebClient.

Before you begin

l Download the Dell EMC PowerPath Management Appliance New Deployment OVAfile from Dell EMC Online Support.

Note

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

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

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 15minutes. 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 bethe same unique IP address specified in the served license file. Fully qualifiedserver name; this should be the same Server name specified in the served licensefile. 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 VMwareenvironment.

2. Navigate to File > Deploy OVF Template.

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

Deploying the Dell EMC PowerPath Management Appliance


https://support.emc.com


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

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

7. In Name and Location:

a. Type Name: ( Dell EMC PowerPath Management Appliance VM) can beanything, no restrictions.

b. Specify an Inventory Location for the appliance within your VMwareenvironment.

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 appliancewill 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 youhave to change the hostname, delete the appliance and redeploy it with thenew hostname. If you need to change the hostname for a longer runningappliance, the preferred method is to set up an alias in your domain nameserver (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 theappliance date and time.

For example,

pool.ntp.org


Deploying the Dell EMC PowerPath Management Appliance (OVA) 11

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

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

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

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

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

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

192.168.0.1, 192.168.0.2

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

g. Click Next.

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

14. Click Finish.

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

15. After deployment is complete, click Close.

After you finish

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

l Launch a browser and point to https://host_name, where host_name is theFQDN 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 Dell EMC PowerPath Management ApplianceYou can use vCenter to reconfigure the appliance properties.

This procedure does not change the Dell EMC PowerPath Management Applianceinstance password. Navigate to Security > Change Password to change thepassword.

Procedure

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



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

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 applianceStart the appliance using vSphere client after deployment. The appliance may takefew minutes to start for the first time depending on the environment. You can monitorthe 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 deploymentAfter 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 theappliance.

The new appliance is listed under the resource pool.

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

4. Verify the services.

Deploying the Dell EMC PowerPath Management Appliance (TBZ)Deploy the Dell EMC PowerPath Management Appliance as a Dockerized containerfrom a TBZ file.

Before you begin

Download the Dell EMC PowerPath Management Appliance New Deployment Dockerfile from Dell EMC Online Support.

Note

Depending on user settings such as browser updates and other factors that are notrelated to PowerPath/VE, some internet browsers might not download the Dell EMCPowerPath Management Appliance TBZ file correctly. If that occurs, try downloadingthe 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>


Deploying the Dell EMC PowerPath Management Appliance (TBZ) 13


For example,

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

2. Start the container.

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

l Use the docker run command. Use this method if you do not have theDocker 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 -p 15672:15672 <container Image> /bin/bash -c "startup"

Where:

n Docker host-ip: IP address of the host/VM where the container isdeployed.

n Docker host name: Fully Qualified Domain Name (FQDN) of the Host/VMwhere container is deployed.

n Database export location: Location on the docker host where thedatabase files are exported for persistence.

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

n Logs export location: Location on the docker host where the various logsfiles are exported for persistence.

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

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

n Port 15672 is used for accessing rabbitmq GUI.

n Container Image: container image for Dell EMC PowerPath ManagementAppliance.

To turn interactive mode to daemon mode, press ctrl-p+ctrl-q. This actionallows you to exit out of the container after running the docker runcommand.

To stop the container, run exit.

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

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



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

b. Open docker-compose.yml with a text editor and provide values forthe following properties.

n hostname: FQDN of the docker host.

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 Licensefiles are exported for persistence

n pathToPersistTomcatLogs: Location on the docker host whereTomcat logs files are exported for persistence

n pathToPersistdatacollectorLogs: Location on the docker host whereDatacollector logs files are exported for persistence

n pathToPersistdatabase: Location on the docker host where thedatabase files are exported for persistence

c. Run the file.

docker-compose up -d

This command runs the container in detach mode.

d. To access the CLI console of Dell EMC PowerPath ManagementAppliance, attach to the container.

docker attach <container id>

After you finish

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

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 in to the PowerPath Management Appliance web console.

Docker container deploymentIf the Dell EMC PowerPath Management Appliance docker container deploymentparameters are changed (such as, IP/host name), stop/remove the existing containerand then bring up a new container from the Dell EMC PowerPath ManagementAppliance container image. This image was previously imported by the user.


Deploying the Dell EMC PowerPath Management Appliance (TBZ) 15

CHAPTER 2

Configuring Dell EMC PowerPath ManagementAppliance


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

Management Appliance......................................................................................22l Creating a CSR and self-signed certificate using OpenSSL................................22l Installing an SSL certificate on the Dell EMC PowerPath Management Appliance

...........................................................................................................................23l ESRS/VE overview............................................................................................ 25l Dell EMC PowerPath Management Appliance Integration with ESRS/VE .........25l Enabling or disabling ESRS/VE in Dell EMC PowerPath Management Appliance

...........................................................................................................................25l Email Alert overview...........................................................................................26l Enabling or disabling Email Alert in Dell EMC PowerPath Management Appliance

...........................................................................................................................26

Configuring Dell EMC 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 theapplications, such as RTOOLS and the PowerPath/VE Electronic License ManagerSystem (ELMS), that are automatically deployed using the virtual appliance.

This procedure applies only to OVA deployments of Dell EMC PowerPath ManagementAppliance.

Procedure

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

2. Log into SSH as root.

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

Changing the Dell EMC PowerPath Management Appliancepassword

For security reasons, you should change the default password after you first deploythe appliance. Make note of the new password. The default password for the Dockercontainer deployment is password.

Procedure

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

Port reservation for Dell EMC PowerPath ManagementAppliance

Reserve the following port numbers for Dell EMC 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 Dell EMCPowerPath Management Appliance web console.

Configuring Dell EMC PowerPath Management Appliance


Adding a PowerPath hostAdd a PowerPath for AIX, HP-UX, Linux, Solaris, or Windows host to Dell EMCPowerPath Management Appliance for license reporting and PowerPath hostmonitoring.

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

Note

Dell EMC PowerPath Management Appliance requires that the ManagementComponent 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 serverAdd a VMware vCenter server to Dell EMC PowerPath Management Appliance forlicense 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 correspondingmanaged hosts.

Note

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

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

Note

If the privileges were set after adding the vCenter to Dell EMC PowerPathManagement Appliance then wait for the next vCenter poll interval or remove thevCenter from Dell EMC 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


Adding a PowerPath host 19

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.

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

6. Select the Register plug-in checkbox to register Dell EMC PowerPathManagement Appliance vCenter plug-in.

Refer to Registering and enabling a vCenter Plugin.

Edit VMware vCenter user credentialsIf VMware vCenter user credentials changed, update the credentials with thefollowing procedure.

Note

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

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 Dell EMC PowerPathManagement Appliance vCenter plugin.

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

6. Click OK.

Remove a VMware vCenter serverRemove 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 selectRemove.

3. Click OK.

Results

The PowerPath/VE hosts are removed from the Dell EMC PowerPath ManagementAppliance but remain licensed.



Note

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

Summary.

Note

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

Change the interval at which to poll the PowerPath/VEhosts

Use this procedure to change the interval at which Dell EMC PowerPath ManagementAppliance 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 Dell EMC PowerPath ManagementAppliance, 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 AMQPUse the following procedure to setup RabbitMQ messaging over AMQP.

Dell EMC PowerPath Management Appliance collects events from PowerPath hostsand sends them to the message queue provided by RabbitMQ. RabbitMQ is enabled bydefault in Dell EMC PowerPath Management Appliance.

Note

Third party AMQP clients have to either run from within Dell EMC PowerPathManagement 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 messageand clicking Send.

2. Subscribe to the RabbitMQ queue.


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

The subscription requires a RabbitMQ client.

Registering and enabling a vCenter PluginThe vCenter plugin provides a minimal view of the PowerPath Management Applianceweb console. Only the details of ESXi hosts belonging to the current instance of avCenter server are displayed.

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

l Register the plugin while adding or editing the vCenter properties in the Dell EMCPowerPath Management Appliance. Browse to the Inventory > vCenter Serverstab, select the Register Plugin checkbox in the Add vCenter dialog box, and thenclick OK.

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

Results

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

Note

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

Using the self-signed certificate that installs with Dell EMCPowerPath Management Appliance

Dell EMC PowerPath Management Appliance ships with a 2048-bit SSL certificateissued by Dell EMC that is used to generate or regenerate a host-based SSLcertificate and key using the customer's hostname at Dell EMC PowerPathManagement Appliance start time.

This certificate expires 821 days after Dell EMC PowerPath Management Applianceinstallation.

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

The Dell EMC PowerPath Management Appliance employs the SLES 12 OperatingSystem and to assist with the steps in this procedure, ships with the secure shell andopenssl utilities, and the vi and vim editors installed.

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



Procedure

1. Generate a Private Key.

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

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 orprovince, locality name, and other attributes of the certificate.

3. Remove the passphrase from the key to avoid entering it each time the webserver 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.orgopenssl 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 Dell EMC PowerPath Management Appliance

Installing an SSL certificate on the Dell EMC PowerPathManagement Appliance

Use this procedure to install an SSL certificate on the Dell EMC PowerPathManagement Appliance host.

Before you begin

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

Procedure

1. Using a terminal emulator program, log into the Dell EMC PowerPathManagement Appliance as root using secure shell.


Installing an SSL certificate on the Dell EMC PowerPath Management Appliance 23

l On OVA deployment:

ssh -l root hostname

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

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

Directory

Certificate /etc/apache2/ssl.crtKey file /etc/apache2/ssl.keyCertificate chain /etc/apache2/ssl.crt

For certificate chain, either put all of the certificates in the directory asseparate files or create a single PEM file from all of the certificates byconcatenating the certificate PEM files together. All of the certificates in theCA 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 thekey for the leaf certificate).

3. Edit the Dell EMC 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 andSSLCertificateKeyFile lines.

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

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

SSLCACertificatePath /etc/apache2/ssl.crt

l If there is only a single CA certificate or if a chain of CA certificate PEM fileshave been concatenated together into a single file, modify theSSLCACertificateFile 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 Dell EMC PowerPath Management Appliance with aweb browser to verify the certificate.

https://hostname_or_ip_address/LicenseReportingApplication/



ESRS/VE overviewSecure Remote Services/Virtual Edition (ESRS/VE) can provide connectivity andremote serviceability solutions for automated Connect Home and Remote Serviceactivities.

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

Dell EMC PowerPath Management Appliance supports the Usage Intelligence featureof 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 forDell EMC customers.

The Dell EMC PowerPath Management Appliance Release Notes provides the versionsof ESRS/VE qualified with Dell EMC PowerPath Management Appliance.

Dell EMC PowerPath Management Appliance Integrationwith ESRS/VE

Dell EMC PowerPath Management Appliance integrates with the ESRS RESTfulservices providing Usage Intelligence (UI).

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

With ESRS Virtual Edition, Dell EMC PowerPath Management Appliance can add itselfas 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 60seconds.

Enabling or disabling ESRS/VE in Dell EMC PowerPathManagement Appliance

After successful installation of Dell EMC PowerPath Management Appliance, followthis procedure to enable or disable the Secure Remote Services/Virtual Edition(ESRS/VE) component in Dell EMC 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 Dell EMC PowerPath Management Appliance as a device toESRS/VE, and reporting served licenses usage begins.


ESRS/VE overview 25

Note

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

If ESRS/VE gateway details change, update the details in Dell EMC PowerPathManagement Appliance.

For additional information on ESRS/VE, refer to the ESRS/VE Dell EMC OnlineSupport product page.

Email Alert overviewThe 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 Settingsscreen, a host-based email alert is sent to the customers when there is a change involume, path, or bus. The host-based email alert triggers from [email protected] it displays the host state with date and time, hostname, status, LUN state,Path/Bus state, PowerPath version, and license state.

Enabling or disabling Email Alert in Dell EMC PowerPathManagement Appliance

After successful installation of Dell EMC PowerPath Management Appliance, followthis procedure to enable or disable the email alert component in Dell EMC PowerPathManagement 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 Dell EMC PowerPathManagement Appliance and the customer starts receiving host-based email alertswhen there is a change in volume, path, and bus.





Note

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


Enabling or disabling Email Alert in Dell EMC PowerPath Management Appliance 27

CHAPTER 3

Configuring the Management Component

This chapter contains the following topics:

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

Configuring the Management Component 29

Configuring Management Component on Windows UsingGUI

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

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

Procedure

1. In the Enable Management Component checkbox, ensure that Enable isselected. 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 recommendedsetting and indicated as Registered under the Port Number field.

l Change the port value if required. For example, if another application is usingthe default port. The valid, alternate port range is 49152–65535 andindicated 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. Dell EMC recommends that the heartbeat interval be based on thenumber of managed hosts.

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

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

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

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

5. Click finish.

Configuring Management Component on LinuxThe Management Component is included in the PowerPath package. Separateinstallation is not required. This procedure describes how to configure theManagement 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 onthe machine, the editor will read the sample configuration.



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

recommends using default configuration parameters. To modify theconfiguration parameters, go to Modifying Configuration Parameters on Linuxand Unix.

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

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

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

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

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

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

The output shows the Management Component package is installed.

Configuring Management Component on Linux with SNMPdaemon

The Management Component is included in the PowerPath package. Separateinstallation is not required. This procedure describes how to configure theManagement 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 Management Component on Linux with SNMP daemon 31

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 SolarisThe Management Component is included in the PowerPathpackage. Separateinstallation is not required. This procedure describes how to configure theManagement Component.

Before you begin

To access the Management Component, go to Inventory > PowerPath Hosts andselect 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, theeditor will read the sample configuration file.

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

recommends using default configuration parameters. To modify theconfiguration parameters, go to Modifying Configuration Parameters on Linuxand 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<date time host name> PowerPath: Management Component: Info: Attempting to start.Version: 5.3-b006.<date time host name> PowerPath: Management Component: Info: Config parameters valid.Config: port#=9083, heartbeat interval=10 mins, singlePathGkOk=1<date time host name> PowerPath: Management Component: Info: Service started.

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



Configuring Management Component on HP-UXThe Management Component is included in the PowerPath package. Separateinstallation is not required. This procedure describes how to configure theManagement Component.

Before you begin

To access the Management Component, go to Inventory > PowerPathHosts andselect 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 onthe machine, the editor will read the sample configuration file.

b. The Management Component is disabled by default. To enable theManagement Component service using default configuration parametervalues, type 1 and 6 to confirm the changes and save. Then type the numberoption to exit, save, and restart the Management Component.

recommends using default configuration parameters. To modify theconfiguration parameters, go to Modifying Configuration Parameters on Linuxand Unix.

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

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

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

Configuring Management Component on AIXThe Management Component is included in the PowerPath package. Separateinstallation is not required. This procedure describes how to configure theManagement 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 onthe machine, the editor will read the sample configuration file.


Configuring Management Component on HP-UX 33

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

recommends using default configuration parameters. To modify theconfiguration parameters, go to Modifying Configuration Parameters on Linuxand 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

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

Modifying Configuration Parameters on Linux and UnixTo modify the configuration parameters on Linux and Unix, perform the followingprocedures:

Procedure

1. Log in as root.

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

3. To modify the heartbeat interval:

l Type 2

l Type the number of the desired heartbeat interval. The valid range inminutes 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 inuse by another application. Note that the Management Component defaultsto port 9083 if the port number entered is already in use. The default andrecommended 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. ThePowerPath release notes for your platform provide information on SNMPsupport.



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

Troubleshooting emcp_mond on Management ComponentTo troubleshoot the emcp_mond on Management Component, follow theseprocedures:

Start and stop the emcp_mond Service on SolarisTo stop the emcp_mond Service, run:

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

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

svcs system/emcpower/emc_mondStart and stop emcp_mond daemon on HP-UXTo stop the emcp_mond daemon, run:

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

/sbin/init.d/emcpmond start


Troubleshooting emcp_mond on Management Component 35

CHAPTER 4

Monitoring PowerPath hosts

This chapter includes the following topics:

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

Monitoring PowerPath hosts 37

Overview of PowerPath host monitoringThe PowerPath Monitor, available in versions 2.0 SP1 and later, provides hostmonitoring capabilities including device/path monitoring. The monitor displaysPowerPath 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-ESXiand ESXi hosts. Non-ESXi PowerPath hosts are organized under their correspondinguser-defined host groups (created from the inventory tab). ESXi hosts are groupedunder corresponding vCenter to which they belong. Entries in the host tree view arehighlighted with an icon to indicate the state.

PowerPath Monitor viewsThe 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 thestatus of the devices and paths of the host, with configured PowerPath options,current host state, and LUN and Path summary details display. Host state warningsare 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 hostinformation was retrieved by thePowerPath Virtual/ManagementAppliance.

IP IP of the host

Host Name FQDN of host as known to Dell EMCPowerPath Management Appliance (viaDNS)

PowerPath Version Version of PowerPath running on thehost

Status Dell EMC PowerPath ManagementAppliance connection status to themanagement component on the host

License License is valid or host is unlicensed



Table 3 Fields and descriptions (continued)

Fields Description

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

OS Version OS Version of the selected PowerPathhost. This is displayed only fromPowerPath versions later thanPowerPath 6.0 for all platforms exceptLinux which needs PowerPath versionlater than 6.0 SP1.

Path and LUNstate

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 ordisabled (PowerPath 6.0 and later)

Autostandby: Proximity(prox)

Autostandby (prox) state and thresholdfor specified storage class.

Auto Standby IOPF If auto standby IOPF is enabled ordisabled

IOPF Aging Period IOPF aging period in days

IOPF Limit IOPF limit

Path Latency Monitor If Path latency monitoring is enabled ordisabled

Path Latency MonitoringThreshold

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

Performance Monitor If PMI is enabled or disabled

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

Persist Path Information If Path information persistence isenabled 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 withunlicensed policy.

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


PowerPath Monitor views 39

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

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 viewBUS view shows the association between HBA Ports > HBA IP > Array Name > ArrayPorts 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 Yellow—Degraded: A few path to the volume/BUS are dead

l Red—Error: All paths to the volume/BUS are dead

Serviceability Data viewServiceability Data view provides details of some host-level parameters and a subsetof 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



l Native Multipathing

l CLARiiON FLARE Version

l CLARiiON Failover Mode

l HBA Information

Context Menu OptionsThe following context menu options are available, based on the node that youselected:

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


PowerPath Monitor views 41

CHAPTER 5

Managing PowerPath licenses


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

...........................................................................................................................46

Managing PowerPath licenses 43

Add a PowerPath/VE licenseAdd PowerPath/VE for VMware vSphere licenses to the Dell EMC PowerPathManagement Appliance.

Before you begin

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

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

Note

You can also add a PowerPath/VE license from the Dell EMC PowerPath ManagementAppliance 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 thenselect the license key.

c. Click OK.

4. Click OK.

Delete a PowerPath/VE licenseDelete PowerPath/VE for VMware vSphere licenses from the Dell EMC PowerPathManagement Appliance.

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

Note

You can also delete a PowerPath/VE license from the Dell EMC PowerPathManagement 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.



Setting a PowerPath/VE host to unmanaged stateThis 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 Dell EMC PowerPath ManagementAppliance.

3. Navigate to PowerPath Licenses > Licensed Hosts.

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

Note

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

View the PowerPath/VElicensesView thePowerPath/VE licenses added or present in the Dell EMC PowerPathManagement Appliance.

Note

You can also view the PowerPath/VE licenses from the Dell EMC PowerPathManagement 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 Dell EMC PowerPathManagement Appliance is displayed.

Export licensed PowerPath and PowerPath/VE host detailsExport 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.


Setting a PowerPath/VE host to unmanaged state 45

Export unlicensed PowerPath and PowerPath/VE hostdetails

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 inunmanaged state

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

Procedure

1. Navigate to PowerPath Licenses > Licensed Hosts.

2. Select the required unmanaged host from the table.

3. Click Release License.



CHAPTER 6

Upgrading Dell EMC PowerPath ManagementAppliance

This section contains the following topic:

l Upgrading from Dell EMC PowerPath Management Appliance 2.1 and earlier to2.4 (script).........................................................................................................48

l Upgrading from Dell EMC PowerPath Management Appliance 2.1 SP1 or later to2.4 (OVA).......................................................................................................... 49

l Upgrading from Dell EMC PowerPath Management Appliance 2.1 SP1 and earlierto 2.4 (TBZ).......................................................................................................50

Upgrading Dell EMC PowerPath Management Appliance 47

Upgrading from Dell EMC PowerPath ManagementAppliance 2.1 and earlier to 2.4 (script)

You can upgrade from Dell EMC PowerPath Management Appliance Version 2.1 andearlier to 2.4 using the export_ppma_config script.

Before you begin

l Download the Dell EMC PowerPath Management Appliance package from DellEMC Online Support. This package contains the upgrade script that is required toupgrade the Dell EMC PowerPath Management Appliance.

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

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

The upgrade to Dell EMC PowerPath Management Appliance Version 2.4 fromPowerPath Virtual Appliance 2.x is supported only by using the upgrade script. Youmust have root privileges to carry out the upgrade.

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

Procedure

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

2. SSH into the Dell EMC PowerPath Management Appliance 2.x VM and then runthe script to export the Dell EMC PowerPath Management Appliance 2.xconfiguration.

chmod +x export_ppma_config

./export_ppma_config

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

4. Take note of the Dell EMC PowerPath Management Appliance deploymentparameter details.

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

5. Power off the Dell EMC PowerPath Management Appliance 2.x VM.

Upgrading Dell EMC PowerPath Management Appliance




https://community.emc.com/videos/26034

Note

Do not delete the Dell EMC PowerPath Management Appliance 2.x VM untilafter successful Dell EMC PowerPath Management Appliance import.

6. Deploy Dell EMC PowerPath Management Appliance 2.4 with the same DellEMC PowerPath Management Appliance Deployment Parameters as Dell EMCPowerPath Management Appliance 2.x.

7. Power on the Dell EMC PowerPath Management Appliance 2.4 VM.

8. In the 2.4 PowerPath Management Appliance web console, browse to System >Settings > Import Config ZIP and then import thePowerPath_management_appliance.zip file.

After you finish

After successful import, Dell EMC PowerPath Management Appliance 2.x can bedeleted.

Upgrading from Dell EMC PowerPath ManagementAppliance 2.1 SP1 or later to 2.4 (OVA)

Before you begin

l Download the Dell EMC PowerPath Management Appliance upgrade package (Zipfile) from Dell EMC Online Support. Copy to the Dell EMC PowerPathManagement Appliance.

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

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

Procedure

1. SSH into the Dell EMC 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 Dell EMC PowerPath Management Appliance Update package.

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

5. Change to the Dell EMC PowerPath Management Appliance update folder.

cd update

6. Change access to the applianceUpdate.

chmod 777 applianceUpdate

7. Run only ./applianceUpdate.


Upgrading from Dell EMC PowerPath Management Appliance 2.1 SP1 or later to 2.4 (OVA) 49


Wait for the update to finish.

8. Restart Dell EMC PowerPath Management Appliance.

Upgrading from Dell EMC PowerPath ManagementAppliance 2.1 SP1 and earlier to 2.4 (TBZ)

Direct upgrade is not supported with Dell EMC PowerPath Management Appliancecontainer images. Perform the following procedure to upgrade from 2.1 SP1 and earlierto 2.4.

Before you begin

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

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

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

Procedure

1. If the Dell EMC PowerPath Management Appliance 2.1 container data is notpersisted outside of the container, in the PowerPath Management Applianceweb console, navigate to Help > Export Config ZIP and save the resultingPowerPath_Management_Appliance.zip file to the local desktop or aremote location.

2. Stop the running container.

docker stop <container_ID>

3. Import the Dell EMC PowerPath Management Appliance 2.4 docker image.

cat <package> | docker import - <container_image_name>

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

5. If the Dell EMC PowerPath Management Appliance 2.1 container data is notpersisted outside of the container, navigate to System > Settings > ImportConfig ZIP and then import the PowerPath_management_appliance.zipfile.

6. Remove the previous container and image.

docker rm <container_ID>

docker rmi <old_container_image_name>




CHAPTER 7

Uninstalling Dell EMC PowerPath ManagementAppliance


l Uninstalling Dell EMC PowerPath Management Appliance (OVA deployment).. 52l Uninstalling Dell EMC PowerPath Management Appliance (TBZ deployment)...52

Uninstalling Dell EMC PowerPath Management Appliance 51

Uninstalling Dell EMC PowerPath Management Appliance(OVA deployment)

Using your vSphere client, you can shut down and remove Dell EMC PowerPathManagement Appliance from your VMware inventory.

This procedure applies only to OVA deployments of Dell EMC PowerPath ManagementAppliance.

Procedure

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

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

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

Uninstalling Dell EMC PowerPath Management Appliance(TBZ deployment)

This procedure applies only to TBZ (Docker container) deployments of Dell EMCPowerPath 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 Dell EMC PowerPath Management Appliance


APPENDIX A

Types of licenses and license status


l Types of PowerPath/VE licenses.......................................................................54l License status....................................................................................................55

Types of licenses and license status 53

Types of PowerPath/VE licensesExplains 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 managePowerPath/VE licenses. In this model, the Electronic License Manager System(ELMS) distributes the PowerPath/VE licenses to vSphere hosts. You install thelicense configuration file on the PowerPath/VE ELMS and it manages the licensesfor 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 validfor the specific vSphere host for which it was generated. An Unserved license isstatic; it cannot be used on another vSphere host.

It does not use a license server. Rather, the PowerPath/VE license is stored onthe remote (rpowermt) PowerPath server. This type of license is also known asthe 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 isavailable to customers with an Enterprise License Agreement only. A Master Keylicense is locked to a domain subnet, for example *.abc.def.com. In this case, itmust contain the Virtual/Management Appliance's subnet. It allows rpowermtcommands to be run against any PowerPath/VE host regardless of the host'saddress or domain.

Trial license

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

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

OverdraftServed 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 ofPowerPath/VE hosts exceed the number of PowerPath/VE licenses. The overdraftcount applies to the Served licenses only.



License statusThe 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 isvalid but is unused

Valid license

Expired license

Invalid license


License status 55

appliance dell emc powerpath management · 2020-03-04 · dell emc powerpath management appliance...

Documents