Release Notes

Version affected: 1.5.1 and later
Resolution/Workaround: Remove the local USB CD-ROM (note that not all local CD-ROM would expose this issue), or plug in
additional USB floppy or USB key on the system, or attach the virtual media (virtual floppy and virtual CD) from the iDRAC.
• Issue 31: 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 32: 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 a hypervisor 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 appears as disconnected.
Version affected: All
Resolution/Workaround: Remove the host from the first vCenter where it is now showing as disconnected.
• Issue 33: CSIOR status is displayed as "Unknown".
Description: A server may show as non-compliant with CSIOR status, "Unknown".
Version affected: All
Resolution/Workaround: An unknown CSIOR state indicates a non-responsive iDRAC on the host. A manual iDRAC reset on the host
fixes this issue.
• Issue 34: Hypervisor installation fails.
Description: Hypervisor 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 35: NFS mount remains mounted after successful deployment by using ESXi 5.0.
Description: After the hypervisor deployment is complete and the host is added to the vCenter tree, there is an entry in the Summary
page under the data sources called, "remote-install-location (inactive) (unmounted)" for the new host added.
Version affected: 1.5 and later
Resolution/Workaround: None
• Issue 36: Health Status is showing Warning for chassis while one or more Power supply 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 37: 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: Storage component health status is shown correctly as Warning.
• Issue 38: 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 Monitor page for VRTX chassis when a Blower is removed from a
slot.
Version affected: 2.0 and later
Resolution/Workaround: You can see the fan inventory before the blower was removed.
• Issue 39: File type '.csv' is not be appended to the file, if the file name is anything other than "Export List".
Description: When we export any of the grid details from any OMIVVC pages (from IE9), the default File Name "ExportList" is shown.
If saved as is, it will be saved as "ExportList.csv". If the file name is changed to anything other than "Export List", the file will be saved
without any extension.
Opening the file will show all details in comma separated value format. Issue is just to append.
Version affected: M1000e firmware version 5.0
8
OpenManage Integration for VMware vCenter Version 4.0 Release Notes