Users Guide

Resolution: Ensure that the host is compliant by using the host compliance wizard of the OpenManage Integration web client. If it is not
compliant, use the Fix Host Compliance to get it compliant.
Version Affected: 2.2 and later
Why is DNS configuration settings restored to original
settings after appliance reboot if appliance IP and DNS
settings are overwritten with DHCP values
There is a known defect where statically assigned DNS settings are replaced by values from DHCP. This can happen when DHCP is used
to obtain IP settings, and DNS values are assigned statically. When the DHCP lease is renewed or the appliance is restarted, the statically
assigned DNS settings are removed.
Resolution: Statically assign IP settings when the DNS server settings are different from DHCP.
Version Affected: All
Using OMIVV to update the Intel network card with
firmware version of 13.5.2 is not supported
There is a known issue with the 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 by using the Lifecycle
Controller. Customers with this version of firmware must update the network driver software by using an operating system. If the Intel
network card has a version of firmware other than 13.5.2, you can update using OMIVV. 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 one-to-many firmware update, avoid selecting Intel network adapters that are at version
13.5.2, as the update fails and stops the update task from updating remaining servers.
Using OMIVV to update 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. Ensure that you use the custom catalog to update the firmware to 15.5.0 before updating
the firmware to 16.x.
Version Affected: All
Why trying firmware update with invalid DUP, hardware
update job status on vCenter console neither fails nor
times-out for hours, although job status in LC prompts as
FAILED
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 must be canceled manually.
Version Affected: All
Frequently Asked Questions-FAQ
133