Deploy and manage OpenManage Enterprise. Dell EMC OpenManage Enterprise

3

Deploy and manage OpenManage Enterprise

Dell EMC OpenManage Enterprise is provided as an appliance that you can deploy on a hypervisor and manage resources to minimize downtime. The virtual appliance can be configured from the application web console after initial network provisioning in the Text User

Interface (TUI). For steps to view and update the console version, see

Check and update the version of the OpenManage Enterprise and the available extensions . This chapter describes the installation prerequisites and minimum requirements.

NOTE: For information about supported browsers, see the OpenManage Enterprise Support Matrix available on the support site.

Related reference

OpenManage Enterprise user role types

OpenManage Enterprise Graphical User Interface overview

Security features in OpenManage Enterprise

Related information

Role-based OpenManage Enterprise user privileges

Topics:

•

Installation prerequisites and minimum requirements

•

Deploy OpenManage Enterprise on VMware vSphere

•

Deploy OpenManage Enterprise on Hyper-V 2012 R2 and earlier host

•

Deploy OpenManage Enterprise on Hyper-V 2016 host

•

Deploy OpenManage Enterprise on Hyper-V 2019 host

•

Deploy OpenManage Enterprise by using Kernel-based Virtual Machine

•

Deploy OpenManage Enterprise programmatically

Installation prerequisites and minimum requirements

For a list of supported platforms, operating systems, and browsers, see the Dell EMC OpenManage Enterprise Support Matrix on the support site and Dell TechCenter.

To install OpenManage Enterprise, you require local system administrator rights and the system you are using must meet the criteria mentioned in the

Minimum recommended hardware

and

Minimum system requirements for installing OpenManange Enterprise

.

Minimum recommended hardware

Table 4. Minimum recommended hardware

Minimum recommended hardware

Number of devices that can be managed by the appliance

RAM

Processors

Hard drive

Large deployments

Up to 8000

16 GB

8 cores total

250 GB

Small deployments

1000

16 GB

4 cores total

50 GB

16 Deploy and manage OpenManage Enterprise

Minimum system requirements for deploying

OpenManange Enterprise

Table 5. Minimum requirements

Particulars

Supported hypervisors

Minimum requirements

• VMware vSphere versions:

• vSphere ESXi 5.5 onwards

• Microsoft Hyper-V supported on:

• Windows Server 2012 R2 onwards

• KVM supported on:

• Red Hat Enterprise Linux 6.5 onwards

Network

Supported browsers

Available virtual NIC which has access to the management networks of all the devices which is managed from OpenManage

Enterprise.

• Internet Explorer (64-bit) 11 and later

• Mozilla Firefox 52 and later

• Google Chrome 58 and later

User interface HTML 5, JS based

NOTE: For the latest update about the minimum requirements for OpenManage Enterprise, see the Dell EMC

OpenManage Enterprise Support Matrix on the support site.

Deploy OpenManage Enterprise on VMware vSphere

NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See

Role-based

OpenManage Enterprise user privileges

.

NOTE: If a secondary adapter is added before powering on the appliance for the first time, the adapter will be configured with IPv4 and IPv6 disabled. Upon login to the TUI, and after accepting the EULA and changing the admin password, the adapter will show up as DISABLED and must be configured by the user.

1. Download the openmanage_enterprise_ovf_format.zip

file from the support site and extract the file to a location accessible by VMware vSphere Client. It is recommended to use a local drive or CD/DVD, because installing from a network location can take up to 30 minutes.

2. In vSphere Client, select File > Deploy OVF Template .

The Deploy OVF Template wizard is displayed.

3. On the Source page, click Browse , and then select the OVF package. Click Next .

4. On the OVF Template Details page, review the information that is displayed. Click Next .

5. On the End User License Agreement page, read the license agreement and click Accept . To continue, click Next .

6. On the Name and Location page, enter a name with up to 80 characters, and then select an inventory location where the template will be stored. Click Next .

7. Depending on the vCenter configuration, one of the following options is displayed:

• If resource pools are configured — On the Resource Pool page, select the pool of virtual servers to deploy the appliance VM.

