Users Guide
Table Of Contents
- Integrated Dell Remote Access Controller 9 (iDRAC9) Version 3.00.00.00 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 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
- Updating device firmware using RACADM
- Scheduling automatic firmware updates
- 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 (SCP) — Import and Export
- Secure Boot Configuration from BIOS Settings (F2)
- Configuring iDRAC
- Viewing iDRAC information
- Modifying network settings
- 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
- 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
- Supported SSH cryptography schemes
- Communicating with iDRAC through serial connection using DB9 cable
- Configuring user accounts 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
- Configuring iDRAC smart card login for local users
- Configuring iDRAC smart card login for Active Directory users
- Enabling or disabling smart card 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 Flex Address and Persistence Policy behavior when iDRAC is set to Flex 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
- 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
Hardware and software RAID
RAID can be implemented with either hardware or software. A system using hardware RAID has a RAID controller that
implements the RAID levels and processes data reads and writes to the physical disks. When using software RAID provided
by the operating system, the operating system implements the RAID levels. For this reason, using software RAID by itself can
slow the system performance. You can, however, use software RAID along with hardware RAID volumes to provide better
performance and variety in the configuration of RAID volumes. For example, you can mirror a pair of hardware RAID 5 volumes
across two RAID controllers to provide RAID controller redundancy.
RAID concepts
RAID uses particular techniques for writing data to disks. These techniques enable RAID to provide data redundancy or better
performance. These techniques include:
● Mirroring — Duplicating data from one physical disk to another physical disk. Mirroring provides data redundancy by
maintaining two copies of the same data on different physical disks. If one of the disks in the mirror fails, the system can
continue to operate using the unaffected disk. Both sides of the mirror contain the same data always. Either side of the
mirror can act as the operational side. A mirrored RAID disk group is comparable in performance to a RAID 5 disk group in
read operations but faster in write operations.
● Striping — Disk striping writes data across all physical disks in a virtual disk. Each stripe consists of consecutive virtual
disk data addresses that are mapped in fixed-size units to each physical disk in the virtual disk using a sequential pattern.
For example, if the virtual disk includes five physical disks, the stripe writes data to physical disks one through five without
repeating any of the physical disks. The amount of space consumed by a stripe is the same on each physical disk. The portion
of a stripe that resides on a physical disk is a stripe element. Striping by itself does not provide data redundancy. Striping in
combination with parity does provide data redundancy.
● Stripe size — The total disk space consumed by a stripe not including a parity disk. For example, consider a stripe that
contains 64KB of disk space and has 16KB of data residing on each disk in the stripe. In this case, the stripe size is 64KB and
the stripe element size is 16KB.
● Stripe element — A stripe element is the portion of a stripe that resides on a single physical disk.
● Stripe element size — The amount of disk space consumed by a stripe element. For example, consider a stripe that contains
64KB of disk space and has 16KB of data residing on each disk in the stripe. In this case, the stripe element size is 16KB and
the stripe size is 64KB.
● Parity — Parity refers to redundant data that is maintained using an algorithm in combination with striping. When one of the
striped disks fails, the data can be reconstructed from the parity information using the algorithm.
● Span — A span is a RAID technique used to combine storage space from groups of physical disks into a RAID 10, 50, or 60
virtual disk.
RAID levels
Each RAID level uses some combination of mirroring, striping, and parity to provide data redundancy or improved read and write
performance. For specific information on each RAID level, see Choosing raid levels.
Organizing data storage for availability and performance
RAID provides different methods or RAID levels for organizing the disk storage. Some RAID levels maintain redundant data so
that you can restore data after a disk failure. Different RAID levels also entail an increase or decrease in the I/O (read and write)
performance of a system.
Maintaining redundant data requires the use of additional physical disks. The possibility of a disk failure increases with an
increase in the number of disks. Since the differences in I/O performance and redundancy, one RAID level may be more
appropriate than another based on the applications in the operating environment and the nature of the data being stored.
When choosing a RAID level, the following performance and cost considerations apply:
● Availability or fault-tolerance — Availability or fault-tolerance refers to the ability of a system to maintain operations
and provide access to data even when one of its components has failed. In RAID volumes, availability or fault-tolerance
is achieved by maintaining redundant data. Redundant data includes mirrors (duplicate data) and parity information
(reconstructing data using an algorithm).
● Performance — Read and write performance can be increased or decreased depending on the RAID level you choose. Some
RAID levels may be more appropriate for particular applications.
192
Managing storage devices