Users Guide
Table Of Contents
- OpenManage Integration for VMware vCenter Version 4.0 Web Client User's Guide
- Introduction
- About Administration Console
- Using Administration Portal
- Registering vCenter server by non-administrator user
- Registering a vCenter server
- Uploading license to Administration Portal
- Managing the virtual appliance
- Restarting virtual appliance
- Changing host name of virtual appliance
- Updating virtual appliance repository location and virtual appliance
- Upgrading OMIVV from existing version to current version
- Updating appliance through backup and restore
- Downloading the troubleshooting bundle
- Setting up HTTP proxy
- Setting up Network Time Protocol (NTP) servers
- Configuring deployment mode
- Generating Certificate Signing Request
- Uploading HTTPS certificate
- Setting up global alerts
- Managing backup and restore
- About vSphere client console
- Using Administration Portal
- Managing multiple appliances
- Accessing OpenManage Integration from web client
- OpenManage Integration for VMware vCenter licensing
- Appliance configuration for VMware vCenter
- Profiles
- Inventory and warranty management
- About firmware updates
- Events, alarms, and health monitoring
- Chassis management
- Deploying hypervisor
- About host, bare-metal, and iDRAC compliance
- Security roles and permissions
- Troubleshooting
- Frequently Asked Questions (FAQ)
- Why Export All button fails to export to .CSV file in Google chrome?
- iDRAC license type and description are displayed incorrectly for non-compliant vSphere hosts
- Dell icon is not displayed after unregistering vCenter from earlier OMIVV version and then registering same vCenter with later OMIVV version
- Configuration wizard settings are overridden by default settings each time it is invoked
- Dell provider is not displayed as health update provider
- Why is inventory failing when performing firmware update task on ESXi 5.x host?
- Host inventory or test connection fails due to invalid or unknown iDRAC IP. How can I get a valid iDRAC IP?
- On running fix noncompliant vSphere hosts wizard, why the status of a specific host is displayed as "Unknown"?
- Dell privileges that are assigned while registering the OMIVV appliance are not removed after unregistering OMIVV
- Dell Management Center does not display all the relevant logs when trying to filter a severity category. How can I view all the logs?
- How do I resolve error code 2000000 caused by VMware Certificate Authority (VMCA)?
- Firmware Update Wizard shows a message mentioning that the bundles are not retrieved from firmware repository. How can I continue with the firmware update?
- In Administration Console, why Update Repository Path is not set to default path after I reset appliance to factory settings?
- Why firmware update for 30 hosts at cluster level fails
- Why warranty and inventory schedule for all vCenters is not applying when selected from the job queue page?
- What should I do when a web communication error in the vCenter web client appears after changing the DNS settings in OMIVV?
- Why does the settings page fail to load, if I navigate away and again go back to the settings page?
- Why “Task cannot be scheduled for the time in the past” error in inventory schedule/warranty schedule page of Initial Configuration Wizard appear?
- Why installation date appears as 12/31/1969 for some of the firmware on the firmware page?
- Successive global refresh cause exception to be thrown in the recent task window. How can I resolve the error?
- Why is web client UI distorted for few Dell screens in IE 10?
- Why am I not seeing OpenManage Integration icon in web client even if registration of plug-in to vCenter was successful?
- Even if repository has bundles for selected 11G system, why is firmware update displaying that there are no bundles for firmware update?
- Why is DNS configuration settings restored to original settings after appliance reboot if appliance IP and DNS settings are overwritten with DHCP values
- Using OMIVV to update the Intel network card with firmware version of 13.5.2 is not supported
- Using OMIVV to update Intel network network card from 14.5 or 15.0 to 16.x fails due to staging requirement from DUP
- 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’?
- Why does Administration Portal display unreachable update repository location?
- Why did system not enter maintenance mode when I performed one-to-many firmware update?
- Why is chassis global health still healthy when some of power supply status has changed to critical?
- Why is processor version displayed “Not Applicable” in processor view in system overview page?
- Why exception is returned when I click finish after editing connection profile through web client?
- Why connection profiles to which host belongs to when I create\edit connection profile in web GUI cannot be seen?
- Why is select host window in web UI is blank on editing connection profile?
- Why error message is displayed after clicking firmware link?
- What generation of Dell servers does OMIVV configure and support for SNMP traps?
- What vCenter servers are managed by OMIVV?
- Does OMIVV support vCenter in linked mode?
- What are required port settings for OMIVV?
- What are minimum requirements for successful installation and operation of virtual appliance?
- Why is password not changed for user used for bare-metal discovery after successfully applying hardware profile that has same user with new changed credentials in iDRAC user list?
- Why am I unable to view new iDRAC version details listed on vCenter hosts and clusters page?
- How can I test event settings by using OMSA to simulate temperature hardware Fault?
- Although OMSA agent is installed on OMIVV host system, I still get error message that OMSA is not installed. How do I resolve this error?
- Can OMIVV support ESXi with lockdown mode enabled?
- When I tried to use lockdown mode, it fails
- What setting should I use for UserVars.CIMoeMProviderEnable with ESXi 4.1 U1?
- What do I do if creation of hardware profile fails if I am using reference server?
- Why attempting to deploy ESXi on Blade server fails?
- Why hypervisor deployments failing on Dell PowerEdge R210 II machines?
- Why auto discovered systems are displayed without model information in Deployment wizard?
- NFS share is set up with ESXi ISO, but deployment fails with errors mounting share location
- How do I force removal of virtual appliance?
- Entering a Password in the Backup Now Screen Receives an Error Message
- In vSphere web client, clicking Dell server management portlet or Dell icon returns 404 error
- What should I do as firmware update failed?
- What should I do as vCenter registration failed?
- Performance during connection profile test credentials is slow or unresponsive
- Does OMIVV support VMware vCenter server appliance?
- Why is firmware level not updated when I have performed firmware update with Apply on Next reboot option and system was rebooted?
- Why is host still displayed under chassis even after removing host from vCenter tree?
- In Administration Console, why Update Repository Path is not set to default path after I reset appliance to factory settings?
- After backup and restore of OMIVV, why alarm settings are not restored?
- Bare-metal deployment issues
- Frequently Asked Questions (FAQ)
- Related Documentation
Deploying hypervisor
OMIVV allows you to configure the following components in the supported bare-metal servers along with deploying the hypervisor and
adding it to the specified data center and cluster in a vCenter.
• Boot order setting
• RAID configuration
• BIOS configuration
• iDRAC configuration
You can create hardware profiles, hypervisor profiles on the bare-metal Dell PowerEdge servers by using VMware vCenter without using
PXE.
To provision hardware and perform deployment, ensure that the physical servers appear in the Deployment Wizard. Ensure that all
physical servers are as per the following requirements:
• Meet specific hardware support information that is available in the OpenManage Integration for VMware vCenter Compatibility
Matrix.
• Meet minimum supported versions of iDRAC firmware, Lifecycle Controller, and BIOS. See the OpenManage Integration for VMware
vCenter Compatibility Matrix for specific firmware support information.
• Configure NICs in PCI slots manually after the deployment. If you are using add-on NICs, the system must have the host LAN on
Motherboard (LOMs) enabled and connected to network. OMIVV supports deployment by using only embedded or integrated LOMs.
• Meet the storage specifications of iDSDM. To know about the storage specifications of iDSDM, see the VMware documentation.
Ensure that you enable the iDSDM from BIOS before you deploy the hypervisor with OMIVV. OMIVV allows deployment on iDSDM or
local hard drives.
• Ensure that there is a route between the vCenter and iDRAC networks if vCenter and iDRAC are connected to different networks.
• Ensure that Collect System Inventory on Reboot (CSIOR) is enabled. Also, before initiating auto/manual discovery, ensure that
retrieved data is current by completely powering off the system and then power on the system (hard reboot).
• Choose to order the Dell servers with auto discovery and handshake options preconfigured by the factory. If a server is not
preconfigured with these options, manually enter the OMIVV IP address or configure your local network to provide this information.
• Ensure that the following conditions are met before initiating hypervisor deployment if OMIVV is not used for hardware configuration:
○ Enable the virtualization technology (VT) flag in BIOS.
○ Set the system's boot order to either a bootable virtual disk or iDSDM for operating system installation.
• Verify that the BIOS setting for VT is automatically enabled even if the BIOS configuration is not part of the hardware profile, if OMIVV
is used for hardware configuration. The Express/Clone RAID configuration is required if a virtual disk is not already present on the
target system.
• Ensure that the custom ESXi images that contain all the Dell drivers are available for deployment. You can find the correct images from
support.dell.com by navigating to the Dell Drivers & Downloads page, and saving the custom images to a CIFS or NFS share
location that OMIVV can access during the deployment process. For up-to-date list of supported ESXi versions for this release, see
OpenManage Integration for VMware vCenter Compatibility Matrix. To use the correct images, see Downloading custom Dell ISO
images.
• Ensure that you have BIOS mode selected in the reference hardware profile before applying the hypervisor profile as OMIVV only
supports BIOS mode to autodeploy hypervisor on the target server. If there is no hardware profile selected, ensure that you manually
configure the boot mode as BIOS and reboot the server before applying the hypervisor profile.
NOTE: If the BOOT mode in the target system is set to UEFI, OMIVV fails to deploy the OS.
If servers are from versions earlier than Dell PowerEdge 12th generation servers, the deployment process performs the following tasks:
• Installs the OMSA package on the target system.
• Automatically configures the SNMP trap destination in OMSA to point to OMIVV.
Topics:
• Device discovery
• Provisioning
• Configuring hardware profile
• Creating hypervisor profile
12
Deploying hypervisor 89