Dell EMC Ready Solution for VMware NFV Platform · 5 Dell EMC Ready Solution for VMware NFV Platform Introduction The Dell EMC with VMware vCloud NFV platform automates the deployment

Dell EMC Automation Deployment Guide

Dell EMC Ready Solution for VMware NFV Platform Automation Deployment Guide for Software Release v2.0.1.02

Dell Engineering June 2018

2 Dell EMC Ready Solution for VMware NFV Platform

Revisions

Date Description

June 2018 Initial release

The information in this publication is provided “as is.” Dell Inc. makes no representations or warranties of any kind regarding the information in this

publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose.

Use, copying, and distribution of any software described in this publication requires an applicable software license.

Copyright © June, 2018 Dell Inc. or its subsidiaries. All Rights Reserved. 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 believes that the information in this document is accurate as of its publication date. The information is subject to change without notice.


Table of contents Revisions............................................................................................................................................................................. 2

Introduction ......................................................................................................................................................................... 5

1 Supported configuration ............................................................................................................................................... 6

1.1 Dell EMC NFV hardware for 14G ....................................................................................................................... 6

2 Deployment environment prerequisites ........................................................................................................................ 7

3 Getting started .............................................................................................................................................................. 8

3.1 OVA deployment................................................................................................................................................. 8

3.1.1 Overview of OVA directory file system ............................................................................................................... 9

3.2 VMware license bundle key .............................................................................................................................. 11

3.3 .yaml data input ................................................................................................................................................ 11

3.4 Run deployment orchestrator on protected site ............................................................................................... 12

3.5 Run orchestrator on recovery site .................................................................................................................... 13

3.6 Logging and reporting ....................................................................................................................................... 13

3.6.1 Sample main log file structure .......................................................................................................................... 14

3.6.2 Sample summary log file structure ................................................................................................................... 14

3.6.3 Sample inventory log file structure ................................................................................................................... 14

4 Supported features ..................................................................................................................................................... 15

4.1 Remediation ...................................................................................................................................................... 15

4.2 Scalability .......................................................................................................................................................... 15

4.3 Cleanup ............................................................................................................................................................ 15

4.3.1 VDP datastore cleanup ..................................................................................................................................... 16

4.4 14G generation hardware support .................................................................................................................... 16

4.5 Automation sanity test validation script ............................................................................................................ 16

4.5.1 Automation sanity test manual cleanup ............................................................................................................ 17

5 Additional configuration requirements ........................................................................................................................ 20

5.1 Time zone ......................................................................................................................................................... 20

5.2 Internet connectivity to stamp ........................................................................................................................... 20

5.3 Partially automated components ...................................................................................................................... 20

6 Install VMware Site Recovery Manager ..................................................................................................................... 21

6.1 Install VMware Site Recovery Manager ........................................................................................................... 22

6.2 Configure DNS .................................................................................................................................................. 26

6.3 Configure SRM site pairing ............................................................................................................................... 28


7 vSphere Replication deployment and configuration ................................................................................................... 29

7.1 vSphere Replication deployment ...................................................................................................................... 29

7.2 vSphere Replication configuration .................................................................................................................... 31

7.3 Pair protected VRM with recovery VRM ........................................................................................................... 34

7.3.1 Additional troubleshooting for connection issues ............................................................................................. 36

8 VDP configuration and deployment ............................................................................................................................ 38

8.1 Unsupported disk types and virtual volumes .................................................................................................... 38

8.2 System requirements ........................................................................................................................................ 38

8.3 Pre-installation configuration ............................................................................................................................ 39

8.3.1 DNS configuration............................................................................................................................................. 39

8.3.2 User account configuration ............................................................................................................................... 39

8.4 VDP deployment ............................................................................................................................................... 40

8.5 Initial configuration ............................................................................................................................................ 42

9 Dell EMC OpenManage Network Manager deployment ............................................................................................ 47

9.1 Deploy OVA template ....................................................................................................................................... 47

9.2 Start the virtual machine ................................................................................................................................... 48

9.3 Initial VM host configuration ............................................................................................................................. 49

9.4 Start the application .......................................................................................................................................... 52

9.5 Connect client browser ..................................................................................................................................... 52

9.6 Application next steps ....................................................................................................................................... 53

9.6.1 Verify virtual host setting .................................................................................................................................. 53

9.6.2 Create users ..................................................................................................................................................... 53

9.6.3 Update file server IP address ........................................................................................................................... 53

9.6.4 Additional information ....................................................................................................................................... 54

10 Dell EMC OpenManage Essentials installation .......................................................................................................... 55


Introduction

The Dell EMC with VMware vCloud NFV platform automates the deployment of the VMware vCloud NFVi

platform as discussed in the Two-pod Design Overview section within the Architecting a vCloud NFV Platform

Reference Architecture v2.0 guide.

The solution in this guide is for the creation of a deployment VM that consists of orchestrator, automation

script, OVA, ISO, and other required files. The automation includes pre-deployment validation, installation,

configuration, and integration of following components:

VMware ESXi™

VMware Platform Services Controller™ (PSC)

VMware vCenter Server® Appliance™ (VCSA)

VMware vSAN™

VMware NSX® Manager™

VMware NSX® Controller™

VMware NSX® Distributed Logical Router (DLR)

VMware NSX® Edge Services Gateway (ESG)

VMware vRealize® Log Insight™ (vRLI)

VMware vRealize® Operation Manger™ (vROPs)

VMware vCloud Director® (vCD)

VMware Site Recovery Manager™ (SRM)

VMware vSphere® Replication™

VMWare vSphere® Data Protection™ (vDP)

Dell EMC OpenManage Network Manager

Dell EMC OpenManage Essentials

AD/DNS/NTP Server

Virtual network configuration

https://www.vmware.com/techpapers/2017/vmware-vcloud-nfv-2-reference-architecture.html

https://www.vmware.com/techpapers/2017/vmware-vcloud-nfv-2-reference-architecture.html


1 Supported configuration

1.1 Dell EMC NFV hardware for 14G Dell EMC PowerEdge R640 or R740xd firmware versions

Firmware Firmware version

BIOS 1.3.7

iDRAC 3.15.17.15

Lifecycle controller 3.15.17.15

Intel® X710 10G/40G NIC 18.3.6

HBA330 Mini (Dell EMC PowerEdge R740xd) 13.17.03.05

BOSS-S1 (Dell EMC PowerEdge R740xd) 2.5.13.2008

Dell EMC switch versions

Switch Version

S4048T-ON 1 (out of band management)

Z9100-ON 2 (leaf switch)

Note: For additional hardware configuration and setup information, see the Dell EMC Ready Solution for

VMware NFV Platform Hardware Deployment and User Guide for Automation Deployment.


2 Deployment environment prerequisites The Dell EMC and VMware vCloud NFV automation solution deployment is bundled in a Linux-based OVA

