Users Guide

Manage deployment profiles

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 you create or edit 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 inventory is successful for each reference host that is managed by 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 you create the system profile, it is recommended that you configure the reference server attribute and value as required.

Apply reference attribute and value to all the required target hosts.

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. Apply these system profiles

across the chassis for the corresponding slots only.

NOTE: A system profile does not support enabling and disabling of boot options.

NOTE:

● While using the system profile, exporting a system profile with Enterprise license and importing the same system profile

on servers with Express license fails.

● You cannot import system profile by using the Express license of iDRAC9 firmware 3.00.00.00. You must have an

Enterprise license.

Create system profile

It is recommended that you use Google Chrome to create or edit System Profile.

The PowerEdge R6515, R7515, R65125, R7525, and C6515 servers which has HBA, BOSS, and PERC connected using slimline

cable. System Profile created in OMIVV with iDRAC version earlier than 4.30.30.30 cannot be used for iDRAC 4.30.30.30 and

later versions. Create new system profile with iDRAC 4.30.30.30 or later and use it when required.

Manage deployment profiles 57