enterprise storage integrator for sap landscape ......preface as part of an effort to improve its...

Enterprise Storage Integrator for SAPLandscape ManagementVersion 6.0

Administrator Guide300-014-915

REV 10

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

Published January 2019

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 Enterprise Storage Integrator for SAP Landscape Management 6.0 Administrator Guide

7Purpose........................................................................................................ 7Audience.......................................................................................................7Scope........................................................................................................... 7Related documentation................................................................................ 8Conventions used in this document.............................................................. 8Where to get help.........................................................................................9Your comments............................................................................................ 9

Enterprise Storage Integrator for SAP Landscape ManagementOverview 11Executive summary..................................................................................... 12Product overview........................................................................................ 12Installation overview....................................................................................14

Solution prerequisites 17Perform solution prerequisite tasks.............................................................18

Deploy and log in to the EHAC appliance 19Deploy the Linux-based EHAC appliance.................................................... 20

Deploy the Linux-based EHAC virtual appliance.............................20Deploy the bare metal Linux-based EHAC appliance......................22Initial configuration of the Linux-based EHAC appliance................23Log in and verify the EHAC appliance deployment.........................25Log in to EHAC for the first time................................................... 27Log in to EHAC with administrative credentials............................. 27

Configure Storage and Virtual Systems in EHAC 29Configure NAS or file-based storage.......................................................... 30

Add file or NAS storage systems................................................... 30Update file storage systems.......................................................... 30Remove file storage systems..........................................................31

Configure SAN or block-based storage....................................................... 31Add REST servers ......................................................................... 31Add and configure WBEM servers................................................. 34Update or remove WBEM servers................................................. 35Enable advanced configuration for VMAX and VMAX3 arrays....... 35Perform prerequisite tasks to view WBEM-managed block storagesystems pools................................................................................ 36View WBEM-managed block storage systems pools......................36View WBEM-managed block storage systems volumes................. 36Add an XtremIO array.................................................................... 36Add VPLEX storage details............................................................ 37

Change the global access level................................................................... 38Add VMware vCenter virtual systems and ESXi hosts................................ 39

Preface

Chapter 1

Chapter 2

Chapter 3

Chapter 4

CONTENTS

Enterprise Storage Integrator for SAP Landscape Management 6.0 Administrator Guide 3

Manage User Accounts 41Manage users............................................................................................. 42

Add a user......................................................................................42Update a user password................................................................ 42Update an administrator password................................................ 42Remove a user............................................................................... 43

Configure access control............................................................................43Grant access to file storage systems and pools............................. 43Revoke access to file storage systems and pools...........................44Grant access to WBEM-managed block storage systems and pools..45Revoke access to WBEM-managed block storage systems andpools..............................................................................................46Grant access to REST-managed VMAX storage systems and pools..46Revoke access to REST-managed VMAX storage systems and pools...................................................................................................... 47Grant access to XtremIO storage systems.................................... 48Revoke access to XtremIO storage systems..................................48Grant access to Unity storage systems......................................... 48Revoke access to Unity storage systems.......................................48

Secure user data........................................................................................ 49

Install the ESI plug-in on the SAP LaMa server 51Perform prerequisite tasks to deploy the ESI plug-in..................................52Deploy the ESI plug-in................................................................................ 53Add an ESI storage manager...................................................................... 55Cache storage information from SAP systems........................................... 56

Utilities 59Start and stop the EHAC service................................................................60Change EHAC Deployment Console settings..............................................60Use EHAC appliance aliases .......................................................................60Configure WildFly by restoring the database from a backup....................... 61Back up and restore an Apache Derby database......................................... 62Monitor EHAC server activities by using logs............................................. 63Configure ESI logs......................................................................................64Collect SRM, ViClient, and SAPACOSPREP logs....................................... 65Upgrade the ESI web service and apply hotfixes........................................ 66

Troubleshoot and clean up storage 67Troubleshooting......................................................................................... 68Clean up storage automatically after a clone fails....................................... 70

Install and configure Windows-based EHAC server 73Install the Windows-based EHAC server ....................................................74Install the Java Development Kit (JDK)...................................................... 74Install the Java Cryptography Extension.....................................................74Install the Apache database........................................................................ 74Install and configure WildFly as a Windows service.....................................75

WildFly troubleshooting tips.......................................................... 76Configure the Windows-based EHAC server.............................................. 76

Enable the EHAC Console to discover and configure storage........ 77

Chapter 5

Chapter 6

Chapter 7

Chapter 8

Appendix A

CONTENTS


Configure the database and update the WildFly configuration files...77

Configure Windows-based EHAC web service in HTTPS mode.................. 78Configure residue cleanup in Windows-based EHAC server........................79Start the Windows-based EHAC server......................................................79

CONTENTS


CONTENTS


Preface

As part of an effort to improve its product lines, Dell EMC periodically releasesrevisions of its software and hardware. Therefore, some functions that are describedin this document might not be supported by all versions of the software or hardwarethat are currently in use. The product release notes provide the most up-to-dateinformation about product features.

Contact your Dell EMC technical support professional if a product does not functionproperly or does not function as described in this document.

Note

This document was accurate at publication time. To ensure that you are using thelatest version of this document and the release notes, go to Dell EMC Online Support.

PurposeThis document describes how storage administrators can deploy, configure, andmanage the EHAC appliance. It also describes how to create user accounts in theEHAC console, add Unisphere REST API servers, assign and manage storage systemsthat are assigned to users, grant and revoke read or write access for storage systemsand pools, and add ESXi servers to the EHAC database.

This document also describes how SAP administrators copy and deploy the EnterpriseStorage Intergrator (ESI) plug-in on the SAP NetWeaver Java Stack, where the SAPLandscape Management (SAP LaMa) add-on is running.

AudienceThis document is for internal Dell EMC personnel, partners, and customers. Theintended audience is storage, network, VMware, and SAP administrators who want tomanage and assign storage space to EHAC users who work on SAP LaMa andconfigure the SAP LaMa to work with ESI.

ScopeThis storage administrator guide is intended to provide an overview of ESI for SAPLaMa and includes the following information:

l ESI for SAP LaMa overview

l Solution prerequisites

l Deploy and log in to the EHAC appliance

l Configure Storage and Virtual Systems in EHAC

l Manage user accounts

l Install ESI plug-in on the SAP LaMa server

l Utilities


https://www.dell.com/support/home/us/en/04

l Troubleshoot and clean up storage

Related documentationThe following documents, which are available on Dell EMC Online Support and on DellEMC.com, provide additional relevant information. Access to these documents isbased on your login credentials. If you do not have access to the following documents,contact your representative:

l Enterprise Storage Integrator for SAP Landscape Management Storage DeploymentGuide

l Enterprise Storage Integrator for SAP Landscape Management Storage Release Notes

l Enterprise Storage Integrator for SAP Landscape Management Storage User Guide

Conventions used in this documentDell EMC uses the following conventions for special notices:

NOTICE

NOTICE is used to address practices not related to personal injury.

Note

A note presents information that is important, but not hazard-related.

Dell EMC uses the following type style conventions in this document:

Table 1 Typographical conventions

Bold Used for names of interface elements, such asnames of windows, dialog boxes, buttons,fields, tab names, key names, and menu paths(what the user specifically selects or clicks).

Italic Used for full titles of publications referencedin text.

MonospaceUsed for:

l System output, such as an error messageor script

l System code

l Path names, filenames, prompts, andsyntax

l Commands and options

Monospace italicUsed for variables.

[ ] Square brackets enclose optional values.

| Vertical bar indicates alternate selections —the bar means “or.”

Preface


Table 1 Typographical conventions (continued)

{ } Braces enclose content that the user mustspecify, such as x or y or z.

... Ellipses indicate nonessential informationomitted from the example.

Where to get helpYou can obtain Dell EMC support, product, and licensing information as follows.

Product informationFor documentation, release notes, software updates, or information about Dell EMCproducts, go to Dell EMC Online Support.

Technical supportGo to Dell EMC Online Support. You see several options for contacting Dell EMCTechnical Support. To open a service request, you must have a valid supportagreement. Contact your Dell EMC sales representative for details about obtaining avalid support agreement or with questions about your account.

Your commentsYour suggestions help us continue to improve the accuracy, organization, and overallquality of the user publications. Send your opinions of this document to:

Send your comments about this document to Feedback.

Preface




mailto:[email protected]?subject=Enterprise%20Storage%20Integration%20for%20SAP%20Landscape%20Management%20Administration%20Guide%20P/N%20300-014-915

Preface


CHAPTER 1

Enterprise Storage Integrator for SAPLandscape Management Overview

This chapter presents the following topics:

l Executive summary.............................................................................................12l Product overview................................................................................................12l Installation overview........................................................................................... 14

Enterprise Storage Integrator for SAP Landscape Management Overview 11

Executive summaryEnterprise Storage Integrator (ESI) for SAP Landscape Management (SAP LaMa) is asoftware solution that integrates Dell EMC storage systems with SAP LaMa. SAPadministrators can use the system provisioning processes such as clone, copy, andrefresh, of SAP LaMa, to create and manage copies of SAP systems, from productionto nonproduction systems. SAP environments can have multiple nonproduction testingand development systems. Automating the management of SAP system copies withthe use of a trusted storage-based cloning technology saves significant time andeffort, reducing the Total Cost of Ownership (TCO) of an SAP Landscape.

ESI 6.0 includes support for SAP instance-specific file systems that are based onblock, file, or both block and file combined (unified) on the same SAP system.

ESI for SAP LaMa also supports physical and virtual hosts on:

l Dell EMC VMAX3™ and PowerMax™ block, file, and unified storage arrays thatleverage service level objectives (SLO) storage provisioning

l Dell EMC XtremIO™ all-flash storage arrays

l Dell EMC Unity™ unified storage arrays

l Dell EMC VMAX™ block, file, or unified storage systems with Embedded NetworkAttached Storage (eNAS) and combined with Unity file storage system.

l Dell EMC VPLEX™ 5.5 systems

Note

See the Enterprise Storage Integrator for SAP Landscape Management Release Notes fora complete list of all new features and changes. Also, see the Enterprise StorageIntegrator for SAP Landscape Management Solution Simple Support Matrix (SSSM) for acomplete list of ESI for SAP LaMa supported environments.

Product overviewThe ESI for SAP LaMa solution uses individual Dell EMC software components tointegrate Dell EMC storage systems with SAP LaMa.

Software integration componentsThe following are the Dell EMC ESI for SAP LaMa components:

l Enterprise Storage Integrator plug-in—The ESI storage adapter plug-in (ESI plug-in) is a storage plug-in distributed as a Java Enterprise Archive (EAR) file Thefilename is esi_4_sap_lama_plugin.6.0.xx.ear, where xx is the patchlevel. The ESI plug-in complies with SAP LaMa storage manager specifications.