file. The deployment VM contains all of the software dependencies required to run the VMware Orchestrator.

OVA operating system details:

CentOS Linux 7.4

Prerequisites:

An additional VMware vSphere Hypervisor (ESXi) server present inside or outside of the stamp

ESXi server version 6.5 U1

Deployment VM with connectivity to stamp specific ToR that can reach both the management and

stamp networks

Deployment server configured with IPv4 and static IP

For pre-existing AD/DNS server, it should be reachable from the stamp network

Network settings are configured with appropriate DNS server list

Pre-existing NTP server should be reachable from the stamp network

Deployment server has date/time synchronized with pre-existing NTP server

Internet proxy settings are disabled

userInput.yaml file is configured and ready for use, with the appropriate inputs and parameters

Verify that the MTU of the physical switch is set to 9216

Ensure that an additional 1G link is available as a backup link for management traffic from each

iDRAC server

Passwords for the iDRAC, switch, and organization Active Directory server are configured using the

supported password characters:

- Alpha-numeric characters such as a-z, A-Z, and 0-9

- Special characters such as !, @, #, and $

Note: For additional information, see the Dell EMC Ready Solution for VMware NFV Platform Automation

Deployment YAML Template File for Software Release v2.0.1.02.


3 Getting started Prior to starting the OVA deployment, verify that the ESXi server is properly configured as indicated in

Chapter 2, and that the physical network topology configuration is configured as outlined in the Dell EMC

Ready Solution for VMware NFV Platform NFV Hardware Deployment and User Guide for Automation

Deployment.

3.1 OVA deployment Prerequisites:

ESXi Installer 6.5 U1 .iso file

iDRAC interface with SD card with at least 16GB enabled on it

Server iDRAC is accessible

The NX/XD bit is enabled for the CPU in the BIOS

Support for hardware virtualization, either Intel VT-x or AMD RVI, is enabled on x64 CPUs

Synchronization of both protected and recovery sites with their NTP servers to ensure that the time

and zone recovery site are consistent and correct

.yaml has the NTP IP of the protected site listed as a primary NTP server

Note: Dell EMC recommends that the SATA host bus adapter be configured in pass-through mode.

To deploy OVA on CentOS, perform the following steps:

1. Login to the VMware ESXi server using VMware vSphere client.

2. From the Home screen, click File then Deploy OVF Template.

3. Within the Source screen, click Browse and navigate to the location of the .ova file, then click Next.

4. Enter the information requested in the remaining screens, then click Finish to complete the

deployment. The deployment server launches.

The pre-configured OVA deployed on the server contains all of the software dependencies necessary and is

ready for use. The OVA deployed on the VMware ESXi server contains an Orchestrator, which is a CLI-based

end user interface. The Orchestrator also allows the user to trigger the deployment automation.

To begin, check the Orchestrator help using the following commands:

Orchestrator help verification commands

Following preferences for use with Orchestrator, are supported and are optional:

Optional Orchestrator arguments


3.1.1 Overview of OVA directory file system To access the OVA directory file system, log in to the CentOS automation VM using the required credentials.

From the ESXi host menu, click Home, Other Location, Go to Test, then click vcloud-ra2.0-phase3.

Within the vcloud-ra2.0-phase3 directory, the following three folders are displayed:

sanityAutomation

software

src

vcloud-ra2.0-phase3 folder contents

3.1.1.1 sanityAutomation directory The sanityAutomation directory contains the following folders:

common

logs

tests

vcdUtils

sanityAutomation directory contents

Each of the folders contains the following:

common – directory contains testing code for the common functionalities for VCD

logs – directory contains the main and summary log files

vcdUtils – directory contains the code for VCD APIs

tests – directory contains userinput.yaml, userInputGenerator.pyc, and vcd_tests.pyc files


- userInput.yaml – file provides the required input data for deployment

- vcd_tests.pyc – file serves as the main script to run sanity automation

3.1.1.2 software directory The software directory contains the OVA files of the software invoked by scripts.

software directory contents

3.1.1.3 src directory The src directory contains the core and orchestration directories as well as the requirements.txt file.

src directory contents

Each of the folders contains the following:

core – directory contains common and component-based libraries used by the Orchestrator for

automation deployment

orchestration – directory contains the .pyc and .yaml files, as well as logs and workflow directories

as follows:

- orchestrator.pyc – main script that runs a complete NFV cloud solution


- userInput.yaml – provides the required input data for deployment

- recoveryUserInput.yaml – provides the required input data for deployment for the recovery site

- release.yaml – consists of build and date information

> logs – directory to save the main, summary, and inventory log files

> config – directory contains the configuration files for the Orchestrator

> workflows – directory contains the code for all of the workflows called by the orchestrator.pyc

for the deployment of the NFV components

requirements.txt – this file contains the third-party software information needed for installation on the

automation VM and that is necessary for running the Orchestrator.

requirements.txt software information

3.2 VMware license bundle key VMware licenses can be obtained for each component or the bundle key can be used. VMware provides the

bundle license key for all vCloud NFV components. Use of the VMware bundle key requires a separate

license be obtained for each optional VMware component, with each license manually added into the .yaml

file by the user.

3.3 .yaml data input The user is required to provide the appropriate data input data to the .yaml file. The input data is logically

categorized to avoid redundancy. Values for some of the parameters are optional and are set to a default

standard value if the user does not configure the values. The following is a sample .yaml input.

Note: A sample userInput.yaml file template is required for the Protected site as where the

recoveryUserInput.yaml file is required for the Recovery site. See the Dell EMC Ready Solution for

VMware NFV Platform Automation Deployment YAML Template File for additional information.

The protected site user input YAML is for all of the components of the management and resource pods. The

management pod components include the ESXi, AuxiliaryComponents, PSC, VCSA, VSAN, Network, VRLI,

VROPS, VCloudDirector, VREP, SRM, OME, OMNM, and VDP components.

The resource pod components include the ESXi, PSC, VCSA, VSAN, Network, VREP, and SRM components.


Sample .yaml template

The recovery site user input YAML is for the management pod only and supports the ESXi,

AuxiliaryComponents, PSC, VCSA, VSAN, Network, VREP, and SRM components.

3.4 Run deployment orchestrator on protected site The deployment VM contains solution executables that can be triggered using the orchestrator provided with

the deployment VM.

Parameters can be changed from the userInput.yaml file in the following location: Tests/vcloud-ra2.0-

phase3/src/orchestration/userIput.yaml

To run the Orchestrator, perform the following steps:

1. Login to the Deployment VM as instructed in section 3.1.

2. Navigate to the operating system CLI and change the directory to the Solution folder as shown:

a. On Microsoft Windows platform:

c: cd \Test\vcloud-ra2.0-phase3\src\orchestration>

