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
31 ESXi deployment using Dell EMC OpenManage Integration for VMware vCenter (OMIVV) and deployment best
practices
If the WSMAN command fails and gives OSD2 (general failure or an unknown error occurred), reset iDRAC
and rerun the command.
For more information, see Event and Error Message Reference Guide
.
4.24 Inaccessible network shares (OSD47, OSD17)
iDRAC consumes network share of OMIVV /nfsstage to mount the ISO images. But if nfs daemon is not
running with the required ports (2049, 4001–4004) in OMIVV, mount operation may fail. Firewall might be
enabled and is preventing access to the share. You must ensure that the firewall is disabled, and nfs daemon
is listening on the correct ports.
This issue occurs if the network share (where the ESXi ISO image is present) is corrupted. Retry after
creating a new CIFS or NFS share and associate with a new ISO profile.
Error codes (OSD17, OSD47) indicates network errors which prevents iDRAC access to the ISO file.
4.25 Auto discovered systems are displayed without model information in
Deployment wizard
This usually indicates that the firmware version that is installed on the system does not meet the
recommended minimum requirements. Sometimes, firmware version is not reflected even after updating the
iDRAC or any firmware to the minimum requirements. This can be resolved by performing cold booting the
system or resetting server or iDRAC.
The newly enabled account on the iDRAC must be disabled and auto discovery should be reinitiated to
provide model information and NIC information to OMIVV.
4.26 Server pending reboot
Sometimes, firmware update is scheduled on the server and the update is reflected on the server after reboot.
The reboot does not happen immediately. ESXi deployment job may fail if the server is pending for reboot.
User can reboot the server and then reschedule or rerun the job.
4.27 Boot order is not guaranteed in UEFI mode
In the UEFI mode, boot sequence option behaves in a different way. The newly created boot label is
appended (queued) rather than stacked. Even when an ESXi installation is completed, server boots to first
boot label. If any other bootable device is available, it boots to that image rather than newly installed image.
OMIVV supports only bare-metal server where nothing is preinstalled in UEFI mode.
4.28 Host credential profile having AD credentials are not listed in
deployment page
OMIVV does not consider AD credentials during an ESXi deployment. OMIVV does not display any host
credential profile in case AD credentials are used for iDRAC or ESXi.