Deployment. Dell EMC OpenManage Enterprise

Add to My manuals
215 Pages

advertisement

Deployment. Dell EMC OpenManage Enterprise | Manualzz

2

Deployment

OpenManage Enterprise is provided as an appliance deployed on a hypervisor, whose resources are managed to minimize downtime. The virtual appliance can be configured from the application web client after initial network provisioning in the Text

User Interface (TUI).

To view and update the current OpenManage Enterprise version, see

Updating the console and plugins

.

Topics:

System requirements

Deployment prerequisites

Deploy OpenManage Enterprise on VMware vSphere

Deploy OpenManage Enterprise on Hyper-V 2012 R2 or earlier

Deploy OpenManage Enterprise on Hyper-V 2016 host

Deploy OpenManage Enterprise on Hyper-V 2019 or Windows 2022 host

Deploy OpenManage Enterprise by using Kernel-based Virtual Machine

Deploy OpenManage Enterprise programmatically

Configure the system using the TUI

System requirements

The minimum system requirements for the deployment of OpenManage Enterprise. Ensure that you have fulfilled the following software requirements.

NOTE: For the latest list of system requirements, see the most current version of the OpenManage Enterprise Support

Matrix on the support site.

Table 4. Minimum system requirements

System components Minimum requirements

Hypervisors

Networks

● VMware vSphere supported on ESXi 5.5 or later

● Microsoft Hyper-V supported on Windows Server 2012 R2 or later

● KVM supported on Red Hat Enterprise Linux 6.5 or later

Available virtual NIC with access to the management networks of all devices managed from

OpenManage Enterprise.

Browsers ● Internet Explorer (64-bit) 11 or later

● Mozilla Firefox 52 or later

● Google Chrome 58 or later

● Microsoft Edge version 41.16299 or later

User interfaces HTML 5, JS-based

Deployment prerequisites

The requirements for a successful OpenManage Enterprise deployment. Ensure you fulfill the prerequisites before deploying on a hypevisor.

Before you deploy OpenManage Enterprise, ensure:

● You have local system administrator rights.

● Your system meets the

System requirements .

● Your appliances must meet the

Appliance hardware requirements

.

24 Deployment

● Your platforms, operating systems, and browsers must meet the minimum requirements defined in the most current version of the OpenManage Enterprise Support Matrix on the support site.

Appliance hardware requirements

The minimum and maximum hardware requirements for an OpenManage Enterprise appliance during a large deployment versus a small deployment.

Table 5. Appliance hardware requirements

Hardware configuration

Maximum number of devices managed by an appliance

Minimum RAM

Minimum processor cores

Minimum hard drive space

Large deployments Small deployments

Up to 8,000 1,000

32 GB

8

400 GB

16 GB

4

400 GB

NOTE: : Ensure that your hypervisor storage has enough free space to support the recommended virtual disk size of the appliance, and enough overhead to support snapshots and future expansion of the virtual disk.

Management ports and protocols

Details the supported ports on managed nodes and protocols on management stations.

Table 6. Ports and protocols on management stations

Port Protoc ol

Type Encryptio n

Source Directio n

Destinatio n

22

25

SSH

SMTP

TCP

TCP

256-bit

None

Managemen t station

In

Usage

OpenManag e Enterprise appliance

Required for incoming only if FSD is used.

OpenManage Enterprise administrator must enable only if interacting with the Dell support staff.

Managemen t station

To receive email alerts from OpenManage

Enterprise.

53

68 /

546

(IPv6)

80*

123

DNS

DHCP

HTTP

NTP

UDP/

TCP

UDP/

TCP

TCP

TCP

None

None

None

None

OpenManag e Enterprise appliance

Out

OpenManag e Enterprise appliance

Out

OpenManag e Enterprise appliance

Out

Managemen t station

In

Managemen t station

For DNS queries.

Managemen t station

Network configuration.

OpenManag e Enterprise appliance

The Web GUI landing screen. This will redirect a user to HTTPS (Port 443).