b. On Linux platform:

<root@user>cd /Test/vcloud-ra2.0-phase3/src/orchestration/

3. Run the following command:

$ python orchestrator.pyc

4. Run the following command to skip to a particular workflow:

$ python orchestrator.pyc --skipWorkflowsTill <workflowName>

5. Run the following command to list the workflows supported:

$ python orchestrator.pyc –help


3.5 Run orchestrator on recovery site The deployment VM contains solution executables that can be triggered using the orchestrator provided with

the deployment VM.

Parameters can be changed from the recoveryUserInput.yaml file in the following location: Tests/vcloud-

ra2.0-phase3/src/orchestration/recoveryUserInput.yaml

To run the Orchestrator, perform the following steps:

1. Login to the Deployment VM as instructed in section 3.1.

2. Navigate to the operating system CLI and change the directory to the Solution folder as shown:

a. On Microsoft Windows platform:

c: cd \Test\vcloud-ra2.0-phase3\src\orchestration>

b. On Linux platform:

<root@user>cd /Test/vcloud-ra2.0-phase3/src/orchestration/


$ python orchestrator.pyc --recoverySite

4. Run the following command to skip to a particular workflow:

$ python orchestrator.pyc --skipWorkflowsTill <workflowName> --

recoverySite

5. Run the following command to list the workflows supported:

python orchestrator.pyc –help

3.6 Logging and reporting This section provides information about monitoring the live deployment status and how to reference the log

files. The status of each workflow and its tasks are displayed on the terminal and are pushed to the logs.

This solution generates the following log files:

Main log – The main log file contains all of the detailed logs with the log level set as DEBUG. These

logs provide detailed information when more logs at task level are required.

Summary log – The summary log file contains high level logs with the log level set as INFO.

Summary logs show which tasks in the workflows have executed.

Inventory log – The inventory log file contains summarized information of inventory files such as

iDRACs, ESXis, and other components in tabular format. These logs provide detailed picture of all

inventory components, access details and their distribution across Management and Edge/Resource

POD.

For every new execution or retrigger (in case of failure), new log files are created with the latest time stamp.

Logs are located in the src/orchestrator/logs folder.

In case of mail log, the log levels can be configured. Following log levels are supported:

Critical


Exception

Error

Warning

Info

Debug

3.6.1 Sample main log file structure The following is a sample of the main log file structure:

3.6.2 Sample summary log file structure The following is a sample of the summary log file structure:

3.6.3 Sample inventory log file structure The following is a sample of the inventory log file structure:


4 Supported features

4.1 Remediation Remediation allows the end user to manually remediate a workflow after a failure occurs during orchestration,

so that the deployment may continue. For manual remediation steps, a separate remediation document aids

in the necessary clean-up and mapping to a playbook section. An error that occurs during a workflow

execution displays on the console and requires instruction input from user to either continue or terminate the

deployment. The option to continue requires validation that verifies the success of the manual remediation

and resumes the workflow.

In this build, the following components for remediation are supported: preDeployment, prepareVSAN,

auxiliaryServices, mgmtVCSApostConfig, mgmtVNetwork, mgmtVsan, resourceVNetwork, resourceVsan,

nsxManager, nsxDLRWorkflow, pscHA, vcsaHA, vrliVropsVcd, and the nsxVRLi wofkflows.

Note: For additional information about manual remediation of the supported workflow, see Dell EMC Ready

Solution for VMware NFV Platform Automation Deployment Remediation Guide for Software Release

v2.0.1.02.

4.2 Scalability The scalability feature supports expansion of ESXi servers on both management and edge/resource pods

from a minimum of four servers, to a maximum of 64 servers. The initial deployment requires four servers in

the management pod, and minimum of four servers in the edge/resource pod which can be extended to a

maximum of 64 servers.

Note: If additional nodes are needed, post-configuration and customization in the management and

edge/resource pods is required.

For scalability, users must provide the details using the IP range of all ESXi servers to be deployed in the

management and edge/resource pods. Along with the ESXi details, iDRAC server details are required to

indicate where ESXi servers are deployed. All ESXi servers deployed as a scalability feature, contribute to

vsanDatastore and ESXi host cluster on both the management and edge/resource pods.

4.3 Cleanup If the setup is partially deployed and all ESXi hosts are up and vSAN datastore is created and is configured to

run from scratch, perform the cleanup process before triggering the deployment. The separate

orchestrator_cleanup.py script performs the cleanup by deleting all VMs from all ESXi hosts and from the

vSAN datastore.

Note: Before running the cleanup script, manually delete any vApps within the organization VCD.

To execute the script cleanup, perform the following steps:


1. Log in to the CentOS automation VM.

2. Open the terminal and navigate to the following file path:

<root@user>cd /Test/vcloud-ra2.0-phase3/src/orchestration


python orchestrator_cleanup.py

Note: SSH must be enabled on all ESXi hosts in order for the cleanup script to run successfully.

4.3.1 VDP datastore cleanup For VDP datastore cleanup, the same cleanup script mentioned in section 4.3, is used. In the event of a

failure, perform the following steps to manually clean or delete the VDP datastore and format it with VMFS:

1. Open the iDRAC console of the ESXi where the VDP datastore is located.

2. Map Ubuntu16.iso with the iDRAC virtual CD-DVD drive.

Note: Make note of the VDP datastore disks naa-ID as it is required in the following step.

3. Select Try Ubuntu without installing for the Boot server 1st option.

4. After Ubuntu starts, open the Disks utility (partition utility) from the user interface.

5. Verify which partitions have a VMFS file system.

6. Click to select the hard drives with the VMFS file systems then delete them.

Note: Do not format or delete VMFS on the SD card as the ESXi server resides on it.

7. Unmount the Ubuntu disk from iDRAC and reboot the server. ESXi reboots with clean disks.

4.4 14G generation hardware support The automation script provides support for 14G hardware. Before running the script, verify that the

HardwareGeneration key within userInput.yaml is set to 14G.

4.5 Automation sanity test validation script The sanity test validation script creates a sample organization that allocates resources to it and deploys a

VMware vApp with two Linux VMs used to check interconnectivity. Parameters can be changed from the

userInput.yaml file in the following location: tests/vcloud-ra.2.0-phase3/sanityAutomation/tests/userInput.yaml

The following is the test execution sequence:

1. Create organization

2. Create organization VDC

3. Add local user to the organization

4. Create organization VDC network

5. Create catalog

6. Create vAPP


a. Deploy VMs

b. Power-on VMs

To run the sanity test validation script, perform the following steps:

Note: The passwords in the automation sanity test userInput.yaml file must be in apostrophes (‘ ‘), for

example, ‘abC@1234’.

1. Log in to the CentOS automation VM.

2. Open the terminal and navigate to the following file path:

<root@user>cd /Test/vcloud-ra2.0-phase3/sanityAutomation/tests/