The ESI plug-in is deployed in the SAP NetWeaver Java stack application serverand integrates with the supported Dell EMC file and block storage systems.

The ESI plug-in provides storage management capabilities for SAP LaMa andenables SAP administrators to manage clones and snapshots of multiple SAPsystem instance-specific file systems stored on Dell EMC storage systems.

l Unisphere REST API—The ESI code contains storage specific REST APIs calls forDell EMC PowerMax, VMAX3, XtremIO, Unity, and VPLEX storage systems.

l Enterprise High-level Storage Administration Console (EHAC)—EHAC is apreconfigured Linux-based appliance (EHAC appliance) that provides a gatewayfor the ESI plug-in to connect to the ESI webservice that manages access to the

Enterprise Storage Integrator for SAP Landscape Management Overview


configured Dell EMC storage systems on the EHAC database. The storageadministrators uses EHAC to manage and connect users, Dell EMC storagesystems, vCenter, ESXi, and Unisphere servers, storage access control to storagesystems and pools, configure the REST API connections, and configure block, file,unified, and virtualized storage systems.Use the EHAC configuration console (EHAC console UI) to:

n Add and remove VMware vCenter and ESXi servers to and from the EHACdatabase

n Discover and configure storage area network (SAN) storage such as Dell EMCUnity™, Dell EMC PowerMAX™, VMAX3™, XtremIO™ All Flash arrays, andVPLEX™ storage systems

n Discover and configure network-attached storage (NAS), such as VMAX3 andPowerMax eNAS, and Unity file storage, in the EHAC database

n Discover and add Dell EMC Unity unified storage systems to the EHACdatabase

n Discover all Dell EMC storage systems and their pools, and set or removeaccess rights

n Create and delete administrator and ESI general users, and grant and revoketheir access to and from Dell EMC storage systems and storage pools,respectively

l Solutions Enabler and Enterprise Storage Library for SAP (ELSA)— Middlewaresoftware that is installed on all the SAP Hosts (SAP systems running on physicalor virtual hosts) with SAP instance-specific file systems from the Dell EMCstorage systems connected through the SAN-FC protocol.Solutions Enabler contains the Storage Resource Management (SRM) module thatincludes a SAP-specific shared library called Enterprise Storage Library for SAP(ELSA). ELSA is represented technically by the libsapacosprep_emc.xxx file.xxx refers to the extension of this file on different operating systemplatforms, .so for Linux, .o for AIX, and .dll for Microsoft Windows operatingsystems.

This solution uses Solutions Enabler to retrieve, precisely identify storage devices,server, HBAs, partitions, volume groups (vgs), and logical groups (lvs) that areused by SAP instance-specific file systems. It also mounts and unmounts them onthe physical(bare-metal) or VMware vSphere virtual SAP hosts.

The SAP Host Agent (SAP HA) and the SAP Adaptive Extensions (SAP AdExt)software integrates with Solutions Enabler/SRM/ELSA, and it is the onlyoperating system-specific component in the ESI for SAP solution. SAP instance-specific file systems, stored on SAN/FC-based storage volumes, are configured asmount points inside the SAP LaMa system instances, and the SAP HA, SAP AdExt,and ELSA integration is used to retrieve and upload these SAP instance-specificfile systems to SAP LaMa, and to mount and unmount them from the SAP hosts.

See the Dell EMC Simple Support Matrix on the Dell EMC support website to findsupported storage systems, their operating environment (OE) releases, and operatingsystem combinations.


Product overview 13

Figure 1 ESI for SAP LaMa storage adapter

Note

Solutions Enabler is not required for SAP instance-specific storage-based or server-based NFS-based file systems.

Installation overviewThe following table contains an ESI installation overview with the high-level steps thatare required to implement SAP LaMa with ESI.

Perform the implementation steps in the following order:



Table 2 Installation overview

Steps Chapter

Solution prerequisites 2

Deploy and log in to the EHAC appliance 3

Configure Storage and Virtual Systems inEHAC

4

Manage user accounts 5

Install ESI plug-in on the SAP LaMa server 6

Utilities 7

Troubleshoot and clean up storage 8


Installation overview 15

CHAPTER 2

Solution prerequisites

This chapter presents the following topic:

l Perform solution prerequisite tasks.................................................................... 18

Solution prerequisites 17

Perform solution prerequisite tasksFor information about the prerequisite tasks that you must perform, see the SolutionPrerequisites section in the Enterprise Storage Integrator for SAP LandscapeManagement Deployment Guide.

Solution prerequisites


CHAPTER 3

Deploy and log in to the EHAC appliance

This chapter presents the following topic:

l Deploy the Linux-based EHAC appliance............................................................20

Deploy and log in to the EHAC appliance 19

Deploy the Linux-based EHAC applianceThe EHAC appliance is the central ESI component. Starting with ESI 5.0, Dell EMCprovides the EHAC virtual appliance as a preconfigured Linux-based vSphere 6.0virtual machine (appliance).

With ESI 6.0, the EHAC appliance is delivered in two exclusive modes:

1. VMware vSphere 6.5 virtual appliance

2. Physical (bare-metal) appliance that is based on the Dell EMC PowerEdge R640rackmount server

Storage administrators use the EHAC appliance to start the ESI web service,configure the EHAC console to connect to Dell EMC storage systems, create andremove users, and grant or revoke access to these users that are added in SAP LaMa> Infrastructure > Storage Managers.

The Linux-based EHAC appliance can be deployed with SUSE Linux Enterprise server(SLES) or Red Hat Enterprise Linux (RHEL) operating systems, both on the EHACvirtual appliance and also on the physical appliance. In both cases, you must subscribeto an online SLES or RHEL patch maintenance service to keep the operating systemupdated and secured, as you do for your own servers that run these operatingsystems.

The EHAC appliance includes the following set of preconfigured software:

l SLES 12 SP3 with the latest security updates

l Java 1.8 SDK

l WildFly Application Server 10.1.0

l ESI web service version 6.0

l ESI Deployment Console version 6.0

l Apache Derby database version 10.12

Deploy the Linux-based EHAC virtual applianceDell EMC recommends that you deploy the EHAC virtual appliance when you have aVMware vSphere 6.5 virtual environment as part of your landscape. When you deploythe virtual appliance, the operating system and all the required software such as Javaand WildFly Application Server are already installed and integrated into the ESI webservice.

Before you begin

Ensure that the environment includes the following prerequisites before using theEHAC appliance:

l vCenter 6.5 U2C, 6.0 U3h



Note

If you only have a vCenter 6.0 U3 in your SAP landscape, Dell EMC stronglyrecommends that you to upgrade to vSphere 6.5 if possible. If you cannotupgrade, ask your Dell EMC representative to put a special request to Dell EMCsupport for a Linux-based EHAC appliance to run on vSphere vCenter server 6.0U3. Be aware that Dell EMC cannot guarantee full backwards interoperabilitybecause the latest versions of ESI are deployed in the latest versions of vSpherevCenter and an additional qualification effort might be required.

l At least 80 GB of available space in a shared datastore that is based on a centralshared external storage system, not on any local ESXi datastore

Procedure

1. Open the Storage Integrator for SAP Landscape Management page on DellEMC Online Support and download the EHAC 6.0 virtual appliance.

2. Log in to vCenter, where the EHAC Open Virtual Appliance (OVA) must bedeployed, using the vSphere Client.

3. Select Actions > Deploy OVF Template.

4. On the Select template screen, specify the location where the OVF file issaved, select all the files, and then click Next.

Note

Type the location or browse to find it, either on the Internet or on yourcomputer or network.

5. On the Select name and location screen, perform the following steps:

a. In the Name field, type a name for the EHAC virtual appliance.

b. Select a data center or folder from the list.

c. Click Next.

6. On the Select a resource screen, select the host or cluster location on which todeploy the template, and then click Next.

7. On the Specify a Specific Host screen, select the ESXi host on which theEHAC virtual appliance must be created, and then click Next.

8. Review the details and click Next.

9. On the Select storage screen, select the provisioning type, select thedatastore on which to store EHAC virtual appliance files, and then click Next.

10. On the Select networks screen, select a destination network.

11. On the Ready to Complete screen, review your selections, and click Finish.

Note

Do not power on the EHAC appliance after the deployment; there are advancedsettings for the appliance that must be set before it is powered on.

12. Go to Edit settings > VM Options tab > Boot options > Firmware, select EFI,and then click OK, as shown in the following screen shot.


Deploy the Linux-based EHAC virtual appliance 21

https://support.emc.com/products/28468_ESI-for-SAP-LVM



Figure 2 Edit EHAC virtual appliance settings

13. Power on the EHAC virtual appliance.

14. After you power on the EHAC virtual appliance, click the Summary tab, andthen on the VM screen to launch the EHAC virtual appliance console.

15. Execute the steps described in Initial Configuration of the Linux-based EHACappliance.

Deploy the bare metal Linux-based EHAC applianceDell EMC recommends that you deploy the physical (bare-metal) EHAC appliancewhen you do not have an existing VMware vSphere vCenter 6.5 U2 virtualenvironment in your IT landscape. When you deploy the virtual appliance, theoperating system and all the required software such as Java, WildFly ApplicationServer, and so on are already installed, configured, and integrated in the ESI webservice.

Before you begin

Ensure that you have the Dell EMC PowerEdge R640 rackmount server installed,configured, cabled to the PDUs and network, and a physical graphical console that isconnected to the server before powering on to start the EHAC applianceconfiguration.



Procedure

1. Power on the bare metal EHAC appliance and follow the instructions that aredescribed in Initial configuration of Linux-based EHAC appliance.

Initial configuration of the Linux-based EHAC applianceExecute the following steps to complete the initial configuration of the Linux-basedEHAC appliance.

Note

This procedure and all the following procedures in subsequent chapters are valid forboth the bare metal (physical) and virtual Linux-based EHAC appliance, unlessotherwise specified.

Procedure

1. Configure the network for EHAC appliance host.

The EHAC appliance network configuration screen is displayed after a fewminutes, as shown in the following screen shot.

Figure 3 EHAC appliance console

2. Press Enter to proceed or use the Tab key to move between the <Yes> and<No> options.

3. Proceed through all the screens and provide valid values to configure the EHACappliance network to enable it to communicate with your network.

4. Provide the host IP address, hostname, subnet mask, gateway, and DNS details.

5. When a summary of all your inputs is provided, as shown in the following screenshot, confirm to complete the deployment.


Initial configuration of the Linux-based EHAC appliance 23

Figure 4 EHAC virtual appliance network configuration summary

