Users Guide

For an ESXi host, ensure that you install OMSA VIB by using the VMware Remote CLI tool, and reboot the system.
Can OMIVV support ESXi with lockdown mode enabled?
Yes, lockdown mode is supported in this Release on hosts ESXi 5.0 and later.
When I tried to use lockdown mode, it fails
When I added a host to the connection profile in lockdown mode, the inventory started, but failed stating that “No Remote Access
Controller was found or Inventory is not supported on this host.”
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 in OMIVV.
What setting should I use for
UserVars.CIMoeMProviderEnable with ESXi 4.1 U1?
Set UserVars.CIMoemProviderEnabled to 1.
What do I do if creation of hardware profile fails if I am
using reference server?
Check to ensure that minimum recommended versions of the iDRAC firmware, the Lifecycle Controller firmware, and BIOS are installed.
To ensure 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.
Why attempting to deploy ESXi on Blade server fails?
1. Ensure that the ISO location (NFS path) and staging folder paths are accurate.
2. Ensure that the NIC selected during assignment of server identity is on the same network as the virtual appliance.
3. If using static IP address, ensure that the network information provided (including subnet mask and Default Gateway) is accurate.
Also, ensure that the IP address is not already assigned on the network.
4. Ensure that at least one Virtual Disk is seen by the system.
ESXi also installs to an internal RIPS SD card.
Why hypervisor deployments failing on Dell PowerEdge
R210 II machines?
A timeout issue on the Dell PowerEdge R210 II systems produces a hypervisor deployment failure error due to the failure of the BIOS to
boot from the attached ISO.
Resolution: Manually install hypervisor on the machine.
Why auto discovered systems are displayed without model
information in Deployment wizard?
This usually indicates that the firmware version installed on the system does not meet the recommended minimum requirements.
Sometimes, a firmware update may not have registered on the system.
Resolution: Cold booting the system or reseating the Blade fixes this issue. The newly enabled account on the iDRAC must be disabled,
and auto discovery reinitiated to provide model information and NIC information to OMIVV.
126
Troubleshooting