• If resource pools are NOT configured — On the Hosts/Clusters page, select the host or cluster on which you want to deploy the appliance VM.

8. If there are more than one datastores available on the host, the Datastore page displays such datastores. Select the location to store virtual machine (VM) files, and then click Next .

9. On the Disk Format page, click Thick provision to pre-allocate physical storage space to VMs at the time a drive is created.

Deploy and manage OpenManage Enterprise 17

10. On the Ready to Complete page, review the options you selected on previous pages and click Finish to run the deployment job.

A completion status window displays where you can track job progress.

Deploy OpenManage Enterprise on Hyper-V 2012

R2 and earlier host

NOTE:

• To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based

OpenManage Enterprise user privileges

• If a secondary adapter is added before powering on the appliance for the first time, the adapter will be configured with IPv4 and IPv6 disabled. Upon login to the TUI, and after accepting the EULA and changing the admin password, the adapter will show up as DISABLED and must be configured by the user.

• Upon an install or an upgrade to OpenManage Enterprise version 3.3.1 on Hyper-V, power off the appliance, remove the standard network adapter and add a legacy network adapter, and then power on the appliance.

1. Download the openmanage_enterprise_vhd_format.zip

file from the support site. Extract the file and then move or copy the enclosed VHD file into an appropriate location on your system where you want to store the OpenManage Enterprise virtual drive.

2. Start the Hyper-V Manager in the Windows Server 2012 R2 or an earlier version. The Windows Hyper-V should be displayed under the Hyper-V Manager. If not, right-click Hyper-V Manager , and then select Connect to Server .

3. Click Actions > New > Virtual Machine to start the New Virtual Machine Wizard .

4. Click Next on the initial Before You Begin page.

5. On the Specify Name and Location page

• provide the Virtual machine name.

• (Optional) Select the Store the virtual machine in a different location check box to activate the Location field, and then browse and navigate to capture a folder location where the VM would be stored.

NOTE: If the check box is not selected, the VM is stored in the default folder.

6. Click Next

7. On the Specify Generation page, select Generation 1 and click Next .

NOTE: OpenManage Enterprise does not support Generation 2.

8. On the Assign Memory page, enter the startup memory in the Startup memory field and click Next .

NOTE: Ensure that a minimum of 16,000 MB (16 GB) is assigned.

9. On the Configure Networking page, select the network adapter in the Connection drop-down list. Ensure that the virtual switch is connected to the network. Click Next .

NOTE: If set to 'Not Connected', OME will not function properly during the first reboot, and requires redeployment if this situation recurs.

10. On the Connect Virtual Hard Disk page, select Use an existing virtual disk drive , and then browse to the location where the VHD file is copied as mentioned in step 1 . Click Next .

11. Complete the on-screen instructions.

NOTE: Make sure to have a minimum storage size of 20 GB

12. Open the Settings of the newly created VM and power on the VM.

13. On the TUI screen, accept the EULA and when prompted, change the password of the appliance and set network parameters to the

IP of the appliance.

Deploy OpenManage Enterprise on Hyper-V 2016 host

NOTE:

• To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based

OpenManage Enterprise user privileges

18 Deploy and manage OpenManage Enterprise

• If a secondary adapter is added before powering on the appliance for the first time, the adapter will be configured with IPv4 and IPv6 disabled. Upon login to the TUI, and after accepting the EULA and changing the admin password, the adapter will show up as DISABLED and must be configured by the user.

• Upon an install or an upgrade to OpenManage Enterprise version 3.3.1 on Hyper-V, power off the appliance, remove the standard network adapter and add a legacy network adapter, and then power on the appliance.

1. Download the openmanage_enterprise_vhd_format.zip

file from the support site. Extract the file and then move or copy the enclosed VHD file into an appropriate location on your system where you want to store the OpenManage Enterprise virtual drive.

2. Start the Hyper-V Manager in the Windows server 2016. The Windows Hyper-V should be displayed under the Hyper-V Manager. If not, right-click Hyper-V Manager , and then select Connect to Server .

3. Click Actions > New > Virtual Machine to start the New Virtual Machine Wizard .

4. Click Next on the initial Before You Begin page.

5. On the Specify Name and Location page