NTP Server Time synchronization (if enabled).

137, 138,

139, 445

CIFS

a

UDP/

TCP

None

OpenManag e Enterprise appliance iDRAC/

CMC

Out

In OpenManag e Enterprise appliance

● To upload or download deployment templates.

● To upload TSR and diagnostic logs.

● To download firmware/driver DUPs.

● For Emergency FSD process, if web UI is not available.

● Boot to network ISO.

Deployment 25

Table 6. Ports and protocols on management stations (continued)

Port Protoc ol

Type Encryptio n

Source Directio n

Destinatio n

111,

2049

(default

)

162

b

NFS UDP/

TCP

SNMP UDP

443

(default

)

HTTPS TCP

514

3269

636

Syslog UDP

LDAPS TCP

LDAPS TCP

None

None

128-bit

SSL

None

None

None

Usage

For more information, refer Built-in

Appliance Share in

Manage console settings

.

OpenManag e Enterprise appliance

Out CIFS share To import firmware/driver catalogs from

CIFS share.

OpenManag e Enterprise appliance

Out External

NFS share

Managemen t station

In/Out OpenManag e Enterprise appliance

Managemen t station

In/Out OpenManag e Enterprise appliance

● To download catalog and DUPs from the NFS share for firmware updates.

● For manual console upgrade from network share.

Event reception through SNMP. The direction is 'outgoing' only if using the Trap forward policy.

● Web GUI.

● To upload or download Deployment templates.

● To upload TSR and diagnostic logs.

● To download firmware/driver DUPs.

● FSD process.

● Boot to Network ISO.

● To download updates and warranty information from Dell.com. 256bit encryption is allowed when communicating with the OpenManage

Enterprise by using HTTPS for the web

GUI.

● Server-initiated discovery.

For more information, refer Built-in

Appliance Share in

Manage console settings

.

OpenManag e Enterprise appliance

OpenManag e Enterprise appliance

OpenManag e Enterprise appliance

Out

Out

Out

Syslog server

Managemen t station

Managemen t station

To send alert and audit log information to

Syslog server.

AD/ LDAP login for Global Catalog.

AD/ LDAP login for Domain Controller.

a.

b.

CIFS protocol is not needed if the built-in appliance share is configured for HTTPS.

Port can be configured up to 499 excluding the port numbers that are already allocated.

26 Deployment

Device ports and protocols

Details the supported ports and protocols on managed devices.

Table 7. Supported ports and protocols on managed devices

Port Protocol Type Encryption Source Direction

22

161

162

a

SSH

SNMP

SNMP

TCP

UDP

UDP

256-bit

None

None

OpenManage

Enterprise appliance

OpenManage

Enterprise appliance

OpenManage

Enterprise appliance

OpenManage

Enterprise appliance

Out

Out

In/ Out

Destinatio n

Managed device

Managed device

Managed device

Usage

For the Linux OS, Windows, and

Hyper-V discovery.

For SNMP queries.

Send and receive SNMP traps.

443 Proprietar y/ WS-

Man/

Redfish

IPMI/

RMCP

TCP

UDP

256-bit Out Managed device

Discovery and inventory of iDRAC7 and later versions.

For the CMC management.

623 None OpenManage

Enterprise appliance

CMC

Out Managed device

IPMI access through LAN.

69 TFTP UDP None In Managemen t station

For updating CMC firmware.

a.

Port can be configured up to 499 excluding the port numbers that are already allocated.

Firewall exceptions

Certain OpenManage Enterprise features leverage external resource URLs. If you have a firewall, add these URLs to your firewall exceptions list.

Table 8. External resources

Feature External resource URL

Upgrade appliance, install or upgrade plugins https://downloads.dell.com/openmanage_enterprise https://dl.dell.com/openmanage_enterprise

Access device warranty

Update catalogs

Push alert notifications to OpenManage

Mobile https://apigtwb2c.us.dell.com/PROD/sbil/eapi/v5/asset-entitlements?

https://downloads.dell.com/catalog https://dl.dell.com/catalog https://openmanagecloud.dell.com

