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
29 ESXi deployment using Dell EMC OpenManage Integration for VMware vCenter (OMIVV) and deployment best
practices
4.12 vCenter license for adding host to vCenter after deployment
OMIVV installs ESXi on the required bare-metal server and adds the same to registered vCenter. While
performing the addition of host to vCenter, vCenter should have valid license so that host gets added
successfully.
4.13 OMIVV does not support installation of ESXi on virtual machine
OMIVV supports ESXi installation only on OMIVV supported servers. For more information about supported
servers, see OMIVV 5.2 compatibility Matrix
.
4.14 Ensure that OMIVV license for host is available
During deployment, once ESXi installation is successful, host gets added to vCenter and to the previously
selected host credential profile. While adding to host credential profile, OMIVV license is consumed. Hence,
user must ensure that enough OMIVV license is available.
4.15 ESXi password requirements
By default, you have to include a mix of characters from four-character classes: lowercase letters, uppercase
letters, numbers, and special characters such as underscore or dash when you create a password. By
default, password length is more than 7 and less than 40. Passwords cannot contain a dictionary word or part
of a dictionary word.
4.16 Port information for ESXi installation
Minimum port requirements for OMIVV appliance and managed nodes are mentioned in OMIVV compatibility
matrix.
4.17 ESXi deployment failure
Whenever ESXi deployment fails, ensure that:
• The ISO location (NFS path) and staging folder paths are accurate.
• The NIC selected during assignment of server identity is accessible by the virtual appliance.
• You select the management NICs based on the network connectivity to the OMIVV.
• The network information provided (including subnet mask and Default Gateway) is accurate if you are
using static IP address. Also, ensure that the IP address is not already assigned on the network.
• At least one Virtual Disk, or IDSDM, or BOSS is detected by the system.