Users Guide

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.
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. Even if the host is removed from the vCenter tree, the host is displayed under the chassis until the
next chassis inventory is run.
After backup and restore of OMIVV, 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 OMIVV GUI, in the Settings tab, manually change the Events and Alarms settings.
OS deployment fails when NPAR is enabled on a target node and
disabled in System Profile
OS deployment fails when a System Profile with a disabled NIC Partitioning (NPAR) is applied on a target machine. Here, NPAR
is enabled on the target node and only one of the partitioned NIC, except partition 1 is selected as the NIC for the Management
Tasks during the deployment process through the deployment wizard.
Resolution: If you are changing the NPAR status using System Profile during deployment, ensure that you select only the first
partition for management network in the deployment wizard.
Version Affected: 4.1 and later
Available OMIVV appliance version displays wrong information
when the available version is lesser than the current version
In the OMIVV Admin console, under Appliance Management, Available Virtual Appliance Version displays the modes RPM
and OVF as available.
NOTE:
It is recommended that update repository path is set to the latest version and downgrading the virtual appliance
version is not supported.
The 267027 exception is thrown while adding a 12G and later bare-
metal server
During bare-metal discovery, if an incorrect credential is entered, the user account is automatically locked for few minutes.
During this period, iDRAC becomes unresponsive and takes a few minutes before restoring normalcy.
Resolution: Wait for few minutes and retype the user credentials.
144
Frequently Asked Questions-FAQ