Users Guide
Table Of Contents
- OpenManage Integration for VMware vCenter Version 4.2 Web Client User's Guide
- Introduction
- About Administration Console
- Using Administration Portal
- Registering vCenter Server by nonadministrator user
- Registering 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 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 EMC icon is not displayed after unregistering vCenter from earlier OMIVV version and then registering same vCenter with later OMIVV version
- 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
- Bare-metal deployment issues
- Frequently Asked Questions-FAQ
- Related Documentation
- System specific attributes
- Customization attributes
- Additional information
- Component vs. baseline version comparison matrix
Deleting hypervisor profile
NOTE: Deleting a hypervisor profile that is part of a running deployment task can cause the task to fail.
1. In OpenManage Integration for VMware vCenter, on the Manage > Deployment tab, select Deployment Templates >
Hypervisor Profiles.
2. Select a profile, and click
.
3. In the confirmation dialog box, to remove the profile, click Delete, or to cancel, click Cancel.
Creating deployment templates
A deployment template contains a system profile, hardware profile, hypervisor profile, a combination of system profile and
hypervisor profile, or a combination of the hardware profile and hypervisor profile. The Deployment Wizard uses this template
to provision server hardware and deploy hosts within vCenter.
1. In OpenManage Integration for VMware vCenter, on the Manage > Deployment tab, select Deployment Templates.
2. Click .
3. In the Deployment Template dialog box, enter a name for the template.
4. Enter Description for the deployment template, which is optional.
5. Click System Profile or Hardware Profile and select the appropriate profile from the drop-down menu.
NOTE: It is recommended to use system profile for 14th generation servers and hardware profile for 13th generation and
earlier servers.
6. Select a Hypervisor Profile from the drop-down menu.
7. To apply profile selections and save changes, click Save. To cancel, click Cancel.
Managing deployment templates
From the OpenManage Integration, there are several management actions you can perform on existing deployment templates,
including:
● Viewing or editing deployment templates
● Deleting deployment templates
Viewing or editing deployment templates
1. In OpenManage Integration for VMware vCenter, on the Manage > Deployment tab, select Deployment Templates.
The deployment template profiles are displayed.
2. In the Deployment Template dialog box, type the new name of the template and description.
Ensure that the template has a unique name.
3. Change the Hardware Profile or System Profile from the drop-down menu.
4. Change the Hypervisor Profile from the drop-down menu and click Save.
Deleting deployment templates
1. In OpenManage Integration for VMware vCenter, on the Manage > Deployment tab, select Deployment Templates.
2. In the Deployment Template page, select a template, and click
.
3. To confirm the template deletion, click Delete on the message box, or to cancel, click Cancel.
About deployment wizard
The deployment wizard describes the deployment process, which is as follows:
116
Deploying hypervisor