Release Notes

Version affected: 3.0 and later
Resolution: None. This is a known defect in the RACADM. The defect will be fixed in the next release of RACADM for
chassis.
● Issue 7: The hard drive name is not displayed at data center and cluster level inventory in some situations.
Description: Although the hard drive name is displayed when you view the inventory at the host level, the hard drive name is
displayed empty when you view the inventory of the host at the data center and cluster level.
Version affected: 3.0 and later
Resolution: This issue does not affect the functionality of the features, and you can view the inventory at the host level to
see the hard drive name.
● Issue 8: Using OMIVV to update an Intel Network card with the firmware version of 13.5.2 is not supported.
Description: There is a known issue with Dell EMC PowerEdge 12th generation servers and some Intel network cards with
the firmware version of 13.5.2. Updating some models of the Intel network cards at this version of firmware fails when the
firmware update is applied using the iDRAC with Lifecycle Controller.
Version affected: All
Resolution: Update the network driver software using an operating system. If the Intel network card has a version of
firmware other than 13.5.2, you can update using OpenManage Integration.
NOTE: When using the one-to-many firmware update, avoid selecting Intel network interface controllers that are at
version 13.5.2, as this fails and stops the update task from updating remaining servers.
● Issue 9: Firmware upgrade or downgrade of Broadcom NetXtreme II 10-Gigabit Ethernet adapter (BCM57712) from
firmware version of 6.2.x or earlier is not supported.
Description: Using OMIVV to upgrade a Broadcom NetXtreme II 10-Gigabit Ethernet adapter (BCM57712) from firmware
version of 6.2.x or earlier, or downgrade to a firmware version of 6.2.x or earlier is not supported.
Version affected: All
Resolution: 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 10: 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 nonresponsive 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: 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 11: 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: 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 12: Events from different vCenter are posted to another vCenter from a shared OMIVV 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
10
Known issues