Users Guide

Version Affected: 2.2 and later
Why am I not seeing OpenManage Integration icon in web client
even if registration of plug-in to vCenter was successful?
OpenManage Integration icon is not displayed in the web client unless the vCenter web client services are restarted or the box
is rebooted. When you register the OpenManage Integration for VMware vCenter appliance, the appliance is registered with
both the desktop client and the web client. If you unregister the appliance and then either re-register the same version or
register a new version of the appliance, it successfully registers with both clients, but the Dell icon may not appear in the web
client. This is due to a caching issue from VMware. To clear the issue, ensure that you restart the web client service on the
vCenter Server. Then the plug-in is displayed in the UI.
Resolution: Restart the web client service on the vCenter server.
Version Affected: 2.2 and later
Even if repository has bundles for selected 11G system, why is
firmware update displaying that there are no bundles for firmware
update?
When I add a host to the connection profile in lockdown mode, the inventory kicks off but failed stating that “No Remote
Access Controller was found or Inventory is not supported on this host.” Inventory is supposed to work for a host in lockdown
mode.
If you put the host in lockdown mode or remove a host from lockdown mode, ensure that you wait for 30 minutes before
performing the next operation. If you use a 11G host for firmware update, the firmware update wizard does not display any
bundles even if the repository has bundles for that system. This occurs because the 11G host might have not been configured
for OMSA to send traps to OpenManage Integration.
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.
126 Troubleshooting