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.
|
Display Current Network Configuration
|
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.
|
Set Appliance Hostname
|
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.
|
Set Networking Parameters
|
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.
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 Dell OpenManage Enterprise support site.
|
Select Primary Network Interface
|
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 Dell OpenManage Enterprise support site.
|
Configure Static Routes
|
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
|
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.
|
Configure Appliance Disk Size
|
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.
- 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
|
Select
Enable Field Service Debug (FSD) Mode (default) for console debugging using HTTPS. For more information, see
Field service debug workflow.
NOTE To avoid excessive consumption of the internal share space, a warning banner is displayed till the FSD mode is active.
|
Restart Services
|
Select
Restart Services with the following options to restart the services and networking:
- Restart All Services
- Restart Networking
|
Setup Debug Logging
|
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
page by clicking
. To download the archived console log, click
Download Log.
|
Enable CIFS share for FSD (emergency use only)
|
Select
Enable CIFS share for FSD (emergency use only) for console debugging using CIFS share. For more information, see
Field service debug workflow.
NOTE A warning banner is displayed till the FSD mode is active.
|
Change keyboard layout
|
Select
Change keyboard layout
to change the keyboard layout if needed.
|
Reboot the Appliance
|
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.
|