python vcd_tests.pyc

Sample VCD test pyc output

Note: An incorrect userInput.yaml file will cause the automation sanity test script to fail. If this occurs,

manually correct the failure using the automation sanity test manual cleanup steps provided in section 4.5.1.

After performing the manual cleanup process, run the sanity test validation script command again.

4.5.1 Automation sanity test manual cleanup The automatic sanity test manual cleanup process is done in the reverse order of the creation of the

components on the VMware vCloud Director.

1. From the vCloud Director Home screen, click Manage & Monitor, then Organizations.

2. In the left navigation panel, click desired organization name.


Organizations listing

A tab with the selected organization name displays next to the System tab.

3. From the Organization tab, expand the virtual datacenters then select the desired organization VDC.

4. Within the organization details, right-click the network name and select Delete.

5. From the Organization tab, click the Catalogs tab, then click the Catalogs sub-tab.

6. Right-click on the name of the catalog and click Delete.

Organization catalog listing

7. From the Organization tab, click Administration, then Virtual Datacenters.

8. On the right-side of the screen, locate and right-click on the desired organization VDC name, click

Disable, then click OK.

9. After the VDC is disabled, right-click on the organization VDC name and select Delete, then OK.

10. Close the Organization tab.

11. From the system, click Manage & Monitor, then Organizations.

12. Click to select the organization to be deleted from the list, right-click on the name of the organization,

then click Disable.

13. Right-click on the organization name again, click Delete, and then click OK. The organization user is

deleted.


Delete Organization option


5 Additional configuration requirements

5.1 Time zone By design, the VMware ESXi only supports the UTC time zone. Time zones other than UTC are not

supported.

5.2 Internet connectivity to stamp Internet connectivity is required for Microsoft Windows activation. The following components use Microsoft

Windows OVA:

Aux component (AD/ DNS/NTP)

SQL server for VCD

SRM

5.3 Partially automated components The following components are partially automated and require further configuration. The following

components require additional configuration efforts:

VMware Site Recovery Manager

VMware vSphere Replication

VMware vSphere Data Protection

Dell OpenManage Network Manager (OMNM)

Note: For Dell OpenManage Network Manager (OMNM), see the Support for Dell OpenManage Network

Manager page.

Dell EMC OpenManage Essentials (OME)

Note: For Dell EMC OpenManage Essentials (OME) post-deployment steps, see Dell EMC OpenManage

Essentials v2.3 User’s Guide.

http://www.dell.com/support/home/us/en/04/product-support/product/dell-openmanage-network-manager/manuals

http://www.dell.com/support/home/us/en/04/product-support/product/dell-openmanage-network-manager/manuals

http://www.dell.com/support/manuals/us/en/04/openmanage-essentials-v2.3/ome_2.3_users_guide/configuring-openmanage-essentials?guid=guid-b560014e-9e79-44cd-a92a-aec1ecee34c1&lang=en-us

http://www.dell.com/support/manuals/us/en/04/openmanage-essentials-v2.3/ome_2.3_users_guide/configuring-openmanage-essentials?guid=guid-b560014e-9e79-44cd-a92a-aec1ecee34c1&lang=en-us


6 Install VMware Site Recovery Manager The VMware vCenter Site Recovery Manager (SRM) is a business continuity and disaster recovery solution

that helps you plan, test, and execute the recovery of vCenter virtual machines between one site (the

protected site) and another site (the recovery site).

Minimum SRM system requirements

Component Requirement

Processor At least two 2.0GHz or higher Intel or AMD x86 processors. Site Recovery Manager deployments that manage large environments require four 2.0GHz CPUs.

Memory 2GB minimum. You might require more memory if you use the embedded database, as the content of the database grows. The memory requirement increases if Site Recovery Manager manages large environments.

Disk Storage 5GB minimum. If you install Site Recovery Manager on a different drive to the C: drive, the Site Recovery Manager installer still requires at least 1GB of free space on the C: drive. This space is required for extracting and caching the installation package. You might require more disk storage if you use the embedded database, as the content of the database grows.

Networking 1GB recommended for communication between Site Recovery Manager sites.

Supported host operating systems for VMware vCenter Server installation

Microsoft Windows OS 6.5 U1

Microsoft Windows Server 2016 64-bit

Yes

Microsoft Windows Server 2012 R2 64-bit

Yes

Microsoft Windows Server 2012 64-bit

Yes

Component requirements for both sites

Protected site Recovery site

VMware vSphere Hypervisor (ESXi)

VMware vSphere Hypervisor (ESXi)

VMware Platform Services Controller

Platform Services Controller


VMware vCenter Server vCenter Server

VMware vSphere Replication

vSphere Replication

VMware Site Recovery Manager

Site Recovery Manager

Domain Name Server (DNS)

Domain Name Server (DNS)

Active Directory (AD-DS) Active Directory (AD-DS)

NTP NTP

Compatible virtual machine hardware version

Compatible virtual machine hardware version

VMware tools VMware tools

VMware Site Recovery Manager architecture with VMware vSphere Replication

6.1 Install VMware Site Recovery Manager Prerequisite:


Microsoft Windows Server is installed

The VMware Site Recovery Manager, or SRM, can be installed on the same machine as VMware vCenter or

on a dedicated server.

Note: If you are using the VMware vCenter Server appliance, the Site Recovery Manager 6.5.1 must be

installed on separate Windows server.

1. Right-click the SRM 6.5.1 installation file and click Run as Administrator to initiate the VMware SRM

6.5.1 installation.

VMware SRM 6.5.1 installation file

The SRM 6.5 installer file extracts the necessary installation files in the temporary folder.

2. From the SRM installation wizard, click Next to start the installation.

3. Review the terms outlined within the License agreement and to agree to the terms, click I agree to

the terms in the license agreement then click Next.

4. From the Installation Prerequisites screen, click Next.

5. Select the destination folder to install Site Recovery Manager 6.5 and click Next.

Destination folder screen

http://www.vmwarearena.com/wp-content/uploads/2017/10/Install-Site-Recovery-Manager-6.5_1.jpg


6. Within the vSphere Platform Services Controller screen, specify the hostname or IP address of

PSC during the installation, enter the single sign-on (SSO) administrative credentials in the fields

provided, and then click Next.

Note: Dell EMC recommends the use of FQDN names throughout the installation of all vCenter, SRM,

vSphere Replication components.

vSphere Platform Service Controller screen

7. Review the PSC certificate information, then click Accept.

8. From the VMware vCenter Server screen, click to select the vCenter Server address in the field

provided instance to register Site Recovery Manager, then click Next.

9. Specify the Local Site name for the SRM site. This specified name appears in the SRM interface.

Enter administrator email address for this site and select the IP address of the local host from the

drop-down to be used by SRM.

