Users Guide
Table Of Contents
- OpenManage Integration for VMware vCenter Version 4.3 Web Client User's Guide
- Introduction
- About Administration Console
- Using Administration Portal
- Registering vCenter server
- Registering vCenter Server by non-administrator user
- 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 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
- Using Baseline tab
- Profiles
- Inventory and warranty management
- Events, alarms, and health monitoring
- About firmware updates
- Chassis management
- Deploying hypervisor
- Device discovery
- Provisioning
- System profiles
- Managing System profiles
- Configuring hardware profile
- Creating hypervisor profile
- Creating deployment templates
- About deployment wizard
- Deployment job timing
- Downloading custom Dell EMC ISO images
- About host, bare-metal, and iDRAC compliance
- Security roles and permissions
- Frequently Asked Questions-FAQ
- Frequently Asked Questions-FAQ
- 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 provider is not displayed as health update provider
- 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.
- On running fix noncompliant vSphere hosts wizard, 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
- OMIVV does not display all the relevant logs when trying to filter a severity category
- How do I resolve error code 2000000 caused by VMware Certificate Authority-VMCA
- In Administration Console, Update Repository Path is not set to default path after I reset appliance to factory settings
- 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
- The settings page fail to load, if I navigate away and again go back to the settings page
- Task cannot be scheduled for the time in the past- error in inventory schedule and warranty schedule page of Initial Configuration Wizard appear
- 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.
- Why is web client UI distorted for few Dell screens in IE 10
- I am 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, 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 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
- Chassis global health still healthy when some of power supply status has changed to critical
- Processor version is displayed as “Not Applicable” in processor view in system overview page
- Does OMIVV support vCenter in linked mode
- What are required port settings for OMIVV
- Password is not changed for user used for bare-metal discovery after successfully applying hardware profile or system profile that has same user with new changed credentials in iDRAC user list
- 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.
- Can OMIVV support ESXi with lockdown mode enabled
- When I tried to use lockdown mode, it fails
- Creation of hardware profile fails if I am using reference server
- Attempting to deploy ESXi on server fails
- Hypervisor deployments failing on Dell PowerEdge R210 II machines
- 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 remove virtual appliance from vCenter
- 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
- Firmware level not updated when I have performed firmware update with Apply on Next reboot option and system was rebooted
- Host still displayed under chassis even after removing host from vCenter tree
- In Administration Console, Update Repository Path is not set to default path after I reset appliance to factory settings
- After backup and restore of OMIVV, alarm settings are not restored
- Hypervisor deployment fails when NPAR is enabled on a target node and disabled in System Profile
- Available virtual appliance version displays wrong information when the available version is lesser than the current version
- The 267027 exception is thrown while adding a 12G bare-metal server with an Express license
- During OS deployment on 14G, hardware profile apply fails due to iDRAC error
- OMIVV RPM upgrade fails when proxy is configured with domain user authentication
- Unable to apply System Profile that has PCIe card in the FX chassis
- Drift Detection shows noncompliant for Modular servers that has PCIe card in the FX chassis
- Unable to deploy an OS on PowerEdge serves when the iDRAC does not populate the MAC address of the selected NIC
- When deploying an OS, the Hardware Profile cannot be applied and the boot order cannot be configured without restarting the host
- When creating a connection profile for the host having ESXi 6.5U1, the Service Tag of the host is not displayed on the Select Hosts page
- Chassis object is not displayed on the left Navigator pane of the Dell EMC Chassis page
- Dell icon is not displayed after backup and restore from an earlier OMIVV version to a later OMIVV version
- When upgrading or downgrading some iDRAC firmware versions using OMIVV, even when the actual firmware update is successful, OMIVV may indicate that the job is failed.
- The deployment job fails when a server is in the UEFI mode and Secure boot feature is enabled
- Configuring the System Lockdown mode at a cluster level sometimes displays a message "No hosts under the cluster has successful inventory"
- Sometimes post RPM upgrade of OMIVV appliance, multiple entries in the logs are seen in vCenter Recent Tasks
- Bare-metal deployment issues
- Frequently Asked Questions-FAQ
- Related Documentation
- System specific attributes
- Customization attributes
- Additional information
- Component vs. baseline version comparison matrix
Fixing iDRAC license compliance for vSphere hosts
The vSphere hosts listed in the vSphere host compliance pages are noncompliant because they do not have a compatible iDRAC
license. The table displays the status of the iDRAC license. You can click a noncomplaint host to view more details such as, how
many days are remaining for the iDRAC license, and then you can update it, as required. The Run inventory job link is active if
the iDRAC compliance status is "non-compliant" or "Unknown" for any one of the host associated to a connection profile.
1. In OpenManage Integration for VMware vCenter, from the Manage tab, click Compliance > vSphere Hosts.
2. Select a host where iDRAC License Status is Non-compliant.
3. If license is out of date, click the Purchase/Renew iDRAC License link.
4. Log in to the Dell License Management page and update or purchase a new iDRAC license.
Use the information in this page to identify and update your iDRAC.
5. After you install an iDRAC license, run an inventory job for the vSphere host and return to this page after the inventory job is
successfully complete for the host to be compliant.
Support for OEM servers
OEM servers are supplied by Dell EMC partners, who offer features or portfolios similar to PowerEdge servers.
● From OMIVV 4.3 onwards, OEM Rack and Tower servers are supported.
● Onboard OEM servers by using the Add OEM Hosts wizard. For more information about adding OEM hosts, see Adding
OEM hosts on page 132.
NOTE:
If the WBEM service is already enabled on the OEM hosts and is added to vCenter, by default, OMIVV adds
those OEM servers to the OMIVV–managed list. Associate the hosts to the connection profile to manage these servers.
For more information about creating a connection profile, see Creating connection profile on page 48.
● After onboarding, all the host management processes will be similar to how Dell EMC PowerEdge servers are managed.
● Bare-metal and hypervisor flows are also supported on OEM servers by using iDRAC.
Adding OEM hosts
Along with Dell EMC PowerEdge servers, OMIVV also supports rebranded and debranded servers. For more information about
OEM, see https://www.dellemc.com.
NOTE:
If the WBEM service is already enabled, OMIVV determines the iDRAC connectivity of the host. If the connection is
available, OMIVV adds the host to the managed list. If OMIVV is unable to determine, you must manually select the host on
the Add OEM Hosts wizard so that the host is added to the OMIVV-managed list.
NOTE: If the WBEM service is disabled or iDRAC is not reachable, use Add OEM Hosts wizard so that the host is added to
the OMIVV-managed list.
1. On the OpenManage Integration for VMware vCenter page, click Manage > Compliance > vSphere Hosts > Add
OEM Hosts.
2. In the Add OEM Hosts window, from the vCenter Instance drop-down list, select a vCenter.
3. From the Connection Profile drop-down list, select the connection profile.
4. To add or remove the associated host, click
.
The Select Hosts window is displayed.
5. In the Select Hosts window, select the hosts and click YES.
NOTE: Only the hosts that are not managed by OMIVV are displayed in the Select Hosts window.
OMIVV tests the connection automatically, and the hosts are displayed in the Add OEM Hosts window.
The Credentials to Test column displays the test connection result for iDRAC Credentials and Host Credentials.
● —Indicates that the test connection is successful.
●
—Indicates that the test connection is failed.
132
About host, bare-metal, and iDRAC compliance