Release Notes

Resolution/Workaround: There is a known issue with the Broadcom NetXtreme II 10-Gigabit Ethernet adapter (BCM57712)
where updating the adapter from firmware version of 6.2.x or earlier, or downgrade to a firmware version of 6.2.x or earlier
fails when the update is applied using the iDRAC with Lifecycle Controller.
When attempting to perform this update using the OpenManage Integration, the update may incorrectly show that it
completed successfully. However, the firmware update has failed and remains at the previous level. One way to successfully
update the adapter software for the Broadcom NetXtreme II 10-Gigabit Ethernet adapter (BCM57712) is to update the
adapter firmware from an operating system.
● Issue 13: Associated host credential profile is not displayed on the management compliance page when inventory is not able
to get iDRAC IP for the host.
Description: If the iDRAC IP is not retrieved because of non-responsive iDRAC, the inventory fails and host to be associated
with the host credential profile is not displayed on the management compliance page.
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.
Known issues
11