Note: By default, vCenter Server address is used if a name is not specified during the installation.

10. If you have dual IP addresses, enter the administrator email address for this site and select the IP

address of the local host from the drop-down to be used by SRM then click Next.

Note: If you have the dual IP address on the server, select the appropriate IP address for the SRM

installation.

11. From the Site Recovery Manager Plug-in ID screen, select one of the two options provided:

a. Default Site Recovery Manager Plug-in Identifier: select if you are installing SRM with a

standard configuration with one protected site and one recovery site.

b. Create a Custom Site Recovery Manager Plug-in identifier: select this option when you install

Site Recovery Manager in a shared recovery site configuration, with multiple protected sites and

one recovery site.

Note: For this example, selection of the Default Site Recovery Manager Plug-in is used for the installation

of a standard configuration, such as one protected and one recovery site.

12. Depending on the plug-in selected, enter the required Plug-in ID, Organization, and Description in

the fields provided, then click Next.


13. From the Certificate Type screen, select the desired server certificate option:

a. Automatically generate a certificate

b. Use a PKCS#12 certificate file

14. Click Next.

15. From the Generate Certificate screen, specify the Organization and Organization Unit in the fields

provided, then click Next.

Certificate generation screen

16. Within the Database Server Selection screen, select either the embedded database (vPostgres

database) or a custom external database for the SRM 6.5 installation.

Note: To use an external database, select Use a custom database server and from the drop-down menu,

select the existing 64-bit DSN. Alternately, you can click on DSN setup to create a new 64-bit DSN for SRM

database. The example in this section uses an embedded database option for SRM 6.5 installation.

17. Click Next.

18. From the Embedded Database Configuration screen, enter the Data source name, DB username

and password in the fields provided. Leave the remaining Database port, Connection count, and Max

Connections field with the default settings, then click Next.

19. Select the user account under which to run the Site Recovery Manager Server service and click Next.

Note: It can be a Local system account or an Active Directory domain account.


Site Recovery Manager Service Account settings screen

20. Click Install to start the SRM installation.

Note: It will take a few minutes to complete the Site Recovery Manager installation.

21. Once the SRM 6.5 installation is completed, click Finish. Once the installation is completed, two

Microsoft Windows related services, VMware vCenter Site Recovery Manager Server and VMware

vCenter Site Recovery Manager Embedded database, begin running on the server where the SRM

is installed.

22. Once installation is complete and SRM related services are started, log in to the vCenter Server site

from the VMware vSphere Web Client.

23. The Site Recovery icon displays in the Inventories section of the Web Client.

VMware vSphere Web Client Inventories screen

6.2 Configure DNS Prior to pairing the protected and recovery site, Forwarders must be added to each DNS site.

1. Open the DNS manager and right-click ADDNSNTPSERVER, then click Properties.

http://www.vmwarearena.com/wp-content/uploads/2017/10/Install-Site-Recovery-Manager-6.5_24.jpg


ADDNSNTPSERVER selection screen

2. Click the Forwarders tab then click Edit.

Forwarders tab

3. Add the DNS IP of the recover site. As soon as the validation is complete, a green check displays.

4. Click OK.

Edit Forwarders screen


5. Repeat the steps in this section for the Recover site to add the protected Forwarders for the DNS

manager.

6.3 Configure SRM site pairing After installing the SRM, you must pair the SRM protected and recovery sites. Once the site pairing is

completed, both the SRM sites display under site recovery plug-in within the VMware vSphere Web Client.

Site pairing can be done either at the protected site or at the recovery site.

1. Log in to your protected vCenter Server site using the VMware vSphere Web Client.

2. From the Home page, click the Site Recovery plug-in then select Sites.

Sites listing

3. From the Objects tab, click Pair Site.

4. Within the Select site screen, enter the PSC address in the field provided.

Note: Do not make any changes to the default port number.

5. Click Next.

6. From the Select vCenter Server screen, click to highlight the SRM extension, then enter the

Username and Password in the fields provided, then click Finish. The SRM is now paired.

Paired SRM

http://www.vmwarearena.com/wp-content/uploads/2015/09/SRM-6.0-Site-Pairing-_1.jpg


7 vSphere Replication deployment and configuration The VMware vSphere Replication is an alternative to storage-based replication as it protects virtual machines

from partial or complete site failure. VMs are protected by replicating the VMs between the following sites:

From a source site to a target site

Within a single site from one cluster to another

From multiple source sites to a shared remote target site

Prerequisites:

ESXI 6.5 U1 Server is installed and running and meets the following requirements:

- Supports 64-bit x86 processors released after September 2006

- A host machine with at least two CPU cores

- 32GB memory, 1 TB local hard drive

Active Directory, DNS, and NTP are installed and running

PSC and vSphere Web Client 6.5.0 installations have been performed for the source and target sites

7.1 vSphere Replication deployment To deploy the OVA file of a vSphere Replication, perform the following steps:

1. Using the VMware vSphere Web Client, log in to the VMware vCenter Server.

2. Click to select the desired ESXi host, then click Deploy OVF Template.

3. Select Local file, then Browse, and navigate to the \bin directory within the ISO image.

4. Click to select the vSphere_Replication_OVF10.ovf, vSphere_Replication-system.vmdk, and

vSphere_Replication-support.vmdk files to mount to the vSphere Replication ISO image.

Select template screen

5. Click Next.

6. From the Select name and location screen, enter the desired name in the Name: field, then expand

each section to select the desired location, then click Next.

7. Within the Select a resource screen, select where to run the deployed template click Next.


Resource selection screen

8. Verify the template details and click Next.

9. Scroll to review the contents of the license agreement and if you accept the terms associated with the

template, click Accept then click Next.

10. Within the Select storage screen, click to select appropriate deployment configuration and click

Next.

Select storage screen

11. From the Destination Network drop-down, select the desired destination network and click Next.

12. Customize the deployment properties of this software solution and click Next.


Template customization screen

13. Verify the vServices to which the deployed OVF template should bind, then click Next.

14. Review the configuration data and click Finish.

15. After the VM is deployed, power it On.

16. Right-click on vReplication vSphere VM and select Edit Settings.

17. Add the new replication-DV-PortGroup (Mgmt-DVS-Infra) network adapter then click OK.

vReplication vSphere VM settings screen

Note: Repeat the steps within this section to deploy vSphere Replication on the target site.

7.2 vSphere Replication configuration Prerequisites:


Verify that the vSphere Replication appliance is powered on

Ensure that you have administrator privileges to configure the vSphere Replication appliance

Check that the vSphere Replication management server is synchronized with the time of the single

sign-on server

To configure the vSphere Replication, perform the following steps:

1. After the VR deployment is completed, access the management URL of the vSphere Replication

appliance using following URL: https://<VR-IP or hostname>:5480

2. Log in using the root user account and password specified during the appliance deployment.