6. Verify that all the network information you typed is correct in the NetworkConfiguration Summary. If the information is correct, press Tab to select<Yes>, and then press Enter to proceed.

7. Change the root password, as shown in the following screen shot. Press Tab,select <Yes>, and then press Enter to proceed.

Figure 5 EHAC virtual appliance Change Root Password

8. Press Enter when the EHAC virtual appliance configuration completion messageis displayed, as shown in the following screen shot.



Figure 6 EHAC virtual appliance configuration completion

The EHAC virtual appliance Linux operating system login screen is displayed.

Log in and verify the EHAC appliance deploymentLog in to the operating system and verify that the EHAC appliance is deployed.

Procedure

1. Open one of the following on vCenter:

l For a virtual appliance, the EHAC appliance virtual machine console on thevCenter web console

l For a physical appliance, the EHAC appliance physical server console

2. Log in to the guest operating system, using the root username and passwordthat is shared with you during the initial configuration steps.

3. Verify that the EHAC appliance deployment was run correctly by running thefollowing command:

systemctl status wildflyThe output is displayed as ACTIVE for the Wildfly system service.

4. Type the following command and search for the word Deployed in the WildFlyserver.log file.

grep Deployed /opt/wildfly/standalone/log/server.logOutput message similar to the following message 2019-01-0810:53:23,001 INFO [org.jboss.as.server] (ServerServiceThread Pool -- 34) WFLYSRV0010: Deployed"esi_sap_lama_saconfig.6.0.0.ear" (runtime-name :"esi_sap_lama_saconfig.6.0.0.ear"): is displayed.This completes the verification of EHAC appliance deployment.


Log in and verify the EHAC appliance deployment 25

Copy the ESI plug-in to the SAP LaMa serverRun the main_esi60_4_saplama30_MMMYY.sh script to copy the ESI plug-in tothe SAP LaMa host. The MMYYYY in the script stands for the month and year thescript was last updated.

Before you begin

To copy the ESI plug-in, you must have an operating system user with administrationpermissions and read/write permissions to the directory /usr on the SAP LaMaserver.

Procedure

1. Log in to the EHAC appliance, using SSH.

2. Run the following commands to copy the ESI plug-in to the SAP LaMa serverrunning the ESI main script, as shown in the following screen shot.

cd /var/binaries/./main_esi60_4_saplama30_Jan19.shFigure 7 EHAC Main implementation script

After the commands are run, perform the following steps:

a. Use the p option to copy the ESI plug-in to the SAP LaMa server. Whenprompted, enter the SAP LaMa host IP address, operating system usernameand password, and press Enter after each entry.

b. After you press Enter for the third time, the ESI plug-in (fileesi_4_sap_lama_plugin.6.0.xx.ear) is copied from the EHACappliance to the SAP LaMa server in the directory /usr and the results aredisplayed.



Log in to EHAC for the first timeThe first time that you log in to EHAC, accept the terms of the software licenseagreement and set up administrative credentials.

Procedure

1. Open EHAC in your web browser, using the following URL:

http://IPAddress:8080/ehac2. Read the Dell EMC Software License Agreement, and then click I Accept.

A window that enables you to set up administrative credentials opens.

3. Type a username and user full name.

4. Type a strong password and type it again to confirm.

For example, use nine or more letters, and use unique combinations ofuppercase and lowercase letters, numbers, and punctuation. Do not use specificwords or phrases.

5. Type an Encryption Key and type it again to confirm.

6. From the Security Question list box, select a question.

Note

Use the security question to retrieve the password if you forget it.

7. Type a secret answer and type it again to confirm.

8. Click Create.

Log in to EHAC with administrative credentialsAfter you set up administrative credentials, log in to EHAC, using the Admin Loginwindow.

Procedure

1. Open EHAC in your web browser, using the following URL:

http://IPAddress:8080/ehac2. Type your username and password.

Note

If you forget your password, click Forgot Password. Answer the securityquestion that you set up during your first login to retrieve your password. See Log in to EHAC with administrative credentials on page 27.

3. Click Login.

The home page is displayed.

Note

The home page is also displayed when you click General > Home underAdministrator Menu.

The page includes two panes:


Log in to EHAC for the first time 27

l The left pane displays NAS, REST, and WBEM servers, and their respectivefile and block storage system details, which are registered in EHAC.

l The right pane displays file and block storage and the pools that are assignedto specific users.



CHAPTER 4

Configure Storage and Virtual Systems in EHAC


l Configure NAS or file-based storage..................................................................30l Configure SAN or block-based storage...............................................................31l Change the global access level...........................................................................38l Add VMware vCenter virtual systems and ESXi hosts........................................39

Configure Storage and Virtual Systems in EHAC 29

Configure NAS or file-based storageUse the following procedures to configure NAS storage systems, such as Unity NAS,VMAX3, and PowerMax eNAS. This section describes how to configure storage-basedNFS file systems.

Note

This section only applies to Dell EMC VMAX3 and PowerMax storage systems with theeNAS module installed and configured in advance. The Dell EMC VMAX3 andPowerMax eNAS (embedded NAS) module is referred to as Celerra in the followingsections.

Add file or NAS storage systemsFollow the instructions below to add NAS storage systems.

Procedure

1. From the Administrator Menu, click Storage Arrays > NAS > CelerraManaged Systems > Storage Systems.

2. Under Storage Array Details, click Add Storage Array.

3. In the NAS Storage Array window, type the following information for the newstorage array:

l The Name for the new storage system

l The Control Station IP Address (for example, the IP address for Unisphere9.0 for VMAX3 or PowerMax eNAS)

l The Model number of the array for the storage system (for example, PMAX2000)

l The username and password for the control station

4. Click Retrieve Data Movers and select one or more Data Movers from the rightpane.

5. Click Add Storage System.

The message Storage system added successfully is displayed whenthe process is complete.

6. Close the New NAS Storage Array window.

The Storage Array Details screen displays the newly added array and DataMovers.

Update file storage systemsTo update file storage systems, follow this procedure.

Procedure


2. Select a storage system and click Update Storage Array.

3. In the Update the Storage Array window, perform the following steps:

l To update the mover IP address, click Update Mover IP Address and typethe new information.



l To update the username or password, click Update UserName/Passwordand type the new updates.

l To update the model, click Update Model and type the new information.

4. Click Update the Storage System.

Remove file storage systemsFollow this procedure to remove file storage systems, if necessary.

Procedure


2. Select the storage system that must be removed.

3. Click Remove Storage Array to remove the array from EHAC.

Configure SAN or block-based storageUse the following procedures to configure block/SAN storage systems such asVMAX3, PowerMax, XtremIO, and Unity storage systems.

Note

Starting with ESI 6.0, the EHAC server communicates with all the Dell EMC storagesystems, including VMAX3 and PowerMax, using REST API calls instead of SMI-SArray Provider (WBEM server). The WBEM server configuration is deprecated, andonly used to provide backward support for older VMAX family storage systems, suchas VMAX2, VMAX, and if VMAX storage systems are used with VPLEX. If VMAX isused with VPLEX, the Dell EMC SMI-S Array Provider 9.0 must be installed andconfigured in the EHAC appliance, where the VMAX and VPLEX storage systems arebeing configured. Dell EMC will only provide support for older VMAX2 and VMAXstorage systems under special circumstances that the Dell EMC ESI productmanagement team authorizes.

Add REST serversAdd a REST server to EHAC for XtremIO, PowerMax, and VMAX3 All flash arrays. ForPowerMax and VMAX3 storage systems, Unisphere for PowerMax version 9.01 isrequired.

Procedure

1. From the Administrator Menu, click Storage Arrays > Servers > RESTServers.

2. Under Add REST Server, do the following:

l From the array type list, select the type of array to be connected.

l Type the IP address, server name, and version number.

l Type the username and password of the REST Server.

3. Click Add.

If the server details are correct and the connection is successful, a message isdisplayed that addition to the database is successful.


Remove file storage systems 31

Perform prerequisite tasks to view block storage pools of REST-managed storage systemsPerform the following prerequisites tasks to view block storage pools of REST-managed storage systems.

Procedure

1. Add storage systems to a Unisphere 9.0 database before viewing the blockstorage pool. Go to Access Control > SAN > REST Managed Systems > Grant

2. Select the REST server and click Retrieve to view all storage systems.

3. Select the storage system from the list, and then click Add to database/Connect the Storage Array to Server.

View REST-managed block storage system poolsFollow this procedure to view block storage pools of REST-managed storage systems.

Procedure

1. From Administrator menu, click Storage Arrays > SAN > REST MangedSystems > Storage Pools.

2. Under REST Server, select a server from the list box and type the usernameand password.

3. Click Retrieve.

4. Under Component Name, select a storage system and click Retrieve Pools.

View REST-managed VMAX storage system volumesFollow this procedure to view block storage pool volumes of REST-managed blockstorage systems.

Procedure

1. From Administrator Menu, go to Storage Arrays > SAN > REST ManagedSystems > Storage Pools.

2. In the left REST server pane, select a server, and then type the username andpassword.

3. Click Retrieve Pools, and then select a pool from the list.

4. Click Retrieve Volumes.

View SRDF configurations to the EHAC database from the REST-managed VMAX storage

Before you begin

Ensure that the EHAC database includes the VMAX array's REST server.

Procedure

1. From Administrator Menu, go to Storage Arrays > SAN > REST ManagedSystems > VMAX.

2. Under List of Available VMAX Systems via REST, select the storage systemprocedure and click Retrieve SRDF Details, as shown in the following screenshot:



Figure 8 Select the VMAX storage system for which SRDF details is to be viewed

A menu is with a list of target arrays that are configured with the selectedVMAX system is displayed.

Figure 9 Select the remote SRDF paired array

3. Select a target system and click Retrieve.

A table with the SRDF group details is displayed.

4. Expand the corresponding row to see the volumes that are associated to eachRDF group.

Figure 10 SRDF details displayed


Add REST servers 33

Add and configure WBEM serversAdd and configure Dell EMC SMI-S Array Provider, ECOM Web-Based EnterpriseManagement (WBEM) block servers.

Before you begin

Ensure that SMI-S Provider with Solutions Enabler is already installed on a separateand dedicated EHAC server with network communication that is established for theLinux-based EHAC appliance that was deployed previously.

Procedure

1. From the Administrator Menu, click Storage Arrays > Servers > WBEMServers.

2. Under Add WBEM Server, complete the fields:

a. From the Connection Schema list, select either Http or Https, dependingon your security requirements.

Dell EMC recommends that you use Https for security reasons.

b. Type the IP address, server name, and port number.

Note

The IP address is usually the same as the IP address of the EHAC server, ifthe SMI-S array provider is installed in the same server.

c. Type a username and password for the WBEM server.

3. Click Add.

