OMIVV allows 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 PowerEdge servers by using VMware
vCenter without using PXE.
NOTE It is recommended to use system profile for 14th generation 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. OMIVV supports
deployment by using only embedded or integrated LOMs.
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 allows 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 off the system and then turn-on the system—hard reboot.
Click to order the Dell EMC servers with auto discovery and handshake options 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 disk 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 disk 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 navigating 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 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 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 generation 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 point to OMIVV.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\