vSphere Replication Appliance log in screen

3. To configure the vSphere Replication appliance, click the VR tab, then click Configuration.

4. In the LookupService Address, enter the FQDN of the vCenter Server.

Note: If your vCenter is an embedded PSC deployment, enter the FQDN of the PSC appliance if vCenter is

an external PSC deployment.

5. Enter the SSO username and the password for the same.

6. Review the EULA and if you agree to the terms, accept the license and click Save and Restart

services.

vSphere Replication Appliance Configuration screen


SSL Certificate confirmation screen

Note: If you have trusted CA certificates, select the SSL certificates policy.

7. Click the Network tab and enter the hostname in the Address tab.

8. Configure IPs for both of the interfaces:

a. In eth0, provide the management IP.

b. In eth1, provide replication IP.

9. Leave the IPIv4 default gateway blank on the first interface, however the gateway of first interface

needs to be added to the second interface, which is a replication network. It means the gateway

which is shown in the image 192.168.78.252 will be added as a default route for vSphere Replication

appliance.

10. Once complete, click Save Settings.

11. To verify the default route, log in to the vSphere Replication appliance console and type the following

command:

# route –n

vSphere Replication Appliance Network Address Settings screen


12. From the VR Configuration tab, reconfigure the vSphere Replication appliance, provide replication

IP address for incoming storage traffic, and then click Apply Network Settings.

13. Click Save and Restart services.

14. Once the vSphere replication is configured, log out and log in again to the Web Client on vCenter to

see vSphere Replication option.

vSphere Replication listing within vCenter Web Client Home screen

7.3 Pair protected VRM with recovery VRM Prerequisites:

If you plan to configure a remote connection, obtain the IP address or domain name of the server

where the PSC runs. The address appears in the LookupService Address text box on the

Configuration tab under VR in the vSphere Replication VAMI on the target site.

1. Click the vSphere Replication listing in the Navigator tree of the vSphere Web Client.

2. Under vSphere Replication, click the Home tab.

3. Click the Manage tab, then from the Manage section, click Configure, Target Sites, and then click

the Connect to target site icon.


Manage section

4. Enter the remote site PSC address and credentials in the fields provided, then click on Log In.

Target Site credentials screen

5. When prompted, click Yes if you trust the remote site.

6. Select the remote site to which you want to connect, and click OK.


Target site connection screen

7. In the vSphere Web Client, from the vSphere Replication tab under Manage, you can check the

state of the connections to target sites.

Target site connection status screen

If Target Site state shows as Not authenticated, this indicates that the remote site is online but the user

session has expired. In this state, you must enter credentials to manage replication tasks. Replications that

are already configured run in the background. Reconnection to the sites is necessary.

If the Target Site state shows as Connection issue, you must repair the connection to manage existing

replications. Select the target site that indicates the Connection issue status and click the Reconnect icon.

Go to recovery site and repeat the steps within this section. Once connection to target site establish at

recovery site go back to protected site and click the Reconnect icon to establish a connection to a remote

site.

7.3.1 Additional troubleshooting for connection issues

Error type Description Solution

Connection issue Sites were not created for both protected and recovery appliances and is only connected in one way.

Proceed with the creation of the missing appliance. Once both sites are configured, the connection status changes.


Authentication error CA certificate is not properly exchanged. 1. Check if firewall is disabled on both internal AD/DNS servers.

2. Check if vReplication appliance iptables have allowed the required ports.

3. Log in to vCenter Appliance Console through the ESXi server on which the primary VCSA (VCSA active) is deployed, and restart vCenter services.

service-control --stop –-

all , service-control --

start –-all

Connection issues


8 VDP configuration and deployment VMware vSphere Data Protection is a backup and recovery solution designed for vSphere environments.

Powered by EMC Avamar, vSphere Data Protection provides agentless, image-level virtual machine backups

to disk. vSphere Data Protection is fully integrated with vCenter Server and the VMware vSphere Web Client.

Prerequisites:

VDP 6.1.6 requires the following software:

VMware vCenter Server 6.5 Update 1e

VDP 6.1.6 supports the Linux-based vCenter server virtual appliance

VMware vSphere Web Client

Note: For information about the browsers supported for the VMware vSphere Web Client, see vSphere Web

Client Software Requirements.

Note: Web browsers must be enabled with Adobe Flash Player 11.3 or later to access the vSphere Web

Client and to support VDP functionality.

VMware vSphere Host 6.5 U1

8.1 Unsupported disk types and virtual volumes When planning for backups, verify that the disks are supported by VDP. Currently, VDP does not support the

following virtual hardware disk types or virtual volumes:

RDM Independent – Virtual Compatibility Mode

RDM Physical Compatibility Mode

VDP Appliance v6.1 does not support backups and restores of VMs on virtual volumes, or VVOLs

8.2 System requirements The following system requirements are necessary for VDP:

VDP is available in the following configurations:

0.5TB

1 TB

2 TB

4 TB

6 TB

8 TB

Note: After VDP is deployed, the size can be increased.

https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.install.doc%2FGUID-F

https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.install.doc%2FGUID-F


Minimum system requirements for VDP

0.5 TB 1 TB 2 TB 4 TB 6 TB 8 TB

Processors Minimum of four 2 GHz processors

Minimum of four 2 GHz processors





Memory 4 GB 4 GB 4 GB 8 GB 10 GB 12 GB

Disk space 873 GB 1,600 GB 3 TB 6 TB 9 TB 12 TB

8.3 Pre-installation configuration

8.3.1 DNS configuration The DNS server must support both forward and reverse lookup on the VDP and the vCenter. Prior to

deployment, you must add an entry to the DNS server for the VDP appliance’s IP address and fully Qualified

Domain Names (FQDN). Additionally, communication to DNS is required by VMware proxy nodes (port 53)

over both TCP and UDP protocols.

Note: Failure to set up DNS properly causes runtime or configuration issues.

To confirm that DNS is configured properly, run the following commands from the command prompt on the

vCenter server:

nslookup <FQDN_of_VDP>

The nslookup command returns the FQDN of the VDP appliance.

nslookup <FQDN_of_vCenter>

The nslookup command returns the FQDN of the vCenter server.

Note: If the nslookup commands return the proper information, close the command prompt.

If the nslookup commands do not confirm proper configuration, manually add the VDP name and address

to the /etc/hosts file in the vCenter.

8.3.2 User account configuration Before the vCenter user account can be used with VDP, or before the SSO admin user can be used with

VDP, add the following users as administrator in the vCenter root node.

Note: Users who inherit permissions from group roles are not valid.

Note: Permission-level restrictions can be placed on user accounts should they be necessary. For additional

user account configuration information, see the User Account Configuration section of the vSphere Data

Protection Administration Guide.

