Release Notes

Resolution/Workaround: None
● Issue 15: Using OpenManage Integration 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 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 Lifecycle Controller.
Version affected: All
Resolution/Workaround: Customers with this version of firmware must 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 adapters that are at version 13.5.2, as this
fails and stops the update task from updating remaining servers.
● Issue 16: 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 the OpenManage Integration to upgrade a Broadcom NetXtreme II 10Gigabit 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/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 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 10Gigabit Ethernet adapter (BCM57712) is for customers to update the adapter firmware from an operating
system.
● Issue 17: Running firmware update may display an error message, The firmware repository file does not exist or is invalid.
Description: While running the Firmware Update wizard, at the data center or cluster level, an error message may be
displayed: The firmware repository file does not exist or is invalid. This may be due to a daily background process that was
unable to download and cache the catalog file from the repository. This occurs if the catalog file is not reachable at the time
the background process runs.
Version affected: All
Resolution/Workaround: After resolving any catalog connectivity issues that may exist, you can reinitiate the background
process by changing the firmware repository location, and then setting it back to the original location. Allow about 5 minutes
for the background process to complete and ensure that there is no @ character present in the credential provided for the
CIFS share. Also, ensure that the DUP file exists in the share location.
● Issue 18: An error occurs while installing the OpenManage Integration for VMware vCenter.
Description: While installing the OpenManage Integration for VMware vCenter, the following error is displayed: Network card
'VirtualE1000' has a DVPort backing, which is not supported. This could be because the host does not support VDS or
because the host has not joined a VDS.
Version affected: All
Resolution/Workaround: Set the network interface to the VM Network during the OVF installation. After the virtual machine
is created, remap the networking to the VDS port group.
● Issue 19: The Service Tag is not displayed during a firmware update.
Description: In the firmware inventory and on the Select Update Bundles tab, the Service Tag information is not displayed
for the Dell PowerEdge 11th generation servers. This information is not displayed if VMware vCenter does not provide the
Service Tag.
Version affected: All
Resolution/Workaround: You can view the Service Tag information on the Host Overview page from where you launched
the firmware update.
● Issue 20: Associated Connection Profile is not displayed in the host compliance page when inventory is not able to get
iDRAC IP for the host.
5