Users Guide
Table Of Contents
- Integrated Dell Remote Access Controller 9 Version 3.31.31.31 User's Guide
- Overview
- Benefits of using iDRAC with Lifecycle Controller
- Key features
- New in this release
- How to use this guide
- Supported web browsers
- iDRAC licenses
- Licensed features in iDRAC9
- Interfaces and protocols to access iDRAC
- iDRAC port information
- Other documents you may need
- Contacting Dell
- Accessing documents from Dell support site
- Logging in to iDRAC
- Logging into iDRAC using OpenID Connect
- Logging in to iDRAC as local user, Active Directory user, or LDAP user
- Logging in to iDRAC as a local user using a smart card
- Logging in to iDRAC using Single Sign-On
- Accessing iDRAC using remote RACADM
- Accessing iDRAC using local RACADM
- Accessing iDRAC using firmware RACADM
- Viewing system health
- Logging in to iDRAC using public key authentication
- Multiple iDRAC sessions
- Accessing iDRAC using SMCLP
- Secure default password
- Changing the default login password
- Enabling or disabling default password warning message
- IP Blocking
- Enabling or disabling OS to iDRAC Pass-through using web interface
- Enabling or disabling alerts using RACADM
- Setting up managed system
- Setting up iDRAC IP address
- Modifying local administrator account settings
- Setting up managed system location
- Optimizing system performance and power consumption
- Setting up management station
- Configuring supported web browsers
- Configuring Internet Explorer
- Configuring Mozilla Firefox
- Configuring web browsers to use virtual console
- Viewing localized versions of web interface
- Updating device firmware
- Updating firmware using iDRAC web interface
- Scheduling automatic firmware updates
- Updating device firmware using RACADM
- Updating firmware using CMC web interface
- Updating firmware using DUP
- Updating firmware using remote RACADM
- Updating firmware using Lifecycle Controller Remote Services
- Updating CMC firmware from iDRAC
- Viewing and managing staged updates
- Rolling back device firmware
- Backing up server profile
- Importing server profile
- Monitoring iDRAC using other Systems Management tools
- Support Server Configuration Profile — Import and Export
- Secure Boot Configuration from BIOS Settings or F2
- BIOS recovery
- Configuring iDRAC
- Viewing iDRAC information
- Modifying network settings
- Cipher suite selection
- FIPS mode
- Configuring services
- Configuring TLS
- Using VNC client to manage remote server
- Configuring front panel display
- Configuring time zone and NTP
- Setting first boot device
- Enabling or disabling OS to iDRAC Pass-through
- Obtaining certificates
- Configuring multiple iDRACs using RACADM
- Disabling access to modify iDRAC configuration settings on host system
- Viewing iDRAC and managed system information
- Viewing managed system health and properties
- Configuring Asset Tracking
- Viewing system inventory
- Viewing sensor information
- Monitoring performance index of CPU, memory, and input output modules
- Checking the system for Fresh Air compliance
- Viewing historical temperature data
- Viewing network interfaces available on host OS
- Viewing network interfaces available on host OS using RACADM
- Viewing FlexAddress mezzanine card fabric connections
- Viewing or terminating iDRAC sessions
- Setting up iDRAC communication
- Communicating with iDRAC through serial connection using DB9 cable
- Configuring BIOS for serial connection
- Enabling RAC serial connection
- Enabling IPMI serial connection basic and terminal modes
- Switching between RAC serial and serial console while using DB9 cable
- Communicating with iDRAC using IPMI SOL
- Communicating with iDRAC using IPMI over LAN
- Enabling or disabling remote RACADM
- Disabling local RACADM
- Enabling IPMI on managed system
- Configuring Linux for serial console during boot in RHEL 6
- Configuring serial terminal in RHEL 7
- Supported SSH cryptography schemes
- Communicating with iDRAC through serial connection using DB9 cable
- Configuring user accounts and privileges
- iDRAC user roles and privileges
- Recommended characters in user names and passwords
- Configuring local users
- Configuring Active Directory users
- Prerequisites for using Active Directory authentication for iDRAC
- Supported Active Directory authentication mechanisms
- Standard schema Active Directory overview
- Configuring Standard schema Active Directory
- Extended schema Active Directory overview
- Configuring Extended schema Active Directory
- Extending Active Directory schema
- Installing Dell extension to the Active Directory users and computers snap-in
- Adding iDRAC users and privileges to Active Directory
- Configuring Active Directory with Extended schema using iDRAC web interface
- Configuring Active Directory with Extended schema using RACADM
- Testing Active Directory settings
- Configuring generic LDAP users
- System Lockdown mode
- Configuring iDRAC for Single Sign-On or smart card login
- Prerequisites for Active Directory Single Sign-On or smart card login
- Configuring iDRAC SSO login for Active Directory users
- Enabling or disabling smart card login
- Configuring Smart Card Login
- Using Smart Card to Login
- Configuring iDRAC to send alerts
- Enabling or disabling alerts
- Filtering alerts
- Setting event alerts
- Setting alert recurrence event
- Setting event actions
- Configuring email alert, SNMP trap, or IPMI trap settings
- Configuring WS Eventing
- Configuring Redfish Eventing
- Monitoring chassis events
- Alerts message IDs
- iDRAC 9 Group Manager
- Managing logs
- Monitoring and managing power
- Inventorying, monitoring, and configuring network devices
- Inventorying and monitoring network devices
- Inventorying and monitoring FC HBA devices
- Dynamic configuration of virtual addresses, initiator, and storage target settings
- Supported cards for IO Identity Optimization
- Supported NIC firmware versions for IO Identity Optimization
- Virtual or Remote assigned Address and Persistence Policy behavior when iDRAC is set to Remote-Assigned Address mode or Console mode
- System behavior for FlexAddress and IO Identity
- Enabling or disabling IO Identity Optimization
- Configuring persistence policy settings
- Managing storage devices
- Understanding RAID concepts
- Supported controllers
- Supported enclosures
- Summary of supported features for storage devices
- Inventorying and monitoring storage devices
- Viewing storage device topology
- Managing physical disks
- Managing virtual disks
- RAID Configuration Features
- Managing controllers
- Configuring controller properties
- Importing or auto importing foreign configuration
- Clearing foreign configuration
- Resetting controller configuration
- Switching the controller mode
- 12 Gbps SAS HBA adapter operations
- Monitoring predictive failure analysis on drives
- Controller operations in non-RAID mode or HBA mode
- Running RAID configuration jobs on multiple storage controllers
- Manage Preserved cache
- Managing PCIe SSDs
- Managing enclosures or backplanes
- Choosing operation mode to apply settings
- Viewing and applying pending operations
- Storage devices — apply operation scenarios
- Blinking or unblinking component LEDs
- BIOS Settings
- Configuring and using virtual console
- Supported screen resolutions and refresh rates
- Configuring virtual console
- Previewing virtual console
- Launching virtual console
- Using virtual console viewer
- HTML5 based virtual console
- Synchronizing mouse pointers
- Passing all keystrokes through virtual console for Java or ActiveX plug-in
- Using iDRAC Service Module
- Using USB port for server management
- Using Quick Sync 2
- Managing virtual media
- Installing and using VMCLI utility
- Managing vFlash SD card
- Configuring vFlash SD card
- Managing vFlash partitions
- Using SMCLP
- Deploying operating systems
- Troubleshooting managed system using iDRAC
- Using diagnostic console
- Viewing post codes
- Viewing boot and crash capture videos
- Viewing logs
- Viewing last system crash screen
- Viewing System status
- Hardware trouble indicators
- Viewing system health
- Checking server status screen for error messages
- Restarting iDRAC
- Erasing system and user data
- Resetting iDRAC to factory default settings
- SupportAssist Integration in iDRAC
- Frequently asked questions
- Use case scenarios
- Troubleshooting an inaccessible managed system
- Obtaining system information and assess system health
- Setting up alerts and configuring email alerts
- Viewing and exporting System Event Log and Lifecycle Log
- Interfaces to update iDRAC firmware
- Performing graceful shutdown
- Creating new administrator user account
- Launching servers remote console and mounting a USB drive
- Installing bare metal OS using attached virtual media and remote file share
- Managing rack density
- Installing new electronic license
- Applying IO Identity configuration settings for multiple network cards in single host system reboot
You can assign only 4K drives as hot spare to 4K virtual disks.
If you have assigned a physical disk as a dedicated hot spare in Add to Pending Operation mode, the pending operation is
created but a job is not created. Then, if you try to unassign the dedicated hot spare, the assign dedicated hot spare pending
operation is cleared.
If you have unassigned a physical disk as a dedicated hot spare in Add to Pending Operation mode, the pending operation is
created but a job is not created. Then, if you try to assign the dedicated hot spare, the unassign dedicated hot spare pending
operation is cleared.
NOTE: While the log export operation is in progress, you cannot view information about dedicated hot spares on the
Manage Virtual Disks page. After the log export operation is complete, reload or refresh the Manage Virtual Disks page
to view the information.
Rename VD
To change the name of a Virtual Disk, the user must have System Control privilege. The virtual disk name can contain
only alphanumeric characters, spaces, dashes and underscores. The maximum length of the name depends on the individual
controller. In most cases, the maximum length is 15 characters. The name cannot start with a space, end with a space, or be left
blank. Every time a virtual disk is renamed, an LC Log gets created.
Edit Disk capacity
Online Capacity Expansion (OCE) allows you to increase the storage capacity of selected RAID levels while the system remains
online. The controller redistributes the data on the array(called Reconfiguration), placing new space available at the end of each
RAID array.
Online Capacity Expansion (OCE) can be achieved in two ways:
● If free space is available on the smallest physical drive on the virtual disks group after starting LBA of Virtual disks, the
virtual disk´s capacity can be expanded within that free space. This option allows you to enter the new increased virtual disk
size. If disk group in a virtual disk has space available only before starting LBA, then Edit Disk Capacity in same disk group is
not permitted even though there is Available Space on a physical drive.
● A virtual disk's capacity can also be expanded by adding additional compatible physical disks to the existing virtual disk group.
This option does not allow you to enter the new increased virtual disk size. New increased virtual disk size is calculated and
displayed to the user based on the used disk space of existing physical disk group on a particular virtual disk, existing raid
level of the virtual disk and the number of new drives added to the virtual disk.
Capacity Expansion allows user to specify the final VD size. Internally final VD size is conveyed to PERC in percentage (this
percentage is the space user would like to use from empty space left in the array for the local disk to expand). Because of this
percentage logic final VD size after reconfiguration completes may be different from what user provided for scenario where user
is not giving maximum VD size possible as the final VD size (percentage turns out to be less than 100%). User does not see
difference in this entered VD size and final VD size after reconfiguration, if maximum possible VD size is entered by user.
Raid Level Migration
RAID Level Migration (RLM) refers to changing a virtual disk´s RAID level. iDRAC9 provides an option to increase the VD size
using RLM. In a way, RLM allows migrating the RAID level of a virtual disk which in turn may increase the size of virtual disk.
RAID level migration is the process of converting a VD with one RAID Level to another. When you migrate a VD to a different
Raid Level, the user data on it is redistributed to the format of the new configuration.
This configuration is supported by both staged and realtime.
The below table describes possible reconfigurable VD layouts while reconfiguring (RLM) a VD with addition of disks and without
addition of disks.
Table 54. Possible VD Layout
Source VD Layout Possible target VD Layout with Disk
Add
Possible target VD Layout Without
disk addition
R0 (single disk) R1 NA
R0 R5/R6 NA
Managing storage devices 225