Version Affected: All

Why is the DNS configuration settings restored to original settings after appliance reboot if using DHCP for appliance IP and DNS settings overwritten

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 will be different from DHCP.

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.

Even if my repository has bundles for selected 11G system, why is firmware update showing that I have no bundles for Firmware Update?

When I added a host to the connection profile in lockdown mode, the inventory kicked 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, right?

If you put the host in lockdown mode or remove a host from lockdown mode, you must wait 30–minutes before performing the next operation on the If I pick a 11G host for firmware update, the firmware update wizard will not show any bundles even if the repository provided has bundles for that system. This will happen because the 11G host might not configured for OMSA to send traps to OpenManage Integration.

Resolution: Ensure that the host is compliant using the host Compliance screen of OpenManage Integration desktop client. If it is not compliant, use the fix Host Compliance to get it compliant.

Version Affected: 2.2 and 2.3

Why Does My ESX / ESXi Deployment Fail on Servers Having a PERC S300 Boot Controller?

Deployments of OpenManage Integration for VMware vCenter using different ESX/ESXi versions on Dell PowerEdge servers with the PERC S300 boot controller failed. The Dell customized ESX/ESXi operating systems do not carry the driver for the PERC S300 boot controller, which causes the boot controller/HDD not to be recognized during operating system installation. Servers with PERC S300 boot controllers are not supported for OpenManage Integration for VMware vCenter deployments.

How Come I See An Error Message Displayed After Clicking The Firmware Link?

If you have a slow network speed (9600BPS), you may get a Communication Error Message. This error message may display when you click the Firmware link in the vSphere Client for the OpenManage Integration for VMware vCenter. It happens when the connection times out while trying to obtain the Software Inventory list. Microsoft Internet Explorer initiates this timeout. For Microsoft Internet Explorer versions 9/10, the default “Receive Time out” value is set to 10 seconds. Fix this issue by using the following steps.

83

Page 83
Image 83
Dell 2.3 manual Version Affected All