Configure OpenManage Enterprise by using Text User Interface
The Text User Interface (TUI) tool provides you a text interface to change the admin password, view appliance status and network configuration, configure networking parameters, and enable field service debug request.
NOTE: To navigate on the TUI interface, use the arrow keys or press Tab to go to the next option on the TUI, and press Shift + Tab to go back to the previous options. Press Enter to select an option. The Space bar toggles the status of a check box.
Before logging in to the TUI, accept EULA when prompted.
On the Change admin password screen, enter the new password and confirm the password.
NOTE: For the first time, you must change the password by using the TUI screen.
Use the arrow keys or press Tab to select Apply.
When prompted for confirmation, select Yes, and then press Enter.
Now you can configure OpenManage Enterprise by using the TUI. On the TUI screen, you can view the following options:
Change the Admin Password
Display Current Appliance Status
Display Current Network Configuration
Set Networking Parameters
Enable Field Service Debug (FSD) Mode
Reboot the Appliance
NOTE: Possibly after running a command to restart the services, it may be observed that the TUI displays the following message: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 36s!
[java:14439]. This 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.
Setup Debug Logging
Enable Debug Logs
Disable Debug Logs
Enable SCP Retention
Disable SCP Retention
Restart Services
To confirm the current appliance administrator password, select Change the Admin Password, and then enter the password. Press Tab and select Continue.
On the TUI screen:
To view appliance status and the IPv4 and IPv6 statuses and addresses, select Current Appliance Status.
To configure network interface, select Set Networking Parameters.
On the Configure Network Interface screen, to enable IPv4, or IPv6, or both, press Enter. Select Apply.
NOTE:
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.
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.
To perform any write operations on TUI, ensure that you type the admin password, and then configure IPv4 or IPv6.
To configure IPv6, ensure that it is already configured by a vCenter server.
In an IPv6 environment, when a Router Advertisement is configured
for stateless configuration of multiple IPv6 IPs on a port,
iDRAC supports a maximum of 16 IPs addresses. In such a case, OpenManage Enterprise displays only the last discovered IP and uses that IP as the out-of-band
interface to iDRAC.
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.
To collect the debug logs of the application, monitoring tasks, events, and task execution history, select Setup Debug Logging . In addition, to collect the template .XML files, select the Enable SCP retention option under Setup Debug Logging . You can download the debug logs by clicking Monitor > Audit Logs > Export > Export Console Logs in OpenManage Enterprise.
To restart OpenManage Enterprise, select Reboot the Appliance.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\