Users Guide

Using OpenManage Integration for VMware vCenter to update an
Intel Network card with the firmware version of 13.5.2 is not
supported.
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 Intel network cards at this version of firmware fails when the firmware update is applied using
the Lifecycle Controller. 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
for VMware vCenter. For more information, see http://en.community.dell.com/techcenter/b/techcenter/archive/2013/03/20/
intel-network-controller-card-with-v13-5-2-firmware-cannot-be-upgraded-using-lifecycle-controller-to-v13-5-6.aspx
NOTE: Note: When using the one-to-many firmware update, avoid selecting Intel network adapters that are at version
13.5.2, as the update will fail and stop the update task from updating remaining servers.
Using OpenManage Integration for VMware vCenter to update an
Intel Network card from 14.5 or 15.0 to 16.x fails due to staging
requirement from DUP
This is a known issue with NIC 14.5 and 15.0. You must use the custom catalog to update the firmware to 15.5.0 first before
updating the firmware to 16.x.
Version Affected: All
On trying a firmware update with an invalid DUP, the hardware
update job status on the vCenter console neither fails nor times-
out for hours, though the job status in LC says ‘FAILED’. Why is
this happening?
When the invalid DUP is picked for firmware update, the status of the task in the vCenter console window remains ‘In Progress’
but the message is changed to the reason of failure. This is a known VMware defect and will be fixed in the future releases of
VMware vCenter.
Resolution: The task has to be cancelled manually.
Version Affected: All
Administration Portal is still showing the unreachable Update
Repository location.
If the user provided a unreachable Update Repository path, the error message “Failed: Error while connecting to the URL …. ” is
displayed on the top of the Appliance Update view, however the Update Repository Path is not cleared out to the value before
update.
Resolution: Move out of this page to another page and make sure the page is refreshed.
Version Affected: All
Why did my system not enter maintenance mode when I performed
a one-to-many firmware update?
Some firmware updates do not require rebooting the host. In that case, the firmware update is performed without putting the
host into maintenance mode.
Troubleshooting
117