Users Guide

When I tried to use lockdown mode, it failed.

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 OpenManage Integration for VMware vCenter.

What Setting Should I Use For UserVars.CIMoeMProviderEnable With ESXi 4.1 U1?

Set UserVars.CIMoemProviderEnabled to 1.

I Am Using A Reference Server to Create a Hardware Profile But it Failed. What Should I

Do?

Check to make sure that minimum recommended versions of iDRAC firmware, Lifecycle Controller firmware, and BIOS

are installed.

To make sure that the data retrieved from the reference server is current, enable Collect System Inventory On Restart

(CSIOR), and restart the reference server prior to extraction of data. See Setting CSIOR on a Reference Server.

I Am Attempting To Deploy ESX/ESXi On A Blade Server And It Failed. What Should I Do?

To resolve this issue, do the following:

1. Make sure the ISO location (NFS path) and staging folder paths are accurate.

2. Make sure the NIC selected during assignment of server identity is on the same network as the virtual appliance.

3. If using static IP address, make sure the network information provided (including subnet mask and default gateway)

is accurate. In addition, , make sure the IPaddress is not already assigned on the network.

4. Make sure at least one Virtual Disk is seen by the system. ESXi also installs to an internal RIPS SD card.

Why Are My Hypervisor Deployments Failing On R210 II Machines?

A timeout issue on R210 II systems produces a hypervisor deployments failure error due to the failure of the BIOS to boot

from attached ISO. To resolve this issue, manually install hypervisor on the machine.

Why Do I See Auto-discovered Systems Without Model Information in the Deployment

Wizard

This usually indicates that the firmware version installed on the system does not meet recommended minimum

requirements. In some cases, a firmware update may not have registered on the system. Cold booting the system or

reseating the blade fixes this problem. The newly enabled account on the iDRAC must be disabled and auto-discovery

reinitiated to provide model information and NIC information to the OpenManage Integration for VMware vCenter.