Users Guide

Table Of Contents
Why is firmware level not updated when I have performed
firmware update with Apply on Next reboot option and
system was rebooted?
To update firmware, run the inventory on the host after the reboot is completed. Sometimes, 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 host still displayed under chassis even after
removing host from 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 is displayed under the chassis until the next
chassis inventory is run.
In Administration Console, why Update Repository Path is
not set to default path after I reset appliance to factory
settings?
After you reset the appliance, go to the Administration Console, and then click APPLIANCE MANAGEMENT in the left pane. In the
Appliance Settings page, the Update Repository Path is not changed to the default path.
Resolution: In Administration Console, manually copy the path in the Default Update Repository field to the Update Repository
Path field.
After backup and restore of OMIVV, why alarm settings
are not restored?
Restoring the OMIVV appliance backup does not restore all the Alarm settings. However, in the OpenManage Integration for VMware GUI,
the Alarms and Events field displays the restored settings.
Resolution: In the OpenManage Integration for VMware GUI, in the Manage > Settings tab, manually change theEvents and Alarms
settings.
Bare-metal deployment issues
This section deals with issues found during the deployment process.
Auto discovery and handshake prerequisites
Prior to running auto discovery and handshake, ensure that iDRAC and Lifecycle Controller firmware and BIOS versions meet the
minimum recommendations.
CSIOR must have run at least once on the system or iDRAC.
Hardware configuration failure
Before initiating a deployment task, ensure that the system has completed CSIOR and is not in the process of rebooting.
BIOS configuration should be run in clone mode so that the reference server is an identical system.
Some controllers do not allow creation of a RAID 0 array with one drive. This feature is supported only on high-end controllers, and the
application of such a hardware profile can cause failures.
128
Troubleshooting