Users Guide

In Administration Console, 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, 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.
Hypervisor deployment fails when NPAR is enabled on a
target node and disabled in System Profile
Hypervisor 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 through System Profile during deployment, ensure that you select only the first partition
for management network in the deployment wizard.
Version Affected: 4.1
Available virtual 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 bare-
metal server with an Express license
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.
Frequently Asked Questions-FAQ
151