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
30 ESXi deployment using Dell EMC OpenManage Integration for VMware vCenter (OMIVV) and deployment best
practices
4.18 When NPAR is enabled on target node and disabled in System
Profile, ESXi deployment fails
An ESXi deployment fails when a system profile with a disabled NIC Partitioning (NPAR) is applied on a
target machine. Here, NPAR is enabled on the target node and only one of the partitioned NIC, except
partition 1 is selected as the NIC for the management tasks during the deployment process through the
deployment wizard.
To overcome this, ensure you are changing the NPAR status using system profile during deployment, ensure
that you select only the first partition for management network in the deployment wizard.
4.19 Sometimes MAC address is populated during ESXi deployment
An ESXi deployment fails on PowerEdge Servers when the iDRAC does not populate the MAC address for
the selected NIC port.
Update the respective NIC firmware and iDRAC firmware to the latest version and ensure that the MAC
address is populated on the NIC port.
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
After ESXi deployment, OMIVV queries vCenter to perform the host actions (Add host, Add Host Profile, or
Enter Maintenance Mode).
If the query does not receive a response within two minutes, the specific action on vCenter is timed out, and a
message is displayed in the task history indicating that the communication failure. However, at times, the
vCenter query operations are successful. Hence, manually adding host IP mentioned in VMware task history
works.
4.21 After performing ESXi deployment, host is either disconnected or not
responding state
ESXi host fails to send heartbeat packets to vCenter because its DNS is not properly configured to lookup
FQDN of the vCenter.
Complete the following tasks:
1. Remove the ESXi host from the vCenter inventory.
2. Add the host using the Add Host wizard in vCenter.
3. Create a host credential profile in OMIVV and run the inventory.
4.22 Deployment job times out when network interface card (NIC) of
OMIVV is not connected to the ESXi host network
An ESXi deployment has dependency on the selection of NIC. If the correct NIC is not selected, ESXi
deployment job times out.
In the Deployment wizard, select an appropriate Appliance NIC connected to Host from Configure Host
Settings. This is required to reach ESXi network during ESXi installation process
.
4.23 General failure
OMIVV uses WSMAN command Boot to Network ISO to deploy an ESXi on the target bare-metal servers.