https://docs.vmware.com/en/VMware-vSphere/6.0/vmware-data-protection-administration-guide-60.pdf

https://docs.vmware.com/en/VMware-vSphere/6.0/vmware-data-protection-administration-guide-60.pdf


Use the following steps to configure the VDP user or SSO admin user using the vSphere Web Client:.

1. From a web browser, access the vSphere Web Client:

https://<IP_address_vCenter_Server>:9443/vsphere-client/

2. Using the required log in credentials, log in with an account that has administrative privileges.

3. Select vCenter, then Hosts and Clusters.

4. From the left navigation panel, click to select the desired vCenter server.

Note: Ensure that you select the vCenter from the root level of the tree structure (represented under Hosts

and Clusters). If you select the vCenter VM, the configuration fails.

vCenter server listing within Navigator panel

5. Click the Permissions tab, then click the Add (+) icon.

6. From the Domain drop-down list, select domain, server, or VSPHERE.LOCAL.

Note: For VMware vCenter version 5.1 and earlier, the default domain is SYSTEM-DOMAIN.

7. Select the user who will administer VDP or be the SSO admin user, and then click Add, then OK.

8. From the Assigned Role list, select Administrator.

9. Confirm that the Propagate to child objects box is selected then click OK.

10. Click Home, Administration, Role Manager, and then Administrator role and verify that the newly

created user is listed under Administrators.

Note: If the VDP backup user using the VDP Configure utility belongs to a domain account, use the

SYSTEM-DOMAIN\admin format in VDP-configure. If the username is entered in the format

admin@SYSTEM-DOMAIN format, tasks related to the backup job may not show up on the Recent Running

tasks.

Note: The domain account password cannot contain spaces.

8.4 VDP deployment The vSphere Data Protection (VDP) installation is completed through two steps:

Deploying the OVF template

Initial configuration


1. Download the VMware vSphere Data Protection OVA.

2. Browse to the VMware vSphere Web Client and right-click the cluster where the virtual appliance will

reside.

3. Click Deploy OVF Template, navigate to the downloaded OVA file, and click Next.

4. In the Select name and location screen, enter a name for the virtual appliance and select a location,

then click Next.

Name and location selection screen

5. From the Select a resource screen, expand each section to select where to run the deployed

template, then click Next.

6. Review the OVF template details and click Next.

7. From the Accept license agreements screen, review the information provided within the End User

License Agreement, and to accept the terms, click Accept then Next.

8. On the Select Storage screen, select the virtual disk format and select vdpDatastore as the location

of the storage for the VDP appliance, then click Next.

Storage selection screen

9. Within the Setup networks screen, use the Destination Network drop-down to select the VDP

appliance and click Next.


Network selection screen

10. From the Customize template screen, specify the DNS, Default Gateway, Network 1 IP Address,

and Network 1 Netmask in the fields provided.

Note: Confirm that the IP addresses are correct and match the entry in the DNS server. Setting incorrect IP

addresses in this dialog box will require the .ova to be redeployed.

Customize template screen

11. Click Next.

12. From the Ready to complete screen, confirm that all of the deployment options are correct, click to

select the Power on after deployment option, and then click Finish.

8.5 Initial configuration Prerequisites:

Ensure successful deployment of the VDP .ova template

DNS values for forward and reverse lookup are set


Manual addition of DNS host record for the IP address of the virtual appliance, the desired host

name, and domain

1. Browse to the following URL: https:// <IP_address_VDP_appliance>:8543/vdp-configure where

<IP_address_VDP_appliance> is the IP address or FQDN of the vSphere Data Protection appliance.

2. From the VDP log in page, type root in the Username: field and changeme in the Password: field,

then click Login.

VDP Configuration Utility login screen

3. From the VDP Welcome page, click Next.

4. Either confirm or specify the following network and server information for the VDP appliance, then

click Next.

Network Settings screen

Note: Ensure that the values are correctly populated, otherwise, the installation fails.

5. From the Time Zone screen, select the appropriate time zone for the VDP appliance, then click Next.

6. Within the VDP Credentials screen, configure a new root password for the virtual appliance and click

Next.


VDP Credentials screen

7. From the vCenter Registration page enter the vCenter user name.

Note: If an SSO admin user is specified as the vCenter username in the format <[email protected]>,

tasks related to VDP operations do not appear in the vCenter Recent Tasks pane of the vSphere web client.

For tasks to appear in the Recent Tasks pane, specify the SSO admin user in the format

<vsphere.local\username>.

8. Click Test Connection. A Connection success message displays.

Note: If this message does not display, troubleshoot your settings and repeat this step until a successful

message appears.

9. Click Next to proceed to the Create Storage screen.

10. From the Create Storage screen, click the option to Create new storage and adjust the size of the

datastore to create for backup data, to 6TB then click Next.

Datastore capacity settings screen


11. From the VDP Migration screen select the storage to use and the provisioning type, then click Next.

12. Within the Device Allocation screen, select the datastore, such as vdpDatastore, created

specifically for VDP to store VDP storage disks.

13. From the Provision drop-down, select Thick Lazy-Zeroed, then click Next.

Device Allocation screen

14. Accept the default CPU and set memory allocations to 10GB which is required for 6TB storage

capacity, then click Next.

15. From the Product Improvement screen, review the participation guidelines and to participate in the

program, click to select the Enable Customer Experience Improvement Participation checkbox or

leave the checkbox blank to decline participation, then click Next.

16. Within the Ready to Complete screen, select whether or not to run performance analysis on the

storage configuration, then click Next.

Ready to complete verification screen


17. Click Yes to confirm reconfiguration and to reboot the virtual appliance. This process can take around

15 minutes depending on the infrastructure. When the appliance is back online, a VDP icon displays

on the home page of the vSphere Web Client, default alarms are also added.

VMware vSphere Web Client Home screen


9 Dell EMC OpenManage Network Manager deployment The Dell EMC OpenManage Network Manager, or OMNM, provides automated, consolidated configuration,

and control of your network’s resources, even if they come from different vendors. OMNM is customizable

and allows for the unification of multiple systems for a single view of IT assets, monitoring, compliance

auditing, and troubleshooting.

For additional OMNM installation information, see the following product guide:

Dell EMC OpenManage Network Manager Version 6.5 User Guide

Prerequisites:

Download of the latest Dell OpenManage Network Manager .ova file

An identified IPv4 address for the VM appliance

Connectivity of the VM host to the target managed devices

Deactivation of firewall or other restrictions-blocked communications for ICMP, SNMP, FTP, TFTP,

SCP, SSH, Telnet, or HTTP

Internet access and SMTP for Dell EMC OpenManage notifications

E-mail address for the license and subscription renewal

9.1 Deploy OVA template To deploy the OVA template, perform the following steps:

1. From the VMware vCenter application, click File, Deploy OVA Template, and then Deploy.

