Users Guide

2. In the Deployment Template page, select a template, and click the icon.
3. To confirm the template deletion, click Delete on the message box, or to cancel, click Cancel.
About deployment wizard
The deployment wizard describes the deployment process, which is as follows:
• Selecting compliant bare-metal servers.
NOTE: If you select the 4th generation servers for deployment, the deployment template list includes a hardware
profile or system profile or hypervisor profile or combination of hardware and hypervisor or combination of system
and hypervisor profiles.
NOTE: If you select non-14th generation servers or a combination of 14th generation and non-14th generation
servers, the deployment template list includes a hardware profile or hypervisor profile, or a combination of hardware
profile and hypervisor profiles.
• Selecting a deployment template, which consists of hardware and hypervisor profiles.
• Selecting the installation target (hard disk or iDSDM).
When you deploy hypervisor, you can deploy to an Internal Dual SD Module. The Internal Dual SD Module should be enabled from
BIOS, before you deploy a hypervisor with OMIVV.
• Selecting the connection profile to be associated with the host.
• Assigning the network details for each host.
• Selecting the vCenter, destination data center or cluster, and an optional host profile.
• Scheduling the server deployment jobs to run.
NOTE:
If you are deploying a hardware profile only, then the Server Identification, Connection Profile, network detail
options of the deployment wizard are skipped and you directly go to the Schedule Deployment page.
NOTE: For trial/evaluation license, you can use deployment wizard as long as the license does not expire.
VLAN support
OMIVV supports hypervisor deployment to a routable VLAN and you can configure VLAN support in the Deployment Wizard. In this
portion of the Deployment Wizard, there is an option to specify use of VLANs and to specify a VLAN ID. When a VLAN ID is provided, it is
applied to the hypervisor's management interface during deployment and tags all traffic with the VLAN ID.
Ensure that the VLAN provided during deployment communicates with both the virtual appliance and the vCenter server. The deployment
of a hypervisor to a VLAN that cannot communicate to one or both of these destinations causes the deployment to fail.
If you have selected multiple bare-metal servers in a single deployment job and want to apply the same VLAN ID to all servers, in the
server identification portion of the Deployment Wizard, use Apply settings to all selected servers. This option enables you to apply the
same VLAN ID along with the other network settings to all the servers in that deployment job.
NOTE:
OMIVV does not support a multihomed configuration. Adding a second network interface to the appliance for
communication with a second network causes problems for the workflow involving hypervisor deployment, server
compliance, and firmware updates.
100 Deploying hypervisor