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
Deploying hypervisor
OMIVV enables you to configure the following components in the supported bare-metal servers along with deploying the
hypervisor and adding it to the specified data center and cluster in a vCenter:
● Boot order setting
●
RAID configuration
● BIOS configuration
● iDRAC configuration
You can create hardware profiles, System profiles, and hypervisor profiles on the bare-metal servers using VMware vCenter
without using PXE.
NOTE: Dell EMC recommends using system profile for 14th Gen and later servers when deploying hypervisor.
To provision hardware and perform deployment, ensure that the physical servers are displayed in the Deployment Wizard.
Ensure that all physical servers are as per the following requirements:
● Meet specific hardware support information that is available in the OpenManage Integration for VMware vCenter
Compatibility Matrix.
● Meet minimum supported versions of the iDRAC firmware, Lifecycle Controller, and BIOS. See the OpenManage Integration
for VMware vCenter Compatibility Matrix for specific firmware support information.
● Configure NICs in PCI slots manually after the deployment. If you are using add-on NICs, the system must have the host LAN
on Motherboard (LOMs) or Network Daughter Card (NDC) enabled and connected to network.
● Meet the storage specifications of IDSDM. To know about the storage specifications of IDSDM, see the VMware
Documentation. Ensure that you enable the IDSDM from BIOS before you deploy the hypervisor with OMIVV. OMIVV enables
deployment on IDSDM or local hard drives.
● Ensure that there is a route between the vCenter and the iDRAC networks if vCenter and iDRAC are connected to different
networks.
● Ensure that Collect System Inventory on Reboot (CSIOR) is enabled. Also, before initiating auto/manual discovery, ensure
that retrieved data is current by completely powering down the system and then turn-on the system—hard reboot.
● Click to order the Dell EMC servers with auto discovery and handshake options that are preconfigured by the factory. If
a server is not preconfigured with these options, manually enter the OMIVV IP address or configure your local network to
provide this information.
● Ensure that the following conditions are met before initiating hypervisor deployment if OMIVV is not used for hardware
configuration:
○ Enable the Virtualization Technology (VT) flag in BIOS.
○ Set the system's boot order to either a bootable virtual drive or IDSDM for operating system installation.
● Verify that the BIOS setting for VT is automatically enabled even if the BIOS configuration is not part of the hardware
profile, if OMIVV is used for hardware configuration. The Express/Clone RAID configuration is required if a virtual drive is not
already present on the target system.
●
Ensure that the custom ESXi images that contain all the Dell drivers are available for deployment. You can find the correct
images from Support.dell.com by going to to the Dell Drivers & Downloads page, and saving the custom images to
a CIFS or NFS share location that OMIVV can access during the deployment process. For up-to-date list of supported ESXi
versions for this release, see OpenManage Integration for VMware vCenter Compatibility Matrix. To use the correct images,
see the Downloading custom Dell ISO images.
● Ensure that you have BIOS mode that is selected in the reference hardware profile before applying the hypervisor profile
as OMIVV only supports BIOS mode to autodeploy hypervisor on the target server. If there is no hardware profile that is
selected, ensure that you manually configure the boot mode as BIOS and reboot the server before applying the hypervisor
profile.
If servers are from versions earlier than PowerEdge 12th Gen servers, the deployment process performs the following tasks:
● Installs the OMSA package on the target system.
● Automatically configures the SNMP trap destination in OMSA to hover over OMIVV.
Topics:
• Device discovery
• Provisioning
13
110 Deploying hypervisor