Install Guide

Version affected: 1.6 and later
Resolution/Workaround: Reset the iDRAC to fix the issue of iDRAC not being responsive, and then rerun the inventory. If the
inventory can get the iDRAC IP, then the host is associated with the correct host credential profile.
• Issue 14: Unable to boot to service partition while deploying OS ISO.
Description: OS deployment is failing on 12th generation PowerEdge servers with the following error on the screen during POST:
"Warning: Unable to boot to Service Partition." There is a BIOS issue to identify the network ISO when there is a local USB CD-ROM
installed on the system and that USB CD- ROM is the only USB mass storage device plugged into the system.
Version affected: 1.5.1 and later
Resolution/Workaround: Remove the local USB CD-ROM (not all local CD-ROM would expose this issue), or plug in extra USB floppy
or USB drive on the system, or attach the virtual media (virtual floppy and virtual CD) from the iDRAC.
• Issue 15: A firmware update fails with an error message saying that USC is in use and it must be retried after 30 seconds.
Description: During a firmware update, the update fails with the error message: If USC is in use, wait until USC has exited and retry the
action. Otherwise retry after 30 seconds to check if network connectivity caused this error.
Version affected:1.5.1 and later
Resolution/Workaround: To fix this issue, reset iDRAC and wait until iDRAC boots properly and try the firmware update again.
• Issue 16: Events from different vCenter are posted to another vCenter from a shared OpenManage Integration appliance.
Description: This situation can occur when a bare-metal server that was deployed in one vCenter is rediscovered again as bare-metal
server but then selected for an OS deployed in another vCenter. This situation occurs if the host that was already on one of the
registered vCenter was added to another registered vCenter. In this case, the host on first vCenter opens as disconnected.
Version affected: All
Resolution/Workaround: Remove the host from the first vCenter where it is now showing as disconnected.
• Issue 17: OS installation fails.
Description: OS installation fails with the error message: Mount network share failed – incorrect IP address or share name.
Version affected: 1.5 and later
Resolution/Workaround: Restart the appliance.
• Issue 18: Health Status is showing Warning for chassis when one or more power supplies is critical.
Description: The overall health information is displayed warning on summary page for VRTX chassis that has power supply in critical
state.
Version affected: All
Resolution/Workaround: Each power supply status is shown correctly as critical.
• Issue 19: Health Status is showing as Healthy for chassis while Storage status is Warning.
Description: The overall health information is displayed Healthy on summary page for VRTX chassis that has a storage component as
Warning.
Version affected: VRTX firmware version 2.0
Resolution/Workaround: Each power supply unit health status correctly shown as critical at OMIVV.
• Issue 20: Blower information is showing as N/A for a chassis when a Blower is removed.
Description: Blower inventory information is displayed as N/A on the Hardware page for VRTX chassis when a Blower is removed from
a slot.
Version affected: 2.0 and later
Resolution/Workaround: You can see the correct status in the CMC console.
• Issue 21: I see a web communication error in the vSphere Client after changing the DNS settings in OpenManage Integration for
VMware vCenter.
Description: If you see any kind of web communication error in the vSphere Client while doing any OMIVV-related tasks after changing
the DNS settings, clear the browser cache or log out and log in from the vSphere Client.
Version affected: 2.x and later
Resolution/Workaround: Clear the browser cache or log out and log in from the vSphere Client.
• Issue 22: OMIVV RPM Upgrade fails when Proxy is configured with Domain user authentication.
Description: If OMIVV appliance is configured with proxy to reach the Internet and proxy is authenticated using NTLM authentication,
then the RPM update fails due to the issues in the underlying yum tool.
Version Affected: OMIVV 4.0 and later
Known issues
11