Users Guide

iDRAC license status is displayed as compliant on the management
compliance page when the iDRAC IP is not reachable
After performing periodic inventory, if iDRAC not reachable, iDRAC License status is displayed as compliant on the management
compliance page.
Resolution: Ensure that the iDRAC is reachable and run the inventory again to get the right iDRAC license details.
ESXi host is either disconnected or not responding state after
successful OS deployment using OMIVV.
ESXi host fails to send heartbeat packets to vCenter because its DNS is not properly configured to lookup FQDN of the
vCenter.
Resolution: Perform the following tasks:
1. Remove the ESXi host from the vCenter inventory.
2. Add the host in vCenter using the Add host wizard.
3. Create a host credential profile and run the inventory.
Deployment job times out when network interface card (NIC) of
OMIVV is not connected to the ESXi host network
OS deployment has dependency on the selection of NIC. If the correct NIC is not selected, then OSD job times out.
Resolution: Select appropriate 'Appliance NIC connected to Host ' from Configure Host Settings page of Deployment wizard .
This is needed by OMIVV to reach ESXi network during OS installation process.
Warranty job is not running for certain hosts
In a PSC environment with multiple vCenters, if you add a host using FQDN to one vCenter and IP to another vCenter, warranty
job runs only for one host instance.
Resolution: Remove the disconnected host instance from the host credential profile and run the inventory and warranty job.
Version Affected: 5.0
Management compliance page shows that incorrect credential
profile name for hosts managed using chassis credential profile
For hosts managed using chassis credential profile, the management compliance shows incorrect credential profile name instead
of actual chassis credential profile name.
Resolution: There is no impact on any OMIVV functionality.
Version Affected: 5.0
Proactive HA initialization is not happening after performing
backup and restore
When you restore OMIVV from the previous version that is registered with the vSphere Client, for Proactive HA enabled
clusters the Dell Provider is disconnected.
Resolution: Disable and enable the Proactive HA for clusters.
Version Affected: 5.0
Frequently Asked Questions-FAQ
149