appliance dell emc powerpath management · 2020-05-23 · deploy the dell emc powerpath management...

Dell EMC PowerPath ManagementApplianceVersion 2.6 and minor releases

Installation and Configuration Guide302-006-057

02

October 2019

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

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 Technologies, Dell, EMC, 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 Installation and Configuration Guide

Revision history

The following table presents the revision history of this document.

Table 1 Revision history

Revision Date Description

02 October 2019 Added procedures for creating non-root user andRabbitMQ user

01 September 2019 First release of the product

Dell EMC PowerPath Management Appliance Installation and Configuration Guide 3

Revision history


Revision history 3

7

Deploying the 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)......13Deploying the Dell EMC PowerPath Management Appliance (VHD).....15

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

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

Tables

Chapter 1

Chapter 2

Chapter 3

CONTENTS


Monitoring PowerPath hosts 39Overview of PowerPath host monitoring.......................................................... 40PowerPath Monitor views.................................................................................40

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

Upgrading PowerPath Management Appliance 49Upgrading from PowerPath Management Appliance 2.1 and earlier to 2.6(script)............................................................................................................. 50Upgrading from PowerPath Management Appliance 2.1 SP1 or later to 2.6(OVA/VHD).......................................................................................................51Upgrading from PowerPath Management Appliance 2.1 SP1 and earlier to 2.6(TBZ)................................................................................................................52

Uninstalling PowerPath Management Appliance 53Uninstalling PowerPath Management Appliance (OVA deployment).................54Uninstalling PowerPath Management Appliance (VHD deployment).................54Uninstalling PowerPath Management Appliance (TBZ deployment)................. 54

Types of licenses and license status 57Types of PowerPath/VE licenses......................................................................58

Overdraft............................................................................................. 59License status...................................................................................................59

Troubleshooting 61Troubleshooting................................................................................................62

Chapter 4

Chapter 5

Chapter 6

Chapter 7

Appendix A

Appendix B

Contents


Revision history...................................................................................................................3Reserved port numbers and their purposes.......................................................................20Fields and descriptions......................................................................................................40Fields and descriptions......................................................................................................42License status...................................................................................................................59

12345

TABLES


Tables


CHAPTER 1

Deploying the PowerPath Management Appliance

This section contains the following topics:

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


Deploy the Dell EMC PowerPath Management ApplianceThe Dell EMC PowerPath Management Appliance packages are available for download from DellEMC Online Support.

There are three software archive packages available for download:

1. PowerPath Management Appliance as a full install virtual machine (OVA file) containingconfig export script file, and

2. PowerPath Management Appliance Docker container image (TBZ file) containing configexport script file and Docker compose file.

3. PowerPath Management Appliance VHD 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)

l Deploying the Dell EMC PowerPath Management Appliance (VHD)Note: Mandatory fields to deploy Dell EMC PowerPath Management Appliance: Hostname, Password, IP, Subnet, Gateway, and DNS.

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

Before you begin

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

Note: Depending on user settings such as browser updates and other factors not related toPowerPath/VE, some internet browsers might not download the Dell EMC PowerPathManagement Appliance OVA file correctly. If that occurs, try downloading the OVA filewith 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 minimizedeployment time. Deployment time should take approximately 5 to 15 minutes. Installationacross 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 sameunique IP address specified in the served license file. Fully qualified server name; this should bethe 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 VMwareenvironment.

2. Navigate to File > Deploy OVF Template.

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



https://www.dell.com/support



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

7. In Name and Location:

a. Type Name: ( Dell EMC PowerPath Management Appliance VM) can be anything, norestrictions.

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 andthen 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 tochange the hostname, delete the appliance and redeploy it with the new hostname. If youneed to change the hostname for a longer running appliance, the preferred method is toset 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 dateand time.

For example,

pool.ntp.org

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



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

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

The static IP address for the appliance should be the unique IP address specified in theserved 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 nameservers (DNS). The appliance does not validate hostnames. Hostnames not registeredwith 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 Onafter Deployment.

14. Click Finish.

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

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

About this task

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

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 take few minutes tostart for the first time depending on the environment. You can monitor the progress on thevSphere 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 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 thedeployment.

4. Verify the services.

Deploying the Dell EMC PowerPath Management Appliance (TBZ)Deploy the Dell EMC PowerPath Management Appliance as a Dockerized container from a TBZfile.

Before you begin

Download the Dell EMC PowerPath Management Appliance New Deployment Docker file from DellEMC 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 PowerPathManagement Appliance TBZ file correctly. If that occurs, try downloading the file with adifferent internet browser or check the browser settings.