• provide the Virtual machine name.

• (Optional) Select the Store the virtual machine in a different location check box to activate the Location field, and then browse and navigate to capture a folder location where the VM would be stored.

NOTE: If the check box is not selected, the VM is stored in the default folder.

6. Click Next

7. On the Specify Generation page, select Generation 1 and click Next .

NOTE: OpenManage Enterprise does not support Generation 2.

8. On the Assign Memory page, enter the startup memory in the Startup memory field and click Next .

NOTE: Ensure that a minimum of 16,000 MB (16 GB) is assigned.

9. On the Configure Networking page, select the network adapter in the Connection drop-down list. Ensure that the virtual switch is connected to the network. Click Next .

NOTE: If set to 'Not Connected', OME will not function properly during the first reboot, and requires redeployment if this situation recurs.

10. On the Connect Virtual Hard Disk page, select Use an existing virtual disk drive , and then browse to the location where the VHD file is copied as mentioned in step 1 . Click Next .

11. Complete the on-screen instructions.

NOTE: Make sure to have a minimum storage size of 20 GB

12. Open the Settings of the newly created VM and power on the VM.

13. On the TUI screen, accept the EULA and when prompted, change the password of the appliance and set network parameters to the

IP of the appliance.

Deploy OpenManage Enterprise on Hyper-V 2019 host

NOTE:

• To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based

OpenManage Enterprise user privileges

• If a secondary adapter is added before powering on the appliance for the first time, the adapter will be configured with IPv4 and IPv6 disabled. Upon login to the TUI, and after accepting the EULA and changing the admin password, the adapter will show up as DISABLED and must be configured by the user.

• Upon an install or an upgrade to OpenManage Enterprise version 3.3.1 on Hyper-V, power off the appliance, remove the standard network adapter and add a legacy network adapter, and then power on the appliance.

1. Download the openmanage_enterprise_vhd_format.zip

file from the support site. Extract the file and then move or copy the enclosed VHD file into an appropriate location on your system where you want to store the OpenManage Enterprise virtual drive.

2. Start the Hyper-V Manager in the Windows Server 2019. The Windows Hyper-V should be displayed under the Hyper-V Manager. If not, right-click Hyper-V Manager , and then select Connect to Server .

3. Click Actions > New > Virtual Machine to start the New Virtual Machine Wizard .

Deploy and manage OpenManage Enterprise 19

4. Click Next on the initial Before You Begin page.

5. On the Specify Name and Location page

• provide the Virtual machine name.

• (Optional) Select the Store the virtual machine in a different location check box to activate the Location field, and then browse and navigate to capture a folder location where the VM would be stored.

NOTE: If the check box is not selected, the VM is stored in the default folder.

6. Click Next

7. On the Specify Generation page, select Generation 1 and click Next .

NOTE: OpenManage Enterprise does not support Generation 2.

8. On the Assign Memory page, enter the startup memory in the Startup memory field and click Next .

NOTE: Ensure that a minimum of 16,000 MB (16 GB) is assigned.

9. On the Configure Networking page, select the network adapter in the Connection drop-down list. Ensure that the virtual switch is connected to the network. Click Next .

NOTE: If set to 'Not Connected', OME will not function properly during the first reboot, and requires redeployment if this situation recurs.

10. On the Connect Virtual Hard Disk page, select Use an existing virtual disk drive , and then browse to the location where the VHD file is copied as mentioned in step 1 . Click Next .

11. Complete the on-screen instructions.

NOTE: Make sure to have a minimum storage size of 20 GB

12. Open the Settings of the newly created VM and power on the VM.

13. On the TUI screen, accept the EULA and when prompted, change the password of the appliance and set network parameters to the

IP of the appliance.

Deploy OpenManage Enterprise by using Kernelbased Virtual Machine

NOTE:

• To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based

OpenManage Enterprise user privileges

• If a secondary adapter is added before powering on the appliance for the first time, the adapter will be configured with IPv4 and IPv6 disabled. Upon login to the TUI, and after accepting the EULA and changing the admin password, the adapter will show up as DISABLED and must be configured by the user.

1. Install the required virtualization packages while installing the operating system.

