Users Guide

deployment jobs running simultaneously. The deployment jobs are run in batches of up to five concurrent servers to improve time for the
overall deployment job. The exact number of concurrent jobs depends on available resources.
The following table displays the average value, and may vary based on factors like configuration of the server, generation of the server,
and number of bare metal servers scheduled for deployment:
Table 3. Approximate deployment time for a single server
Deployment type Approximate time per deployment
ISO profile only Between 30–130
System profile only 5–6 minutes
System profile and ISO profile 30–60 minutes
Server status within deployment sequence
The servers that are discovered during auto discovery or manually are classified in different states to help determine if the server is new to
the data center or has a pending deployment job scheduled. The administrators can use these statuses to check the hardware
configuration status.
Table 4. Server states in the deployment sequence
Server state Description
Unconfigured The server is added to OMIVV and is waiting to be configured.
Configured The server is configured with all hardware information that is
required for a successful operating system deployment.
System profile
The system profile captures the component-level settings and configuration of iDRAC, BIOS, RAID, Event Filters, FC, and NICs. These
configurations can be applied to other identical servers during an operating system deployment on bare-metal servers. The system profile
can be used in cluster profile to maintain baseline for configuration.
Prerequisites
Before creating or editing the system profile, ensure that:
• The CSIOR feature is enabled on the reference server. The reference server must be restarted after enabling CSIOR so that the data
returned from iDRAC is up to date.
• The OMIVV has performed a successful inventory operation for each reference host that is managed by the vCenter.
• Bare-metal servers have the minimum required BIOS and firmware versions installed. For more information, see the OMIVV
Compatibility Matrix available on the support site.
• The reference server and target servers are homogeneous (same model, same hardware configuration, and same firmware level).
• The hardware (for example, FC, NIC, and RAID controller) is present in the identical slots of the reference server and target servers.
• Before you include or exclude any attribute from the default selection, hover over attribute name to understand the details of the
attribute.
• The iDRAC user that is used to discover the iDRAC is selected when you configure the iDRAC users in system profile.
NOTE:
Do not clear the attributes that are linked with the iDRAC user that is used to discover the bare-metal, else
system profile deployment job fails.
• You do not change the username of iDRAC user that is used to discover the iDRAC. This results in connectivity issue with iDRAC, the
system profile deployment job fails without applying any attributes.
Before creating the system profile, it is recommended that you configure the reference server attribute and value as required, and then
apply it to all the required target servers.
The system profiles search for an exact instance (FQDD) while applying the profile, which works successfully on rack servers (identical),
but may have few restrictions in modular servers. For example, in FC640, the system profiles that are created from one modular server
cannot be applied on other modular servers in the same FX chassis because of NIC level restrictions. In this case, it is recommended that
you have a reference system profile from each slot of the chassis and applies these system profiles across the chassis for the
corresponding slots only.
NOTE: A system profile does not support enabling and disabling of boot options.
54 Deployment