If the server details are correct, the Adding Server Details Successfulmessage is displayed.

Note

Storage administrators must configure a WBEM infrastructure and an ECOMaccount, with the administrator role to provide full access. For detailedinformation about ECOM, see the ECOM Deployment and Configuration Guide,which is available in Dell EMC Online Support.

4. From the Administrator Menu, click Storage Arrays > SAN > WBEM ManagedSystems > Storage Systems.

5. Under WBEM Server, perform the following steps:

a. From the Select Server list box, select the WBEM server on which you wantto add the storage system.

You can view details for the selected server in the other fields.

b. Type the WBEM server username and password.

c. Click Retrieve.

The right pane under List of Storage Systems Managed by the Server liststhe storage systems.

6. Click Add.



https://support.emc.com/docu43613_ECOM-Deployment-and-Configuration-Guide.pdf?language=en_US


A Storage System Added Successful message is displayed.

Update or remove WBEM serversFollow this procedure to update or remove WBEM servers.

Note

Before you remove a block server, first remove users who have access to the storagearrays and storage pools.

Procedure

1. From the Administrator Menu, click Storage Arrays > Servers > WBEMServers.

2. Select a server from the right pane.

3. Click Remove/Update Server.

The Remove/Update the WBEM Server window is displayed.

4. Change the username or password:

a. Click Update UserName/Password.

b. Enter the new information.

c. Click Update UserName/Password.

5. Update the connection type or protocol:

a. Click Update Connection Schema/Port.

b. From the Connection Schema list box, select either Http or Https.

c. Update information in thePort field.

d. Click Update Connection Schema/Port.

6. Remove a WBEM server:

a. Click Remove the WBEM Server.

b. Click Remove Server.

Enable advanced configuration for VMAX and VMAX3 arraysEnable the advanced storage configuration for VMAX and VMAX3 arrays if advancedstorage configurations such as cascaded initiator groups, parent/child storage groups,or multiple masking views are used during the SAP system setup.

Note

This procedure is only required when using older VMAX and VMAX2 storage arraysthat are configured under the WBEM server.

Procedure

1. From the Administrator Menu, click Storage Arrays > SAN > WBEM ManagedSystems > Storage Systems.

2. Under WBEM Server, select the WBEM server that manages the VMAX array.

3. Click Retrieve to retrieve the arrays.


Update or remove WBEM servers 35

4. Under Select the Storage System, select the VMAX array, and then clickConfiguration.

5. Under Add Configuration to DB, select Storage Configuration For SpecificHost: and click Apply.

Perform prerequisite tasks to view WBEM-managed block storage systemspools

Perform the following prerequisite tasks to view WBEM-managed block storagesystems pools.

Procedure

1. Add storage systems to the EHAC database before viewing the block storagepool. Go to Access Control > SAN > WBEM Managed Systems > Grant.

2. Select the WBEM server and then click Retrieve to view all storage systems.

3. Select the storage system from the list and then click Add to database/Connect the Storage Array to Server.

View WBEM-managed block storage systems poolsFollow this procedure to view block storage pools of WBEM-managed block storagesystems.

Procedure

1. From the Administrator Menu, click Storage Arrays > SAN > WBEM ManagedSystems > Storage Pools.

2. Under WBEM Server, select a server from the list box and type the usernameand password.

3. Click Retrieve.

4. Under Component Name, select a storage system and click Retrieve Pools.

View WBEM-managed block storage systems volumesView block storage pool volumes of WBEM-managed block storage systems.

Procedure

1. From the Administrator Menu, click Storage Arrays > SAN > WBEM ManagedSystems > Storage Pools.

2. In the left WBEM Server pane, select a server and type the username andpassword.

3. Click Retrieve Pools, and then select a pool from the list.

4. Click Retrieve Volumes.

Add an XtremIO arrayAdd an XtremIO array.

Procedure

1. From the Administrator Menu, click Storage Arrays > SAN > REST ManagedSystems > XtremIO.

2. Under Add New XtremIO System, type the XMS IP Address, XMS Version,Friendly Name, User Name, and Password.



Note

If the XtremIO Management Server (XMS) manages a clustered XtremIO 4.0array, after you add the XtremIO details, the List of Available XtremIOSystems shows each of the clusters' X-Brick™ building blocks that XMSmanages.

Update or remove XtremIO arraysUpdate or remove an XtremIO storage array.

Procedure

1. From the Administrator Menu, click Storage Arrays > SAN > REST ManagedSystems > XtremIO.

2. From the List of Available XtremIO Systems, select the array and clickUpdate/Remove XtremIO.

3. To update XtremIO credential details, type the username and password, andthen click Update User Name/Password.

4. To remove XtremIO details, select Remove the XtremIO system, and thenclick Remove XtremIO Array.

Add VPLEX storage detailsAdd details for a VPLEX storage system. These details include a friendly name,username, password, and IP address.

Procedure

1. From the Administrator Menu, click Virtual System > VPLEX.

2. Under List of VPLEX Systems, click Add VPLEX Details.

3. Under New VPLEX, type a friendly name that is unique among your VPLEXstorage systems.

4. From the VPLEX Type list box, select Local or Metro, and then click Next

5. Click Add Cluster Details.

Note

Add single cluster details for a Local VPLEX type. Add two cluster details forthe Metro VPLEX type.

6. In the Add Cluster window, perform the following steps:

a. Type the IP address.

b. Type the username and password.

c. Click Add.

7. Click Next to view cluster details in the Physical Storage Details window.

8. Click Next to open the Mapping Storage and WBEM window.

9. Do one of the following if VPLEX has VMAX or VMAX3 has backend array:

l If the storage systems and the corresponding WBEM servers are alreadyconfigured for EHAC, click Map at the top of the page to select all of thestorage arrays that are connected to VPLEX.


Add VPLEX storage details 37

l If the storage systems and WBEM servers are not configured, click NewWBEM to configure them.

Note

ESI currently supports VPLEX with VMAX3 or XtremIO as its backend storage.

10. Click Next to open the Assign Pools window.

11. Click Retrieve Pools to view a list of the pools in an array that must be used tocreate the cloned virtual volume.

12. Select a pool, and then move the username that requires access to the pool tothe list on the right by either dragging the username or clicking the right arrow.

Note

If no users are listed, to add them, see Add a user on page 42.

13. Under Grant Pools, move the username that requires access to the pool to thelist on the right by either dragging the username or clicking the right arrow.

14. Click Grant.

15. Click Next, and then click Add VPLEX System.

Remove VPLEX storage details

Follow the procedure to remove VPLEX storage details.

Procedure

1. From the List of VPLEX Systems, select the VPLEX system to be removed.

2. Click Update/Remove VPLEX Details.

3. Under Update/Remove VPLEX Details, click the Remove VPLEX tab.

4. Click Remove VPLEX, and then click Yes to confirm.

Change the global access levelChange a global access level to enable or disable read/write access to storagesystems for all users. When you enable global access level overrides, they override allother settings. If the Global Access Level is set to read-only, all write access is alsodisabled.

Note

You can also enable or disable access for individual users. When you add an array, thedefault global access level is the read/write mode. See Configure NAS or file-basedstorage for more information.

Procedure

1. From the Administrator Menu, click General > Global Access Level.

2. Select a storage system from the list.

3. Click Change Access Type.



An Access Level Changed confirmation message is displayed to confirmthe change.

Add VMware vCenter virtual systems and ESXi hostsAdd VMware vCenter virtual systems and ESXi hosts to the EHAC database.

Note

This process is only required for SAP systems running on VMware vSphere that SAPLaMa manages and participates in system operations, such as System or instancePrepare, Unprepare, and Relocation, and System provisioning processes, such asSystem Clone, Copy, Refresh, and Destroy.

Procedure

1. From Administrator Menu, click Virtual System > vCenter.

Note

The default Connection Schema is https.

2. Under Add New vCenter System, perform the following steps:

a. Type the IP Address.

b. Type a friendly name, which is a short name that is unique among yourvCenter storage systems.

c. Type the vCenter username and password.

This user must have administrator permission.

3. Click Add vCenter.

If the server details are correct, a Successfully Added message isdisplayed.

Note

You can click Test Connection to check the connection after adding a vCentersystem. A Successfully Added message confirms a successful connection.

4. Under List of Available vCenter Systems, select a system and click RetrieveDataCenter.

5. Under List of DataCenter in selected vCenter on the upper right, select a datacenter.

6. Click Retrieve ESX.

7. Under List of ESXs in the selected vCenter on the right, select an ESX server.

8. Click Retrieve VMs to view the virtual machines in the selected ESXi.

9. Click Add to DB to add the ESXi host to EHAC.


Add VMware vCenter virtual systems and ESXi hosts 39

Note

Starting with EHAC 4.6.8, virtual machine information is no longer maintained inthe EHAC database, although you can retrieve virtual machines and view them.Only ESXi details are added to EHAC database currently.



CHAPTER 5

Manage User Accounts


l Manage users.....................................................................................................42l Configure access control................................................................................... 43l Secure user data................................................................................................ 49

Manage User Accounts 41

Manage usersUse the following procedures to manage users and their passwords.

Add a userA user account is required to be created on the EHAC console to enable SAP LaMaintegrated with the ESI storage manager to manage SAP systems with instance-specific file systems stored on storage volumes from supported Dell EMC storagesystems. It is also required to communicate with the Dell EMC storage systems in useby these systems to run the SAP LaMa System Provisioning processes that involvestorage operations such as clones and snapshots.

Procedure

1. From the Administrator Menu, click General > Users.

2. Under User Details, click Add New User.

3. Under New User, perform the following steps:

a. Type a username and user full name.

b. Type a strong password and then type it again for confirmation.

4. Click Create User.

Update a user passwordFollow this procedure to update a user password.

Procedure


2. Under User Details, select a user and click Update User.

3. Under Update User/Administrator, perform the following steps:

a. Type the old password.

b. Type a new strong password and then type it again for confirmation.

4. Click Update.

Update an administrator passwordFollow this procedure to update an administrator password.

Procedure


2. Click Update User > Update Administrator.

3. In the Update Administrator Password dialog box, type the old password.

4. Type a new strong password and then type it again for confirmation.

5. Click Update.



Remove a userFollow this procedure to remove a user.

Procedure


2. Click Remove User.

3. Select the user that must be removed and click Yes to confirm the action.

Configure access controlUse the following procedures to grant access for users to file and block storagesystems and pools, and to XtremIO storage arrays.

Grant access to file storage systems and poolsFollow this procedure to grant access to file storage systems and pools

Note

The Dell EMC VMAX3 and PowerMax eNAS (embedded NAS) module is referred inthe following sections as Celerra.

Procedure

1. From the Administrator Menu, click Access Control > NAS > CelerraManaged Systems > Grant.