2. Download the openmanage_enterprise_kvm_format.zip

file from the support site. Extract the file to an appropriate location on your system where you want to store the OpenManage Enterprise virtual drive.

3. Start the virtual manager and select File > Properties .

4. On the Network Interfaces page, click Add .

5. Select Bridge as the interface type and click Forward .

6. Set the start mode to onboot and select the Activate now check box.

7. Select the interface to bridge from the list and ensure the properties match with the host device, and then click Finish .

A virtual interface is now created, and you can configure the firewall settings by using the terminal.

8. On the Virtual Machine Manager, click File > New .

9. Enter a name for the VM and select the Import existing disk image option, and then click Forward .

10. Navigate the file system and select the QCOW2 file that is downloaded in step 1, and then click Forward .

11. Assign 16 GB as the memory and select two processor cores, and then click Forward .

12. Assign the required disk space for the VM and click Forward .

13. Under Advanced options , ensure that the bridged host device network is selected and KVM is selected as the Virt Type.

14. Click Finish .

20 Deploy and manage OpenManage Enterprise

OpenManage Enterprise appliance is now deployed by using the KVM. To get started with OpenManage Enterprise, see Log in to

OpenManage Enterprise

.

Deploy OpenManage Enterprise programmatically

OpenManage Enterprise can be deployed programmatically (using a script) on VMWare ESXi version 6.5 or later.

NOTE: Programmatic/scripted deployment is only supported using the primary interface.

NOTE: If a secondary adapter is added before powering on the appliance for the first time, the adapter will be configured with IPv4 and IPv6 disabled. Upon login to the TUI, and after accepting the EULA and changing the admin password, the adapter will show up as DISABLED and must be configured by the user.

NOTE: You must use the latest versions of OVF Tool and Python 3.0 or later for the programmatic deployment.

To programmatically deploy OpenManage Enterprise, do the following:

1. Download and extract the openmanage_enterprise_ovf_format.zip

file or download the following OVF files individually from the support site:

• openmanage_enterprise.x86_64-0.0.1-disk1.vmdk

• openmanage_enterprise.x86_64-0.0.1.mf

• openmanage_enterprise.x86_64-0.0.1.ovf

• openmanage_enterprise.x86_64-0.0.1.vmx

• ovf_properties.config

• update_ovf_property.py

2. Open the ovf_properties.config

and set the following parameters:

Table 6. Parameters used in ovf_properties.config

Parameter bEULATxt

Accepted Values true or false

Description

By setting this value to true, you agree to the terms and conditions in the End-User

License Agreement (EULA). The EULA is available at the bottom of the ovf_properties.config file.

adminPassword bEnableDHCP bEnableIpv6AutoConfig

Must contain at least one character in: uppercase, lowercase, digit, and special character. For example,

Dell123$

Type a new administrator password for the

OpenManage Enterprise.

true or false true or false

Set to true if you want the appliance to enable IPv4 DHCP and to ignore the static

IPv4.

Set to true if you want the appliance to enable IPv6 auto configuration and to ignore the static IPv6.

staticIP gateway static IP in CIDR format

IPv4 or IPv6

Can be IPv4 or IPv6. (You cannot set both the IPv4 and IPv6 types at a time.)

You cannot set static Gateway as IPv4 and

IPv6 types at a time.

3. Run the update_ovf_property.py

script.

This script modifies the openmanage_enterprise.x86_64-0.0.1.ovf

file for deployment in accordance with the values set in the ovf_properties.config file. When the script finishes execution, a sample ovftool command is displayed. It contains tags such as

<DATASTORE>, <user>, <password>, <IP address> , and so on, that you must replace as per your deployment environment. These settings define the resources that are used on the target ESXi system and also the credentials and IP address of the target system.

NOTE: Remember to replace the entire tag including the < and > symbols.

4. Run the modified ovftool command from the previous step.

Deploy and manage OpenManage Enterprise 21

NOTE: The ovftool command must be run with the --X:injectOvfEnv and --powerOn flags because they are required for programmatic deployment.

After the ovftool command is run, the manifest validates and the deployment begins.

22 Deploy and manage OpenManage Enterprise