White Papers
Table Of Contents
- 1
- 1
- 1
- 1 Introduction
- 2 Bare-metal discovery
- 1
- 1
- 1
- 1
- 1
- 3 Create an ISO Profile
- 4 Best practices for OS deployment
- 4.1 Customized ISO images
- 4.2 Lifecycle Controller busy
- 1.1
- 4.3 Disconnected network interfaces
- 4.4 First boot disk selection
- 4.5 Correct boot sequence
- 4.6 Boot sequence enablement
- 4.7 Virtual Disk should be created for controller (PERC or BOSS)
- 4.8 In Multi-NIC environment, selection of right OMIVV network selection is important
- 4.9 OMIVV does not support software controller
- 1.1
- 4.10 Ensure while providing static network details, valid network details are entered
- 4.11 Minimum requirements for ESXi installation
- 4.12 vCenter license for adding host to vCenter after deployment
- 4.13 OMIVV does not support installation of ESXi on virtual machine
- 4.14 Ensure that OMIVV license for host is available
- 4.15 ESXi password requirements
- 4.16 Port information for ESXi installation
- 1.1
- 1.1
- 4.17 ESXi deployment failure
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 4.18 When NPAR is enabled on target node and disabled in System Profile, ESXi deployment fails
- 1.1
- 4.19 Sometimes MAC address is populated during ESXi deployment
- 1.1
- 1.1
- 4.20 After ESXi deployment, OMIVV fails to add ESXi host to vCenter or failed to add host profile or enter maintenance mode is failed for host
- 1.1
- 4.21 After performing ESXi deployment, host is either disconnected or not responding state
- 1.1
- 1.1
- 1.1
- 4.22 Deployment job times out when network interface card (NIC) of OMIVV is not connected to the ESXi host network
- 1.1
- 1.1
- 4.23 General failure
- 1.1
- 4.24 Inaccessible network shares (OSD47, OSD17)
- 1.1
- 4.25 Auto discovered systems are displayed without model information in Deployment wizard
- 4.26 Server pending reboot
- 4.27 Boot order is not guaranteed in UEFI mode
- 4.28 Host credential profile having AD credentials are not listed in deployment page
- 4.29 Even though ESXi deployment is successful, inventory fails when selected ISO profile has ESXi 6.5 (or earlier version) image and host credential profile have different or no ESXi password other than which is set in deployment wizard
- 4.30 After performing an ESXi deployment, existing iDRAC jobs are not in seen
- 4.31 After performing upgrade to latest version, scheduled ESXi deployment job fails
- 1.1
- 4.32 Discovered user used during bare-metal discovery is disabled after performing ESXi deployment
- 4.33 ESXi deployment is blocked when secure boot is enabled
- 4.34 Deployment fails when other OS (RHEL or WINDOWS) is previously installed
- 5 Conclusion
28 ESXi deployment using Dell EMC OpenManage Integration for VMware vCenter (OMIVV) and deployment best
practices
4.9 OMIVV does not support software controller
Onboard SATA controller for Dell EMC PowerEdge servers provides an option to create RAID. The software
RAID LUNs are not supported because VMware ESXi does not carry supported drivers. ESXi does not
support any software RAID functions. Due to this, OMIVV does not support ISO deployment on software
controller.
For more information, see VMware vSphere 6 on Dell EMC PowerEdge Servers Release Notes
4.10 Ensure while providing static network details, valid network details
are entered
OMIVV provides an option for user to enter static network details for ESXi. During which a fully qualified
domain name for the hostname is mandatory. The use of “ localhost “ for the FQDN is not supported. The
FQDN is used when adding the host to vCenter.
Create a DNS record that resolves the IP address with the FQDN. Configure the DNS server to support
reverse lookup requests. The DHCP reservations and DNS host names must be in place and verified before
the deployment job is scheduled to run. It is mandatory to enter preferred DNS server, alternate DNS server,
IP address, subnet mask, and default gateway.
4.11 Minimum requirements for ESXi installation
Following are the minimum requirements for ESXi installation:
• A host machine with at least two CPU cores
• A minimum of 4 GB of physical RAM. Provide at least 8 GB of RAM to run virtual machines in typical
production environments.
• A boot disk of at least 8 GB for USB or SD devices, and 32 GB for other device types such as HDD,
SSD, or NVMe. A boot device must not be shared between ESXi hosts.
• Virtualization Technology (VT) flag in BIOS is enabled.
• OMIVV System profiles can be included in deployment profiles to prepare system for OS deployment.
Configurations like boot settings and virtual disk configurations along with other settings can be
performed using system profiles deployment. For more information about system profile deployment,
see OMIVV User’s Guide
.
Note: The OS deployment is blocked from iDRAC firmware version 4.00.00.00 to 4.32.20.00 when secure
boot is enabled.
For more information about installing ESXi, see the following documents:
https://docs.vmware.com/en/VMware-vSphere/7.0/vsphere-esxi-70-installation-setup-guide.pdf
https://docs.vmware.com/en/VMware-vSphere/6.7/vsphere-esxi-67-installation-setup-guide.pdf
https://docs.vmware.com/en/VMware-vSphere/6.5/vsphere-esxi-vcenter-server-65-installation-setup-guide.pdf