2. Select a storage system from the Select the Storage System to Grant theAccess Level pane.

3. Grant access to users:

a. Click User Level.

The Select the Users to Grant the Storage System Access Level dialogbox is displayed.

b. Select one or more users from the left pane of the dialog box.

c. Click the right arrow to move the user or users into the right pane.

Note

The selection list does not include users who currently have access to thestorage system.

d. Click Grant To Users.

4. Grant access to storage pools:

a. Click Retrieve Pools to display a list of file storage pools.

b. Select a storage pool and click Grant to Users.


Remove a user 43

Note

You can only grant access to storage pools that correspond to a storagesystem where the user already has been granted access.

The Select the User to Grant the Storage Pool Access dialog box isdisplayed.


Note

The selection list does not include users who currently have access to thestorage pool.

d. Click Grant.

Revoke access to file storage systems and poolsFollow this procedure to revoke access to file storage systems and pools.

Note

The Dell EMC VMAX3 and PowerMax eNAS (embedded NAS) module is referred inthe following sections as Celerra.

Procedure

1. From the Administrator Menu, click Access Control > NAS > CelerraManaged Systems > Revoke.

2. Select a storage system from the Select the Storage System from which theAccess rights need to be revoked pane.

3. To revoke user access to file storage:

a. Click Revoke From Users.

The Select the Users to Revoke the Access Level dialog box is displayed.


c. Click the right arrow to move a user or users into the right pane.

Note

The selection does not include users whose access to the selected storagesystem is already revoked.

d. Click Revoke to revoke access for the selected user or users.

Note

When you revoke user access to a storage system, you also revoke access toall storage pools that are related to that storage system.

4. To revoke user access to file storage pools:

a. Click Retrieve Pools to display a list of file storage pools.



b. Select a storage pool and click Revoke From Users.

The Select the Users to Revoke the Access Level dialog box is displayed.

c. Select the user or users, and then click the right arrow to move them to theright pane.

d. Click Revoke to revoke access for the selected user or users.

Grant access to WBEM-managed block storage systems and poolsFollow this procedure to grant access to WBEM-managed block storage systems andpools.

Procedure

1. From the Administrator Menu, click Access Control > SAN > WBEM ManagedSystems > Grant.

2. In the left WBEM Server pane, select a server from the Select Server field.

3. Type the server username and password, and then click Retrieve.

4. From Storage Systems available and connected to the server in the localDatabase for Granting Read-Write Access pane, select a storage system.

5. Grant access to users:

a. Click Grant to Users.

The Select the Users to Grant the Storage System Access Level dialogbox is displayed.



Note

The selection list also includes users who currently have access to a selectedstorage system.

d. Click Grant to grant access to the selected user or users.

6. Grant access to storage pools:

a. Click Retrieve Pools.

The Select the Users to Grant the Storage System Pool Access Leveldialog box is displayed.

b. From the Select Pools for Granting Read-Write Access pane, select astorage pool.

c. Click Grant to Users.

d. Select one or more users from the left pane of the dialog box.

e. Click the right arrow to move the user or users into the right pane.

Note

The selection list does not include users who currently have access to aselected storage pool.


Grant access to WBEM-managed block storage systems and pools 45

f. Click Grant to grant access to the selected user or users.

Revoke access to WBEM-managed block storage systems and poolsFollow this procedure to revoke access to WBEM-managed block storage systems andpools.

Procedure

1. From Administrator Menu, click Access Control > SAN > WBEM ManagedSystems > Revoke.

2. In the left WBEM Server pane, select a server from the Select Server field.

3. Type the server username and password, and then click Retrieve.

4. From the Select Storage System to Revoke the Access level pane, select astorage system.

5. To revoke a users' access, do the following:

a. Click Revoke from Users.

The Select the Users to Revoke the Storage System Access Level dialogbox is displayed.



d. Click Revoke to revoke access from the selected user or users.

6. To revoke storage pools' access, do the following:


b. From the Select Pools for Revoking Read-Write Access pane, select astorage pool.

c. Click Revoke from Users.

The Select the Users To Revoke the Storage System Pool Read-WriteAccess dialog box is displayed.



f. Click Revoke to revoke access from the selected user or users.

Grant access to REST-managed VMAX storage systems and poolsFollow this procedure to grant user access to REST-managed block storage systemsand pools.

Procedure

1. From the Administrator Menu, click Access Control > SAN > REST ManagedSystems > VMAX > Grant.

2. From the Available VMAX Systems via REST for Granting Access rightspane, select a storage system

3. Grant user access:

a. Click Grant to Users.

The Select the Users to Grant the Storage System Level Access dialogbox is displayed.





d. Click Grant to grant read/write access to the selected user or users.

4. Grant user access to storage pools:


b. From the Select Pools to Grant Read-Write Access pane, select a storagepool.

c. Click Grant to Users.

The Select the Users to Grant the Storage System Pool Access Leveldialog box is displayed.



f. Click Grant to grant access to the selected user or users.

Revoke access to REST-managed VMAX storage systems and poolsFollow this procedure to revoke a user's access to REST-managed VMAX storagesystems and pools.

Procedure

1. From the Administrator Menu, click Access Control > SAN > REST ManagedSystems > VMAX > Revoke.

2. From the Select VMAX System to Revoke the Access level, select a storagesystem.

3. Revoke user access:

a. Click Revoke User Access.

The Select the Users to Revoke the Storage System Access Level dialogbox is displayed.



d. Click Revoke to revoke access from the selected user or users.

4. Revoke access from storage pools:


b. From the Select Pools for Revoking Read-Write Access pane, select astorage pool.

c. Click Revoke from Users.

The Select the Users to Revoke the Storage System Pool Access Leveldialog box is displayed.



f. Click Revoke to revoke access from the selected user or users.


Revoke access to REST-managed VMAX storage systems and pools 47

Grant access to XtremIO storage systemsFollow this procedure to assign users to an XtremIO array.

Procedure

1. From the Administrator Menu, click Access Control > SAN > REST ManagedSystems > XtremIO.

2. Select the server and click Grant to Users.

3. Under Select the Users to Grant the Storage System Access Level, selectusers from the left column.

4. Click the right arrow to move users to the right column and click Grant toconfirm your selections.

Revoke access to XtremIO storage systemsFollow this procedure to revoke user access to an XtremIO array.

Procedure

1. From the Administrator Menu, click Access Control > SAN > REST ManagedSystem > XtremIO.

2. Select the server from the list box and click Revoke From Users.

3. Under Select the Users to Revoke the Storage System Access Level, selectusers from the left column.

4. Click the right arrow to move users to the right column and click Revoke toconfirm your selections.

Grant access to Unity storage systemsFollow this procedure to assign users to a Unity array.

Procedure

1. From the Administrator Menu, click Access Control > SAN > REST ManagedSystems > Unity.

2. Select the server and click Grant to Users.

3. Under Select the Users to Grant the Storage System Access Level, selectusers from the left column.

4. Click the right arrow to move users to the right column and click Grant toconfirm your selections.

Revoke access to Unity storage systemsFollow this procedure to revoke user access to Unity array.

Procedure

1. From the Administrator Menu, click Access Control > SAN > REST ManagedSystem > Unity.

2. Select the server from the list box and click Revoke From Users.

3. Under Select the Users to Revoke the Storage System Access Level, selectusers from the left column.



4. Click the right arrow to move users to the right column and click Revoke toconfirm your selections.

Secure user dataEHAC safeguards sensitive information by encapsulating all passwords such asUnisphere passwords, WBEM server passwords, and control station passwords forNAS arrays. To further reduce the risk of attacks, do the following:

l Close your browser when the administration console is not in use to preventaccess by unauthorized users.

l Lock the server if you leave it unattended. Secure the EHAC server in the sameway as any other server with sensitive information.

l Set up a strong password when you log in to EHAC for the first time. Thispassword must be used each time you log in to EHAC.

l Create an ESI user on vSphere vCenter and Dell EMC storage systems withadministrator privileges to enable storage and VMware administrators to trackoperations on vCenter, if errors occur.


Secure user data 49

CHAPTER 6

Install the ESI plug-in on the SAP LaMa server


l Perform prerequisite tasks to deploy the ESI plug-in......................................... 52l Deploy the ESI plug-in........................................................................................53l Add an ESI storage manager.............................................................................. 55l Cache storage information from SAP systems...................................................56

Install the ESI plug-in on the SAP LaMa server 51

Perform prerequisite tasks to deploy the ESI plug-inFollow this procedure to perform the prerequisite tasks to deploy the ESI plug-in.

Before you begin

On the SAP LaMa host, where the SAP NetWeaver Java Stack server is running, SAPNetWeaver Java administrator credentials (username and password) with fulladministration privileges are required to deploy the ESI plug-in successfully.

Note

Run the Telnet commands locally on the SAP LaMa server.

Additionally, perform the following tasks before you deploy the ESI plug-in:

Procedure

1. Log in to the SAP LaMa web-based UI and complete all system provisioningprocesses such as System Clone, Copy, Refresh, and Destroy. Also, completeall SAP LaMa system operations, such as mass or instance-specific prepare,unprepare, and relocation.

2. Postpone all planned SAP LaMa planned processes or operations.

3. Go to Infrastructure > Storage Managers, select ESI and then click Remove.

4. Log in to the SAP LaMa web-based UI Storage Cache, using the link below:

http://xxx.xxx.xxx.xxx:50000/LVMMonitoring/Overview?advanced=truewhere the <xxx.xxx.xxx.xxx> is the IP address of the SAP LaMa server.

5. Do the following for the storage caches available in the Caches section drop-down list:

a. Check if StorageSystemCache, StoragePoolCache, StorageVolumeCache,StorageGroupCache, StoragePrefetchPackagesCache,StorageCustomCloningPropsCache, StorageMountMappingCache, andStorageVolumeGroupCache caches are cleared. To check if they arecleared, select a cache from the drop-down list and view the table, at thebottom of the screen, and check if there are no entries, as shown in thefollowing screen shot.



Figure 11 SAP LaMa Storage Caches

b. If the table has entries, click Clear next to the drop-down list.

c. Repeat these steps for all the required caches.

This step cleans up all the storage-based data from the Dell EMC storagesystems that are loaded in the SAP LaMa storage cache.

Note

Ensure that you are only using Dell EMC storage systems with SAP LaMa andthat one ESI appliance manages the systems.

Deploy the ESI plug-inAfter the ESI plug-in is copied to the SAP LaMa host where the SAP NetWeaver Javastack is running, the ESI plug-in must be deployed inside the SAP NetWeaver JavaStack server where the SAP LaMa add-on is running.

Before you begin

For information about prerequisites to deploy the ESI plug-in, see Performprerequisite tasks to deploy the ESI plug-in.