2. Browse to the location where the OpenManage Network Manager OVA file is saved.

Deployment source location selection screen

3. After the file location is selected, click Next.

4. From the OVF Template Details screen, verify the product details provided, then click Next.

http://downloads.dell.com/Manuals/all-products/esuprt_ser_stor_net/esuprt_networking/dell-openmanage-network-manager_User%27s_Guide9_en-us.pdf


5. In the Name: field within the Name and Location screen, enter the desired name for the deployed

template, and then click Next.

Name and Location screen

6. Within the Disk Format screen, select the desired disk provisioning option, then click Next.

7. Select the necessary network mapping settings, then click Next.

8. From the Ready to Complete screen, review the selections made and if no changes are necessary,

click Finish. The deployment process beings.

Deployment status screen

9.2 Start the virtual machine 1. After deploying of the OVA template in vSphere, right-click on the VM and select the option to boot

the appliance.

2. From the log in screen, enter the following default credentials:

user name: synergy

password: synergyP@$$

Appliance log in screen


9.3 Initial VM host configuration After logging in to the VM appliance, perform the following steps:

1. Within the appliance, enter the following command:

./setup

Setup command

2. From the Configure the VM for initial VM setup menu, enter 1 in the Please select a menu option:

field.

VM setup option screen

The initialization status screen provides the completion rate.

3. From the VM Configuration screen, press Enter to proceed with the configuration.


Configuration start screen

4. In the list of available Ethernet interfaces on the VM, enter the target Ethernet interface in the field

provided.

Available Ethernet interfaces screen

Note: The VM is designed to start up using the eth0 interface available. Make sure eth<zero> is entered

when asked. ethO (oh) is not a valid Linux interface and interface configuration will not be successful. If

customized VM configuration is required to support alternate interfaces, DNS or other environments, consult

you Linux and network administrator.

Ethernet interface selection screen

5. Review the information within the Settings page, then press Enter to continue.


Settings page

6. From the VM restart confirmation screen, press Enter to restart the VM.

VM restart screen

7. After the VM restarts, go to the . /setup menu within the appliance.


field.

Virtual Appliance Configuration menu


9.4 Start the application 1. On completion of the VM setup, confirm the option to reboot the VM.

2. After the VM restarts, go to the . /setup menu within the appliance.


field. The option continuously checks the server status until an error is encountered or until the

servers come up successfully. A successful check results in the following status:

Check status screen

On reboot or system restart, by default, the application server, web server, and the database are configured

to autostart. To stop or start the server without rebooting the VM, use the following commands:

To stop or start the Application server:

sudo service oware start | stop

To stop or start the Synergy server (web server service):

sudo service synergy start | stop

Note: The startup process typically takes a few minutes, and depends on the speed of the host. The

application server needs to be fully operational before the web server can provide full client access.

9.5 Connect client browser 1. After configuring the network and rebooting the server, allow three to five minutes for the servers to

come up after restart.

2. Navigate to https://<OMNM VM IP Address>:8080 access the OMNM Login screen.

3. Enter the following default portal login credentials:

Username: admin

Password: admin

4. Click the Sign in button.


OMNM Login screen

5. When prompted, enter a password reminder question for the admin user.

9.6 Application next steps

OMNM Home screen

9.6.1 Verify virtual host setting 1. From the top navigation, click Go To, Control Panel, then click Portal, Portal Settings, then Virtual

Host.

2. Verify that the virtual host IP displays as <OMNM VM IPaddress> for this VM.

9.6.2 Create users From the top navigation, click Go To, Control Panel, then click Portal, Portal Settings, Users and

Organizations, then Add.

9.6.3 Update file server IP address Update the file server IP address to use the pre-configured file server within OMNM.

1. From the Resources page, navigate to the File Management subpage.

2. In the File Servers portlet, right-click the listing and select New

3. Set the following parameters:


- Name: Local File server

- Enabled: Checked

- Select File Server Type: FTP, TFTP

- IP address: The <OMNM_VM_IP_address> set for the VM

- Login: ftpuser

- Password: ftpuserPa$$

- External IP Address: Leave blank. This is only required if the managed devices are using a

different IP address to reference this same File server.

- Net Mask: The mask for the <OMNM VM IPaddress>

4. Click the Test button to confirm that the server is working.

5. Click Save. You have set up a file server for your system.

9.6.4 Additional information The OpenManage Network Manager software is now prepared to perform the following tasks:

Discover devices and links

View topology

Performance monitoring

File management: backup, restore, and deploy

Receive alarms

Receive traffic flows

Run reports

Note: See the Dell EMC OpenManage Network Manager Quick Start Guide or the Dell EMC OpenManage

Network Manager User Guide for additional task information.

For reference, verify the information within the OMNM license for specific product, device, and subscription

information.

License viewer


10 Dell EMC OpenManage Essentials installation The Dell EMC OpenManage Essentials, or OME, is a lightweight, web-based one-to-many console that

provides a comprehensive view of Dell EMC systems, devices, and components in an enterprise network.

Prerequisites:

Microsoft Windows 2012 R2 with minimum 4GB RAM, 2 cores, and 10GB hard drive space for small

deployment of up to 100 devices

Note: Dell EMC recommends the use of small deployments

Network of 1Gbps or higher

Dell EMC OpenManageEssentials_2_3_A00.exe file package

Download and installation of KB2919355 manually from MSDN before installing the other pre-

requisites on Microsoft Windows 2012 R2

Local SQL express data base, SQL Server 2012 SP1

Microsoft .NET Framework 4.6.2

Microsoft Visual Studio Runtime 14.0

Internet connection

Enable SNMP services after OME installation

1. Place the OpenManageEssentials_2_3_A00.exe file package within the Microsoft Windows machine

and extract the OME package files to the local drive. The Autorun.exe window launches.

Open File security warning

2. Select the Dell EMC OpenManage Essentials check box and click Install. The Dell EMC

OpenManage Essentials Prerequisites screen displays.


Application installation selection screen

3. Click Install All Critical Prerequisites then click Yes to proceed.

Note: The installation may take approximately 35 minutes to complete.

4. Click Install Essentials.

Installation confirmation screen

5. From the Welcome to the Install Wizard for Dell EMC OpenManage Essentials screen, click Next.

6. Review the information within the License Agreement and if you agree to the terms, click Accept then

click Next.

7. For the Installation type, select Typical installation and click Next.


Installation type election screen

8. Click Install to proceed.

9. Click to place a check in the Launch Dell EMC OpenManage Essentials checkbox, then click Finish

to complete installation.

Installation Completed screen

OpenManage Essential GUI page displays using the default browser.

Documents

Dell EMC Ready Solution for VMware NFV Platform · 5 Dell EMC Ready Solution for VMware NFV Platform Introduction The Dell EMC with VMware vCloud NFV platform automates the deployment