Users Guide

Table Of Contents
Does OMIVV support VMware vCenter server appliance?
Yes, OMIVV supports the VMware vCenter Server appliance since v2.1.
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.
Hypervisor deployment fails when NIC Partitioning (NPAR) is
enabled on a target node and disabled in System Profile
Hypervisor deployment fails when a System Profile with a disabled 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
Troubleshooting
133