Deploy OpenManage Enterprise on VMware vSphere

Deploy OpenManage Enterprise on Hyper-V 2016 R2 version by downloading the Virtual Hard Disk (VHD) file available on the support site.

Prerequisites

To perform any tasks on OpenManage Enterprise, you must have necessary user privileges, as described in Role and scope-based access

.

Deployment 27

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

Steps

1.

NOTE: If you are using VMware vSphere v6.0 or the earlier versions, you must install the Client Integration plug-in before you deploy an OVF template. Then, in vSphere Client select File > Deploy OVF Template .

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. Right-click any inventory object that is a valid parent object of a virtual machine, such as a data center, folder, cluster, resource pool, or host, and select Deploy OVF Template .

3. On the Select an OVF template screen, specify the location of the source OVF template and click Next .

The Deploy OVF Template wizard is displayed.

4. Click on File > Deploy a Virtual Machine from OVF/OVA File.

.

5. On the Source screen, click on Browse and select the OVF package then select Next .

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

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

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

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

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

● If there is more than one datastore available on the host, the Datastore page all of them. Select the location to store virtual machine (VM) files, and then click Next .

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

10. On the Ready to Complete screen , 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 or earlier

Deploy OpenManage Enterprise on Hyper-V 2012 R2 or earlier hosts.

Prerequisites

Ensure you have the necessary user privileges as described in Role and scope-based access .

● If a secondary adapter is added before powering on an 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 will need to be configured.

Steps

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

5. On the Specify Name and Location screen

● provide the Virtual machine name.

28 Deployment

