Users Guide
Table Of Contents
- OpenManage Integration for VMware vCenter Version 4.0.1 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 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 does server move to quarantine or maintenance mode when Proactive HA is turned on cluster?
- RPM upgrade is unsuccessful when necessary vCenter privileges are not provided
- 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

NOTE: To ensure that OMIVV continues to display updated information, Dell recommends that you schedule a periodic
inventory job. The inventory job consumes minimal resources and does not degrade host performance.
NOTE: The chassis gets discovered automatically after the inventory for all the blades of the chassis are run. If the chassis
is added to a chassis profile, the chassis inventory automatically runs. In an SSO environment with multiple vCenter servers,
the chassis inventory runs automatically with every vCenter when the inventory for any vCenter is run at a scheduled time.
NOTE: The settings in this page are reset to default each time the configuration wizard is invoked. If you have previously
configured a schedule for inventory, ensure that you replicate the previous schedule in this page before completing the
wizard functions so that the previous schedule is not overridden by the default settings.
1. In the Initial Configuration Wizard, from the Inventory Schedule dialog box, select Enable Inventory Data Retrieval, if
it is not enabled. By default, Enable Inventory Data Retrieval is enabled.
2. Under Inventory Data Retrieval Schedule, perform the following steps:
a. Select the check box next to each day of the week that you want to run the inventory.
By default, all the days are selected.
b. In Data Retrieval Time, enter the time in HH:MM format.
The time you enter is your local time. Therefore, if you want to run the inventory at the virtual appliance time zone,
calculate the time difference between your local and virtual appliance time zone, and then enter the time appropriately.
c. To apply the changes and continue, click Next.
Once you click next, all details that you provide in this wizard is saved and you cannot modify the details from this wizard.
You can modify inventory schedule details of the hosts from the Manage > Settings tab after completing the configuration
from the configuration wizard. See Modifying inventory job schedules on page 48.
Running warranty retrieval jobs
The warranty retrieval job configuration is available from the Settings tab in OMIVV. In addition, you can also run or schedule
warranty retrieval job from Job Queue > Warranty. The scheduled jobs are listed in the job queue. In an SSO environment with
multiple vCenter servers, the chassis warranty runs automatically with every vCenter when the warranty for any vCenter is run.
However, warranty does not automatically run if it is not added to chassis profile.
NOTE:
The settings in this page are reset to default each time the configuration wizard is invoked. If you have previously
configured a warranty retrieval job, ensure that you replicate that schedule warranty retrieval job in this page before
completing the wizard functions so that the previous warranty retrieval is not overridden by the default settings.
1. In the Warranty Schedule dialog box, select Enable Warranty Data Retrieval.
2. In Warranty Data Retrieval Schedule, do the following:
a. Select the check box next to each day of the week that you want to run the warranty.
b. Enter the time in HH:MM format.
The time you enter is your local time. Therefore, if you want to run the inventory at the virtual appliance time zone,
calculate the time difference between your local and virtual appliance time zone, and then enter the time appropriately.
3. To apply the changes and continue, click Next, and then proceed with the Event and Alarm settings.
Once you click next, all details that you provide in this wizard is saved and you cannot modify the details from the wizard.
You can modify warranty job schedules from the Settings tab after completing the configuration from the configuration
wizard. See Modifying warranty job schedules on page 50.
Configuring events and alarms
You can configure events and alarms by using the Initial Configuration Wizard or from the Settings tab for events and
alarms. To receive events from the servers, OMIVV is configured as trap destination. For 12th generation hosts and later, ensure
that the SNMP trap destination is set in iDRAC. For hosts earlier than 12th generation, ensure that the trap destination is set in
OMSA.
NOTE:
OMIVV supports SNMP v1 and v2 alerts for 12th generation hosts and later and supports only SNMP v1 alerts for
hosts earlier than 12th generation.
1. In the Initial Configuration Wizard, under Event Posting Levels, select one of the following:
● Do not post any events—block hardware events
● Post all events—post all hardware events
● Post only Critical and Warning events—post only critical or warning level hardware events
34
Appliance configuration for VMware vCenter