Procedure

1. Import the container image.

l cat <package> | docker import - <container_image_name>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 following steps:





l Use the docker run command. Use this method if you do not have the DockerCompose 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 is deployed.

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

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

n License files export location: Location on the docker host where the License files areexported for persistence.

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

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

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

n Port 15672 is used for accessing rabbitmq GUI.

n Container Image: container image for PowerPath Management Appliance.

To turn interactive mode to daemon mode, press ctrl-p+ctrl-q. This action allows you toexit out of the container after running the docker run command.

To stop the container, run exit.

Run sudo service docker restart ; sleep 10; if the iptables issue is seen afterrunning 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 ManagementAppliance package to the Docker host.

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

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 License files areexported for persistence

n pathToPersistTomcatLogs: Location on the docker host where Tomcat logs filesare exported for persistence

n pathToPersistdatacollectorLogs: Location on the docker host where Datacollectorlogs files are exported for persistence



n pathToPersistdatabase: Location on the docker host where the database files areexported 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 PowerPath Management Appliance, attach to thecontainer.

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 theFQDN of the Appliance Virtual Machine or its IP address.

l Log in to the PowerPath Management Appliance web console.

Docker container deploymentIf 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 containerfrom the PowerPath Management Appliance container image. This image was previously importedby the user.

Deploying the Dell EMC PowerPath Management Appliance (VHD)Deploy the PowerPath Management Appliance from a VHD file using a Windows Hyper-Vsupported host.

Before you begin

l Download the PowerPath Management Appliance New Deployment VHD file from the DellEMC Online Support.

Note: Depending on user settings such as browser updates and other factors that are notrelated to PowerPath/VE, some browsers might not download the PowerPathManagement Appliance VHD file correctly. If that occurs, try downloading the VHD filewith a different browser or check the browser settings.

l Details of the Hyper-V server where you are installing the virtual appliance.

l Details of the drive location you can use for VM deployment.

l For IPv4 and IPv6:

n Static IP address to assign to your appliance - This IP address should be the same unique IPaddress that is specified in the served license file.

n Fully qualified server name - This server name should be the same Server name that isspecified in the served license file.

n Gateway

n Netmask (IPv4 only)

n Prefix length (IPv6 only)

n DNS servers





l NTP (time) server IP address

l Password for the virtual appliance

About this task

Perform the following tasks to deploy PowerPath Management Appliance on Windows Hyper-Vsupported host:

l Deploy the virtual machine.

l Create an ISO image.

l Deploy the appliance on the virtual machine.

Deploy the virtual machineThe Hyper-V bundle must be available in the local server. Copy the bundle to the Hyper-V host, ifthe file was downloaded using a different server.

Before you begin

The vhd.zip file contains the following files which are required for Hyper-V PPMA deployment:

l OVF Property Editor Tool

l PowerPath.x86_64-2.6.0.0.30.ovf template file

l VHD hard disk image file

You can either create your own path for deploying the virtual machine or choose the defaultdirectory when deploying the virtual machine. If you create a custom directory for deployment,copy the VHD hard disk image file to the directory. This task ensures that all the details of PPMAvirtual machine are available in the same location.

Procedure

1. In Hyper-V manager, click New > Virtual Machine.

2. Click Next on the Before You Begin screen.

3. Enter the required name for the virtual machine on the Specify Name and location page,and then click Next.

If you want to use the custom directory which you have created, then enable the Store the virtualmachine in a different location checkbox and browse to the required location.

4. In the Specify Generation page , select Generation 1, and then click Next.

5. In the Assign Memory page, enter the memory that is required for the PPMA, and thenclick Next.

The recommended memory size is 4098 MB.

6. In the Configure Networking page, select the network adapter from the dropdown box,and then click Next.

7. In the Connect Virtual Hard disk page, select Use an existing virtual hard disk option, andbrowse to the VHD Hard disk image file that you have extracted from the downloaded .zipfile. Click Next and then Finish.

Results

The PPMA virtual machine is created.



ISO image creationISO image is created using OVF Property Editor tool which needsPowerPath.x86_64-2.6.0.0.30.ovf template file. This file contains fields to enter the requiredNetwork Parameter for the PPMA VM.

Before you begin

Procedure

1. Open the OVF Property Editor tool. Select the File from the Menu and click Open.

2. Select the downloaded .ovf file from the local drive.

