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

If any of the selected servers do not support an IDSDM, or an IDSDM is not present during deployment, perform one of the
following actions:
○ Select Deploy the hypervisor to the first hard disk for servers that do not have an available Internal Dual SD
Module check box, if you want to deploy a hypervisor on the first hard disk of the servers.
CAUTION: If you select this option and deploy the hypervisor on the first hard disk drive of the servers, all
the data on the disk drives are erased.
○ To skip the deployment on the selected servers and continue with hypervisor deployment on the next server, clear Deploy
the hypervisor to the first hard disk for servers that do not have an available Internal Dual SD Module.
c. Under Credential Profile, perform either of the following actions:
• Select the Use this Credential Profile for all Servers option button, and to assign all servers to the same existing profile,
select the connection profile from the drop-down list.
• Click the Select a Connection Profile for each Server option button, and then select an individual connection profile for
each server from the drop-down list.
7. Click Next.
The Server Identification page is displayed.
The server identification can be provided in two ways:
• Enter networking information (IP address, subnet mask, and gateway)—a fully qualified domain name for the host name is
mandatory. The use of localhost for the FQDN is not supported. The FQDN is used when adding the host to vCenter.
• Use Dynamic Host Configuration Protocol (DHCP) to configure IP addresses, subnet mask, gateway IP, host name, and preferred/
alternate DNS servers—the DHCP assigned IP address is used when adding the host to vCenter. When using DHCP, Dell
recommends that an IP reservation for selected NIC MAC addresses is used.
NOTE:
Use a Fully Qualified Domain Name (FQDN) for host name instead of localhost. Starting with ESXi 5.1, a value
of localhost impairs the OMIVV plug-in from processing events sent from the host. Create a DNS record that
resolves the IP address with the FQDN. For SNMP alerts from ESXi 5.1 to be identified correctly, configure the DNS
server to support reverse lookup requests. The DHCP reservations and DNS host names must be in place and verified
before the deployment job is scheduled to run.
8. In the Server Identification page, do the following:
The page provides the option to specify a VLAN ID. When a VLAN ID is provided, it is applied to the management interface of
hypervisor during deployment and tags all traffic with the VLAN ID. Server Identification assigns new names and network identification
to deployed servers. See VLAN support.
a. To expand and view individual server information, under Selected Servers, click
.
b. Under Host Name and NIC, enter a Fully Qualified Host Name for the server.
c. In the NIC for Management Tasks drop-down list, select the NIC for managing the server.
d. Enter IP addresses, subnet mask, default gateway, and DNS details, or select the Obtain using DHCP check box.
e. If deploying to a network that requires a VLAN ID, select the VLAN check box and then enter the VLAN ID.
For the VLAN ID, use the numbers 1 through 4094. VLAN ID 0 is reserved for tagging the priority of frames.
f. Repeat steps a through h for all servers to be deployed, or select the Apply settings to all selected servers check box.
If you select the Apply settings to all selected servers, enter FQDN name and IP address for the other servers.
NOTE: While specifying FQDN name for servers, ensure to provide unique host names for each server.
9. Click Next.
10. In the Schedule Deployment page, perform the following actions:
a. Enter a Job Name and Job Description.
b. For vCenter Settings, enter the following:
i. In vCenter Instance, select the server instance that manages a host after deployment.
ii. In vCenter Destination Container, click Browse to search for vCenter destinations.
iii. In vCenter Host Profile, select a profile that encapsulates host configuration and helps to manage host configuration, which
is optional.
c. Determine when to run a deployment job by selecting a job schedule:
i. Select Schedule Deployment Job
• Use the calendar control to select the date.
• Enter the time.
Deploying hypervisor
101