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
8 ESXi deployment using Dell EMC OpenManage Integration for VMware vCenter (OMIVV) and deployment best
practices
2 Bare-metal discovery
Discovery is the process of adding supported bare-metal server. After a server is discovered, you can use it for
system profile and an ISO profile deployment.
Prerequisites:
• The network connectivity from the iDRAC of bare-metal server to the OMIVV virtual machine is
required.
• The hosts with existing ESXi instances should not be discovered into OMIVV. Add hosts to the
vCenter and host credential profile.
• To deploy ESXi on SD card and to use system profile features in 12G and 13G PowerEdge servers,
ensure that iDRAC 2.50.50.50 and later is installed.
OMIVV supports discovering bare-metal servers using auto discovery and manual discovery.
2.1 Auto discovery
Auto discovery is an iDRAC feature that enables newly installed servers to be discovered automatically by
OMIVV. Remote management console IP address must be configured.
Prerequisites:
Before attempting to discover the PowerEdge bare-metal servers, ensure that OMIVV is installed. The
PowerEdge servers with iDRAC Express or iDRAC Enterprise can be discovered into a pool of bare-metal
servers.
For auto discovery to function, the following conditions must be met in your environment:
• Power—ensure that you connect the server to the power outlet.
• Network connectivity—ensure that the iDRAC of the server has network connectivity and communicates
with the provisioning server over port 4433. You can obtain the IP address of provisioning server by using
a DHCP server or manually specifying it in the iDRAC configuration utility.
• Extra network settings—To resolve DNS names, enable Get DNS server address in DHCP settings.
• Provisioning service location—ensure that iDRAC knows the IP address or hostname of the provisioning
service server. OMIVV supports auto discovery with provisioning server functions only.
Note: iDRAC9 auto discovery and iDRAC9 push notifications are not supported.
For more information, see the OMIVV User’s Guide.
• Account access disabled—if there are any iDRAC accounts with administrator privileges, first disable
them from the iDRAC web console. Once auto discovery completes successfully, the administrative
iDRAC account is reenabled with deployment credentials that are entered on the Settings page. For more
information about deployment credentials, see the OMIVV User’s Guide
.
• Auto discovery enabled—ensure that the iDRAC of the server has auto discovery enabled so that the
auto discovery process can begin. For more information, see the OMIVV User’s Guide
.
2.2 Manual discovery of bare-metal servers
You can manually add a bare-metal server that is not added using the auto discovery process. Once added,
the server is displayed in the list of servers on the Bare-metal Servers page of OMIVV.
To add the bare-metal servers, on the OMIVV home page, click Compliance and Deployment >
Deployment > DISCOVER.
You can create the discovery job to discover range of servers simultaneously. You can configure maximum of
1024 servers in a single discovery job.
Class C IPs are supported and difference in last octet values of start, and end IP are considered to find range
of IPs between them. You can configure a maximum of 1024 nodes in a single discovery.