3. The OVF Property Editor tool takes the product .ovf file as input and displays a list of userconfigurable properties that are defined in the .ovf file.

4. In Deployment properties

a. Set the "Appliance fully qualified hostname"

For example,

myHost.emc.com

The hostname of the appliance cannot be changed after deployment. If the hostnamemust be changed, delete the appliance and redeploy it with the new hostname. If thehostname for a longer running appliance must be changed, set up an alias in your domainname 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 dateand time.

For example,

pool.ntp.org

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

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

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

The static IP address for the appliance should be the unique IP address that is specifiedin the served license file. To change the IP address of the appliance after deployment,redeploy 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



Independently register the hostname for the appliance with the domain name servers(DNS). The appliance does not validate hostnames. Hostnames that are not registeredwith the corresponding DNS may prevent normal operation.

5. Click ISO to create the ISO file. This ISO file can be saved to any required location.

Deploy the Dell EMC PowerPath Management Appliance on Windows Hyper-V hostThe created ISO file is mounted on the virtual machine to deploy the PowerPath ManagementAppliance.

About this task

Procedure

1. Mount the ISO file on the virtual machine using the image file option.

Make sure that the virtual machine is switched off when the ISO is being mounted.

2. Turn on the virtual machine to complete the deployment.

The virtual machine detects the ISO file and copies the file to /opt/vmware/etc/vami/ovfEnv.xml file. The appliance works on all the required configurations automatically.

After you finish

Deployment takes 2 minutes to 3 minutes for completion. Use one of the following methods toverify if the deployment is successful:

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

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

service tomcat status



CHAPTER 2

Configuring PowerPath Management Appliance


l Logging into the appliance using SSH (OVA/VHD deployment)............................................ 20l Changing the PowerPath Management Appliance password................................................. 20l Port reservation for Dell EMC PowerPath Management Appliance....................................... 20l Adding a PowerPath host.......................................................................................................21l Adding a VMware vCenter server.......................................................................................... 22l Edit VMware vCenter user credentials.................................................................................. 23l Remove a VMware vCenter server........................................................................................ 23l Change the interval at which to poll the PowerPath/VE hosts.............................................. 23l Setting up RabbitMQ messaging over AMQP ....................................................................... 24l Registering and enabling a vCenter Plug-in........................................................................... 24l Using the self-signed certificate that installs with PowerPath Management Appliance.........25l Creating a CSR and self-signed certificate using OpenSSL...................................................25l Installing an SSL certificate on the PowerPath Management Appliance................................26l SRS/VE overview..................................................................................................................27l PowerPath Management Appliance Integration with SRS/VE .............................................. 27l Enabling or disabling SRS/VE in PowerPath Management Appliance.................................... 28l Email Alert overview..............................................................................................................28l Enabling or disabling Email Alert in PowerPath Management Appliance................................ 28l Customizing Email Alert in PowerPath Management Appliance.............................................29l Creating a non-root user....................................................................................................... 29l Changing the password for a non-root user.......................................................................... 30l Changing or Deleting a non-root user....................................................................................30l Creating a RabbitMQ user.....................................................................................................30l Changing or Deleting a RabbitMQ user..................................................................................30