Procedure

1. Ensure that the ESI plug-in esi_4_sap_lama_plugin.6.0.xx.ear file thatwas copied previously is available in /usr directory.

For information about how to copy the ESI plug-in, see Copy the ESI Plugin.


Deploy the ESI plug-in 53

2. Open the SAP LaMa server console, log in to the operating system.

3. Log in to the SAP NetWeaver Java Stack server, using the command telnetlocalhost 50008, and then type the administrator username and password,as shown in the following screen shot.

Figure 12 Logging in to SAP Java Stack and listing plug-ins installed

4. Run the following command to determine if a previous version of the plug-in isalready installed:

list_app | grep plugin5. Manually undeploy the previous versions of the plug-in identified in the previous

step, using the following command:

undeploy name=esi_sap_lvm_plugin.5.0.x vendor=JavaEEon_undeploy_error=stop

6. Deploy the new ESI plug-in version available in the directory /usr/, using thefollowing command:

deploy /usr/esi_4_sap_lama_plugin.6.0.xx.ear version_rule=allon_deploy_error=stop

7. Confirm that the ESI for SAP LaMa plug-in was deployed, as shown in thefollowing screen shot.



Figure 13 Adapter is deployed

Add an ESI storage managerSAP LaMa needs a storage manager to communicate with the supported Dell EMCunderlying storage systems, where the SAP instance-specific file systems are stored.

ESI and its associated libraries send queries to the storage systems to managerelevant information, such as storage pools, mount paths, and snapshots. They alsoprovide SAP LaMa support for the system provisioning processes such as SystemClone, System Copy, and System Refresh, and system operations such as SystemPrepare, Unprepare, and Relocation.

Procedure

1. Open the SAP Landscape Management UI web page.

2. Type your username and password, and then click Log On.

3. Select Infrastructure > Storage Managers and click Add.

4. In the list of supported storage manager types, select Dell EMC Corp ESI forSAP NW LaMa and click Next.

5. Type the Basic Properties for the storage manager.

a. In Label, type a name that identifies this storage manager.

b. Type the username and password of a registered EHAC user.Only the storage arrays that the user grants are visible to the adapter on theSAP LaMa server.

c. In URL, type the IP address and port number of the EHAC server.

d. In Monitoring Interval (Seconds), add the monitoring interval for storagecaching while configuring the adapter in SAP LaMa 3.0. The recommendedvalue is 3600s, as shown in the following screen shot.


Add an ESI storage manager 55

Figure 14 Added storage manager

6. To test the configuration before adding it, click Test Configuration on thebottom of the page.

7. After you receive confirmation that the configuration is correct, click Next.

8. Click Save.

The storage manager is installed and a list of storage systems that are assignedto this user is displayed in the Storage Systems section of the SAP LandscapeManagement window. Click Reload Storage Systems to see an updated list ofstorage systems that are assigned to this user.

9. Confirm that the list of supported storage shows the added storage manager asESI version 6.0.x and the ELSA as version 9.0.x or later.

Cache storage information from SAP systemsWith ESI and SAP LaMa 3.0, you can use the SAP LaMa storage cache feature toretrieve storage information from VMAX3, PowerMax, Unity, XtremIO, and VPLEXstorage systems. ESI for SAP LaMa caches all storage volumes to which the SAPLaMa storage manager has been provided access control in the EHAC UI. This featurespeeds up the storage-related operations.

The storage cache information also shows the volume group and logical volumeinformation. SAP LaMa uses the cached information during the system provisioningprocesses, such as the:

l System Clone, System Copy, and System Refresh processes

l Mass Unprepare, Mass Prepare, and System Relocation operations

The following screen shot shows a VMAX3 storage cache tree with block storagesystem, pool, and volume details when you go to Operations > Storage > Storage



Overview. The same format is used for VMAX, XtremIO, Unity, and VPLEX storagesystems.

Figure 15 Storage caching for the storage adapter

The following screen shot shows storage caching for VMAX3 block storage.

Figure 16 Storage caching for VMAX3 block storage

The following screen shot shows storage caching for volume groups on a host. Duringcloning, the volume group information about the SAP hosts is retrieved and populatedin the Storage tab.


Cache storage information from SAP systems 57

Note

After the SAP LaMa Storage Cache is populated with all the Dell EMC storagesystems' storage volumes information, after all SAP hosts and instances areconfigured, as described in the Enterprise Storage Integrator for SAP LandscapeManagement User Guide and Enterprise Storage Integrator for SAP LandscapeManagement User Guide, the SAP-instance specific file systems and at least a SystemClone process is executed up to the storage step. After this, SAP LaMa then creates across reference information between the SAP instance-specific file systems and thestorage volumes they are based on, and enables the SAP administrator to graphicallyvisualize from the SAP system to instance, to its file systems, lvs, vgs, and storagevolumes they are based on and from which Dell EMC storage system they are comingfrom and from which ESI storage manager, if more than one is configured in yourenvironment.

Figure 17 Storage caching for volume groups on a host



CHAPTER 7

Utilities


l Start and stop the EHAC service....................................................................... 60l Change EHAC Deployment Console settings..................................................... 60l Use EHAC appliance aliases .............................................................................. 60l Configure WildFly by restoring the database from a backup............................... 61l Back up and restore an Apache Derby database.................................................62l Monitor EHAC server activities by using logs.....................................................63l Configure ESI logs............................................................................................. 64l Collect SRM, ViClient, and SAPACOSPREP logs............................................... 65l Upgrade the ESI web service and apply hotfixes................................................66

Utilities 59

Start and stop the EHAC serviceWhen EHAC is running, start and stop the EHAC service.

Note

This procedure is valid only for the Linux-based EHAC vSphere virtual appliance.

Procedure

1. Navigate to the /opt/wildfly directory.

2. To verify the status of the EHAC service, run the following command:

./systemctl status wildfly3. To start the service, type the following command:

./systemctl start wildfly4. To stop the service, type the following command:

./systemctl stop wildfly

Change EHAC Deployment Console settingsOn Linux-based EHAC appliances, run the EHAC Deployment Console utility toreconfigure the log level and residue cleanup settings.

Procedure

1. Open the EHAC appliance graphical console (EHAC console).

2. Log in to the guest operating system, using the root username and passwordyou were informed when you deployed the EHAC appliance.

3. To start the EHAC Deployment Console, double-click theEHACDeploymentConsole.desktop icon on the desktop of the graphicalconsole.

Use EHAC appliance aliasesAliases enable you to customize the shell session interface. ESI aliases are pre-definedin the EHAC appliance. They provide an easy method to access ESI-specificinformation about an EHAC appliance.

Note

This procedure is valid only for the Linux-based EHAC appliance.

When you use an alias, you can run frequently used commands by using a different,preferred term. You can also use complex or commonly used options as the defaultsfor a specific command.

The following aliases are defined in the .bash_profile file:

l alias cddeploy='cd /usr/local/wildfly-10.1.0.Final/standalone/deployments/'

l alias cdlog='cd /usr/local/wildfly-10.1.0.Final/standalone/log/'

Utilities


l alias viesi='vi /usr/local/wildfly-10.1.0.Final/ESI_application.properties'

l alias viesilog='vi /usr/local/wildfly-10.1.0.Final/Log.properties'

l alias tails='tail -f /usr/local/wildfly-10.1.0.Final/standalone/log/server.log'

These aliases are loaded automatically when you log in to the terminal as root.

The following examples show how to use aliases:

l To scroll through the currently generating WildFly log:ehac:~# tails

l To go to the WildFly log folder directly:ehac:~# cdlog

Configure WildFly by restoring the database from a backupUse the following procedure to configure the WildFly server from an existing databasebackup of another EHAC server from release 5.0 or 6.0 only, in case of anunrecoverable failure of the current EHAC appliance.

Note

Use this procedure only if you have an existing EHAC server that is configured andtake backups from that EHAC database, using the EHAC Deployment Console. EHACsupports database backup and restore across different operating system platforms.For example, you can take a backup of a database from an existing Windows EHACserver and restore it on a Linux EHAC appliance, using the Deployment console.

When restoring the database from the remote location to the local database directoryand configuring the WildFly server by using the database, some information might belost from the time after the last backup was performed to the time when the currentEHAC system failed.

Note

Use these instructions on a separate host where you want to restore the Derbydatabase backup.To avoid implementation delays and additional Dell EMC support, we stronglyrecommend that you always deploy a new virtual EHAC appliance and test the restore.Then, perform the restore on the final configuration only if you cannot configure theEHAC console with your environment information.

Dell EMC recommends that, whenever possible, you deploy and reconfigure the EHACappliance again to avoid inconsistencies in case the ESI database is older than theprior 5.0 release.

Procedure

1. To start the EHAC Deployment Console on a Linux-based appliance, double-click the EHACDeploymentConsole.desktop icon on the desktop.

2. Select the Configure using Remote Database Backup check box to configurethe database from an existing backup on a remote network share.

3. Type the Database Name.

Utilities

Configure WildFly by restoring the database from a backup 61

4. In the Path where Remote Backup is Located field, type the absolute path ofthe remote path of the database backup.

Note

This field is disabled if the Configure using Remote Database Backup checkbox is cleared.

5. In the Path Where Database Needs to be Created field, select the path.

6. In the Derby Client Jar field, select the Derby Jar file.

7. Click Configure.

Note

A Server Configuration Successful message confirms theconfiguration.

Figure 18 Configuring WildFly

8. Open the WildFly Application Server and start EHAC, using the backed-up datafrom the Derby database.

Back up and restore an Apache Derby databaseThe Apache Derby database runs as an in-memory database within EHAC. Thedatabase holds critical information about user-to-storage access mappings, storagearray details, and runtime information that can be used to correct SAP LaMa. For datawrites, data might be lost if a user loses the host where EHAC and the Derby databaseis running. If data is lost during a data write, the user loses all data, and the datacannot be re-created.

The Derby database backup and restore utility enables administrators to initiatebackups of the Derby database on remote network file shares and to restore the dataon a new host. To help prevent critical data loss, the administrator must only installEHAC components on a different host and restore database data through the back upcopy of data files.

Utilities


The Apache Derby database inside the EHAC appliance persists all user configurationson EHAC as well as data relevant for SAP LaMa user activities such as SystemOperations—Prepare, Unprepare, and Relocation, and System Provisioning options—System Clone, Copy, and Refresh.

This utility is critical for ESI with VPLEX because most data for VPLEX operationspersists in the Derby database. The utility is always available when the WildFlyApplication Server is running.

To use this utility, ensure that the following requirements are met:

l Users must have complete access privileges to place the backup of the Derbydatabase and to restore the database to any system.

l The network share must be accessible from both source and target hosts.

