Users Guide

NOTE: Make sure that the virtual appliance can resolve the DNS server you entered.
Performance during Connection Profile Test Credentials is
extremely slow or unresponsive.
The iDRAC on a server has only one user (for example, only root) and the user is in a disabled state, or all users are in a disabled
state. Communicating to a server in a disabled state causes delays. To fix this issue, you can either fix the disable state of the
server, or reset iDRAC on the server to re-enable the root user to default setting.
To fix a server in a disabled state:
1. Open the Chassis Management Controller console and select the disabled server.
2. To automatically open the iDRAC console, click Launch iDRAC GUI.
3. Navigate to the user list in iDRAC console, and choose one of the following:
● iDRAC 6 : Select iDRAC settings > Network/Security tab > Users tab.
● iDRAC 7 : Select iDRAC settings > Users tab.
● iDRAC 8 : Select iDRAC settings > Users tab.
4. To edit the settings, in the User ID column, click the link for the admin (root) user.
5. Click Configure User, and then click Next.
6. In the User Configuration page for the selected user, select the check box next to Enable user, and then and click Apply.
Does the OpenManage Integration for VMware vCenter support the
VMware vCenter Server appliance?
Yes, the OpenManage Integration for VMware vCenter supports the VMware vCenter Server appliance since v2.1.
Does the OpenManage Integration for VMware vCenter support the
vSphere Web Client?
Yes, the OpenManage Integration for VMware vCenter supports the VMware vSphere Web client.
Why is my firmware level still not updated when I have performed
firmware update with Apply on Next reboot option and the system
was rebooted?
To update firmware, run the inventory on the host after the reboot is completed. In some cases, where the reboot event does
not reach the appliance, the inventory is not automatically triggered. In such situation, you must rerun the inventory manually to
get the updated firmware versions.
Why is the host still shown under the chassis even after removing
the host from the vCenter tree?
The hosts under the chassis are identified as part of the chassis inventory. After a successful chassis inventory, the host list
under the chassis is updated. Therefore, even if the host is removed from the vCenter tree, the host still shows under the
chassis till the next chassis inventory is run.
Troubleshooting
123