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
NOTE: If you had registered any vCenter servers with the appliance, unregister and re-register all the vCenter
instances.
NOTE: Ensure that you manually update all references to the virtual appliance across its environment such as
provisioning server in iDRAC, DRM.
Updating virtual appliance repository location and virtual appliance
To ensure that all data is protected, perform a backup of the OMIVV database prior to an update of the virtual appliance. See Managing
backup and restore on page 19.
1. In the APPLIANCE UPDATE section of the APPLIANCE MANAGEMENT page, verify the current and available version.
NOTE: The OMIVV appliance requires internet connectivity to display available upgrade mechanisms and perform the
RPM upgrade. Ensure that the OMIVV appliance has internet connectivity. Depending on the network settings,
enable proxy and provide proxy settings, if the network needs proxy. See Setting up the HTTP proxy.
NOTE: Ensure that the Update Repository Path is valid.
For the available virtual appliance version, the applicable RPM and OVF virtual appliance upgrade mechanisms are displayed with a tick
symbol. The following are the possible upgrade mechanism options, and you can perform either of the tasks for the upgrade
mechanism:
• If a tick symbol is displayed against RPM, you can do an RPM upgrade from the existing version to the latest available version. See
Upgrading from an existing version to the latest version.
• If a tick symbol is displayed against OVF, you can take a backup of the OMIVV database from the existing version, and restore it in
the latest available appliance version. See Updating the appliance through backup, and restore.
• If a tick symbol is displayed against both RPM and OVF, you can perform either of the mentioned options to upgrade your
appliance. In this scenario, the recommended option is RPM upgrade.
2. To update the virtual appliance, perform the mentioned tasks for the upgrade mechanisms as applicable from the version of OMIVV.
NOTE: Ensure that you log out from all web client sessions to the registered vCenter servers.
NOTE: Ensure that you update all appliances simultaneously under the same Platform Service Controller (PSC)
before logging in to any of the registered vCenter servers.
3. Click APPLIANCE MANAGEMENT, and verify the upgrade mechanisms.
Upgrading OMIVV from existing version to current version
1. In the APPLIANCE MANAGEMENT page, depending on your network settings, enable proxy and provide proxy settings if your
network needs proxy. See Setting up HTTP proxy.
2. To upgrade the OpenManage Integration plug in from an existing version to the current version, perform one of the following steps:
• Ensure that Update Repository Path is set to the path: http://linux.dell.com/repo/hardware/vcenter-plugin-x64/latest/. If the
path is different, in the Appliance Management window, in the APPLIANCE UPDATE area, click Edit to update the path to
http://linux.dell.com/repo/hardware/vcenter-plugin-x64/latest/ in the Update Repository Path text box. To save, click Apply.
• If there is no internet connectivity, download all the files and folders from the http://linux.dell.com/repo/hardware/vcenter-
plugin-x64/latest/ path and copy them to an HTTP share. In the Appliance Management window, in the APPLIANCE UPDATE
section, click Edit, and then in the Update Repository Path text box, include the path to the off line HTTP share, and click
Apply.
3. Compare the available virtual appliance version and current virtual appliance version and ensure that the available virtual appliance
version is greater than the current virtual appliance version.
4. To apply the update to the virtual appliance, under Appliance Settings, click Update Virtual Appliance.
5. In the UPDATE APPLIANCE dialog box, click Update.
After you click Update, you are logged off from the ADMINISTRATION CONSOLE window.
6. Close the web browser.
NOTE:
After the RPM upgrade is complete, you can view the login screen in the OMIVV console. Open a browser,
provide the https:\\<ApplianceIP|hostname> link, and navigate to the APPLIANCE UPDATE area. You can verify
that the available and current virtual appliance versions are same.
16 About Administration Console