l The database backup must not run while you are performing any other SAP LaMaoperations, as it results in data inconsistency in the backup.

Procedure

1. Open EHAC in your web browser by using the following URL:

http://IPAddress:8080/ehac2. Log in with the username and password that you configured when you opened

the EHAC console the first time.

3. From the Administrator tab on the upper right of the page, select Utilities.

4. Click Database Backup Utility.

5. Under Configure Database Backup Properties, perform the following steps:

a. Type the Path of Remote Directory backup.

b. Type the Time to start backup in hours.

Note

For example, type 23 for a backup time of 23 hours. Use a decimal for timesthat are less than one hour.

c. From the Backup interval list box, select Daily, Weekly, or Monthly.

6. Click Configure.

7. Click Database Backup Scheduler to display your selections.

8. Click Start Scheduler.

Note

Do not select the Force Run Now checkbox.

Monitor EHAC server activities by using logsESI for SAP LaMa uses logs to monitor the operation of the system. This enablessystem administrators and Dell EMC Support engineers to troubleshoot issues thatusers may encounter.

While configuring and deploying EHAC, you can also configure logging to monitor theoperation of the system. Because no logs can be kept on the SAP LaMa servers, both

Utilities

Monitor EHAC server activities by using logs 63

the EHAC appliance and the ESI plug-in store logs in the EHAC server using the samelogging facility.

The following information is collected:

l Java Thread Dump Collector logs

l WildFly and EHAC Web Service logs

l SMI-S Provider logs

In case of error, review the logs in the log folder that you specified while configuringEHAC. If users encounter issues, the storage administrator can retrieve the logs fromthe EHAC server to which the user might not have access.

Note

There are two automated ways to view EHAC logs in ESI:

l Double-click the desktop shortcuts in the graphical console of the EHACappliance.

l Log in to the EHAC appliance with the root user, using SSH, and run the /var/binaries/main_esi60_4_saplama30_MMMYY.sh script and choose (v)ViewEHACConfigLogFiles.

Dell EMC Support might request these logs to troubleshoot issues. See Configure ESIlogs for more information.

Procedure

1. Open EHAC in your web browser by using the following URL:

http://IPAddress:8080/ehac2. Log in with the username and password that you configured when you opened

the EHAC console the first time.

3. From the Administrator list box on the upper right of the page, select Utilities.

4. Click Collect WildFly, ESI, SMI-S Logs.

5. Click either Open or Save to open or save the ESI_LOGS.zip file.

Configure ESI logsConfigure logs to monitor the operation of the system to enable system administratorsand Dell EMC Support engineers to troubleshoot issues that users might encounter.

Use the EHAC Deployment Console to modify the configuration of the log level andresidue cleanup.

Procedure

1. Start the EHAC Deployment Console:

l On a Windows-based EHAC appliance, double-click theEHAC_DeploymentConsole_ESISAPLaMa.jar file.

l On a Linux-based EHAC appliance, double-click theEHACDeploymentConsole.desktop icon on the desktop of the graphicalconsole.

2. In the Configuration Utility, click Configure Properties > Configure Logs.

3. In the Directory Where Logs need to be Created field, type the full path of thefolder to save the logs.

Utilities


4. Click Select to select the directory path that you entered.

5. Select a logging level to create logs that contain the following data:

l INFO—Informational data only, which does not include errors

l DEBUG—INFO data and debugging information

l TRACE—INFO, DEBUG, and stack trace data that generates more logs

l ERROR—INFO and error messages

6. Click Configure.

A Log Folder and Log level configured successfullyconfirmation message is displayed.

Note

You can click Collect Logs to create a .zip file that contains logs that ESIgenerates. You might have to set the error level to TRACE and run a transactionthat generated an error again to create all the required logs by Dell EMCSupport to troubleshoot issues.

Collect SRM, ViClient, and SAPACOSPREP logsFollow the procedure below to collect SRM, ViClient, and SAPACOSPREP logs.

Before you begin

l Confirm that you have network connectivity between the EHAC appliance hostand the SAP hosts from which you are trying to collect logs. If there is firewallbetween the EHAC appliance and the SAP hosts you are trying to get the logs,ensure the network ports for SSH and SFTP are open.

l Obtain user credentials with administrator permissions on the SAP hosts fromwhich you are trying to get the logs.

Administrators can collect the following logs when using Linux-based and AIX-basedhosts:

l Storage Resource Manager (SRM)—Provides file system and HBA details aboutthe SAP hosts

l Virtual Infrastructure Client (ViClient)—Provides information about the ESX/vCenter activities that are performed through the SRM

l SAPACOSPREP partner libraries—Provides information about the mounting,unmounting, and retrieving of file systems by SRM, and the activating anddeactivating of virtual hostnames

Note

There two automated methods to collect SE/SRM/ViClient and SAPACOSPREP logsfrom the Linux-based SAP hosts. The first method is valid for both Linux-based andAIX-based SAP hosts and it is described below. The second method is valid only forLinux-based SAP hosts, and uses the host configuration script for Linux-based SAPhosts options (g) InstallRunGrab and (c) CollectSAPHALogs, which aredescribed in detail in the Enterprise Storage Integrator for SAP Landscape ManagementUser Guide.

Utilities

Collect SRM, ViClient, and SAPACOSPREP logs 65

Procedure

1. From the Administrator tab on the upper right, select Utilities.

2. Click Collect SRM, ViClient, and SAPACOSPREP LOGS and do the following:

a. Type the host IP address.

b. Type the username and password.

c. Type the Solutions Enabler location or directory where SYMCLI is installedon the host.

d. Click Collect Logs.

3. Click either Open or Save to open or save the SRmViClient.zip filecontaining the SRM, ViClient, and SAPCOSPREP logs.

Upgrade the ESI web service and apply hotfixesYou can upgrade ESI from version 5.0 to version 6.0 on EHAC, without changing theconfiguration.

Perform this procedure only if Dell EMC ESI support instructs you to do so andprovides the updated ESI files.

This procedure is applicable only when the WildFly Application Server is alreadypresent in the server. Otherwise, backup the database in the existing EHAC applianceand restore it in the newly deployed Linux-based EHAC appliance.

Note

This procedure is applicable to both a Windows-based or a Linux-based EHAC server.

Procedure

1. Stop the EHAC server.

2. On a Windows-based EHAC server only, uninstall the older version of SMI-SProvider and install the latest 9.0 version, using instructions in the SolutionsEnabler Version 9.0 Installation and Configuration Guide in Dell EMC OnlineSupport.

3. Delete the older version of esi_sap_lvm_saconfig.5.x.x.x.ear in theWildFly installation path/standalone/deployments folder.

4. Copy the newer Java EAR file named esi_4_sap_lama_saconfig.6.0.x.ear into the WildFly installation path/standalone/deployments folder, where x is the latest ESI patch you received from DellEMC support. On the Linux-based EHAC appliance, the WildFly installation pathis /opt/wildfly.

5. Restart the EHAC server.

Utilities


https://support.emc.com/docu88914_Solutions-Enabler-9.0-Installation-and-Configuration-Guide.pdf?language=en_US

https://support.emc.com/docu88914_Solutions-Enabler-9.0-Installation-and-Configuration-Guide.pdf?language=en_US



CHAPTER 8

Troubleshoot and clean up storage


l Troubleshooting................................................................................................. 68l Clean up storage automatically after a clone fails...............................................70

Troubleshoot and clean up storage 67

TroubleshootingThe following table provides troubleshooting information for ESI for SAP LaMa.

Table 3 Troubleshooting

Symptom Prevention, resolution, or workaround

After you assign the XtremIO array to a user,the array details are not displayed in the homepage.

l Verify that the GlobalAccessLevel for

the XtremIO array was changed to Read-Write.

l If the level was not changed, change it to

Read-Write and then assign the array to

a user on the Access Control tab.

When you go to Storage Systems > SAN >

WBEM Managed Systems > StoragePools, a retrieve pool request fails.

The issue occurs because the array was notregistered to EHAC. Do the following:

l Go to Access Control > SAN >

WBEM Managed Systems > Grant.

Select the WBEM and click Retrieve toview all storage systems. Select the

storage system and click Add.

l After you have added the array to theEHAC database, access the StoragePools page to retrieve the information.

The EHAC Configuration Utility fails to startcorrectly or there are errors in the WildFlyconsole.

Ensure that:

l EHAC is configured. Configure WildFly byrestoring the database from a backup onpage 61 provides details.

l The user has:

n Full read/write control to the WildFlydirectory

n Permission to create the database inthe specified directory

n Permission to start and stop WildFly

A404 not found error is displayed when

you try to access the EHAC URL.

Ensure that:

l The EHAC web service is configuredcorrectly.

l WildFly is running.

l No other service is using the WildFly port.

You cannot access EHAC from anotherserver.

Ensure that both the WildFly outbound andinbound ports are open in the firewall.

You cannot add a WBEM server. Ensure that:



Table 3 Troubleshooting (continued)


l The WBEM server hostname, portnumber, connection schema, and usercredentials are all valid.

l The WBEM server is accessible fromEHAC.

l The WBEM server is running.

Note

SMI-S Provider documentation providesmore information.

You cannot remove a WBEM server. Ensure that:

l The WBEM server is accessible from theEHAC web service.

l The WBEM server is running.

You cannot add a storage system. l Ensure that the storage systemcredentials are valid.

l For file storage systems, ensure that thestorage system is accessible from theEHAC server.

l For block storage systems, ensure that:

n A WBEM server manages the storagesystem.

n The WBEM server is added to EHAC.

n SP_A and SP_B information is valid.

Storage system is not available. Check if the storage system has beenremoved from the WBEM server.

Users are suddenly unable to access EHAC. l Ensure that WildFly is still responsive.WildFly can become unresponsive duringperiods of inactivity.

l Restart WildFly.

You cannot create an admin user. Ensure that:

l The latest derby.jar file is used in the

deployment utility. Otherwise, downloadthe latest version.

l The JCE policies are copied to: C:\Program Files\Java\jdk1.8.0_131\jre\lib\security

When EHAC retrieves storage pools, an error

occurs at Storage Arrays > SAN > WBEMManaged Systems > Storage Pools.

The issue occurs because the array was notadded to the database. To correct this


Troubleshooting 69

Table 3 Troubleshooting (continued)


problem, go to Access Control, select the

array, and click Add to database.

Note

After you add the array to the EHAC database

on the Storage Pools page, EHAC retrievesthe required information.

EHAC deployment fails while being restoredfrom a backup database.

Ensure that:

l The remote database backup directorypath is correct, because the deploymentconsole does not have provision toprovide user credentials to access theremote network share.

l The remote database backup path isaccessible outside the deploymentconsole, and that the required credentialsare displayed.

