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
32 ESXi deployment using Dell EMC OpenManage Integration for VMware vCenter (OMIVV) and deployment best
practices
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
OMIVV recommends update the ESXi credentials at host credential profile to ensure inventory is run
successfully after ESXi deployment, if password is not entered in host credential profile, the password that is
entered in deployment wizard is used.
4.30 After performing an ESXi deployment, existing iDRAC jobs are not in
seen
OMIVV clears all iDRAC jobs once ESXi deployment is completed on bare-metal servers.
4.31 After performing upgrade to latest version, scheduled ESXi
deployment job fails
Scheduled ESXi deployment jobs of older version of OMIVV are not valid for latest version of OMIVV. When
user is using latest version of OMIVV, it is recommended to cancel the scheduled job (which was created in
older version) and rediscover the bare-metal server followed by ISO profile creation and new deployment job.
4.32 Discovered user used during bare-metal discovery is disabled after
performing ESXi deployment
It is recommended to select the host credential profile whose credentials are same as used during bare-metal
discovery. Otherwise, the discovered user gets disabled in iDRAC after ESXi deployment as credentials used
in host credential profile is used during the same.
4.33 ESXi deployment is blocked when secure boot is enabled
ESXi deployment is blocked from iDRAC 4.00.00.00 to 4.32.20.00 when secure boot is enabled.
4.34 Deployment fails when other OS (RHEL or WINDOWS) is previously
installed
OMIVV deploys an OS on bare-metal servers. If any other hypervisor is already installed, deployment might
fail. Remove OS by deleting virtual disk and recreate it.