● (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 screen, select Generation 1 and click Next .

NOTE: OpenManage Enterprise does not support Generation 2.

8. On the Assign Memory screen, 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 screen, 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 ', OpenManage Enterprise will not function properly during the first reboot, and requires re-deployment if this situation recurs.

10. On the Connect Virtual Hard Disk screen, 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.

Results

OpenManage Enterprise is deployed.

Next steps

After deploying or upgrading an appliance on Hyper-V:

1. Power off the appliance.

2. Remove the standard network adapter.

3. Add a legacy network adapter.

4. Power on the appliance.

Deploy OpenManage Enterprise on Hyper-V 2016 host

Deploy OpenManage Enterprise on Hyper-V 2016 R2 version by downloading the VHD file available on the support site.

Prerequisites

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

Role and scope-based access

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

● After installing or upgrading the appliance on Hyper-V, power off the appliance, remove the standard network adapter and add a legacy network adapter, and then power on the appliance.

Steps

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

Deployment 29

5. On the Specify Name and Location screen

● 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 screen, select Generation 1 and click Next .

NOTE: OpenManage Enterprise does not support Generation 2.

8. On the Assign Memory screen, 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 screen, 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 ', OpenManage Enterprise will not function properly during the first reboot, and requires redeployment if this situation recurs.

10. On the Connect Virtual Hard Disk screen, 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 or

Windows 2022 host

Deploy OpenManage Enterprise on Hyper-V 2019 or Windows 2022 devices by downloading the Virtual Hard Disk (VHD) file available on the support site.

Prerequisites

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

Role and scope-based access

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

● After installing or upgrading the appliance on Hyper-V, power off the appliance, remove the standard network adapter and add a legacy network adapter, and then power on the appliance.

Steps

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

5. On the Specify Name and Locations creen

● 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

30 Deployment

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

NOTE: OpenManage Enterprise does not support Generation 2.

8. On the Assign Memory screen, 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 screen, 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 ', OpenManage Enterprise will not function properly during the first reboot, and requires redeployment if this situation recurs.

10. On the Connect Virtual Hard Disk screen, 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 Kernel-based

Virtual Machine

Deploy OpenManage Enterprise using the kernel-based Virtual Machine (KVM) by downloading the KVM file available on the support site.

Prerequisites

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

Role and scope-based access

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

Steps

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 screen, 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 .

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

Log into an appliance

.

Deployment 31

Deploy OpenManage Enterprise programmatically

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

Open Virtualization Format (OVF) files from the support site.

Prerequisites

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

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

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

Steps

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

Type a new administrator password for the OpenManage Enterprise.

adminPassword Must contain at least one character in: uppercase, lowercase, digit, and special character. For example, Dell123$ true or false bEnableDHCP bEnableIpv6AutoConfig staticIP true or false static IP in CIDR format

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.

Can be IPv4 or IPv6. (You cannot set both the IPv4 and IPv6 types at a time.) gateway IPv4 or IPv6 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.

32 Deployment

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.

Configure the system using the TUI

Use the Text User Interface (TUI) to change the Administrator password, view appliance status and network configuration, configure networking parameters, enable field service debug request, select the primary network, and to configure the appliance for automatic discovery of the servers in your network.

When you boot the system for the first time from the TUI, you are prompted to accept the End User License Agreement

(EULA). Next, change the administrator password and configure network parameters for the appliance and load the web console in a supported browser to get started. Only users with OpenManage Administrator privileges can configure

OpenManage Enterprise.

Navigate the TUI using:

● The arrow keys or Tab to highlight menu options.

● Shift + Tab to go back to previous menus.

● Enter to select an option.

● Space bar to toggle a checkbox's status.

NOTE:

● To configure IPv6, ensure that it is already configured by a vCenter Server.

● By default, the last discovered IP of a device is used by OpenManage Enterprise for performing all operations. To make any IP change effective, you must rediscover the device.

You can configure OpenManage Enterprise by using the TUI. The TUI screen has the following options:

Table 10. Text User Interface options

Options Descriptions

Change the Admin Password Select Change the Admin Password screen to enter a new password and confirm the password.

For the first time, you must change the password by using the TUI screen.

Display Current Appliance Status Select Display Current Appliance Status to view the URL and the status of the appliance. You can also view statuses of the Task Execution, Event Processing,

Tomcat, Database, and Monitoring services.

NOTE: The Backup and Restore status is listed with its current status.

Display Current Network

Configuration

Set Appliance Hostname

Set Networking Parameters

Select Display Current Network Configuration to view the IP configuration details.

Choose Network Adapter menu lists all the available network adapters. Clicking on a network adapter will display its current settings.

Select Set Appliance Hostname to configure the appliance hostname on the DNS.

This field supports the following valid characters for host names: alphanumeric (a-z,

A-Z, 0-9), periods ( . ), and dashes ( - ).

NOTE: Using periods will designate domain name information. If the appliance

DNS information is configured statically rather than getting domain details from

DHCP, you must configure the hostname using the fully qualified domain name

(FQDN) so that the domain search information can be populated.

Select Set Networking Parameters to reconfigure the network adapters.

Choose Network Adapter menu lists all the available networks adapters. Select a network adapter, reconfigure its network parameters, and select Apply to save the changes to the appropriate interface.

Deployment 33

Table 10. Text User Interface options (continued)

Options Descriptions

By default, only IPv4 is enabled on primary network interface with a private static IP in the appliance. However, if a new network interface is added, both IPv4 and IPv6 are enabled for multihoming.

If the OpenManage Enterprise appliance fails to acquire a IPv6 address, check if the environment is configured for router advertisements to have the managed bit (M) turned on. Network Manager from current Linux distributions causes a link failure when this bit is on, but DHCPv6 is not available. Ensure that DHCPv6 is enabled on the network or disable the managed flag for router advertisements.

NOTE:

● DNS configuration is only available on the primary network interface. If DNS resolution is wanted on this interface, all host names must be resolvable by the DNS server configured on the primary interface.

● For more information about multihoming, see the Multihoming on

OpenManage Enterprise technical whitepaper on the OpenManage Enterprise support site.

Select Primary Network Interface

Configure Static Routes

Select Primary Network Interface allows you to designate a primary network.

Primary interface selection gives priority to the selected interface in terms of routing and is used as the default route. This interface will have the routing priority if there is any ambiguity. The primary interface is also expected to be the 'public facing' interface which allows for corporate network/internet connectivity. Different firewall rules are applied to the primary interface, which allow for tighter access control such as access restriction by IP range.

NOTE: If multihoming is enabled, the appliance can be accessed from two networks. In this case, the primary interface is used by the appliance for all external communication and when proxy settings are used. For more information about multihoming, see the Multihoming on OpenManage Enterprise technical whitepaper on the OpenManage Enterprise support site.

Select Configure Static Routes if the networks require a static route to be configured to reach a specific subnet over the IPv4 and IPv6 networks.

NOTE: A maximum of 20 static routes per interface is supported.

Configure Server Initiated

Discovery

Configure Appliance Disk Size

Select Configure Server Initiated Discovery to allow the appliance to automatically register the required records with the configured DNS server.

NOTE:

● Ensure that the appliance is registered with DNS, and can dynamically update records.

● The target systems must be configured to request registration details from

DNS.

● To change the DNS Domain Name, ensure Dynamic DNS registration is enabled on the DNS server. Also, for appliance to be registered on the DNS server, select the Nonsecure and secure option under Dynamic updates.

Select Configure Appliance Disk Size to scan for the availability of disk space or new disk(s) and then allocate the additional disk space or disk(s) for the appliance if required.

NOTE:

● It is highly recommended to take a VM snapshot of the console as a backup before applying any disk configuration changes.

● Post addition of the disk space, deletion or reduction of the expanded disk space is not supported. To remove a newly added disk or to reverse the increase in size of an existing disk you must revert to prior VM snapshot.

34 Deployment

Table 10. Text User Interface options (continued)

Options Descriptions

● If the initial scan detects no unallocated space, then allocate additional disk space or disks to the console on your hypervisor and rescan.

● Scanning and allocation of disk space is limited to a maximum of four disks.

Enable Field Service Debug (FSD)

Mode

Restart Services

Setup Debug Logging

Enable CIFS share for FSD

(emergency use only)

Select Enable Field Service Debug (FSD) Mode (default) for console debugging

using HTTPS. For more information, see Field service debugging

.

NOTE: To avoid excessive consumption of the internal share space, a warning banner is displayed till the FSD mode is active.

Select Restart Services with the following options to restart the services and networking:

● Restart All Services

● Restart Networking

Select Setup Debug Logging using the following options :

● Enable All Debug Logs

○ To collect the Debug logs of the all the application monitoring tasks, events, the task execution history, and installed plugins.

NOTE: As long as the debug log collection is active, a warning banner is on display.

● Disable All Debug Logs

○ To disable all the Debug logs.

NOTE: The warning banner indicating the debug log collection is removed.

● Configure Debug Logging

○ To selectively enable debug logging for appliance and plugin services.

○ Use the Options menu to select all services, clear all selections or restore state prior to making any modifications.

● Enable SCP Retention —to collect the template .XML files.

NOTE: SCP file retention is not applicable for MX7000 chassis templates.

● Disable SCP Retention —to disable the SCP retention.

You can create a console log archive from the Monitor > Troubleshoot screen by clicking Log > Generate Log . To download the archived console log, click Download

Log .

Select Enable CIFS share for FSD (emergency use only) for console debugging

using CIFS share. For more information, see Field service debugging .

NOTE: A warning banner is displayed till the FSD mode is active.

Change keyboard layout

Reboot the Appliance

Select Change keyboard layout to change the keyboard layout if needed.

Select Reboot the Appliance to restart the appliance.

NOTE: After running a command to restart the services, the TUI may display the following message: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 36s! [java:14439].

The soft lockup issue likely occurs as a result of the hypervisor being overloaded.

In such situations, it is recommended to have at least 16 GB of RAM and

CPU of 8000 MHz reserved to the OpenManage Enterprise appliance. It is also recommended that the OpenManage Enterprise appliance be restarted when this message is displayed.

Deployment 35

advertisement

Related manuals

Download PDF

advertisement

Table of contents