Multiple NAS mount points from the same filesystem are not supported.

For SAP systems with NAS mount points, youmust have 1:1 mapping between the NAS filesystem and the NFS export on the array.Configure individual file systems for each NASmount point because the same file systemcannot be mounted as different mount points.

An SAP LaMa System Clone or Copy processon a VMAX3-based SAP system fails with thefollowing error: Failed to acquiredevice lock on all devices inthe request

This issue occurs when the VMAX3 arraylocks certain devices. Release the lock byusing the following SYMCLI command on anyhost with the Solutions Enabler command lineinterface (CLI) and that is zoned to the array:symdev -lock # release

Clean up storage automatically after a clone failsYou can use the residue cleanup procedure to clean up storage if a clone volumesprocess fails or if the postprocess clone volumes process fails.

l If the clone volumes process fails, all of the residue that is created on the array isremoved.

l If the postprocess clone volumes process fails, the following cleanup is performed:

n All LUNs are cleaned up on the array that is created for a distributed virtualvolume.

n All VPLEX virtual volumes are cleaned up.

n Clones are cleaned up based on the array type:

– For Unity arrays, all thin clones are cleaned up.

– For VMAX and PowerMax arrays, all and snapshots clones are cleaned up.



Note

For information about how to configure residue cleanup, see Configure residuecleanup in Windows-based EHAC server on page 79.


Clean up storage automatically after a clone fails 71

APPENDIX A

Install and configure Windows-based EHACserver

The appendix presents the following topics:

l Install the Windows-based EHAC server ........................................................... 74l Install the Java Development Kit (JDK).............................................................. 74l Install the Java Cryptography Extension............................................................ 74l Install the Apache database................................................................................74l Install and configure WildFly as a Windows service............................................ 75l Configure the Windows-based EHAC server...................................................... 76l Configure Windows-based EHAC web service in HTTPS mode.......................... 78l Configure residue cleanup in Windows-based EHAC server............................... 79l Start the Windows-based EHAC server............................................................. 79

Install and configure Windows-based EHAC server 73

Install the Windows-based EHAC serverThe Windows-based EHAC server is deprecated starting with ESI 6.0. A contract forlimited support shall be provided during the transition to the Linux-based EHACappliance, which is the new standard EHAC delivery model.

Use the following procedures only if you are an existing ESI customer using aWindows-based EHAC server. Otherwise, follow the steps in Deploy the Linux-basedEHAC virtual appliance on page 20.

Install the Java Development Kit (JDK)Install the JDK.

Procedure

1. Download and install JDK version 1.8 from the Java SE Downloads page on theOracle website.

2. Set the JAVA_HOME directory to the JDK1.8 installation directory. Forexample:

C:\Program Files\Java\jdk1.8.0_131\

Install the Java Cryptography ExtensionInstall the Java Cryptography Extension.

Procedure

1. Download the software and follow the installation instructions from the JavaCryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 8Download page.

2. Unzip the UnlimitedJCEPolicyJDK8.zip file to the applicable temporaryfolder or directory.

3. Copy the local_policy.jar and the US_export_policy.jar files to the%JAVA_HOME%\jre\lib\security folder

Install the Apache databaseInstall the Apache database.

Procedure

1. Navigate to the Apache Derby Downloads page.

2. Go to the latest 10.12.* version link and download the db-derby-10.12*-lib.zip file.

3. Extract the derby.jar file and copy it to a location on the EHAC server.

Install and configure Windows-based EHAC server


http://www.oracle.com/technetwork/java/javase/downloads/index.html

http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html



https://db.apache.org/derby/derby_downloads.html

Install and configure WildFly as a Windows serviceInstall WildFly Application Server version 10.1.0 or later, and configure as a Windowsservice.

Procedure

1. Download the wildfly-10.1.0.Final.zip file from the WildFly Downloadspage.

2. Create the c:\wildfly directory. Extract the contents of thewildfly-10.1.0.Final.zip file into the directory.

3. Put the service folder, which is in the docs\contrib\ directory, into thebin\ directory in the WildFly Installation folder.

4. Under the bin\services directory, open the service.bat file and confirmthat the following modifications have been made and saved:

a. Replace set JAVA_OPTS=-Xrs with REM set JAVA_OPTS=-Xrs.

b. Replace all occurrences of standalone.bat with standalone.bat -b="IP-Address of Server."

5. Open a command line window as administrator.

a. Select Run, type cmd, and press Enter.

b. Change the location to the WildFly service directory at<wildfly_home_directory>.For example: C:\Eclipse\wildfly-10.1.0.Final\wildfly-10.1.0.Final\bin\service

6. Run the service.bat install command at the command prompt.

The following screen shot shows the expected results.

Figure 19 Result of the service.bat install command

7. After the WildFly service is installed, go to Services and Application >Computer Management > WildFly.

8. Right-click WildFly, and then select Properties.


Install and configure WildFly as a Windows service 75

http://wildfly.org/downloads/

9. Select a Startup Type of Automatic.

10. Click Start, and then click OK, as shown in the following screen shot.

Figure 20 Starting the WildFly service

WildFly troubleshooting tipsThe following information describes how to address WildFly errors.

l If you see a Failed installing WildFly, Access is denied error, openthe command line prompt as an administrator:

1. Select Run to open the command line prompt as an administrator.

2. Type cmd, and then press Ctrl+Shift+Enter.

l If an Out of Memory error occurs, increase the memory that is allocated byediting the -Xms and -Xmx values in JAVA_OPTS in thestandalone.conf file inthe bin directory in WildFly.For example, at C:\Program Files\wildfly-10.1.0.Final\bin

if [ "x$JAVA_OPTS" = "x" ]; then JAVA_OPTS="-Xms128m -Xmx512m -XX:MaxPermSize=512m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000" JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true" JAVA_OPTS="$JAVA_OPTS -Djboss.server.default.config=standalone.xml"

Configure the Windows-based EHAC serverUse the following procedures to enable the EHAC Console to find the storage to beconfigured and to configure the database and update the WildFly configuration files.



Enable the EHAC Console to discover and configure storageAs part of configuring EHAC, you can enable the EHAC Console to find the storage tobe configured.

This procedure is applicable to a Windows-based EHAC server.

Configure the database and update the WildFly configuration filesAs part of configuring EHAC, you can configure the database and update the WildFlyconfiguration files.

Note

The database is already configured in Linux EHAC appliances, so this step is onlyrequired on Windows-based EHAC server.

Procedure

1. Download the EHAC_DeploymentConsole_ESISAPLaMa.jar file from the Storage Integrator for SAP Landscape Management page on Dell EMC OnlineSupport.

If you are using the EHAC appliance, the file is available in the /home/software directory.

2. Double-click EHAC_DeploymentConsole_ESISAPLaMa.jar.

3. In the Configuration Utility, click Configure Server.

4. Click Download to download the JCE files from the Oracle website.

5. In the Downloaded (Unzipped) Location of the JCE files field, click Select toselect the downloaded JCE files in the displayed location.

Note

If you are deploying EHAC for the first time, select the downloaded JCE filesand also click Configure JCE Files. It replaces the local_policy.jar andthe US_export_policy.jar files in the %JAVA_HOME%\jre\lib\security folder. A Configured JCE Files Successfully messageconfirms the JCE configuration.

6. In the WildFly Location field, type the location where WildFly is installed orclick Select and browse to find the location.

Note

Click Check Whether Configured to confirm whether WildFly is alreadyconfigured. You receive a WildFly is already configured message ifWildFly is configured.

7. Select Configure using Remote Database Backup if the WildFly Server mustbe configured, using a remote database backup.


Enable the EHAC Console to discover and configure storage 77

https://support.emc.com/products/28468_ESI-for-SAP-LVM



Note

For detailed instructions, see Configure WildFly by restoring the database froma backup on page 61.

8. Type the applicable database name.

9. If you selected Configure using Remote Database Backup, type the absolutepath of the Remote Database backup directory.

10. In the Path Where Database needs to be created field, type the applicablepath or click Select to choose a path.

11. Copy the Java EAR file named esi_4_sap_lama_saconfig.6.0.x.x.earinto the WildFly Installation path/standalone/deploymentsfolder.

12. Click Configure.

After the configuration is complete, esi_4_sap_lama_saconfig.6.0.x.x.ear is ready to be deployed.

Configure Windows-based EHAC web service in HTTPSmode

Configuring the EHAC web service to communicate through HTTPS is optional but ishighly recommended.

Note

This procedure is only applicable to a Windows-based EHAC appliance. A Linux-basedEHAC virtual appliance is already configured with these settings.

Procedure

1. Click EHAC_DeploymentConsole_ESISAPLaMa.jar to start the EHACConfiguration Utility.

2. In the Configuration Utility field, click the Configure Https tab.

3. In the Configured Database on WildFly Server Path field, type the path to theWildFly installation folder.

4. Click Check Whether Configured.

If EHAC is not configured, configure it before going to the next step. ConfigureWildFly by restoring the database from a backup on page 61 provides details.

5. For Generate a Self Signed Certificate, do the following:

a. In the Path Where Self Signed Certificate Needs to be Stored field, clickSelect and then browse to find the path in which a certificate can begenerated.

b. Type the Name of the Keystore and the Keystore alias.

c. Click Generate.

6. For Configure Server to Use Self Signed Certificate, do the following:

a. In the Keystore alias field, click Select and then browse to find the path tothe certificate that must be used.



b. Type the applicable password and alias in the Keystore Password and theKeystore alias fields.

c. Click Configure.

Configure residue cleanup in Windows-based EHAC serverConfigure residue cleanup.

Note

This procedure is only applicable for a Windows-based EHAC server. A Linux-basedappliance is already configured.

Procedure

1. In Configure Properties, select Configure Residue Clean Up.

2. In the Retry Count field, type the number of times to run the cleanup.

Note

Type a number larger than 1 to repeat the cleanup in case of failure.

3. In the Enable Residue Clean Up field, select True.

4. In the Residue Object Expiry field, type the number of hours to run thecleanup.

5. In the Residue Object Thread Sleep Time field, type the amount of time inseconds for the residue cleanup thread to sleep.

6. Click Select and browse to select the Residue Objects Directory.

7. Click Configure.

Start the Windows-based EHAC serverFollow the procedure to start the ESI services in the Windows-based EHAC server.

Note

This procedure is only applicable to a Windows-based EHAC server.

Procedure

1. Open the Windows Services dialog, and search for the service Wildfly > Start.

2. Open the EHAC UI from either one of these locations:

l http://IP Address:port/ehacl https://IP Address:port/ehac


Configure residue cleanup in Windows-based EHAC server 79

enterprise storage integrator for sap landscape ......preface as part of an effort to improve its...

Documents