Logging into the appliance using SSH (OVA/VHD 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 areautomatically deployed using the virtual appliance.

About this task

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

Procedure

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

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 passwordAbout this task

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

Procedure

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

Port reservation for Dell EMC PowerPath ManagementAppliance

Reserve the following port numbers for Dell EMC PowerPath Management Appliance:

About this task

Table 2 Reserved port numbers and their purposes

Source Destination TransportProtocol

Source Port DestinationPort

Function

PowerPathManagementAppliance

ESXi Hosts TCP Dynamic(Range ofportsavailable)

5989 Port forPowerPathManagementAppliance toESX hostcommunication.


vCenterServer

TCP Dynamic(Range ofportsavailable)

443 Port forPowerPathManagementAppliance tovCentercommunication



Table 2 Reserved port numbers and their purposes (continued)

Source Destination TransportProtocol

Source Port DestinationPort

Function


Non-ESXiHosts

TCP Dynamic(Range ofportsavailable)

9083 Port forPowerPathManagementAppliance tonon-ESXi hostscommunication.


ELMS TCP(loopbackaddress)

Dynamic(Range ofportsavailable)

27010 Port forPowerPathManagementAppliance toELMScommunication.

ESXi Hosts PowerPathManagementAppliance

TCP 5989 Dynamic(Range ofportsavailable)

Port for ESXhost toPowerPathManagementAppliancecommunication.

vCenterServer



Port forvCenterPowerPathManagementAppliancecommunication.

Non-ESXiHosts



Port for non-ESXi hosts toPowerPathManagementAppliancecommunication.

ELMS PowerPathManagementAppliance

TCP(loopbackaddress)

27010 Dynamic(Range ofportsavailable)

Port for ELMSto PowerPathManagementAppliancecommunication.

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

About this task

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

Note: PowerPath Management Appliance requires that the Management Component feature isenabled 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 PowerPath Management Appliance for license deployment andPowerPath monitoring.

Before you begin

In order to discover vCenter, your vCenter user must contain the following privileges. The usershould 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 vCenterserver.

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

Note: If the privileges were set after adding the vCenter to PowerPath Management Appliancethen wait for the next vCenter poll interval or remove the vCenter from PowerPathManagement 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.

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

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

Refer to Registering and enabling a vCenter Plugin.



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

About this task

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 PowerPath Management AppliancevCenter 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 select Remove.

3. Click OK.

Results

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

Note: When a VMware vCenter server is removed from the virtual appliance, thePowerPath/VE licenses for the ESXi hosts managed by that VMware vCenter server are notremoved. The trial licenses applied to any of PowerPath/VE hosts remain continue 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/VE hostsUse this procedure to change the interval at which PowerPath Management Appliance polls theESXi hosts for changes.

About this task

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, youshould increase default polling interval. For a large configuration, polling interval should be setto 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.

About this task

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

Note: Third party AMQP clients have to either run from within PowerPath ManagementAppliance or implement mechanisms to proxy the AMQP traffic.

Procedure

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

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

2. Subscribe to the RabbitMQ queue.

The subscription requires a RabbitMQ client.

Registering and enabling a vCenter Plug-inThe vCenter plug-in provides a minimal view of the PowerPath Management Appliance webconsole. Only the detail of ESXi hosts belonging to the current instance of a vCenter server aredisplayed.

About this task

The Web client plug-in can be registered on the vCenter server in two ways. Select one of thefollowing options:

l Register the plug-in while adding or editing the vCenter properties in the PowerPathManagement Appliance. Browse to the Inventory > vCenter Servers tab, select the RegisterPlugin 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 thepage.

Results

Access the plug-in after registering. Use the short-cut, PowerPath Management Appliance,located in the vCenter Web client.

Note: If you use the default self-signed certificate of PowerPath Management Appliance, openthe PowerPath Management Appliance web console using FQDN (example: https://<FQDN>)in a new tab to accept the certificate before accessing the plug-in through the vCenter webclient.



Note: The vCenter PPMA plug-in can be viewed through vCenter Flex view only as thevCenter plug-in does not support HTML view.

Using the self-signed certificate that installs with PowerPathManagement Appliance

PowerPath Management Appliance ships with a Dell EMC issued 2048-bit SSL certificate. Thiscertificate is used to generate or regenerate a host-based SSL certificate and key using thehostname at PowerPath Management Appliance start time.

About this task

This certificate expires 821 days after PowerPath Management Appliance installation.

Note: Self-signed certificate that is generated during PPMA installation is prone to "SSLCertificate Cannot Be Trusted" medium risk vulnerability. Purchase or generate a certificatefrom a Certificate Authority to avoid this vulnerability.

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

About this task

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

Consult your companies' information security department for assistance with SSL certificate andkey 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 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, localityname, and other attributes of the certificate.

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

If you are getting a certificate signed by a third-party certificate authority (CA) then this isyour 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 PowerPath Management Appliance

Installing an SSL certificate on the PowerPath ManagementAppliance

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 Appliancehost. 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 rootusing secure shell.

l On OVA deployment:

ssh -l root hostname

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

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 as separate files orcreate a single PEM file from all of the certificates by concatenating the certificate PEMfiles together. All of the certificates in the CA chain must be in PEM format beforeconcatenating them into a single file. Their key will be the bottom most key in thecertification chain (this is called the key for the leaf certificate).

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



l For the certificate and key file, modify the SSLCertificateFile and SSLCertificateKeyFilelines.

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 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 beenconcatenated 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 verifythe certificate.

https://hostname_or_ip_address/LicenseReportingApplication/

SRS/VE overviewSecure Remote Services/Virtual Edition (SRS/VE) can provide connectivity and remoteserviceability solutions for automated Connect Home and Remote Service activities.

The service is available through an IP-based solution that is enhanced by a comprehensive securitysystem.

PowerPath Management Appliance supports the Usage Intelligence feature of SRS/VE whendeployed into the SRS Virtual Edition Gateway. Usage Intelligence (UI) is available for thecollection, transfer, analysis, and reporting of usage data for Dell EMC customers.

The PowerPath Management Appliance Release Notes provides the versions of SRS/VE qualifiedwith PowerPath Management Appliance.

PowerPath Management Appliance Integration with SRS/VEPowerPath Management Appliance integrates with the SRS RESTful services providing UsageIntelligence (UI).

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

With SRS Virtual Edition, PowerPath Management Appliance can add itself as a device to SRS/VE,and send license usage reports to SRS/VE, every 24 hours. It can also update the device IP, deletethe device, and keep live messages every 60s.



Enabling or disabling SRS/VE in PowerPath ManagementAppliance

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

Procedure

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

SRS/VE is enabled by default.Note: To disable SRS/VE, click Disable.

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

3. Click Update.

Results

The procedure adds PowerPath Management Appliance as a device to SRS/VE, and reportingserved licenses usage begins.

Note: You must have a PowerPath UI-enabled served or subscription license to receive licenseusage reports.

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

For additional information about SRS/VE, see the SRS/VE Dell EMC Online Support product page.

Email Alert overviewThe email alert feature, when enabled, triggers a host-based alert to the recipients' email ids whenthere 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. Thehost-based email alert triggers from mailto:[email protected] and it displays the host statewith date and time, hostname, status, LUN state, Path/Bus state, PowerPath version, and licensestate.

Enabling or disabling Email Alert in PowerPath ManagementAppliance

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

Procedure

1. Browse to System > Configure Email Alerts.

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.

If there are multiple recipients, enter comma-separated email Ids.




mailto:[email protected]

5. Click Test Email Setup.

6. Click Save.

A pop-up window is displayed for confirmation.

7. Click OK.

8. Click Save.

Results

The procedure enables email alert functionality to the PowerPath Management Appliance and thecustomer starts receiving host-based email alerts when there is a license expiry or change involume, path, and bus.

Note: For the email alert functionality to enable or disable, you must click Save followed byOK.

Customizing Email Alert in PowerPath Management ApplianceThe Customize Configuration feature provides option to disable or enable email notification foreach host.

Procedure

1. Browse to System > Configure Email Alerts.

The email alert custom configuration is disabled by default.

2. Click Enable to enable the custom configuration functionality.

3. Click Update, and then click Ok.

4. In the Manage Hosts Here section, select the hosts which require email notifications. ClickDone.

A pop-up is displayed which confirms the hosts for which the email alerts are enabled. ClickOk to close the pop-up.

Results

The email notifications are enabled for the hosts that are selected in the Manage Hosts Heresection.

Creating a non-root userUse this procedure to create a non-root user.

Procedure

1. Log in to the PowerPath Management Appliance using the root user credentials.

2. Go to the Security tab > PowerPath User.

3. Click Change.

4. Enter the New Login ID and Password.

5. Click Save.

Creating a non-root user is done.

6. Log in to the PowerPath Management Appliance with the newly created non-root usercredentials.



Changing the password for a non-root userUse this procedure to change the password for a non-root user.

Procedure

1. Log in to the PowerPath Management Appliance using the non-root user credentials.

2. Go to the Security tab > Change Password.

3. Enter the Old Password and the New Password.

4. Click Change.

The change of password for the non-root user is done.

Changing or Deleting a non-root userUse this procedure to change or delete a non-root user.

Procedure

1. Log in to the PowerPath Management Appliance with root user credentials.

2. Go to the Security tab > PowerPath User.

3. Click Change/Delete on non-root user ID display.

The changing or deleting of the non-root user is done.

Creating a RabbitMQ userUse this procedure to create a RabbitMQ user.

Procedure


2. Go to the Security tab > RabbitMQ.

3. Click Change.

4. Enter the Login ID and Password.

5. Click Save.

Creating a RabbitMQ user is done.

Changing or Deleting a RabbitMQ userUse this procedure to change or delete a RabbitMQ user.

Procedure


2. Go to the Security tab > RabbitMQ.

3. Click Change/Delete.

The changing or deleting of the RabbitMQ user is done.



CHAPTER 3

Configuring the Management Component

This chapter contains the following topics:

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


Configuring Management Component on Windows Using GUIThe Management Component is included in the Dell EMC PowerPath package. Separateinstallation is not required. This procedure describes how to configure the ManagementComponent.

About this task

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

Procedure

1. In the Enable Management Component checkbox, ensure that Enable is selected. It shouldbe 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 andindicated as Registered under the Port Number field.

l Change the port value if required. For example, if another application is using the defaultport. The valid, alternate port range is 49152–65535 and indicated as Alternatives underthe 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 EMCrecommends 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 thefollowing:

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

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

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

5. Click finish.

Configuring Management Component on LinuxThe Management Component is included in the Dell EMC PowerPath package. Separateinstallation is not required. This procedure describes how to configure the ManagementComponent.

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.

b. The Management Component is disabled by default. To enable the ManagementComponent service using default configuration parameter values, type 1 and 13 to



confirm and save. Then type the number option to exit, save, and restart theManagement Component.

Dell EMC PowerPath Virtual Appliance recommends using default configuration parameters.To modify the configuration parameters, go to Modifying Configuration Parameters on Linuxand Unix.

2. Verify that emcp_mond is running and that Dell EMC PowerPath Management Componentis started. Type:

> pgrep -xl emcp_mond Alternatively, verify the messages log for successful ManagementComponent 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 hosts where you haveinstalled 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 Dell EMC PowerPath package. Separateinstallation is not required. This procedure describes how to configure the ManagementComponent.

About this task

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

2. Start the SNMP service.

svcadm enable -s system/emcpower/emcp_mond



3. Restart the Dell EMC 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 Dell EMC PowerPathpackage. Separate installationis not required. This procedure describes how to configure the Management Component.

Before you begin

To access the Management Component, go to Inventory > Dell EMC PowerPath Hosts and selectMgmt 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 willread the sample configuration file.

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

Dell EMC PowerPath Virtual Appliance recommends using default configuration parameters.To modify the configuration 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_mond onManagement Component

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

Before you begin

To access the Management Component, go to Inventory > Dell EMC PowerPathHosts and selectMgmt 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 ManagementComponent service using default configuration parameter values, type 1 and 6 to confirmthe changes and save. Then type the number option to exit, save, and restart theManagement Component.

Dell EMC PowerPath Virtual Appliance recommends using default configuration parameters.To modify the configuration parameters, go to Modifying Configuration Parameters on Linuxand Unix.

2. To verify that the Management Component is installed and started, check that the systemlog 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 Troubleshooting emcp_mond onManagement Component for more information.

Configuring Management Component on AIXThe Management Component is included in the Dell EMC PowerPath package. Separateinstallation is not required. This procedure describes how to configure the ManagementComponent.

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.

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

Dell EMC PowerPath Virtual Appliance recommends using default configuration parameters.To modify the configuration 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 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 byanother application. Note that the Management Component defaults to port 9083 if theport number entered is already in use. The default and recommended port number is9083. 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 Dell EMCPowerPath release notes for your platform provide information on SNMP support.

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

Troubleshooting emcp_mond on Management ComponentTo 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_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_mond



Start and stop emcp_mond daemon on HP-UX

To stop the emcp_mond daemon, run:

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

/sbin/init.d/emcpmond start



CHAPTER 4

Monitoring PowerPath hosts

This chapter includes the following topics:

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


Overview of PowerPath host monitoringThe PowerPath Monitor, available in versions 2.0 SP1 and later, provides host monitoringcapabilities including device/path monitoring. The monitor displays PowerPath volume, path, andbus 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 ESXihosts. Non-ESXi PowerPath hosts are organized under their corresponding user-defined hostgroups (created from the inventory tab). ESXi hosts are grouped under corresponding vCenter towhich they belong. Entries in the host tree view are highlighted 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 the status of thedevices and paths of the host, with configured PowerPath options, current host state, and LUNand Path summary details display. Host state warnings are highlighted at the top and bottom ofSummary view.

Table 3 Fields and descriptions

Parameters 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 PowerPathManagement Appliance (via DNS)

PowerPath Version Version of PowerPath running on thehost

Status PowerPath Management Applianceconnection status to the managementcomponent on the host

License License is valid or host is unlicensed

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



Table 3 Fields and descriptions (continued)


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

LUN view

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



Table 4 Fields and descriptions


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 view

BUS view shows the association between HBA Ports > HBA IP > Array Name > Array Ports alongwith 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 view

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



CHAPTER 5

Managing PowerPath licenses


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


Add a PowerPath/VE licenseAdd 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 localmachine.

About this task

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

Note: You can also add a PowerPath/VE license from the PowerPath Management AppliancevCenter 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 thelicense key.

c. Click OK.

4. Click OK.

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

About this task

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

Note: You can also delete a PowerPath/VE license from the PowerPath ManagementAppliance 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 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 asunmanaged 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 stateon page 48 for more information.

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

About this task

Note: You can also view the PowerPath/VE licenses from the PowerPath ManagementAppliance 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 isdisplayed.

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.

Export unlicensed PowerPath and PowerPath/VE host detailsExport 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 in PowerPathLicenses > 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 PowerPath Management Appliance

This section contains the following topic:

l Upgrading from PowerPath Management Appliance 2.1 and earlier to 2.6 (script)................50l Upgrading from PowerPath Management Appliance 2.1 SP1 or later to 2.6 (OVA/VHD)....... 51l Upgrading from PowerPath Management Appliance 2.1 SP1 and earlier to 2.6 (TBZ)........... 52


Upgrading from PowerPath Management Appliance 2.1 andearlier to 2.6 (script)

You can upgrade from PowerPath Management Appliance Version 2.1 and earlier to 2.6 using theexport_ppma_config script.

Before you begin

l Download the PowerPath Management Appliance package from Dell EMC Online Support. Thispackage contains the upgrade script that is required to upgrade the PowerPath ManagementAppliance.

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

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

About this task

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

For script-based upgrade from PowerPath Virtual Appliance 1.2 to PowerPath ManagementAppliance 2.0, refer to the video on the PowerPath EMC Community Network for a demonstrationon 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 ManagementAppliance 2.x VM.

2. SSH into the PowerPath Management Appliance 2.x VM and then run the script to exportthe PowerPath Management 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 ora 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 off the PowerPath Management Appliance 2.x VM.

Note: Do not delete the PowerPath Management Appliance 2.x VM until aftersuccessful PowerPath Management Appliance import.




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

6. Deploy PowerPath Management Appliance 2.6 with the same PowerPath ManagementAppliance Deployment Parameters as PowerPath Management Appliance 2.x.

7. Power on the PowerPath Management Appliance 2.6 VM.

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

After you finish

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

Upgrading from PowerPath Management Appliance 2.1 SP1 orlater to 2.6 (OVA/VHD)

Before you begin

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

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

If the passphrase is lost, recreate the lockbox and re-enter the PowerPath/VE hostinformation and credentials to perform rpowermt commands, or supply the host usernameand 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 DellEMCPower.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 only ./applianceUpdate.

Wait for the update to finish.

8. Restart PowerPath Management Appliance.





Upgrading from PowerPath Management Appliance 2.1 SP1and earlier to 2.6 (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.6.

Before you begin

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

l The CST Standalone Lockbox passphrase is required after an upgrade from earlier versions ofPowerPath Management Appliance to the current version .You are prompted to reenter the passphrase when you attempt to run the first rpowermtcommand on the appliance.

If the passphrase is lost, re-create the lockbox and reenter the PowerPath/VE hostinformation and credentials to perform rpowermt commands, or supply the host usernameand password on the rpowermt command line.

Procedure

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

2. Stop the running container.

docker stop <container_ID>

3. Import the PowerPath Management Appliance 2.6 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 thecontainer, go to System > Settings > Import Config ZIP and then import thePowerPath_management_appliance.zip file.

6. Remove the previous container and image.

docker rm <container_ID>

docker rmi <old_container_image_name>





CHAPTER 7

Uninstalling PowerPath Management Appliance


l Uninstalling PowerPath Management Appliance (OVA deployment)..................................... 54l Uninstalling PowerPath Management Appliance (VHD deployment)..................................... 54l Uninstalling PowerPath Management Appliance (TBZ deployment)......................................54


Uninstalling PowerPath Management Appliance (OVAdeployment)

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

About this task

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 windowfor 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 (VHDdeployment)

About this task

This procedure applies only to Windows Hyper-V VHD deployments of PowerPath ManagementAppliance.

Using Hyper-V Manager, the PowerPath Management Appliance can be shut down and removedfrom the Hyper-V inventory.

Procedure

1. Open the Hyper-V manager.

2. Right-click the Dell EMC PowerPath Management Appliance virtual machine in the VirtualMachines pane. Select Turn Off.

3. Right-click the PowerPath Management Appliance virtual machine in the Virtual Machinespane. Select Delete.

Uninstalling PowerPath Management Appliance (TBZdeployment)

About this task

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

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>



APPENDIX A

Types of licenses and license status


l Types of PowerPath/VE licenses.......................................................................................... 58l License status....................................................................................................................... 59


Types of PowerPath/VE licensesThe PowerPath/VE for VMware vSphere supports the following licenses:

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 the license configurationfile on the PowerPath/VE ELMS and it manages the licenses for all the PowerPath/VE hostsfor which the license was generated.

Unserved license

The Unserved licensing model binds PowerPath/VE to a specific vSphere host. Moreaccurately, to a vSphere unique system ID. An Unserved license is only valid for the specificvSphere host for which it was generated. An Unserved license is static; it cannot be used onanother 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 that is connected to PowerMax FX enabled arrays. Formore information about FX licenses, see PowerMax documentation.

Master Key license

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

Trial license

The PowerPath Management Appliance comes with a 45-day trial license period for anunlimited number of PowerPath/VE version hosts. The addition of Permanent or Temporarylicense keys to the PowerPath/VE hosts that are using Trial license, transition into therespective licenses that are added.

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

Subscription license

Subscription licenses provide an option for the customer to try PowerPath before buying apermanent key. Two types of subscriptions are available.

l 1-year license

l 2-year license

Similar to Served license licensing mode, the Subscription licensing model also uses a licenseserver to store, distribute, and manage PowerPath/VE licenses. In subscription license model,the Electronic License Manager System (ELMS) distributes the PowerPath/VE licenses tovSphere hosts. Install the license configuration file on the PowerPath/VE ELMS. ThePowerPath/VE ELMS manages the licenses for all the PowerPath/VE hosts for which thelicense was generated.



OverdraftServed licenses contain an overdraft count which provides a temporary buffer of 10% above thecount of licenses purchased.

The overdraft feature provides a temporary buffer license when the number of PowerPath/VEhosts exceed the number of PowerPath/VE licenses. The overdraft count applies to the Servedlicenses 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



APPENDIX B

Troubleshooting

l Troubleshooting.................................................................................................................... 62


TroubleshootingThe following table lists the PowerPath Management Appliance installation troubleshootingscenarios:

Symptoms Prevention, resolution, or workaround

The PowerPath Management Appliance plug-in icon is invisible in vCenter

Perform the following steps:

1. Verify if PowerPath ManagementAppliance host FQDN resolution existsbetween vCenter and PowerPathManagement Appliance.

2. Manually unregister vCenter plug-in fromthe PowerPath Management ApplianceGUI

3. Remove PowerPath plug-in entries fromvCenter.For vCenter 6.5/6.7, do the following:

a. Log in to the affected vSpherevCenter server.

b. Navigate to /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/.

c. Run rm -rfcom.emc.asd.powerpath* to

clean the PowerPath plug-in entries.

d. Restart the vSphere client serviceusing /usr/lib/vmware-vmon/vmon-cli -r vsphere-client.

Note: The vCenter GUI isunavailable for few minutes whenthe vSphere client service isrestarted

e. After vSphere client service restarts,manually register the plug-in from thePowerPath Management ApplianceGUI.

For vCenter 6.0, do the following:

a. Log in to the affected vSpherevCenter server.

b. Navigate to /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/.

c. Run rm -rfcom.emc.asd.powerpath* to

clean the PowerPath plug-in entries.

Troubleshooting


Symptoms Prevention, resolution, or workaround

d. Navigate to /var/lib/vmware/vsphere-client/vc-packages/vsphere-client-serenity/.

e. Run rm -rfcom.emc.asd.powerpath* to

clean the PowerPath plug-in entries ifthey exist.

f. Stop the vSphere client service usingservice vsphere-client stop.

g. Start the vSphere client service usingservice vsphere-clientstart.

Note: The vCenter GUI isunavailable for few minutes whenthe vSphere client service isrestarted

h. After vSphere client service restarts,manually register the plug-in from thePowerPath Management ApplianceGUI.

4. Manually register the plug-in fromPowerPath Management Appliance GUIafter successful restart.

The PowerPath Management Appliance plug-in page does not load or an empty screen isdisplayed.

Perform the following steps:

1. Verify if the PowerPath ManagementAppliance host FQDN resolution existsbetween vCenter and PowerPathManagement Appliance.

2. Open a new tab and login to PowerPathManagement Appliance using FQDNname. Example: https://<FQDN name>/LicenseReportingApplication/

3. Relaunch the PowerPath ManagementAppliance plug-in from vCenter.

Troubleshooting


Troubleshooting


appliance dell emc powerpath management · 2020-05-23 · deploy the dell emc powerpath management...

Documents