Users Guide

NOTE: You can perform the Quick Deploy action only if the Action When Server is Inserted option in the Deploy
iDRAC page is set to Server Prole or Quick Deploy then Server Prole. Selecting this option allows you to apply the
server prole assigned when a new server is inserted in the chassis.
2. From the drop-down menu, select the prole to assign to the required slot. You can select proles to apply to multiple slots.
3. Click Assign Prole.
The prole gets applied to the selected slots.
NOTE: When the FM120x4 sled is inserted, the stored prole assigned to the server slot is applied to all the four servers.
NOTE:
A slot that does not have any prole assigned to it is indicated by the term "No Prole Selected" that appears in the select
box.
To remove a prole assignment from one or more slots, select the slots and click Remove Assignment. A message is
displayed warning you that removing a prole from the slot or slots removes the XML conguration settings in the prole
from any servers inserted in the slots when Quick Deploy Proles feature is enabled. Click OK to remove the prole
assignments.
To remove all prole assignments from a slot, in the drop-down menu, select No Prole Selected.
NOTE: When a prole is deployed to a server using the Quick Deploy Prole feature, the progress and results of the
application are retained in the Prole Log.
NOTE:
The Network Share option is enabled and the details are displayed in the Stored Proles section only if the network share is
mounted and is accessible. If the Network Share is not connected, congure the Network Share for the chassis. To congure
the Network Share, click Edit in the Stored Proles section. For more information, see Conguring Network Share Using CMC
Web Interface.
Boot Identity Proles
To access the Boot Identity Proles page in the CMC web interface, in the system tree, go to Chassis OverviewServer
Overview
. Click SetupProles. The Server Proles page is displayed. On the Server Proles page, click Boot Identity Proles.
The boot identity proles contain the NIC or FC settings that are required to boot a server from a SAN target device and unique
virtual MAC and WWN. As these are available across multiple chassis through a CIFS or NFS share, you can quickly and remotely
move an identity from a non-functional server in a chassis to a spare server located in the same or another chassis and thus enabling
it to boot with the operating system and applications of the failed server. The main advantage of this feature is the use of a virtual
MAC address pool that is unique and shared across all chassis.
This feature allows you to manage server operations online without physical intervention if the server stops functioning. You can
perform the following tasks by using the Boot Identity Proles feature:
Initial setup
Create a range of virtual MAC addresses. To create a MAC address, you must have Chassis Conguration Administrator and
Server Administrator privileges.
Save boot identity prole templates and customize the boot identity proles on the network share by editing and including
the SAN boot parameters that are used by each server.
Prepare the servers that use initial conguration before applying their Boot Identity proles.
Apply Boot Identity proles to each server and boot them from SAN.
Congure one or more spare standby servers for quick recovery.
Prepare the standby servers that use initial conguration before applying their Boot Identity proles.
Use the workload of a failed server in a new server by performing the following tasks:
Clear the boot identity from the non-functioning server to avoid duplicating the MAC addresses in case the server recovers.
Apply the boot identity of a failed server to a spare standby server.
85