Integrated Dell Remote Access Controller 8 (iDRAC8) Version 2.00.00.
Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2014 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Overview...............................................................................................................16 Benefits of Using iDRAC With Lifecycle Controller............................................................................16 Key Features......................................................................................................................................... 17 New In This Release...............................................................................
Enabling or Disabling Default Password Warning Message Using Web Interface...................... 41 Enabling or Disabling Warning Message to Change Default Login Password Using RACADM.........................................................................................................................................41 3 Setting Up Managed System and Management Station..............................42 Setting Up iDRAC IP Address..............................................................................
Backing Up Server Profile Using iDRAC Web Interface............................................................... 76 Backing Up Server Profile Using RACADM................................................................................... 77 Scheduling Automatic Backup Server Profile............................................................................... 77 Importing Server Profile......................................................................................................................
Enabling or Disabling OS to iDRAC Pass-through Using iDRAC Settings Utility........................ 97 Obtaining Certificates......................................................................................................................... 97 SSL Server Certificates.................................................................................................................. 98 Generating a New Certificate Signing Request............................................................................
Switching From Serial Console to RAC Serial............................................................................ 123 Switching From RAC Serial to Serial Console............................................................................ 123 Communicating With iDRAC Using IPMI SOL..................................................................................123 Configuring BIOS For Serial Connection....................................................................................
Configuring Browser to Enable Active Directory SSO............................................................... 167 Configuring iDRAC SSO Login for Active Directory Users.............................................................. 168 Configuring iDRAC SSO Login for Active Directory Users Using Web Interface......................168 Configuring iDRAC SSO Login for Active Directory Users Using RACADM..............................168 Configuring iDRAC Smart Card Login for Local Users......................
Viewing Lifecycle Log Using Web Interface...............................................................................186 Viewing Lifecycle Log Using RACADM.......................................................................................186 Exporting Lifecycle Controller Logs.................................................................................................186 Exporting Lifecycle Controller Logs Using Web Interface........................................................
13 Managing Storage Devices........................................................................... 203 Understanding RAID Concepts........................................................................................................ 204 What Is RAID?..............................................................................................................................205 Organizing Data Storage For Availability And Performance.....................................................
Preparing to Remove PCIe SSD.................................................................................................. 237 Erasing PCIe SSD Device Data....................................................................................................238 Managing Enclosures or Backplanes............................................................................................... 239 Configuring Backplane Mode..........................................................................................
15 Managing Virtual Media.................................................................................261 Supported Drives and Devices......................................................................................................... 262 Configuring Virtual Media.................................................................................................................262 Configuring Virtual Media Using iDRAC Web Interface.............................................................
18 Using SMCLP................................................................................................... 283 System Management Capabilities Using SMCLP............................................................................. 283 Running SMCLP Commands............................................................................................................ 283 iDRAC SMCLP Syntax.....................................................................................................................
Deploying Operating System Using Remote File Share..................................................................306 Managing Remote File Share......................................................................................................307 Configuring Remote File Share Using Web Interface............................................................... 308 Configuring Remote File Share Using RACADM........................................................................
Virtual Media......................................................................................................................................332 vFlash SD Card.................................................................................................................................. 334 SNMP Authentication........................................................................................................................335 Storage Devices......................................................
Overview 1 The Integrated Dell Remote Access Controller (iDRAC) is designed to make server administrators more productive and improve the overall availability of Dell servers. iDRAC alerts administrators to server issues, helps them perform remote server management, and reduces the need for physical access to the server. iDRAC with Lifecycle controller technology is part of a larger datacenter solution that helps keep business critical applications and workloads available at all times.
Remote Services (WS-Management) interfaces for remote deployment integrated with Dell OpenManage Essentials and partner consoles. For more information on Lifecycle Controller GUI, see Lifecycle Controller User’s Guide and for remote services, see Lifecycle Controller Remote Services User’s Guide available at dell.com/support/manuals. Key Features The key features in iDRAC include: NOTE: Some of the features are available only with iDRAC Enterprise license.
– Virtual disks: * Create virtual disks * Edit virtual disks cache policies * Check virtual disk consistency * Initialize virtual disks * Encrypt virtual disks * Assign or unassign dedicated hot spare * Delete virtual disks – Controllers: * Configure controller properties * Import or auto-import foreign configuration * Clear foreign configuration * Reset controller configuration * Create or change security keys – PCIe SSD devices: * Inventory and remotely monitor the health of PCIe
• Use iDRAC Service Module to: – View Operating System (OS) information – Replicate Lifecycle Controller logs to operating system logs – Automatic system recovery options – Populate Windows Management Instrumentation (WMI) information – Integrate with Technical Support Report. This is applicable only if iDRAC Service Module Version 2.0 or later is installed. For more information, see Generating Tech Support Report. – Integrate with NVMe Management for Prepare to Remove operation on a NVMe class PCIe SSD.
• Update device firmware using TFTP or HTTP. • Out-of-band monitor and alert the performance index of CPU, memory, and I/O modules. • Configure warning threshold for inlet Temperature. • Configure persistence policy for virtual addresses, initiator, and storage targets. • View network interfaces available on host operating systems. • Enable SNMPv3 authentication for a user to receive SNMP traps. • Configure the SNMPv3 trap format. • Set the warning threshold for power consumption.
• • – Automatic — Using iDRAC Service Module that automatically invokes the OS Collector tool. – Manual — Using OS Collector tool Erase system and user data Six users can launch the Virtual Console at any point of time. How To Use This User's Guide The contents of this User's Guide enable you to perform the tasks by using: • • • iDRAC Web interface — Only the task-related information is provided here.
• E-mail — License is attached to an email that is sent after requesting it from the technical support center. • Self-service portal — A link to the Self-Service Portal is available from iDRAC. Click this link to open the licensing Self-Service Portal on the internet. Currently, you can use the License Self-Service Portal to retrieve licenses that were purchased with the server. You must contact the sales representative or technical support to buy a new or upgrade license.
For more information about this utility and to download this tool, click here. License Component State or Condition and Available Operations The following table provides the list of license operations available based on the license state or condition. Table 1.
Feature iDRAC8 Basic iDRAC8 Express iDRAC8 Express for Blades iDRAC8 Enterprise Web-based GUI Yes Yes Yes Yes Racadm command line (local/remote) Yes Yes Yes Yes SMASH-CLP (SSH-only) Yes Yes Yes Yes Telnet Yes Yes Yes Yes SSH Yes Yes Yes Yes WSMAN Yes Yes Yes Yes Network Time Protocol No Yes Yes Yes Shared NIC Yes Yes N/A Yes1 Dedicated NIC2 Yes Yes Yes Yes2 VLAN tagging Yes Yes Yes Yes IPv4 Yes Yes Yes Yes IPv6 Yes Yes Yes Yes DHCP Yes Yes Y
Feature iDRAC8 Basic iDRAC8 Express iDRAC8 Express for Blades iDRAC8 Enterprise Single sign-on No No No Yes PK authentication No Yes Yes Yes Power control Yes Yes Yes Yes Boot control Yes Yes Yes Yes Serial-over-LAN Yes Yes Yes Yes Virtual Media No No Yes Yes Virtual Folders No No No Yes Remote File Share No No No Yes Virtual Console No No Yes Yes VNC connection to OS No No No Yes Quality/bandwidth control No No No Yes Virtual Console collaboration
Feature iDRAC8 Basic iDRAC8 Express iDRAC8 Express for Blades iDRAC8 Enterprise Full agent-free monitoring Yes Yes Yes Yes Predictive failure monitoring Yes Yes Yes Yes SNMPv1, v2, and v3 (traps Yes and gets) Yes Yes Yes Email Alerting No Yes Yes Yes Configurable thresholds Yes Yes Yes Yes Fan monitoring Yes Yes Yes Yes Power Supply monitoring Yes Yes Yes Yes Memory monitoring Yes Yes Yes Yes CPU monitoring Yes Yes Yes Yes RAID monitoring Yes Yes Yes Yes N
Feature iDRAC8 Basic iDRAC8 Express iDRAC8 Express for Blades iDRAC8 Enterprise Embedded configuration tools Yes Yes Yes Yes Auto-Discovery No Yes Yes Yes Remote OS deployment No Yes Yes Yes Embedded driver pack Yes Yes Yes Yes Full configuration inventory Yes Yes Yes Yes Inventory export Yes Yes Yes Yes Remote configuration Yes Yes Yes Yes Zerotouch configuration No No No Yes System Retire/Repurpose Yes Yes Yes Yes Diagnostics, Service, and Logging Embedded
Feature iDRAC8 Basic iDRAC8 Express iDRAC8 Express for Blades iDRAC8 Enterprise Crash screen capture No Yes Yes Yes Crash video capture No No No Yes Boot capture No No No Yes Manual reset for iDRAC Yes Yes Yes Yes Virtual NMI Yes Yes Yes Yes OS watchdog Yes Yes Yes Yes Embedded Health Report Yes Yes Yes Yes System Event Log Yes Yes Yes Yes Lifecycle Log Yes Yes Yes Yes Work notes Yes Yes Yes Yes Remote Syslog No No No Yes License management Yes Yes
Interface or Protocol Description are encrypted using 128-bit SSL to provide privacy and integrity. Any connection to the HTTP port is redirected to HTTPS. Administrators can upload their own SSL certificate through an SSL CSR generation process to secure the Web server. The default HTTP and HTTPS ports can be changed. The user access is based on user privileges. RACADM Use this command line utility to perform iDRAC and server management. You can use RACADM locally and remotely.
Interface or Protocol Description Reference Guide available at dell.com/support/manuals. For details about SMCLP, see Using SMCLP. NOTE: Telnet is not a secure protocol and is disabled by default. Telnet transmits all data, including passwords in plain text. When transmitting sensitive information, use the SSH interface. SSH Use SSH to run RACADM and SMCLP commands. It provides the same capabilities as the Telnet console using an encrypted transport layer for higher security.
Interface or Protocol Description • DTMF Web site — dmtf.org/standards/profiles/ iDRAC Port Information The following ports are required to remotely access iDRAC through firewalls. These are the default ports iDRAC listens to for connections. Optionally, you can modify most of the ports. To do this, see Configuring Services. Table 3.
Port Number Function 445 Common Internet File System (CIFS) 636 LDAP Over SSL (LDAPS) 2049 Network File System (NFS) 123 Network Time Protocol (NTP) 3269 LDAPS for global catalog (GC) * Configurable port Other Documents You May Need In addition to this guide, the following documents available on the Dell Support website at dell.com/ support/manuals provides additional information about the setup and operation of iDRAC in your system.
• The Glossary provides information about the terms used in this document. The following system documents are available to provide more information: • The iDRAC Overview and Feature Guide provides information about iDRAC, its licensable features, and license upgrade options. • The safety instructions that came with your system provide important safety and regulatory information. For additional regulatory information, see the Regulatory Compliance home page at dell.com/regulatory_compliance.
– For Client Systems Management documents — dell.com/clientsystemsmanagement – For Serviceability Tools documents — dell.com/serviceabilitytools – For OpenManage Connections Enterprise Systems Management documents — dell.com/ OMConnectionsEnterpriseSystemsManagement – For OpenManage Connections Client Systems Management documents — dell.com/ connectionsclientsystemsmanagement • From the Dell Support site: a. Go to dell.com/support/manuals. b. Under General support section, click Software & Security. c.
Logging into iDRAC 2 You can log in to iDRAC as an iDRAC user, as a Microsoft Active Directory user, or as a Lightweight Directory Access Protocol (LDAP) user. The default user name and password is root and calvin, respectively. You can also log in using Single Sign-On or Smart Card. NOTE: You must have Login to iDRAC privilege to log in to iDRAC.
If the domain is not specified in the user name, select the Active Directory domain from the Domain drop-down menu. 5. For an LDAP user, in the Username and Password fields, enter your LDAP user name and password. Domain name is not required for LDAP login. By default, This iDRAC is selected in the drop-down menu. 6. Click Submit. You are logged into iDRAC with the required user privileges.
3. Enter the Smart Card PIN for local Smart Card users. You are logged into the iDRAC. NOTE: If you are a local user for whom Enable CRL check for Smart Card Logon is enabled, iDRAC attempts to download the CRL and checks the CRL for the user's certificate. The login fails if the certificate is listed as revoked in the CRL or if the CRL cannot be downloaded for some reason.
• You have logged into your system using a valid Active Directory user account. • Single Sign-On option is enabled during Active Directory configuration. To login to iDRAC using Web interface: 1. Log in to your management station using a valid Active Directory account. 2. In a Web browser, type https://[FQDN address] NOTE: If the default HTTPS port number (port 443) has been changed, type: https://[FQDN address]:[port number] where, [FQDN address] is the iDRAC FQDN (iDRACdnsname.domain.
To validate the certificate for using remote RACADM: 1. Convert the certificate in DER format to PEM format (using openssl command line tool): openssl x509 -inform pem -in [yourdownloadedderformatcert.crt] –outform pem -out [outcertfileinpemformat.pem] –text 2. Find the location of the default CA certificate bundle on the management station. For example, for RHEL5 64-bit, it is /etc/pki/tls/cert.pem. 3. Append the PEM formatted CA certificate to the management station CA certificate.
Multiple iDRAC Sessions The following table provides the list of multiple iDRAC sessions that are possible using the various interfaces. Table 5. Multiple iDRAC Sessions Interface Number of Sessions iDRAC Web Interface 6 Remote RACADM 4 Firmware RACADM / SMCLP SSH - 2 Telnet - 2 Serial - 1 Changing Default Login Password The warning message that allows you to change the default password is displayed if: • You log in to iDRAC with Configure User privilege.
NOTE: Continue is enabled only if the passwords entered in the New Password and Confirm Password fields match. For information about the other fields, see the iDRAC Online Help. Changing Default Login Password Using RACADM To change the password, run the following RACADM command: racadm set iDRAC.Users..Password where, is a value from 1 to 16 (indicates the user account) and is the new user— defined password.
Setting Up Managed System and Management Station 3 To perform out-of-band systems management using iDRAC, you must configure iDRAC for remote accessibility, set up the management station and managed system, and configure the supported Web browsers. NOTE: In case of blade servers, install CMC and I/O modules in the chassis and physically install the system in the chassis before performing the configurations. Both iDRAC Express and iDRAC Enterprise ship from the factory with a default static IP address.
NOTE: In case of blade servers, you can configure the network setting using the Chassis LCD panel only during initial configuration of CMC. After the chassis is deployed, you cannot reconfigure iDRAC using the Chassis LCD panel. • CMC Web interface (see Dell Chassis Management Controller Firmware User’s Guide) In case of rack and tower servers, you can set up the IP address or use the default iDRAC IP address 192.168.0.
IPv4 Settings IPv6 Settings IPMI Settings VLAN Settings Network Settings To configure the Network Settings: NOTE: For information about the options, see the iDRAC Settings Utility Online Help. 1. Under Enable NIC, select the Enabled option. 2. From the NIC Selection drop-down menu, select one of the following ports based on the network requirement: • Dedicated — Enables the remote access device to use the dedicated network interface available on the Remote Access Controller (RAC).
Common Settings If network infrastructure has DNS server, register iDRAC on the DNS. These are the initial settings requirements for advanced features such as Directory services—–Active Directory or LDAP, Single Sign On, and smart card. To register iDRAC: 1. Enable Register DRAC on DNS. 2. Enter the DNS DRAC Name. 3. Select Auto Config Domain Name to automatically acquire domain name from DHCP. Else, provide the DNS Domain Name. IPv4 Settings To configure the IPv4 settings: 1.
VLAN Settings You can configure iDRAC into the VLAN infrastructure. To configure VLAN Settings: 1. Under Enable VLAN ID, select Enabled. 2. In the VLAN ID box, enter a valid number from 1 to 4094. 3. In the Priority box, enter a number from 0 to 7 to set the priority of the VLAN ID. NOTE: After enabling VLAN, the idrac IP is not accessible for sometime.
You can enable auto-discovery using iDRAC Settings Utility or using Lifecycle Controller. For information on using Lifecycle Controller, see Lifecycle Controller User’s Guide available at dell.com/support/ manuals. If auto-discovery feature is not enabled on the factory-shipped system, the default administrator account (user name as root and password as calvin) is enabled. Before enabling auto-discovery, make sure to disable this administrator account.
You can configure individual servers using different configuration files mapped using individual host names. In an environment that has different servers with specific requirements, you can use different XML filenames to distinguish each server. For example, if there are two servers – a PowerEdge R720 and a PowerEdge R520, you must use two XML files, R720-config.xml and R520-config.xml.
With Dell PowerEdge servers, the iDRAC identifies itself with vendor ID: iDRAC. Therefore, you must add a new ‘Vendor Class’ and create a ‘scope option’ under it for ‘code 60,’ and then enable the new scope option for the DHCP server. Related Links Configuring Option 43 on Windows Configuring Option 60 on Windows Configuring Option 43 and Option 60 on Linux Configuring Option 43 on Windows To configure option 43 on Windows: 1.
13. Select 060iDRAC option. 14. Enter the string value that must be sent to the iDRAC (along with a standard DHCP provided IP address). The string value will help in importing the correct XML configuration file. For the option’s DATA entry, String Value setting, use a text parameter that has the following letter options and values: • Filename – iDRAC_Config.XML or iDRAC_Config-.XML. (-f ) • Sharename – (-n) • ShareType – -s (0 = NFS, 2 = CIFS) • IPAddress – IP address of the file share.
To enable Auto Config: 1. In the iDRAC Web interface, go to Overview → iDRAC Settings → Network. The Network page is displayed. 2. In the Auto Config section, select one of the following options to enable Auto Config: • Enable Once — Configures the component only once using the XML file referenced by the DHCP server. After this, Auto Config is disabled. • Enable Once After Reset — After the iDRAC is reset, configures the components only once using the XML file referenced by the DHCP server.
NOTE: The attributes are not applicable to the INI configuration file. Hash Password in Server Configuration Profile The new hash passwords can be optionally exported in the server configuration profile. When importing server configuration profile, you can uncomment the existing password attribute or the new password hash attribute(s). If both are uncommented an error is generated and the password is not set. A commented attribute is not applied during an import.
• Blade servers — The management station must be on the same network as CMC. For more information on isolating CMC network from the managed system’s network, see Chassis Management Controller User’s Guide available at dell.com/support/manuals. • Rack and tower servers — Set the iDRAC NIC to Dedicated or LOM1 and make sure that the management station is on the same network as iDRAC. To access the managed system’s console from a management station, use Virtual Console through iDRAC Web interface.
For information about the options, see the iDRAC Online Help. 3. Click Apply. The system location details is saved in iDRAC. Setting Up Managed System Location Using RACADM To specify the system location details, use the System.Location group objects. For more information, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/ manuals. Setting Up Managed System Location Using iDRAC Settings Utility To specify the system location details: 1.
– Maximum Performance (Performance Optimized) : * Reduced probability of memory or CPU throttling. * Increased probability of turbo mode activation. * Generally, higher fan speeds at idle and stress loads. – Minimum Power (Performance per Watt Optimized): * Optimized for lowest system power consumption based on optimum fan power state. * Generally, lower fan speeds at idle and stress loads.
– Custom — Enter the percentage value. The allowable range for minimum fan speed PWM is dynamic based on the system configuration. The first value is the idle speed and the second value is the configuration max (which may or may not be 100% based on system configuration). System fans can run higher than this speed as per thermal requirements of the system but not lower than the defined minimum speed. For example, setting Minimum Fan Speed at 35% limits the fan speed to never go lower than 35% PWM.
Object Description Usage Example The output is: Object value modified successfully. If a system does not support a particular air exhaust temperature limit, then when you run the following command: racadm set system.thermalsettings.AirE xhaustTemp 0 The following error message is displayed: ERROR: RAC947: Invalid object value specified. Make sure to specify the value depending on the type of object. For more information, see RACADM help. To set the limit to the default value: racadm set system.
Object Description FanSpeedMax OffsetVal • • • FanSpeedMed iumOffsetVa l • • • FanSpeedOff set • • • MFSMaximumL imit Usage Example Getting this variable reads Values from 0-100 the fan speed offset value in %PWM for Max Fan Speed Offset setting. This value depends on the system. Use FanSpeedOffset to set this value using index value 3 racadm get system.
Object Description Usage MFSMinimumL imit Read Minimum limit for MFS Values from 0 to To display the lowest value that can MFSMaximumLimi be set using MinimumFanSpeed t option. MinimumFanS peed • • • ThermalProf ile • • Example Default is 255 (means None) racadm get system.thermalsettings.MFSM inimumLimit Allows configuring the Minimum Fan speed that is required for the system to operate.
The thermal settings are configured. Configuring Supported Web Browsers iDRAC is supported on Internet Explorer, Mozilla Firefox, Google Chrome, and Safari Web browsers. For information about the versions, see the Readme available at dell.com/support/manuals. If you are connecting to iDRAC Web interface from a management station that connects to the Internet through a proxy server, you must configure the Web browser to access the Internet from through this server.
• Scripting of Java applets: Enable 5. Go to Tools → Internet Options → Advanced. 6.
NOTE: When you log in to iDRAC Web interface using Internet Explorer 9.x, sometimes contents in few pages are not shown properly. To resolve this, press . In the Internet Explorer 9 Debug window, select Document Mode as Internet Explorer 7. The browser refreshes and the iDRAC Login page is displayed.
• Spanish (es) • Japanese (ja) • Simplified Chinese (zh-cn) The ISO identifiers in parentheses denote the supported language variants. For some supported languages, resizing the browser window to 1024 pixels wide is required to view all features. iDRAC Web interface is designed to work with localized keyboards for the supported language variants. Some features of iDRAC Web interface, such as Virtual Console, may require additional steps to access certain functions or letters.
• Repository Manager User's Guide. iDRAC automatically provides a difference between the BIOS and the firmware that is installed on the server and the repository location or FTP site. All applicable updates contained in the repository are applied to the system. This feature is available with iDRAC Enterprise license. Scheduling recurring automated firmware updates using the catalog file in the FTP site or the network repository location.
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 Downloading Device Firmware The image file format that you download depends on the method of update: • iDRAC Web interface — Download the binary image packaged as a self-extracting archive. The default firmware image file is firmimg.d7.
When you click Install, Install and Reboot or Install Next Reboot, the message Updating Job Queue is displayed. 6. Click Job Queue to display the Job Queue page, where you can view and manage the staged firmware updates or click OK to refresh the current page and view the status of the firmware update. NOTE: If you navigate away from the page without committing the updates, an error message is displayed and all the uploaded content is lost.
When you click Install, Install and Reboot or Install Next Reboot, the message Updating Job Queue is displayed. 6. Click Job Queue to display the Job Queue page, where you can view and manage the staged firmware updates or click OK to refresh the current page and view the status of the firmware update.
Updating Device Firmware Using TFTP You can directly connect to the TFTP site from iDRAC to perform the firmware updates. You can use the Windows based update packages (DUPs) and a catalog file available on the TFTP site instead of creating custom repositories. Before performing an update, make sure that: • Lifecycle Controller is enabled. • You have Server Control privilege to update firmware for devices other than iDRAC. To update device firmware using TFTP: 1.
• You have Server Control privilege to update firmware for devices other than iDRAC. To update device firmware using HTTP: 1. In the iDRAC Web interface, go to Overview → iDRAC Settings → Update and Rollback . The Firmware Update page is displayed. 2. On the Update tab, select HTTP as the File Location. 3. In the HTTP Server Settings section, enter the HTTP details. For information about the fields, see the iDRAC Online Help. 4. Click Check for Update. 5.
Scheduling Automatic Firmware Updates You can create a periodic recurring schedule for iDRAC to check for new firmware updates. At the scheduled day and time, iDRAC connects to the specified network share (CIFS or NFS) or the FTP, checks for new updates and applies or stages all applicable updates. A log file on the remote server contains information about server access and staged firmware updates. Automatic updates is available only with the iDRAC Enterprise license.
Scheduling Automatic Firmware Update Using RACADM To schedule automatic firmware update, use the following commands: • To enable automatic firmware update: racadm set lifecycleController.lcattributes.AutoUpdate.Enable 1 • To view the status of automatic firmware update: racadm get lifecycleController.lcattributes.
NOTE: While updating the iDRAC firmware using the DUP utility in Linux, if you see error messages such as usb 5-2: device descriptor read/64, error -71 displayed on the console, ignore them. • If the system has ESX hypervisor installed, then for the DUP file to run, make sure that the "usbarbitrator" service is stopped using command: service usbarbitrator stop To update iDRAC using DUP: 1. Download the DUP based on the installed operating system and run it on the managed system. 2. Run the DUP.
Viewing and Managing Staged Updates Using iDRAC Web interface To view the list of scheduled jobs using iDRAC Web interface, go to Overview → Server → Job Queue. The Job Queue page displays the status of jobs in the Lifecycle Controller job queue. For information about the displayed fields, see the iDRAC Online Help. To delete job(s), select the job(s) and click Delete. The page is refreshed and the selected job is removed from the Lifecycle Controller job queue.
• Lifecycle Controller-Remote Services Related Links Rollback Firmware Using iDRAC Web Interface Rollback Firmware Using CMC Web Interface Rollback Firmware Using RACADM Rollback Firmware Using Lifecycle Controller Rollback Firmware Using Lifecycle Controller-Remote Services Rollback Firmware Using iDRAC Web Interface To roll back device firmware: 1. In the iDRAC Web interface, go to Overview → iDRAC Settings → Update and Rollback → Rollback.
Rollback Firmware Using RACADM To rollback device firmware using racadm: 1. Check the rollback status and the FQDD using the swinventory command: racadm swinventory For the device for which you want to rollback the firmware, the Rollback Version must be Available. Also, make a note of the FQDD. 2. Rollback the device firmware using: racadm rollback For more information, see iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/manuals.
• Install a TFTP server on the operating system. Backing Up Server Profile You can backup the system configuration, including the installed firmware images on various components such as BIOS, RAID, NIC, iDRAC, Lifecycle Controller, and Network Daughter Cards (NDCs) and the configuration settings of those components. The backup operation also includes the hard disk configuration data, motherboard, and replaced parts.
5. Click Backup Now. The backup operation is initiated and you can view the status on the Job Queue page. After a successful operation, the backup file is created in the specified location. Backing Up Server Profile Using RACADM To backup the server profile using RACADM, use systemconfig backup subcommand. For more information, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/ support/manuals.
time period is created. The backup server profile operation is performed at the scheduled date and time. Scheduling Automatic Backup Server Profile Using RACADM To enable automatic backup use the command: racadm set lifecyclecontroller.lcattributes.
Import events are recorded in the Lifecycle Log. Related Links Restore Operation Sequence Importing Server Profile Using iDRAC Web Interface To import the server profile using iDRAC Web interface: 1. Go to Overview → iDRAC Settings → Server Profile → Import. The Import Server Profile page is displayed. 2. Select one of the following to specify the location of the backup file: • Network 3. • vFlash Enter the backup file name and decryption passphrase (optional). 4.
Monitoring iDRAC Using Other Systems Management Tools You can discover and monitor iDRAC using Dell Management Console or Dell OpenManage Essentials. You can also use Dell Remote Access Configuration Tool (DRACT) to discover iDRACs, update firmware, and set up Active Directory. For more information, see the respective user’s guides.
Configuring iDRAC 4 iDRAC enables you to configure iDRAC properties, set up users, and set up alerts to perform remote management tasks. Before you configure iDRAC, make sure that the iDRAC network settings and a supported browser is configured, and the required licenses are updated. For more information about the licensable feature in iDRAC, see Managing Licenses.
Modifying Network Settings Configuring Services Configuring Front Panel Display Setting Up Managed System Location Configuring Time Zone and NTP Setting Up iDRAC Communication Configuring User Accounts and Privileges Monitoring and Managing Power Enabling Last Crash Screen Configuring and Using Virtual Console Managing Virtual Media Managing vFlash SD Card Setting First Boot Device Enabling or Disabling OS to iDRAC Pass-through Configuring iDRAC to Send Alerts Viewing iDRAC Information You can view the bas
NOTE: Changing the network settings may terminate the current network connections to iDRAC. Modifying Network Settings Using Web Interface To modify the iDRAC network settings: 1. In the iDRAC Web interface, go to Overview → iDRAC Settings → Network. The Network page is displayed. 2. Specify the network settings, common settings, IPv4, IPv6, IPMI, and/or VLAN settings as per your requirement and click Apply.
racadm racadm racadm racadm racadm racadm racadm racadm racadm racadm set set set set set set set set set set iDRAC.IPv4.Netmask 255.255.255.0 iDRAC.IPv4.Gateway 192.168.0.120 iDRAC.IPv4.DHCPEnable 0 iDRAC.IPv4.DNSFromDHCP 0 iDRAC.IPv4.DNS1 192.168.0.5 iDRAC.IPv4.DNS2 192.168.0.6 iDRAC.Nic.DNSRegister 1 iDRAC.Nic.DNSRacName RAC-EK00002 iDRAC.Nic.DNSDomainFromDHCP 0 iDRAC.Nic.DNSDomainName MYDOMAIN NOTE: If cfgNicEnable or iDRAC.Nic.Enable is set to 0, the iDRAC LAN is disabled even if DHCP is enabled.
– cfgRacTuneIpRangeEnable – cfgRacTuneIpRangeAddr – cfgRacTuneIpRangeMask • With set command, use the objects in the iDRAC.IPBlocking group: – RangeEnable – RangeAddr – RangeMask The cfgRacTuneIpRangeMask or the RangeMask property is applied to both the incoming IP address and to the cfgRacTuneIpRangeAddr or RangeAddr property. If the results are identical, the incoming login request is allowed to access iDRAC. Logging in from IP addresses outside this range results in an error.
• SSH — Access iDRAC through firmware RACADM. • Telnet — Access iDRAC through firmware RACADM • Remote RACADM — Remotely access iDRAC. • SNMP Agent — Enables support for SNMP queries (GET, GETNEXT, and GETBULK operations) in iDRAC. • Automated System Recovery Agent — Enable Last System Crash Screen. • VNC Server — Enable VNC server with or without SSL encryption. Configuring Services Using Web Interface To configure the services using iDRAC Web interface: 1.
– iDRAC.Racadm – iDRAC.SNMP For more information about these objects, see iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/manuals. Enabling or Disabling HTTPs Redirection If you do not want automatic redirection from HTTP to HTTPs due to certificate warning issue with default iDRAC certificate or as a temporary setting for debugging purpose, you can configure iDRAC such that redirection from http port (default is 80) to https port (default is 443) is disabled.
VNC server disables Virtual Console and allows only Virtual Media. After termination of the VNC session, VNC server restores the original state of Virtual Console (enabled or disabled). NOTE: • When iDRAC NIC is in shared mode and the host system is power cycled, the network connection is lost for a few seconds. During this time, if you perform any action in the active VNC client, the VNC session may close.
disabled when configuring the VNC server settings in iDRAC, then to connect to the VNC Viewer do the following: In the VNC Viewer dialog box, enter the iDRAC IP address and the VNC port number in the VNC Server field. The format is For example, if the iDRAC IP address is 192.168.0.120 and VNC port number is 5901, then enter 192.168.0.120:5901. Configuring Front Panel Display You can configure the front panel LCD and LED display for the managed system.
If you select None, home message is not displayed on the server LCD front panel. 3. Enable Virtual Console indication (optional). If enabled, the Live Front Panel Feed section and the LCD panel on the server displays the Virtual console session active message when there is an active Virtual Console session. 4. Click Apply. The server LCD front panel displays the configured home message. Configuring LCD Setting Using RACADM To configure the server LCD front panel display, use the objects in the System.
Configuring System ID LED Setting Using RACADM To configure system ID LED, use the setled command. For more information, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/manuals. Configuring Time Zone and NTP You can configure the time zone on iDRAC and synchronize the iDRAC time using Network Time Protocol (NTP) instead of BIOS or host system times. You must have Configure privilege to configure time zone or NTP settings.
• BIOS Boot Manager NOTE: • BIOS Setup (F2), Lifecycle Controller (F10), BIOS Boot Manager (F11) only support boot once enabled. • Virtual Console does not support permanent boot configuration. It is always boot once. • The first boot device setting in iDRAC Web Interface overrides the System BIOS boot settings. Setting First Boot Device Using Web Interface To set the first boot device using iDRAC Web interface: 1. Go to Overview → Server → Setup → First Boot Device.
For more information, see Windows documentation. 3. Use Server Administrator to enable the Auto Recovery timer, set the Auto Recovery action to Reset, Power Off, or Power Cycle, and set the timer in seconds (a value between 60 - 480). For more information, see the Dell OpenManage Server Administrator Installation Guide at dell.com/ support/manuals. 4.
• In shared mode, the host operating system's IP address is used. • In dedicated mode, you must provide a valid IP address of the host operating system. If more than one LOM is active, enter the first LOM’s IP address. After enabling OS to iDRAC Pass-through feature, if it is not working: • Check whether the iDRAC's dedicated NIC cable is connected properly. • Make sure that at least one LOM is active.
• Windows Server 2012 SP1 • SLES 10 SP4 (64-bit) • SLES 11 SP2 (64-bit) • RHEL 5.9 (32-bit and 64-bit) • RHEL 6.4 • vSphere v5.0 U2 ESXi • vSphere v5.1 U1 ESXi • vSphere v5.5 ESXi On servers with Windows 2008 SP2 64-bit operating system, the iDRAC Virtual CD USB Device is not discovered automatically (or enabled). You must enable this manually.
• Turn off and turn on the system. On systems with RHEL 5.9 operating system, if the USB NIC was disabled and if you turn off the system or vice-versa, when the system is turned on and if the USB NIC is enabled, the USB NIC device is not active automatically. To make it active, check if any ifcfg-ethX.bak file is available in the /etc/sysconfig/networkscript directory for the USB NIC interface. If it is available, rename it to ifcfg-ethX and then use the ifup ethX command.
Do not enter 169.254.0.3 and 169.254.0.4 IPs. These IPs are reserved for the USB NIC port on the front panel when a A/A cable is used. 5. Click Apply to apply the settings. 6. Click Test Network Configuration to check if the IP is accessible and the link is established between the iDRAC and the host operating system. Enabling or Disabling OS to iDRAC Pass-through Using RACADM To enable or disable OS to iDRAC Pass-through using RACADM, use the objects in the iDRAC.OS-BMC group.
Login Type Certificate Type How to Obtain SHA-2 certificates are also supported. Smart Card login as a local or Active Directory user • • User certificate Trusted CA certificate • • User Certificate — Export the smart card user certificate as Base64-encoded file using the card management software provided by the smart card vendor. Trusted CA certificate — This certificate is issued by a CA. SHA-2 certificates are also supported.
Authority is a business entity that is recognized in the Information Technology industry for meeting high standards of reliable screening, identification, and other important security criteria. Examples of CAs include Thawte and VeriSign. To initiate the process of obtaining a CA-signed certificate, use either iDRAC Web interface or RACADM interface to generate a Certificate Signing Request (CSR) with your company’s information. Then, submit the generated CSR to a CA such as VeriSign or Thawte.
After the CA approves the CSR and issues the SSL server certificate, it can be uploaded to iDRAC. The information used to generate the CSR, stored on the iDRAC firmware, must match the information contained in the SSL server certificate, that is, the certificate must have been generated using the CSR created by iDRAC. Related Links SSL Server Certificates Generating CSR Using Web Interface To generate a new CSR: NOTE: Each new CSR overwrites any previous CSR data stored in the firmware.
iDRAC resets and the new certificate is applied. The iDRAC is not available for a few minutes during the reset. NOTE: You must reset iDRAC to apply the new certificate. Until iDRAC is reset, the existing certificate is active. Uploading Server Certificate Using RACADM To upload the SSL server certificate, use the sslcertupload command. For more information, see the RACADM Command Line Reference Guide for iDRAC available at dell.com/support/manuals.
The Upload Custom SSL Certificate Signing Certificate page is displayed. 3. Click Browse and select the custom SSL certificate signing certificate file. Only Public-Key Cryptography Standards #12 (PKCS #12) compliant certificate is supported. 4. If the certificate is password protected, in the PKCS#12 Password field, enter the password. 5. Click Apply. The certificate is uploaded to iDRAC. 6. A pop-up message is displayed asking you to reset iDRAC immediately or at a later time.
3. A pop-up message is displayed asking you to reset iDRAC immediately or at a later time. Click Reset iDRAC or Reset iDRAC Later as required. After iDRAC resets, a new self-signed certificate is generated. Deleting Custom SSL Certificate Signing Certificate Using RACADM To delete the custom SSL certificate signing certificate using RACADM, use the sslcertdelete subcommand. Then, use the racreset command to reset iDRAC. For more information, see the iDRAC8 2.00.00.
Creating an iDRAC Configuration File The configuration file .cfg can be: • Created • Obtained from racadm getconfig -f .cfg command or racadm get -f .cfg • Obtained from racadm getconfig -f .cfg command or racadm get -f .cfg, and then edited For information about the getconfig and get commands, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/manuals . The .
• Use the racresetcfg subcommand to reset the iDRAC to the default setting, and then run the racadm config -f .cfg or racadm set -f .cfg command. Make sure that the .cfg file includes all required objects, users, indexes, and other parameters. CAUTION: Use the racresetcfg subcommand to reset the database and the iDRAC NIC settings to the default settings and remove all users and user configurations.
Modifying the iDRAC IP Address When you modify the iDRAC IP address in the configuration file, remove all unnecessary =value entries. Only the actual variable group’s label with "[" and "]" remains, including the two =value entries pertaining to the IP address change. For example: # # Object Group "cfgLanNetworking" # [cfgLanNetworking] cfgNicIpAddress=10.35.10.110 cfgNicGateway=10.35.10.
• Disable the iDRAC Local Configuration using iDRAC Settings — Disables access to modify the configuration settings in iDRAC Settings utility. • 3. Disable the iDRAC Local Configuration using RACADM — Disables access to modify the configuration settings in Local RACADM. Click Apply. NOTE: If access is disabled, you cannot use Server Administrator or IPMITool to perform iDRAC configurations. However, you can use IPMI Over LAN.
Viewing iDRAC and Managed System Information 5 You can view iDRAC and managed system’s health and properties, hardware and firmware inventory, sensor health, storage devices, network devices, and view and terminate user sessions. For blade servers, you can also view the flex address information.
• RAID controller • Batteries • CPUs • DIMMs • HDDs • Backplanes • Network Interface Cards (integrated and embedded) • Video card • SD card • Power Supply Units (PSUs) • Fans • Fibre Channel HBAs • USB The Firmware Inventory section displays the firmware version for the following components: • BIOS • Lifecycle Controller • iDRAC • OS driver pack • 32-bit diagnostics • System CPLD • PERC controllers • Batteries • Physical disks • Power supply • NIC • Fibre Cha
NOTE: The Storage ROMB battery settings are available only if the system has a ROMB with a battery. • Fan (available only for rack and tower servers) — Provides information about the system fans —fan redundancy and fans list that display fan speed and threshold values. • CPU — Indicates the health and state of the CPUs in the managed system. It also reports processor automatic throttling and predictive failure.
View Sensor Information For Using Web Interface Using RACADM For more information, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/ manuals.
The four system utilization parameters are: • CPU Utilization - There are individual Resource Monitoring counters (RMCs) for each CPU core which are aggregated to provide cumulative utilization of all the cores in the system. This utilization is based on time spent in active state and time spent in inactive state. Each sample of RMC is taken every six seconds.
– You can reset the peak utilization for a particular sensor. Click Reset Historical Peak. You must have Configure privilege to reset the peak value. • Performance Metrics section: – View status and present reading – View or specify the warning threshold utilization limit. You must have server configure privilege to set the threshold values. For information about the displayed properties, see the iDRAC Online Help.
The collected data is represented in a graphical format to track the 10% and 1% levels. The logged temperature data can be cleared only before shipping from the factory. An event is generated if the system continues to operate above the normally supported temperature threshold for a specified operational time. If the average temperature over the specified operational time is greater than or equal to the warning level (> = 8%) or the critical level (> = 0.
centigrade, the system automatically calculates and displays the Fahrenheit value. Similarly, if you enter Fahrenheit, the value for Centigrade is displayed. 3. Click Apply. The values are configured. NOTE: Changes to default thresholds are not reflected in the historical data chart since the chart limits are for fresh air limit values only. Warnings for exceeding the custom thresholds are different from warning associated to exceeding fresh air thresholds.
Viewing FlexAddress Mezzanine Card Fabric Connections In blade servers, FlexAddress allows the use of persistent, chassis-assigned World Wide Names and MAC addresses (WWN/MAC) for each managed server port connection. You can view the following information for each installed embedded Ethernet and optional mezzanine card port: • Fabrics to which the cards are connected. • Type of fabric. • Server-assigned, chassis-assigned, or remotely assigned MAC addresses.
The Sessions page displays the session ID, username, IP address, and session type. For more information about these properties, see the iDRAC Online Help. 2. To terminate the session, under the Terminate column, click the Trashcan icon for a session. Terminating iDRAC Sessions Using RACADM You must have administrator privileges to terminate iDRAC sessions using RACADM. To view the current user sessions, use the getssninfo command. To terminate a user session, use the closessn command.
Setting Up iDRAC Communication 6 You can communicate with iDRAC using any of the following modes: • iDRAC Web Interface • Serial connection using DB9 cable (RAC serial or IPMI serial) - For rack and tower servers only • IPMI Serial Over LAN • IPMI Over LAN • Remote RACADM • Local RACADM • Remote Services For an overview of the supported protocols, supported commands, and pre-requisites, see the following table. Table 10.
Mode of Communication Supported Protocol Supported Commands Prerequisite Firmware RACADM SSH Firmware RACADM Firmware RACADM is installed and enabled Telnet Local RACADM IPMI Local RACADM Local RACADM is installed. Remote Services [1] WS-MAN WinRM (Windows) WinRM is installed (Windows) or OpenWSMAN is installed (Linux). OpenWSMAN (Linux) [1] For more information, see the Lifecycle Controller Remote Services User’s Guide available at dell.com/support/manuals.
Based on where the managed system is in its boot process, you can see either the POST screen or the operating system screen. This is based on the configuration: SAC for Windows and Linux text mode screens for Linux. 4. Enable RAC serial or IPMI serial connections in iDRAC.
• IPMI basic mode — Supports a binary interface for program access, such as the IPMI shell (ipmish) that is included with the Baseboard Management Utility (BMU). For example, to print the System Event Log using ipmish via IPMI Basic mode, run the following command: ipmish -com 1 -baud 57600 -flow cts -u root -p calvin sel get • IPMI terminal mode — Supports ASCII commands that are sent from a serial terminal.
4. • Using config command: racadm config -g cfgIpmiSerial -o cfgIpmiSerialFlowControl 1 • Using set command: racadm set iDRAC.IPMISerial.FlowControl 1 Set the IPMI serial channel minimum privilege level: • Using config command: racadm config -g cfgIpmiSerial -o cfgIpmiSerialChanPrivLimit • Using set command: racadm set iDRAC.IPMISerial.ChanPrivLimit where is 2 (User), 3 (Operator), or 4 (Administrator). 5.
Switching From Serial Console to RAC Serial To switch to RAC Serial Interface communication mode when in Serial Console Mode, use the following key sequence: + <9> The key sequence directs you to the "iDRAC Login" prompt (if the iDRAC is set to RAC Serial mode) or to the Serial Connection mode where terminal commands can be issued if iDRAC is set to IPMI Serial Direct Connect Terminal Mode.
NOTE: This is applicable only for iDRAC on rack and tower servers. 1. Turn on or restart the system. 2. Press . 3. Go to System BIOS Settings → Serial Communication. 4. Specify the following values: • Serial Communication — On With Console Redirection • Serial Port Address — COM2. NOTE: You can set the serial communication field to On with serial redirection via com1 if serial device2 in the serial port address field is also set to com1.
• Using config command: racadm config -g cfgIpmiSol o cfgIpmiSolMinPrivilege • Using set command: racadm set iDRAC.IPMISol.MinPrivilege 1 where is 2 (User), 3 (Operator), 4 (Administrator). NOTE: The IPMI SOL minimum privilege level determines the minimum privilege to activate IPMI SOL. For more information, see the IPMI 2.0 specification. 3.
– Using set command:racadm set iDRAC.SSH.Port You can use tools such as: • IPMItool for using IPMI protocol • Putty/OpenSSH for using SSH or Telnet protocol Related Links SOL Using IPMI Protocol SOL Using SSH or Telnet Protocol SOL Using IPMI Protocol IPMItool <−−> LAN/WAN connection <−−> iDRAC The IPMI-based SOL utility and IPMItool uses RMCP+ delivered using UDP datagrams to port 623.
NOTE: Run OpenSSH from a VT100 or ANSI terminal emulator on Windows. Running OpenSSH at the Windows command prompt does not result in full functionality (that is, some keys do not respond and no graphics are displayed). Before using SSH or Telnet to communicate with iDRAC, make sure to: 1. Configure BIOS to enable Serial Console. 2. Configure SOL in iDRAC. 3. Enable SSH or Telnet using iDRAC Web interface or RACADM.
NOTE: If required, you can change the default SSH or Telnet session time-out at Overview → iDRAC Settings → Network → Services. 1. Start a shell. 2. Connect to iDRAC using the following command: • For SSH: ssh -l • For Telnet: telnet NOTE: If you have changed the port number for the Telnet service from the default (port 23), add the port number to the end of the Telnet command. 3.
Configuring Backspace Key For Your Telnet Session Depending on the Telnet client, using the key may produce unexpected results. For example, the session may echo ^h. However, most Microsoft and Linux Telnet clients can be configured to use the key. To configure a Linux Telnet session to use the key, open a command prompt and type stty erase ^h. At the prompt, type telnet. To configure Microsoft Telnet clients to use the key: 1.
The iDRAC Settings Network page is displayed. 2. For IPMI Settings, specify the values. For information about the options, see the iDRAC Settings Utility Online Help. 3. Click Back, click Finish, and then click Yes. The IPMI over LAN settings are configured. Configuring IPMI Over LAN Using RACADM To configure IPMI over LAN using set or config command: 1. Enable IPMI over LAN: • Using config command: racadm config -g cfgIpmiLan -o cfgIpmiLanEnable 1 • Using set command: racadm set iDRAC.IPMILan.
• Using config command: racadm config -g cfgRacTuning -o cfgRacTuneRemoteRacadmEnable 1 • Using set command: racadm set iDRAC.Racadm.Enable 1 To disable the remote capability, type one of the following command: • Using config command: racadm config -g cfgRacTuning -o cfgRacTuneRemoteRacadmEnable 0 • Using set command: racadm set iDRAC.Racadm.Enable 0 NOTE: It is recommended to run these commands on the local system. Disabling Local RACADM The local RACADM is enabled by default.
default=0 timeout=10 #splashimage=(hd0,2)/grub/splash.xpm.gz serial --unit=1 --speed=57600 terminal --timeout=10 serial title Red Hat Linux Advanced Server (2.4.9-e.3smp) root (hd0,0) kernel /boot/vmlinuz-2.4.9-e.3smp ro root=/dev/sda1 hda=ide-scsi console=ttyS0 console=ttyS1,115200n8r initrd /boot/initrd-2.4.9-e.3smp.img title Red Hat Linux Advanced Server-up (2.4.9-e.3) root (hd0,00) kernel /boot/vmlinuz-2.4.9-e.3 ro root=/dev/sda1 s initrd /boot/initrd-2.4.9-e.3.im 4.
pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down" #If power was restored before the shutdown kicked in, cancel it.
Table 11.
Generating Public Keys for Windows To use the PuTTY Key Generator application to create the basic key: 1. Start the application and select either SSH-2 RSA or SSH-2 DSA for the type of key to generate. (SSH-1 is not supported). The supported key generation algorithms are RSA and DSA only. 2. Enter the number of bits for the key. For RSA, it is between 768 and 4096 bits and for DSA, it 1024 bits. 3. Click Generate and move the mouse in the window as directed. The keys are generated. 4.
3. Under SSH Key Configurations, select Upload SSH Key(s) and click Next. The Upload SSH Key(s) page is displayed. 4. Upload the SSH keys in one of the following ways: • Upload the key file. • Copy the contents of the key file into the text box For more information, see iDRAC Online Help. 5. Click Apply. Uploading SSH Keys Using RACADM To upload the SSH keys, run the following command: NOTE: You cannot upload and copy a key at the same time.
Deleting SSH Keys Using Web Interface To delete the SSH key(s): 1. In Web interface, go to Overview → iDRAC Settings → Network → User Authentication → Local Users. The Users page is displayed. 2. In the User ID column, click a user ID number. The Users Main Menu page is displayed. 3. Under SSH Key Configurations, select View/Remove SSH Key(s) and click Next. The View/Remove SSH Key(s) page displays the key details. 4. Select Remove for the key(s) you want to delete, and click Apply.
7 Configuring User Accounts and Privileges You can setup user accounts with specific privileges (role-based authority) to manage your system using iDRAC and maintain system security. By default iDRAC is configured with a local administrator account. This default user name is root and the password is calvin. As an administrator, you can setup user accounts to allow other users to access iDRAC.
4. Enable the user ID and specify the user name, password, and access privileges for the user. You can also enable SNMPv3 authentication for the user. For more information about the options, see the iDRAC Online Help. 5. Click Apply. The user is created with the required privileges. Configuring Local Users Using RACADM NOTE: You must be logged in as user root to execute RACADM commands on a remote Linux system. You can configure single or multiple iDRAC users using RACADM.
When you manually enable or disable a user with the racadm config subcommand, you must specify the index with the -i option. Observe that the cfgUserAdminIndex object displayed in the previous example contains a '#' character. It indicates that it is a read-only object. Also, if you use the racadm config -f racadm.cfg command to specify any number of groups/objects to write, the index cannot be specified. This behavior allows more flexibility in configuring multiple iDRAC with the same settings.
NOTE: You can use the getconfig and config commands or get and set commands. 1. 2. Locate an available user index using the command syntax: • Using getconfig command: racadm getconfig -g cfgUserAdmin -i • Using get command: racadm get iDRAC.Users Type the following commands with the new user name and password. • Using config command: racadm config -g cfgUserAdmin -o cfgUserAdminPrivilege -i • Using set command: racadm set iDRAC.Users..
Table 13. iDRAC User Privileges Current Generation Prior Generation Description Login Login to iDRAC Enables the user to log in to iDRAC. Configure Configure iDRAC Enables the user to configure iDRAC. Configure Users Configure Users Enables the user to allow specific users to access the system. Logs Clear Logs Enables the user to clear the System Event Log (SEL). System Control Execute Server Control Allows power cycling the host system.
Certificate Authority (CA)—the root certificate of which is also uploaded into iDRAC. For iDRAC to authenticate to any domain controller—whether it is the root or the child domain controller—that domain controller must have an SSL-enabled certificate signed by the domain’s CA. If you are using Microsoft Enterprise Root CA to automatically assign all your domain controllers to an SSL certificate, you must: 1. Install the SSL certificate on each domain controller. 2.
Importing iDRAC Firmware SSL Certificate iDRAC SSL certificate is the identical certificate used for iDRAC Web server. All iDRAC controllers are shipped with a default self-signed certificate. If the Active Directory Server is set to authenticate the client during an SSL session initialization phase, you need to upload iDRAC Server certificate to the Active Directory Domain controller.
Figure 1. Configuration of iDRAC with Active Directory Standard Schema In Active Directory, a standard group object is used as a role group. A user who has iDRAC access is a member of the role group. To give this user access to a specific iDRAC, the role group name and its domain name need to be configured on the specific iDRAC. The role and the privilege level is defined on each iDRACand not in the Active Directory. You can configure up to five role groups in each iDRAC.
NOTE: The Bit Mask values are used only when setting Standard Schema with the RACADM. Single Domain Versus Multiple Domain Scenarios If all the login users and role groups, including the nested groups, are in the same domain, then only the domain controllers’ addresses must be configured on iDRAC. In this single domain scenario, any group type is supported.
The Active Directory Configuration and Management Step 4a of 4 page is displayed. 8. Enter the location of Active Directory global catalog server(s) and specify privilege groups used to authorize users. 9. Click a Role Group to configure the control authorization policy for users under the standard schema mode. The Active Directory Configuration and Management Step 4b of 4 page is displayed. 10. Specify the privileges and click Apply.
For Bit Mask values for specific Role Group permissions, see Default Role Group Privileges. Enter the FQDN of the domain controller, not the FQDN of the domain. For example, enter servername.dell.com instead of dell.com. At least one of the three addresses is required to be configured. iDRAC attempts to connect to each of the configured addresses one-by-one until it makes a successful connection.
address> racadm config -g cfgLanNetworking -o cfgDNSServer2 • 4. Using set command: racadm set iDRAC.IPv4.DNSFromDHCP 0 racadm set iDRAC.IPv4.DNSFromDHCP.DNS1 racadm set iDRAC.IPv4.DNSFromDHCP.
groups of users, or iDRAC device objects as required. The users and iDRAC user groups can be members of any domain in the enterprise. However, each association object can be linked (or, may link users, groups of users, or iDRAC device objects) to only one privilege object. This example allows an administrator to control each user’s privileges on specific iDRAC devices. iDRAC device object is the link to iDRAC firmware for querying Active Directory for authentication and authorization.
Accumulating Privileges Using Extended Schema The Extended Schema Authentication mechanism supports Privilege Accumulation from different privilege objects associated with the same user through different Association Objects. In other words, Extended Schema Authentication accumulates privileges to allow the user the super set of all assigned privileges corresponding to the different privilege objects associated with the same user.
Configuring Active Directory With Extended Schema Using RACADM Extending Active Directory Schema Extending your Active Directory schema adds a Dell organizational unit, schema classes and attributes, and example privileges and association objects to the Active Directory schema. Before you extend the schema, make sure that you have Schema Admin privileges on the Schema Master Flexible Single Master Operation (FSMO) Role Owner of the domain forest.
Classes and Attributes Table 15. Class Definitions for Classes Added to the Active Directory Schema Class Name Assigned Object Identification Number (OID) delliDRACDevice 1.2.840.113556.1.8000.1280.1.7.1.1 delliDRACAssociation 1.2.840.113556.1.8000.1280.1.7.1.2 dellRAC4Privileges 1.2.840.113556.1.8000.1280.1.1.1.3 dellPrivileges 1.2.840.113556.1.8000.1280.1.1.1.4 dellProduct 1.2.840.113556.1.8000.1280.1.1.1.5 Table 16. dellRacDevice Class OID 1.2.840.113556.1.8000.1280.1.7.1.
Table 18. dellRAC4Privileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.3 Description Defines the privileges (Authorization Rights) for iDRAC Class Type Auxiliary Class SuperClasses None Attributes dellIsLoginUser dellIsCardConfigAdmin dellIsUserConfigAdmin dellIsLogClearAdmin dellIsServerResetUser dellIsConsoleRedirectUser dellIsVirtualMediaUser dellIsTestAlertUser dellIsDebugCommandAdmin Table 19. dellPrivileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.
Table 21. List of Attributes Added to the Active Directory Schema Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued dellPrivilegeMember 1.2.840.113556.1.8000.1280.1.1.2.1 FALSE List of dellPrivilege Objects that belong to this Attribute. Distinguished Name (LDAPTYPE_DN 1.3.6.1.4.1.1466.115.121.1.12) dellProductMembers 1.2.840.113556.1.8000.1280.1.1.2.2 FALSE List of dellRacDevice and DelliDRACDevice Objects that belong to this role.
Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued TRUE if the user has Virtual Media rights on the device. dellIsTestAlertUser TRUE if the user has Test Alert User rights on the device. dellIsDebugCommandAdmin TRUE if the user has Debug Command Admin rights on the device. dellSchemaVersion 1.2.840.113556.1.8000.1280.1.1.2.1 TRUE 0 Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.7) 1.2.840.113556.1.8000.1280.1.1.2.1 TRUE 1 Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.
:\SYSMGMT\ManagementStation\support\OMActiveDirectory_SnapIn64 For more information about the Active Directory Users and Computers Snap-in, see Microsoft documentation. Adding iDRAC Users and Privileges to Active Directory Using the Dell-extended Active Directory Users and Computers Snap-in, you can add iDRAC users and privileges by creating device, association, and privilege objects.
NOTE: iDRAC association object is derived from the group and its scope is set to Domain Local. 1. In the Console Root (MMC) window, right-click a container. 2. Select New → Dell Remote Management Object Advanced. This New Object window is displayed. 3. Enter a name for the new object and select Association Object. 4. Select the scope for the Association Object and click OK. 5. Provide access privileges to the authenticated users for accessing the created association objects.
3. Click the Privilege Object tab to add the privilege object to the association that defines the user’s or user group’s privileges when authenticating to an iDRAC device. Only one privilege object can be added to an Association Object. Adding iDRAC Devices or iDRAC Device Groups To add iDRAC devices or iDRAC device groups: 1. Select the Products tab and click Add. 2. Enter iDRAC devices or iDRAC device group name and click OK. 3. In the Properties window, click Apply and click OK. 4.
• • Using config command: racadm config -g cfgActiveDirectory racadm config -g cfgActiveDirectory racadm config -g cfgActiveDirectory racadm config -g cfgActiveDirectory rac domain name> racadm config -g cfgActiveDirectory qualified domain name or IP Address racadm config -g cfgActiveDirectory qualified domain name or IP Address racadm config -g cfgActiveDirectory qualified domain name or IP Address -o -o -o -o cfgADEnable 1 cfgADType 1 cfgADRacName cfgADRacDomain
3. 4. • Using config command: racadm config -g cfgLanNetworking -o cfgDNSServersFromDHCP 1 • Using set command: racadm set iDRAC.IPv4.
Testing Active Directory Settings Using RACADM To test the Active Directory settings, use the testfeature command. For more information, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/manuals. Configuring Generic LDAP Users iDRAC provides a generic solution to support Lightweight Directory Access Protocol (LDAP)-based authentication. This feature does not require any schema extension on your directory services.
7. Click Role Group. The Generic LDAP Configuration and Management Step 3b of 3 page is displayed. 8. Specify the group distinguished name, the privileges associated with the group, and click Apply. NOTE: If you are using Novell eDirectory and if you have used these characters—#(hash), "(double quotes), ;(semi colon), > (greater than), , (comma), or <(lesser than)—for the Group DN name, they must be escaped. The role group settings are saved.
8 Configuring iDRAC for Single Sign-On or Smart Card Login This section provides information to configure iDRAC for Smart Card login (for local users and Active Directory users), and Single Sign-On (SSO) login (for Active Directory users.) SSO and smart card login are licensed features. iDRAC supports Kerberos based Active Directory authentication to support Smart Card and SSO logins. For information on Kerberos, see the Microsoft website.
Registering iDRAC as a Computer in Active Directory Root Domain To register iDRAC in Active Directory root domain: 1. Click Overview → iDRAC Settings → Network → Network. The Network page is displayed. 2. Provide a valid Preferred/Alternate DNS Server IP address. This value is a valid DNS server IP address that is part of the root domain. 3. Select Register iDRAC on DNS. 4. Provide a valid DNS Domain Name. 5. Verify that network DNS configuration matches with the Active Directory DNS information.
A keytab file is generated. NOTE: If you find any issues with iDRAC user for which the keytab file is created, create a new user and a new keytab file. If the same keytab file which was initially created is again executed, it does not configure correctly. Creating Active Directory Objects and Providing Privileges Perform the following steps for Active Directory Extended schema based SSO login: 1. Create the device object, privilege object, and association object in the Active Directory server. 2.
Configuring iDRAC SSO Login for Active Directory Users Before configuring iDRAC for Active Directory SSO login, make sure that you have completed all the prerequisites. You can configure iDRAC for Active Directory SSO when you setup an user account based on Active Directory.
Enabling or Disabling Smart Card Login Uploading Smart Card User Certificate Before you upload the user certificate, make sure that the user certificate from the smart card vendor is exported in Base64 format. SHA-2 certificates are also supported. Related Links Obtaining Certificates Uploading Smart Card User Certificate Using Web Interface To upload smart card user certificate: 1. In iDRAC Web interface, go to Overview → iDRAC Settings → Network → User Authentication → Local Users.
Uploading Trusted CA Certificate For Smart Card Using RACADM To upload trusted CA certificate for smart card login, use the usercertupload object. For more information, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/ support/manuals. Configuring iDRAC Smart Card Login for Active Directory Users Before configuring iDRAC Smart Card login for Active Directory users, make sure that you have completed the required prerequisites. To configure iDRAC for smart card login: 1.
Enabling or Disabling Smart Card Login Using Web Interface To enable or disable the Smart Card logon feature: 1. In the iDRAC Web interface, go to Overview → iDRAC Settings → User Authentication → Smart Card . The Smart Card page is displayed. 2. From the Configure Smart Card Logon drop-down menu, select Enabled to enable smart card logon or select Enabled With Remote RACADM. Else, select Disabled. For more information about the options, see the iDRAC Online Help. 3. Click Apply to apply the settings.
Configuring iDRAC to Send Alerts 9 You can set alerts and actions for certain events that occur on the managed system. An event occurs when the status of a system component is greater than the pre-defined condition. If an event matches an event filter and you have configured this filter to generate an alert (e-mail, SNMP trap, IPMI alert, remote system logs, or WS events), then an alert is sent to one or more configured destinations.
• 3. Select Enable to enable alert generation or perform an event action. • Select Disable to disable alert generation or disable an event action. Click Apply to save the setting. Enabling or Disabling Alerts Using RACADM To enable or disable generating alerts or event actions using config command: racadm config -g cfgIpmiLan -o cfgIpmiLanAlertEnable 1 To enable or disable generating alerts or event actions using set command: racadm set iDRAC.IPMILan.
4. • Critical Click Apply. The Alert Results section displays the results based on the selected category and severity. Filtering Alerts Using RACADM To filter the alerts, use the eventfilters command. For more information, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/manuals.
Setting Alert Recurrence Event You can configure iDRAC to generate additional events at specific intervals if the system continues to operate at a temperature which is greater than the inlet temperature threshold limit. The default interval is 30 days. The valid range is 0 to 366 days. A value of ‘0’ indicates no event recurrence. NOTE: You must have Configure iDRAC privilege to set the alert recurrence value. Setting Alert Recurrence Events Using iDRAC Web Interface To set the alert recurrence value: 1.
• eventfilters command. • cfgIpmiPefAction object with config command. For more information, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/manuals. Configuring Email Alert, SNMP Trap, or IPMI Trap Settings The management station uses Simple Network Management Protocol (SNMP) and Intelligent Platform Management Interface (IPMI) traps to receive data from iDRAC.
The alert destinations are configured. 7. In the SNMP Trap Format section, select the protocol version to be used to send the traps on the trap destination(s) — SNMP v1, SNMP v2, or SNMP v3 and click Apply. NOTE: The SNMP Trap Format option applies only for SNMP Traps and not for IPMI Traps. IPMI Traps are always sent in SNMP v1 format and is not based on the configured SNMP Trap Format option. The SNMP trap format is configured.
Configuring IP Alert Destinations Using iDRAC Settings Utility You can configure alert destinations (IPv4, IPv6, or FQDN) using the iDRAC Settings utility. To do this: 1. In the iDRAC Settings utility, go to Alerts. The iDRAC Settings Alerts page is displayed. 2. Under Trap Settings, enable the IP address(es) to receive the traps and enter the IPv4, IPv6, or FQDN destination address(es). You can specify up to eight addresses. 3. Enter the community string name. 4.
where [index] is the email destination index. 0 disables the email alert and 1 enables the alert. The email destination index can be a value from 1 through 4. For example, to enable email with index 4, enter the following command: racadm set iDRAC.EmailAlert.Enable.4 1 2.
• Using set command: racadm set iDRAC.RemoteHosts.SMTPServerIPAddress • Using config command: racadm config -g cfgRemoteHosts -o cfgRhostsSmtpServerIpAddr Configuring WS Eventing The WS Eventing protocol is used for a client service (subscriber) to register interest (subscription) with a server (event source) for receiving messages containing the server events (notifications or event messages).
Message ID Description DIS Auto-Discovery ENC Storage Enclosr FAN Fan Event FSD Debug HWC Hardware Config IPA DRAC IP Change ITR Intrusion JCP Job Control LC Lifecycle Contr LIC Licensing LNK Link Status LOG Log event MEM Memory NDR NIC OS Driver NIC NIC Config OSD OS Deployment OSE OS Event PCI PCI Device PDR Physical Disk PR Part Exchange PST BIOS POST PSU Power Supply PSUA PSU Absent PWR Power Usage RAC RAC Event 181
Message ID Description RDU Redundancy RED FW Download RFL IDSDM Media RFLA IDSDM Absent RFM FlexAddress SD RRDU IDSDM Redundancy RSI Remote Service SEC Security Event SEL Sys Event Log SRD Software RAID SSD PCIe SSD STOR Storage SUP FW Update Job SWC Software Config SWU Software Change SYS System Info TMP Temperature TST Test Alert UEFI UEFI Event USR User Tracking VDR Virtual Disk VF vFlash SD card VFL vFlash Event VFLA vFlash Absent VLT Voltage 182
Message ID Description VME Virtual Media VRM Virtual Console WRK Work Note 183
Managing Logs 10 iDRAC provides Lifecycle log that contains events related to system, storage devices, network devices, firmware updates, configuration changes, license messages, and so on. However, the system events are also available as a separate log called System Event Log (SEL). The lifecycle log is accessible through iDRAC Web interface, RACADM, and WS-MAN interface. When the size of the lifecycle log reaches 800 KB, the logs are compressed and archived.
If no arguments are specified, the entire log is displayed. To display the number of SEL entries: racadm getsel -i To clear the SEL entries: racadm clrsel For more information, see iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/manuals. Viewing System Event Log Using iDRAC Settings Utility You can view the total number of records in the System Event Log (SEL) using the iDRAC Settings Utility and clear the logs. To do this: 1.
Filtering Lifecycle Logs Exporting Lifecycle Controller Logs Using Web Interface Adding Comments to Lifecycle Logs Viewing Lifecycle Log Using Web Interface To view the Lifecycle Logs, click Overview → Server → Logs → Lifecycle Log.The Lifecycle Log page is displayed. For more information about the options, see the iDRAC Online Help. Filtering Lifecycle Logs You can filter logs based on category, severity, keyword, or date range. To filter the lifecycle logs: 1.
• Local — Export the Lifecycle Controller logs to a location on the local system. NOTE: While specifying the network share settings, it is recommended to avoid special characters for user name and password or percent encode the special characters. For information about the fields, see the iDRAC Online Help. 3. Click Export to export the log to the specified location. Exporting Lifecycle Controller Logs Using RACADM To export the Lifecycle Controller logs using RACADM, use the lclog export command.
Configuring Remote System Logging Using RACADM To configure the remote syslog server settings, use one of the following: • Objects in the cfgRemoteHosts group with the config command. • Objects in the iDRAC.SysLog group with the set command. For more information, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/manuals.
Monitoring and Managing Power 11 You can use iDRAC to monitor and manage the power requirements of the managed system. This helps to protect the system from power outages by appropriately distributing and regulating the power consumption on the system. The key features are: • Power Monitoring — View the power status, history of power measurements, the current averages, peaks, and so on for the managed system.
Monitoring Power Using RACADM To view the power monitoring information, use the System.Power group objects with the get command or the cfgServerPower object with the getconfig command. For more information, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/manuals. Setting Warning Threshold for Power Consumption You can set the warning threshold value for the power consumption sensor in the rack and tower systems.
3. • Power Off System • NMI (Non-Masking Interrupt) • Graceful Shutdown • Reset System (warm boot) • Power Cycle System (cold boot) Click Apply. For more information, see the iDRAC Online Help. Executing Power Control Operations Using RACADM To perform power actions, use the serveraction command. For more information, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/manuals.
650W to 525W. From that point onwards, the system's performance is dynamically adjusted to maintain power consumption so as to not exceed the user-specified threshold of 525W. If the power cap value is set to be lower than the minimum recommended threshold, iDRAC may not be able maintain the requested power cap. You can specify the value in Watts, BTU/hr, or as a percentage (%) of the recommended maximum power limit.
NOTE: The Power Configuration link is available only if the server power supply unit supports power monitoring. The iDRAC Settings Power Configuration page is displayed. 2. Select Enabled to enable the Power Cap Policy Else, select Disabled. 3. Use the recommended settings, or under User Defined Power Cap Policy, enter the required limits. For more information about the options, see the iDRAC Settings Utility Online Help. 4. Click Back, click Finish, and then click Yes.
• System.Power.PFC.Enable For more information, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/manuals. Configuring Power Supply Options Using iDRAC Settings Utility To configure the power supply options: 1. In iDRAC Settings utility, go to Power Configuration. NOTE: The Power Configuration link is available only if the server power supply unit supports power monitoring. The iDRAC Settings Power Configuration page is displayed. 2.
12 Inventory, Monitoring, and Configuring Network Devices You can inventory, monitor, and configure the following network devices: • Network Interface Cards (NICs) • Converged Network Adapters (CNAs) • LAN On Motherboards (LOMs) • Network Daughter Cards (NDCs) • Mezzanine cards (only for blade servers) Related Links Inventory and Monitoring FC HBA Devices Dynamic Configuration of Virtual Addresses, Initiator, and Storage Target Settings Inventory and Monitoring Network Devices You can remotely m
Additional properties may be displayed when using RACADM or WS-MAN in addition to the properties displayed in the iDRAC Web interface. Inventory and Monitoring FC HBA Devices You can remotely monitor the health and view the inventory of the Fibre Channel Host Bus Adapters (FC HBA) devices in the managed system. The Emulex and QLogic (except FC8) FC HBAs are supported.
• • • View and configure the virtual addresses for network devices (for example, NIC, CNA, FC HBA) Configure the initiator (for iSCSI and FCoE) and storage target settings (for iSCSI, FCoE, and FC) Specify persistence or clearance of the configured values over a system AC power loss, cold, and warm system resets.
Manufacturer Emulex Type • QLE2662 PCIe FC16 • • • • • • • • LPM16002 Mezz FC16 LPe16000 PCIe FC16 LPe16002 PCIe FC16 LPM16002 Mezz FC16 OCm14104-UX-D rNDC 10Gb OCm14102-U2-D bNDC 10Gb OCm14102-U3-D Mezz 10Gb Ce14102-UX-D PCIe 10Gb NOTE: I/O Identity Optimization is not supported on the following cards: • Intel x520 Mezz 10 GB • Mellanox cards Supported BIOS Version for I/O Identity Optimization In 13th generation Dell PowerEdge servers, the required BIOS version is available by default.
Enabling or Disabling I/O Identity Optimization Using Web Interface To enable or disable I/O Identity Optimization: 1. In the iDRAC Web interface, go to Overview → Hardware → Network Devices. The Network Devices page is displayed. 2. Click the I/O Identity Optimization tab, select the I/O Identity Optimization option to enable this feature. To disable, clear this option. 3. Click Apply to apply the setting.
Default Values for Persistence Policy Persistence Policy AC Power Loss Cold Boot Warm Boot Virtual Address: Auxiliary Not selected Powered Devices Selected Selected Virtual Address: NonAuxiliary Powered Devices Not selected Not selected Selected Initiator Selected Selected Selected Storage Target Selected Selected Selected Related Links Enabling or Disabling I/O Identity Optimization Configuring Persistence Policy Settings Using iDRAC Web Interface To configure the persistence policy: 1.
Table 23. iSCSI Initiator —Default Values iSCSI Initiator Default Values in IPv4 mode Default Values in IPv6 mode IscsiInitiatorIpAddr 0.0.0.0 :: IscsiInitiatorIpv4Addr 0.0.0.0 0.0.0.0 IscsiInitiatorIpv6Addr :: :: IscsiInitiatorSubnet 0.0.0.0 0.0.0.0 IscsiInitiatorSubnetPrefix 0 0 IscsiInitiatorGateway 0.0.0.0 :: IscsiInitiatorIpv4Gateway 0.0.0.0 0.0.0.0 IscsiInitiatorIpv6Gateway :: :: IscsiInitiatorPrimDns 0.0.0.0 :: IscsiInitiatorIpv4PrimDns 0.0.0.0 0.0.0.
iSCSI Storage Target Attributes Default Values in IPv4 mode Default Values in IPv6 mode FirstTgtChapId Value Cleared Value Cleared FirstTgtChapPwd Value Cleared Value Cleared FirstTgtIpVer Ipv4 ConnectSecondTgt Disabled Disabled SecondTgtIpAddress 0.0.0.
Managing Storage Devices 13 In the iDRAC 2.00.00.00 release, iDRAC expands its agent-free management to include direct configuration of the new PERC9 controllers. It enables you to remotely configure the storage components attached to your system at run-time. These components include RAID and non-RAID controllers and the channels, ports, enclosures, and disks attached to them.
alarms, and so on) associated with external enclosures. Physical disks can be contained in an enclosure or attached to the backplane of a system. In addition to managing the physical disks contained in the enclosure, you can monitor the status of the fans, power supply, and temperature probes in an enclosure. You can hot plug enclosures. Hot plugging is defined as adding of a component to a system while the operating system is still running.
concepts, as well as some familiarity with how the RAID controllers and operating system view disk space on your system. What Is RAID? RAID is a technology for managing the storage of data on the physical disks that reside or are attached to the system. A key aspect of RAID is the ability to span physical disks so that the combined storage capacity of multiple physical disks can be treated as a single, extended disk space.
• 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.
• RAID Level 0 (Striping) • RAID Level 1 (Mirroring) • RAID Level 5 (Striping With Distributed Parity) • RAID Level 6 (Striping With Additional Distributed Parity) • RAID Level 50 (Striping Over RAID 5 Sets) • RAID Level 60 (Striping Over RAID 6 Sets) • RAID Level 10 (Striping Over Mirror Sets) RAID Level 0 (Striping) RAID 0 uses data striping, which is writing data in equal-sized segments across the physical disks. RAID 0 does not provide data redundancy.
RAID 1 characteristics: • Groups n + n disks as one virtual disk with the capacity of n disks. The controllers currently supported by Storage Management allow the selection of two disks when creating a RAID 1. Because these disks are mirrored, the total storage capacity is equal to one disk. • Data is replicated on both the disks. • When a disk fails, the virtual disk still works. The data is read from the mirror of the failed disk. • Better read performance, but slightly slower write performance.
RAID 5 characteristics: • Groups n disks as one large virtual disk with a capacity of (n-1) disks. • Redundant information (parity) is alternately stored on all disks. • When a disk fails, the virtual disk still works, but it is operating in a degraded state. The data is reconstructed from the surviving disks. • Better read performance, but slower write performance. • Redundancy for protection of data.
RAID 6 characteristics: • Groups n disks as one large virtual disk with a capacity of (n-2) disks. • Redundant information (parity) is alternately stored on all disks. • The virtual disk remains functional with up to two disk failures. The data is reconstructed from the surviving disks. • Better read performance, but slower write performance. • Increased redundancy for protection of data. • Two disks per span are required for parity. RAID 6 is more expensive in terms of disk space.
RAID 50 characteristics: • Groups n*s disks as one large virtual disk with a capacity of s*(n-1) disks, where s is the number of spans and n is the number of disks within each span. • Redundant information (parity) is alternately stored on all disks of each RAID 5 span. • Better read performance, but slower write performance. • Requires as much parity information as standard RAID 5. • Data is striped across all spans. RAID 50 is more expensive in terms of disk space.
RAID 60 characteristics: • Groups n*s disks as one large virtual disk with a capacity of s*(n-2) disks, where s is the number of spans and n is the number of disks within each span. • Redundant information (parity) is alternately stored on all disks of each RAID 6 span. • Better read performance, but slower write performance. • Increased redundancy provides greater data protection than a RAID 50. • Requires proportionally as much parity information as RAID 6.
RAID 10 characteristics: • Groups n disks as one large virtual disk with a capacity of (n/2) disks, where n is an even integer. • Mirror images of the data are striped across sets of physical disks. This level provides redundancy through mirroring. • When a disk fails, the virtual disk still works. The data is read from the surviving mirrored disk. • Improved read performance and write performance. • Redundancy for protection of data.
RAID Level Data Availability Read Performanc e Write Performanc e Rebuild Performanc e Minimum Disks Required Suggested Uses logs, and critical information. RAID 5 Good Sequential reads: good. Transactiona l reads: Very good Fair, unless using writeback cache Fair N + 1 (N = at least two disks) Databases and other read intensive transactional uses. RAID 10 Excellent Very Good Fair Good 2N x X Data intensive environment s (large records).
Supported Controllers Supported RAID Controllers The iDRAC interfaces support the following PERC9 controllers: • PERC H830 • PERC H730P • PERC H730 • PERC H330 The iDRAC interfaces support the following PERC8 controllers: • PERC H810 • PERC H710P • PERC H710 • PERC H310 Supported Non-RAID Controllers The iDRAC interfaces supports 12Gbps SAS HBA External Adapter. NOTE: iDRAC does not support software RAID.
Feature Name PERC 9 Controllers PERC 8 Controllers PCIe SSD H830 H730 H730 P H330 H810 H710P H710 H310 Check virtual disk consistency Real- Realtime time Realtime Realtime Staged Staged Staged Staged Not applica ble Cancel check consistency Real- Realtime time Realtime Realtime Not applica ble Not Not applicabl applica e ble Not applica ble Not applica ble Initialize virtual disks Real- Realtime time Realtime Realtime Staged Staged Staged Staged Not applica ble Cancel ini
Feature Name PERC 9 Controllers PERC 8 Controllers PCIe SSD H830 H730 H730 P H330 H810 H710P H710 H310 Check Consistency Rate Real- Realtime time Realtime Realtime Staged Staged Staged Staged Not applica ble Rebuild Rate Real- Realtime time Realtime Realtime Staged Staged Staged Staged Not applica ble BGI Rate Real- Realtime time Realtime Realtime Staged Staged Staged Staged Not applica ble Reconstruct Rate Real- Realtime time Realtime Realtime Staged Staged Staged
Feature Name PERC 9 Controllers PERC 8 Controllers H710 H830 H730 H730 P H330 H810 H710P Configure Backplane mode Real- Realtime time Realtime Realtime Not applica ble Not Not applicabl applica e ble Not applica ble Not applica ble Blink or unblink component LEDs Real- Realtime time Realtime Realtime Realtime Realtime Realtime Realtime Realtime H310 PCIe SSD Inventory and Monitoring Storage Devices You can remotely monitor the health and view the inventory of the following Comprehe
For more information on the displayed properties and to use the filter options, see iDRAC Online Help. Monitoring Storage Device Using RACADM To view the storage device information, use the raid or storage subcommand. For more information, see the iDRAC RACADM Command Line Reference Guideavailable at dell.com/support/manuals. Monitoring Backplane Using iDRAC Settings Utility In the iDRAC Settings utility, go to System Summary. The iDRAC Settings.System Summary page is displayed.
When deleting virtual disks, all assigned global hot spares may be automatically unassigned when the last virtual disk associated with the controller is deleted. If you reset the configuration, the virtual disks are deleted and all the hot spares are unassigned. You must be familiar with the size requirements and other considerations associated with hot spares. Before assigning a physical disk as a global hot spare: • Make sure that Lifecycle Controller is enabled.
1. Press while restarting the server, and then select the required controller. 2. Press and select the Convert to RAID capable option, and then complete the operation. NOTE: • This task is not supported on PERC hardware controllers running in HBA mode. • This task is only supported as a staged operation. Convert To Non-RAID Disk This task converts a disk to a Non-RAID disk.
Before creating a virtual disk, you should be familiar with the information in Considerations Before Creating Virtual Disks. You can create a Virtual Disk using the Physical Disks attached to the PERC controller. To create a Virtual Disk, you must have the Server Control user privilege. You can create a maximum of 64 virtual drives and a maximum of 16 virtual drives in the same drive group. You cannot create a virtual disk if: • Physical disk drives are not available for virtual disk creation.
b. From the Controller drop-down menu, select the controller for which you want to create the virtual disk. c. From the Layout drop-down menu, select the RAID level for the Virtual Disk. Only those RAID levels supported by the controller appear in the drop-down menu and it is based on the RAID levels are available based on the total number of physical disks available. d. Select the Media Type, Stripe Size, Read Policy, Write Policy, Disk Cache Policy, T10 PI Capability.
performance since subsequent read requests can retrieve data quickly from the cache then from the disk. However, data loss may occur in the event of a system failure which prevents that data from being written on a disk. Other applications may also experience problems when actions assume that the data is available on the disk. • Force Write Back — The write cache is enabled regardless of whether the controller has a battery.
Initializing Virtual Disks Initializing virtual disks erases the all the data on the disk but does not change the virtual disk configuration. You must initialize a virtual disk that is configured before it is used. NOTE: Do not initialize virtual disks when attempting to recreate an existing configuration. You can perform a fast initialization, a full Initialization, or cancel the initialization operation. NOTE: The cancel initialization is a real-time operation.
NOTE: Full initialize is supported only in real-time. Only few controllers support full initialization. Encrypting Virtual Disks When encryption is disabled on a controller (that is, the security key is deleted), manually enable encryption for virtual disks created using SED drives. If the virtual disk is created after encryption is enabled on a controller, the virtual disk is automatically encrypted.
– No Read Ahead – Read Ahead • Edit Policy: Write Cache — Change the write cache policy to one of the following options: – Write Through – Write Back – Force Write Back • Edit Policy: Disk Cache — Change the disk cache policy to one of the following options: – Default – Enabled – Disabled • Initialize: Fast — Updates the metadata on the physical disks so that all the disk space is available for future write operations.
• Create, change, or delete security keys Related Links Configuring Controller Properties Importing or Auto Importing Foreign Configuration Clearing Foreign Configuration Resetting Controller Configuration Supported Controllers Summary of Supported Features for Storage Devices Convert To RAID Capable Disk Convert To Non-RAID Disk Configuring Controller Properties You can configure the following properties for the controller: • Patrol read mode (auto or manual) • Start or stop patrol read if patrol rea
In addition, the Patrol Read operation suspends during heavy I/O activity and resumes when the I/O is complete. NOTE: For more information on how often the Patrol Read operation runs when in auto mode, see the respective controller documentation. Load Balance The Load Balance property provides the ability to automatically use both controller ports or connectors connected to the same enclosure to route I/O requests. This property is available only on SAS controllers.
each encryption-capable controller. The security key is managed using the Local Key Management (LKM) feature. LKM is used to generate the key ID and the password or key required to secure the virtual disk. If you are using LKM, you must create the encryption key by providing the Security Key Identifier and the Passphrase. This task is not supported on PERC hardware controllers running in HBA mode.
• To create, modify, or delete security key to encrypt virtual drives: racadm storage createsecuritykey: -key -passwd racadm storage modifysecuritykey: -key -oldpasswd -newpasswd racadm storage deletesecuritykey: Importing or Auto Importing Foreign Configuration A foreign configuration is data residing on physical disks that have been moved from one controller to another.
This task is not supported on PERC hardware controllers running in HBA mode. NOTE: It is not recommended to remove an external enclosure cable while the operating system is running on the system. Removing the cable could result in a foreign configuration when the connection is re-established. You can manage foreign configurations in the following cases: • All the physical disks in a configuration are removed and re-inserted. • Some of the physical disks in a configuration are removed and re-inserted.
physical disk contains a foreign configuration (virtual disk) by checking the physical disk state. If the physical disk state is Foreign, then the physical disk contains all or some portion of a virtual disk. You can clear or erase the virtual disk information from the newly attached physical disks. The Clear Foreign Configuration operation permanently erases all data residing on the physical disks that are added to the controller.
Based on the selected operation mode, the settings are applied. Resetting Controller Configuration Using RACADM To reset the controller configuration, use the following command: racadm storage resetconfig: For more information, see the iDRAC RACADM Command Line Reference Guide available at dell.com/ esmmanuals. 12Gbps SAS HBA Adapter Operations The non-RAID controllers are the HBAs that do not have few RAID capabilities. They do not support virtual disks.
SMART performs predictive failure analysis on each disk and sends alerts if a disk failure is predicted. The controllers check physical disks for failure predictions and, if found, pass this information to iDRAC. iDRAC immediately logs an alert. Controller Operations in Non-RAID (HBA) Mode If the controller is in non-RAID mode (HBA mode), then: • Virtual disks or hot spares are not available. • Security state of the controller is disabled. • All physical disks are in non-RAID mode.
Level Cell (SLC) and Multi-Level Cell (MLC) NAND flash technology with a high-speed PCIe 2.0 or PCIe 3.0 compliant interface. Using iDRAC interfaces, you can view and configure NVMe PCIe SSDs. The key features of PCIe SSD are: • Hot plug capability • High-performance device The PCIe SSD subsystem consists of the Backplane, PCIe Extender card which is attached to the backplane of the system and provides PCIe connectivity for up to four or eight PCIe SSDs at the front of the chassis and the PCIe SSDs.
To view PCIe SSD backplane information: racadm storage get enclosures NOTE: For all the mentioned commands, PERC devices are also displayed. For more information, see the iDRAC RACADM Command Line Reference Guide available at dell.com/ esmmanuals. Preparing to Remove PCIe SSD PCIe SSDs support orderly hot swap allowing you to add or remove a device without halting or rebooting the system in which the devices are installed.
If the job is not created, a message indicating that the job creation was not successful is displayed. Also, the message ID and the recommended response action is displayed. If the job is created successfully, a message indicating that the job ID is created for the selected controller is displayed. Click Job Queue to view the progress of the job in the Job Queue page. If pending operation is not created, an error message is displayed.
4. From the Apply Operation Mode drop-down menu, select one of the following options: • At Next Reboot — Select this option to apply the actions during the next system reboot. This is the default option for PERC 8 controllers. • At Scheduled Time — Select this option to apply the actions at a scheduled day and time: – Start Time and End Time — Click the calendar icons and select the days. From the drop-down menus, select the time. The action is applied between the start time and end time.
Viewing Universal Slots Setting SGPIO Mode Configuring Backplane Mode The 13th generation Dell PowerEdge servers supports a new internal storage topology, where two storage controllers (PERCs) can be connected to a set of internal drives through a single expander. This configuration is used for high performance mode with no failover or High Availability (HA) functionality. The expander splits the internal drive array between the two storage controllers.
4. • Split From the Apply Operation Mode drop-down menu, select Apply Now to apply the actions immediately, and then click Apply. 5. Go to the Job Queue page and verify that it displays the status as Completed for the job. 6. Power cycle the system for the setting to take affect. A job ID is created. Configuring Enclosure Using RACADM To configure the enclosure or backplane, use the BackplaneMode object with the set subcommand. For example, to set the BackplaneMode attribute to split mode: 1.
The output is: BackplaneRequestedMode=SplitMode 9. Run the following command to cold reboot the server: serveraction powercycle 10. After the system completes POST and CSIOR, type the following command to verify the backplanerequestedmode: get storage.enclosure.1.backplanerequestedmode The output is: BackplaneRequestedMode=None 11. Run the following to verify is the backplane mode is set to split mode: get storage.enclosure.1.backplanecurrentmode The output is: BackplaneCurrentMode=SplitMode 12.
Setting SGPIO Mode The storage controller can connect to the backplane in I2C mode (default setting for Dell backplanes) or Serial General Purpose Input/Output (SGPIO) mode. This connection is required for blinking LEDs on the drives. Dell PERC controllers and backplane support both these modes. To support certain channel adapters, the backplane mode must be changed SGPIO mode. The SGPIO mode is only supported for passive backplanes.
2. • Overview → Storage → Pending Operations Select one of the following from the Apply Operation Mode drop-down menu: • Apply Now — Select this option to apply the settings immediately. This option is available for PERC 9 controllers only. If there are jobs to be completed, then this option is grayed-out. This job take at least 2 minutes to complete. • At Next Reboot — Select this option to apply the settings during the next system reboot. This is the default option for PERC 8 controllers.
The Pending Operations page is displayed. 2. From the Component drop-down menu, select the controller for which you want to view, commit, or delete the pending operations. The list of pending operations is displayed for the selected controller. NOTE: • 3. 4. Pending operations are created for import foreign configuration, clear foreign configuration, security key operations, and encrypt virtual disks. But, they are not displayed in the Pending Operations page and in the Pending Operations pop-up message.
Storage Devices — Apply Operation Scenarios Case 1: Selected an Apply Operation (Apply Now, At Next Reboot, or At Scheduled Time) and there are no existing pending operations If you have selected Apply Now, At Next Reboot, or At Scheduled Time and then clicked Apply, first the pending operation is created for the selected storage configuration operation. • If the pending operation is successful and there are no prior existing pending operations, then the job is created.
– Click OK to remain on the page to perform more storage configuration operations. – Click Pending Operations to view the pending operations for the device. Until the job is created on the selected controller, these pending operations are not applied. • If the pending operation is not created successfully and if there are no existing pending operations, then an error message is displayed.
• 2. Overview → Storage → Virtual Disks → Identify- Displays the Identify Virtual Disks page where you can blink or unblink the virtual disks. If you are on the Identify Component LED page: • Select or deselect all component LEDs — Select the Select/Deselect All option and click Blink to start blinking the component LEDs. Similarly, click Unblink to stop blinking the component LEDs. • 3.
Configuring and Using Virtual Console 14 You can use the virtual console to manage a remote system using the keyboard, video, and mouse on your management station to control the corresponding devices on a managed server. This is a licensed feature for rack and tower servers. It is available by default in blade servers. The key features are: • A maximum of six simultaneous Virtual Console sessions are supported. All the sessions view the same managed server console simultaneously.
Screen Resolution Refresh Rate (Hz) 1024x768 60, 70, 72, 75, 85 1280x1024 60 It is recommended that you configure your monitor display resolution to 1280x1024 pixels or higher. NOTE: If you have an active Virtual Console session and a lower resolution monitor is connected to the Virtual Console, the server console resolution may reset if the server is selected on the local console. If the system is running a Linux operating system, an X11 console may not be viewable on the local monitor.
Related Links Configuring Virtual Console Configuring IE to Use ActiveX Plug-in You must configure the IE browser settings before you launch and run ActiveX based Virtual Console and Virtual Media applications. The ActiveX applications are delivered as signed CAB files from the iDRAC server. If the plug-in type is set to Native-ActiveX type in Virtual console, when you try to launch the Virtual Console, the CAB file is downloaded to the client system and ActiveX based Virtual Console is launched.
Additional Settings for Windows Vista or Newer Microsoft Operating Systems The Internet Explorer browsers in Windows Vista or newer operating systems have an additional security feature called Protected Mode. To launch and run ActiveX applications in Internet Explorer browsers with Protected Mode: 1. Run IE as an administrator. 2. Go to Tools → Internet Options → Security → Trusted Sites. 3. Make sure that the Enable Protected Mode option is not selected for Trusted Sites zone.
The Java Cache viewer is displayed. 2. Delete the items titled iDRAC Virtual Console Client. Importing CA Certificates to Management Station When you launch Virtual Console or Virtual Media, prompts are displayed to verify the certificates. If you have custom Web server certificates, you can avoid these prompts by importing the CA certificates to the Java or ActiveX trusted certificate store.
Configuring Web Browsers to Use Virtual Console Launching Virtual Console Configuring Virtual Console Using Web Interface To configure Virtual Console using iDRAC Web interface: 1. Go to Overview → Server → Virtual Console. The Virtual Console page is displayed. 2. Enable virtual console and specify the required values. For information about the options, see the iDRAC Online Help. 3. Click Apply. The virtual console is configured.
While launching Virtual Console using 32-bit or 64-bit IE browsers, the required plug-in (Java or ActiveX) is available in the respective browser. The Internet Options settings are common for both the browsers. While launching the Virtual Console using Java plug-in, occasionally you may see a Java compilation error. To resolve this, go to Java control panel → General → Network Settings and select Direct Connection.
• Control Panel → Power Options → High–Performance → Advanced Settings → Hard Disk → Turnoff Hard Disk After Launching Virtual Console Using URL To launch the Virtual Console using the URL: 1. Open a supported Web browser and in the address box, type the following URL in lower case: https://iDRAC_ip/console 2.
NOTE: If the remote server is powered off, the message ’No Signal’ is displayed. The Virtual Console Viewer title bar displays the DNS name or the IP address of the iDRAC you are connected to from the management station. If iDRAC does not have a DNS name, then the IP address is displayed.
If synchronization problems continue, do the following additional change in the /.gconf/ desktop/gnome/peripherals/mouse/%gconf.xml file: Change the values for motion_threshold and motion_acceleration to -1. If you turn off mouse acceleration in GNOME desktop, in the Virtual Console viewer, go to Tools → Session Options → Mouse. Under Mouse Acceleration tab, select None.
Java-based Virtual Console Session running on Windows Operating System • Ctrl+Alt+Del key is not sent to the managed system, but always interpreted by the management station.
– echo "1" > /proc/sys/kernel/sysrq • When Pass all keystrokes to server is enabled, the magic SysRq keys are sent to the operating system on the managed system. The key sequence behavior to reset the operating system, that is reboot without un-mounting or sync, depends on whether the magic SysRq is enabled or disabled on the management station: – If SysRq is enabled on the management station, then or resets the management station irrespective of the system’s state.
Managing Virtual Media 15 Virtual media allows the managed server to access media devices on the management station or ISO CD/DVD images on a network share as if they were devices on the managed server. Using the Virtual Media feature, you can: • Remotely access media connected to a remote system over the network • Install applications • Update drivers • Install an operating system on the managed system This is a licensed feature for rack and tower servers.
Figure 4. Virtual Media Setup Supported Drives and Devices The following table lists the drives supported through virtual media. Table 27. Supported Drives and Devices Drive Supported Storage Media Virtual Optical Drives • • • • • Virtual floppy drives USB flash drives • Legacy 1.44 floppy drive with a 1.
Configuring Virtual Media Using RACADM To configure the virtual media, • Use the objects in the iDRAC.VirtualMedia group with the set command. • Use the objects in the cfgRacVirtual group with the config command. For more information, see the RACADM Command Line Reference Guide for iDRAC available at dell.com/support/manuals. Configuring Virtual Media Using iDRAC Settings Utility You can attach, detach, or auto-attach virtual media using the iDRAC Settings utility. To do this: 1.
If the RFS connection is not active and you attempt to launch the Virtual Media client, the client launches successfully. You can then use the Virtual Media client to map devices and files to the Virtual Media virtual drives. Related Links Configuring Web Browsers to Use Virtual Console Configuring Virtual Media Launching Virtual Media Using Virtual Console Before you launch Virtual Media through the Virtual Console, make sure that: • Virtual Console is enabled.
The following message is displayed: Virtual Console has been disabled. Do you want to continue using Virtual Media redirection? 3. Click OK . The Virtual Media window is displayed. 4. From the Virtual Media menu, click Map CD/DVD or Map Removable Disk. For more information, see Mapping Virtual Drive. NOTE: The virtual device drive letters on the managed system do not coincide with the physical drive letters on the management station.
If Virtual Media is connected, this information is displayed. If Virtual Media is not connected, the “Virtual Media is not connected” message is displayed. If the Virtual Media is launched without using the Virtual Console, then the Virtual Media section is displayed as a dialog box. It provides information about the mapped devices. Resetting USB To reset the USB device: 1. In the Virtual Console viewer, click Tools → Stats. The Stats window is displayed. 2. Under Virtual Media, click USB Reset.
If the image is created in the default path (Desktop), when you select Map Removable Disk, the created image is available for selection in the drop-down menu. If image is created in a different location, when you select Map Removable Disk, the created image is not available for selection in the drop-down menu. Click Browse to specify the image. 4. Select Read-only to map writable devices as read-only. For CD/DVD devices, this option is enabled by default and you cannot disable it. 5.
To enable the managed system to boot: 1. Boot the managed system. 2. Press to enter the System Setup page. 3. Go to System BIOS Settings → Boot Settings → BIOS Boot Settings → Boot Sequence. In the pop-up window, the virtual optical drives and virtual floppy drives are listed with the standard boot devices. 4. Make sure that the virtual drive is enabled and listed as the first device with bootable media. If required, follow the on-screen instructions to modify the boot order. 5.
Installing and Using VMCLI Utility 16 The Virtual Media Command Line Interface (VMCLI) utility is an interface that provides virtual media features from the management station to iDRAC on the managed system. Using this utility you can access virtual media features, including image files and physical drives, to deploy an operating system on multiple remote systems in a network. NOTE: You can run the VMCLI utility only on the management station that is installed with 32–bit operating system.
VMCLI Syntax The VMCLI interface is identical on both Windows and Linux systems. The VMCLI syntax is: VMCLI [parameter] [operating_system_shell_options] For example, vmcli -r iDRAC-IP-address:iDRAC-SSL-port The parameter enables VMCLI to connect to the specified server, access iDRAC, and map to the specified virtual media. NOTE: VMCLI syntax is case-sensitive. To ensure security, it is recommended to use the following VMCLI parameters: • vmcli -i — Enables an interactive method of starting VMCLI.
If the file is not write-protected, Virtual Media may write to the image file. To make sure that Virtual Media does not write to the media: • Configure the operating system to write-protect a floppy image file that must not be overwritten. • Use the write-protection feature of the device. When virtualizing read-only image files, multiple sessions can use the same image media simultaneously. When virtualizing physical drives, only one session can access a given physical drive at a time.
Managing vFlash SD Card 17 The vFlash SD card is a Secure Digital (SD) card that plugs into the vFlash SD card slot in the system. You can use a card with a maximum of 16 GB capacity. After you insert the card, you must enable vFlash functionality to create and manage partitions. vFlash is a licensed feature. If the card is not available in the system's vFlash SD card slot, the following error message is displayed in the iDRAC Web interface at Overview → Server → vFlash: SD card not detected.
Viewing vFlash SD Card Properties Using Web Interface To view the vFlash SD card properties, in the iDRAC Web interface, go to Overview → Server → vFlash. The SD Card Properties page is displayed. For information about the displayed properties, see the iDRAC Online Help. Viewing vFlash SD Card Properties Using RACADM To view the vFlash SD card properties using RACADM, use one of the following: • Use the cfgvFlashSD object with the getconfig command.
Enabling or Disabling vFlash Functionality Using RACADM To enable or disable the vFlash functionality using RACADM, use one of the following: • Using config command: – To enable vFlash: racadm config -g cfgvFlashsd -o cfgvflashSDEnable 1 – To disable vFlash: racadm config -g cfgvFlashsd -o cfgvflashSDEnable 0 • Using set command: – To enable vFlash: racadm set iDRAC.vflashsd.Enable 1 – To disable vFlash: racadm set iDRAC.vflashsd.
• Using vFlashSD command: racadm vflashsd initialize • Using set command: racadm set iDRAC.vflashsd.Initialized 1 All existing partitions are deleted and the card is reformatted. For more information about these commands, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/manuals and dell.com/esmmanuals. Initializing vFlash SD Card Using iDRAC Settings Utility To initialize the vFlash SD card using iDRAC Settings utility: 1.
• Attaching or Detaching Partitions • Deleting Existing Partitions • Downloading Partition Contents • Booting to a Partition NOTE: If you click any option on the vFlash pages when an application such as WS-MAN, iDRAC Settings utility, or RACADM is using vFlash, or if you navigate to some other page in the GUI, iDRAC may display the message: vFlash is currently in use by another process. Try again after some time.
Creating a Partition Using an Image File You can create a new partition on the vFlash SD card using an image file (available in the .img or .iso format.) The partitions are of emulation types: Floppy (.img), Hard Disk (.img), or CD (.iso). The created partition size is equal to the image file size. Before creating a partition from an image file, make sure that: • You have Access Virtual Media privilege. • The card is initialized. • The card is not write-protected.
NOTE: This feature is not supported in local RACADM. NOTE: Creating vFlash partition from an image file located on the CFS or NFS IPv6 enabled network share is not supported. Formatting a Partition You can format an existing partition on the vFlash SD card based on the type of file system. The supported file system types are EXT2, EXT3, FAT16, and FAT32. You can only format partitions of type Hard Disk or Floppy, and not CD. You cannot format read-only partitions.
racadm vflashpartition status -a NOTE: The -a option is valid only with the status action. Modifying a Partition You can change a read-only partition to read-write or vice-versa. Before modifying the partition, make sure that: • The vFlash functionality is enabled. • You have Access Virtual Media privileges. NOTE: By default, a read-only partition is created. Modifying a Partition Using Web Interface To modify a partition: 1. In the iDRAC Web interface, go to Overview → Server → vFlash → Manage.
racadm set iDRAC.vflashpartition..EmulationType Attaching or Detaching Partitions When you attach one or more partitions, they are visible to the operating system and BIOS as USB mass storage devices. When you attach multiple partitions, based on the assigned index, they are listed in an ascending order in the operating system and the BIOS boot order menu. If you detach a partition, it is not visible in the operating system and the BIOS boot order menu.
racadm set iDRAC.vflashpartition..AttachState 0 Operating System Behavior for Attached Partitions For Windows and Linux operating systems: • The operating system controls and assigns the drive letters to the attached partitions. • Read-only partitions are read-only drives in the operating system. • The operating system must support the file system of an attached partition. Else, you cannot read or modify the contents of the partition from the operating system.
Before downloading the partition contents, make sure that: • You have Access Virtual Media privileges. • The vFlash functionality is enabled. • An initialize operation is not being performed on the card. • For a read-write partition, it must not be attached. To download the contents of the vFlash partition: 1. In the iDRAC Web interface, go to Overview → Server → vFlash → Download. The Download Partition page is displayed. 2.
Using SMCLP 18 The Server Management Command Line Protocol (SMCLP) specification enables CLI-based systems management. It defines a protocol for management commands transmitted over standard character oriented streams. This protocol accesses a Common Information Model Object Manager (CIMOM) using a human-oriented command set. The SMCLP is a sub-component of the Distributed Management Task Force (DMTF) SMASH initiative to streamline systems management across multiple platforms.
SMCLP prompts: • yx1x blade servers use -$. • yx1x rack and tower servers use admin->. • yx2x blade, rack, and tower servers use admin->. where, y is a alpha-numeric character such as M (for blade servers), R (for rack servers), and T (for tower servers) and x is a number. This indicates the generation of Dell PowerEdge servers. NOTE: Scripts using -$ can use these for yx1x systems, but starting with yx2x systems one script with admin-> can be used for blade, rack, and tower servers.
Table 31.
Target Definitions admin1/system1/sp1/settings1 Service Processor settings collection admin1/system1/sp1/settings1/ clpsetting1 CLP service settings data admin1/system1/sp1/clpsvc1 CLP service protocol service admin1/system1/sp1/clpsvc1/clpendpt* CLP service protocol endpoint admin1/system1/sp1/clpsvc1/tcpendpt* CLP service protocol TCP endpoint admin1/system1/sp1/jobq1 CLP service protocol job queue admin1/system1/sp1/jobq1/job* CLP service protocol job admin1/system1/sp1/pwrmgtsvc1 Power
Target Definitions admin1/system1/sp1/rolesvc3/Role1-3 CLP role admin1/system1/sp1/rolesvc3/Role1-3/ privilege1 CLP role privilege Related Links Running SMCLP Commands Usage Examples Navigating the MAP Address Space Objects that can be managed with SM-CLP are represented by targets arranged in a hierarchical space called the Manageability Access Point (MAP) address space. An address path specifies the path from the root of the address space to an object in the address space.
Using the -level Option The show -level option executes show over additional levels beneath the specified target. To see all targets and properties in the address space, use the -l all option. Using the -output Option The -output option specifies one of four formats for the output of SM-CLP verbs: text, clpcsv, keyword, and clpxml. The default format is text, and is the most readable output. The clpcsv format is a comma-separated values format suitable for loading into a spreadsheet program.
The following message is displayed: system1 has been reset successfully SEL Management The following examples show how to use the SMCLP to perform SEL-related operations on the managed system.
show help exit version • To view the SEL record: show/system1/logs1/log1 The following output is displayed: /system1/logs1/log1/record4 Properties: LogCreationClassName= CIM_RecordLog CreationClassName= CIM_LogRecord LogName= IPMI SEL RecordID= 1 MessageTimeStamp= 20050620100512.
MAP Target Navigation The following examples show how to use the cd verb to navigate the MAP. In all examples, the initial default target is assumed to be /. Type the following commands at the SMCLP command prompt: • To navigate to the system target and reboot: cd system1 reset The current default target is /. • To navigate to the SEL target and display the log records: cd system1 cd logs1/log1 show • To display current target: type cd . • To move up one level: type cd ..
Using iDRAC Service Module 19 The iDRAC Service Module is a software application that is recommended to be installed on the server (it is not installed by default). It complements iDRAC with monitoring information from the operating system. It does not have an interface but, complements iDRAC by providing additional data to work with iDRAC interfaces such as the Web interface, RACADM, and WSMAN.
• • • • • Replicate Lifecycle Controller logs to operating system logs Perform automatic system recovery options Populate Windows Management Instrumentation (WMI) Management Providers Integrate with Technical Support Report. This is applicable only if iDRAC Service Module Version 2.0 or later is installed. For more information, see Generating Tech Support Report. Integrate with NVMe Management for Prepare to Remove operation on a NVMe class PCIe SSD. For more information, see Preparing to Remove PCIe SSD.
The classes can be accessed using any of the standard WMI client interfaces. For more information, see the profile documents. The following example is using the DCIM_account class to illustrate the capability that WMI information feature provides in iDRAC Service Module. For the details of the supported classes and profiles, see the WSMAN profiles documentation available at Dell Tech Center.
Co-existence of OpenManage Server Administrator and iDRAC Service Module In a system, both OpenManage Server Administrator and the iDRAC Service Module can co-exist and continue to function correctly and independently. If you have enabled the monitoring features during the iDRAC Service Module installation, then after the installation is complete if the iDRAC Service Module detects the presence of OpenManage Server Administrator, it disables the set of monitoring features that overlap.
20 Using USB Port for Server Management In Dell PowerEdge 12th generation servers, all USB ports are dedicated to the server. With the 13th generation of servers, one of the front panel USB port is used by iDRAC for management purposes such as pre-provisioning and troubleshooting. The port has an icon to indicate that it is a management port. All 13th generation servers with LCD panel support this feature.
5. After using, disconnect the cable. The LED turns off. Configuring iDRAC Using Server Configuration Profile on USB Device With the new iDRAC Direct feature, you can configure iDRAC at-the-server. First configure the USB Management port settings in iDRAC, insert the USB device that has the server configuration profile, and then import the server configuration profile from the USB device to iDRAC.
• Allowed notifications: Email, SNMP trap, remote syslog and WS-Eventing. • Actions: None. An error message is displayed and logged to Lifecycle Controller log when: • You try to configure the USB management port without the Server Control user privilege. • A USB device is in use by iDRAC and you attempt to modify the USB Management Port Mode. • A USB device is in use by iDRAC and you remove the device. Configuring USB Management Port Using Web interface To configure the USB port: 1.
The iDRAC Settings Media and USB Port Settings page is displayed. 2. 3. From the USB Management Port Mode drop-down menu, do the following: • Automatic — USB Port is used by iDRAC or the server’s operating system. • Standard OS Use — USB port is used by the server OS. • iDRAC Direct only — USB pot is used by iDRAC.
• Set iDRAC Managed: USB XML Configuration to Enabled with default credentials or Enabled. Insert the USB key (that has the configuration.xml and the control.xml file) to the iDRAC USB port. 2. 3. The server configuration profile is discovered on the USB device in the System_Configuration_XML sub-directory under the USB device root directory. It is discovered in the following sequence: • -config.xml • -config.xml • config.xml A server configuration profile import job starts. 4.
• Service tag – Data is recorded after the import operation has either returned a job ID or returned an error. • Job ID – Data is recorded after the import operation has returned a job ID. • Start Date and Time of Job - Data is recorded after the import operation has returned a job ID. • Status – Data is recorded when the import operation returns an error or when the job results are available.
Using iDRAC Quick Sync 21 A few 13th generation Dell PowerEdge servers have the Quick Sync bezel that supports the Quick Sync feature. This feature enables at-the-server management with a mobile device. This allows you to view inventory and monitoring information and configure basic iDRAC settings (such as root credential setup and configuration of the first boot device) using the mobile device. You can configure iDRAC Quick Sync access for your mobile device (example, OpenManage Mobile) in iDRAC.
Configuring iDRAC Quick Sync Using iDRAC Web interface or RACADM, you can configure iDRAC Quick Sync feature to allow access to the mobile device: • Read-write access – Allows you to configure the basic iDRAC settings. • Read-only access – Allows you to view inventory and monitoring information. • Disabled access – Does not allow you to view information and configure settings. • Enables you to specify a time after which the Quick Sync mode is turned off.
The settings are applied. Using Mobile Device to View iDRAC Information To view iDRAC information from the mobile device, see the OpenManage Mobile User’s Guide available at dell.com/support/manuals for the steps.
Deploying Operating Systems 22 You can use any of the following utilities to deploy operating systems to managed systems: • Virtual Media Command Line Interface (CLI) • Virtual Media Console • Remote File Share Related Links Deploying Operating System Using VMCLI Deploying Operating System Using Remote File Share Deploying Operating System Using Virtual Media Deploying Operating System Using VMCLI Before you deploy the operating system using the vmdeploy script, make sure that: • VMCLI utility is
vmdeploy.bat -r -u -p [ -f { | < device-name>} | -c { |} ] [-i ] NOTE: vmdeploy does not support IPv6, since IPv6 does not support the IPMI tool. NOTE: The vmdeploy script processes the -r option slightly differently than the vmcli -r option.
NOTE: While creating the image file, follow standard network-based installation procedures, and mark the deployment image as read-only to make sure that each target system boots and executes the same deployment procedure. To deploy an operating system using RFS: 1. Using Remote File Share (RFS), mount the ISO or IMG image file to the managed system through NFS or CIFS. 2. Go to Overview → Setup → First Boot Device. 3. Set the boot order in the First Boot Device drop-down list to Remote File Share. 4.
If you update the iDRAC firmware from version 1.30.30 to 1.50.50 firmware while there is an active RFS connection and the Virtual Media Attach Mode is set to Attach or Auto Attach, the iDRAC attempts to reestablish the RFS connection after the firmware upgrade is completed and the iDRAC reboots. If you update the iDRAC firmware from version 1.30.30 to 1.50.
This displays the text that identifies the device (example, SCSI device sdc). This procedure also applies to Virtual Media when you are using Linux distributions in runlevel init 3. By default, the virtual media is not auto-mounted in init 3.
Configuring Virtual Media Setting First Boot Device Configuring iDRAC Installing Operating System From Multiple Disks 1. Unmap the existing CD/DVD. 2. Insert the next CD/DVD into the remote optical drive. 3. Remap the CD/DVD drive. Deploying Embedded Operating System On SD Card To install an embedded hypervisor on an SD card: 1. Insert the two SD cards in the Internal Dual SD Module (IDSDM) slots on the system. 2. Enable SD module and redundancy (if required) in BIOS. 3.
You can view the status, health, and the availability of IDSDM using iDRAC Web Interface or RACADM. The SD card redundancy status and failure events are logged to SEL, displayed on the front panel, and PET alerts are generated if alerts are enabled.
23 Troubleshooting Managed System Using iDRAC You can diagnose and troubleshoot a remote managed system using: • • • • • • • • • Diagnostic console Post code Boot and crash capture videos Last system crash screen System event logs Lifecycle logs Front panel status Trouble indicators System health Related Links Using Diagnostic Console Scheduling Remote Automated Diagnostics Viewing Post Codes Viewing Boot and Crash Capture Videos Viewing Logs Viewing Last System Crash Screen Viewing Front Panel Status Ha
reboot or maintenance cycle (similar to updates). When diagnostics are run, the results are collected and stored in the internal iDRAC storage. You can then export the results to an NFS or CIFS network share using the diagnostics export racadm command. You can also run diagnostics using the appropriate WSMAN command(s). For more information, see the WSMAN documentation. You must have iDRAC Express license to use remote automated diagnostics.
To export the last run remote diagnostics results, use the following command: racadm diagnostics export -f -l -u -p For more information about the options, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/manuals.
Viewing Logs You can view System Event Logs (SELs) and Lifecycle logs. For more information, see Viewing System Event Log and Viewing Lifecycle Log . Viewing Last System Crash Screen The last crash screen feature captures a screenshot of the most recent system crash, saves, and displays it in iDRAC. This is a licensed feature. To view the last crash screen: 1. Make sure that the last system crash screen feature is enabled. 2.
To view LCD front panel status using RACADM, use the objects in the System.LCD group. For more information, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/ support/manuals. Related Links Configuring LCD Setting Viewing System Front Panel LED Status To view the current system ID LED status, in iDRAC Web interface, go to Overview → Hardware → Front Panel.
CAUTION: You should only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by online or telephone service and support team. Damage due to servicing that is not authorized by Dell is not covered by your warranty. Read and follow the safety instructions that came with the product.
The report is generated in the standard ZIP format. The report contains information that is similar to the information available in the DSET report such as: • Hardware inventory for all components • System, Lifecycle Controller, and component attributes • Operating system and application information • Active Lifecycle Controller logs (archived entries are not included) • PCIe SSD logs • Storage controller logs After the report is generated, you can view the report.
NOTE: While specifying the network share settings, it is recommended to avoid special characters for user name and password or percent encode the special characters. • Click Advanced Export Options to select the following additional options: – RAID Controller Log – Enable Report Filtering under OS and Application Data Based on the options selected, the time taken to collect the data is displayed next to these options. 3.
NOTE: – CentOS is supported only for iDRAC Service Module 2.0 or later. – If the IPMI modules are not present, then you can install the respective modules from the OS distribution media. The service starts once the installation is complete. • On Windows operating system: – Check if the WMI service is running: * If WMI is stopped, OS Collector starts the WMI automatically and continues with the collection. * If WMI is disabled, OS Collector collection stops with an error message.
11. Select the I agree to allow Technical Support to use this data option and click Export to export the data to the specified location. Generating Technical Support Report Manually Using RACADM To generate the TSR using RACADM, use the techsupreport subcommand. For more information, see the iDRAC RACADM Command Line Reference Guide available at dell.com/esmmanuals.com.
The Lifecycle Controller Data option erases any content such as the LC Log, configuration database, rollback firmware, factory as-shipped logs, and the configuration information from the FP SPI (or management riser). NOTE: The Lifecycle Controller log contains the information about the system erase request and any information generated when the iDRAC restarts. Prior information does not exist.
Frequently Asked Questions 24 This section lists the frequently asked questions for the following: • • • • • • • • • • • • • System Event Log Network Security Active Directory Single Sign On Smart Card Login Virtual Console Virtual Media vFlash SD Card SNMP Authentication Storage Devices iDRAC Service Module RACADM Miscellaneous System Event Log While using iDRAC Web interface through Internet Explorer, why does SEL not save using the Save As option? This is due to a browser setting. To resolve this: 1.
upload a iDRAC server certificate issued by a trusted CA (for example, Microsoft Certificate Authority, Thawte or Verisign). Why the DNS server not registering iDRAC? Some DNS servers register iDRAC names that contain only up to 31 characters. When accessing the iDRAC Web-based interface, a security warning is displayed stating that the SSL certificate host name does not match the iDRAC host name.
– The Group Name and Group Domain Name matches the Active Directory configuration if you are using standard schema. – If the user and the iDRAC object is in different domain, then do not select the User Domain from Login option. Instead select Specify a Domain option and enter the domain name where the iDRAC object resides. • Check the domain controller SSL certificates to make sure that the iDRAC time is within the valid period of the certificate.
If you are using standard schema and all the users and role groups are in the same domain, Global Catalog Address(es) are not required. If you are using extended schema, the Global Catalog Address is not used. How does standard schema query work? iDRAC connects to the configured domain controller address(es) first. If the user and role groups are in that domain, the privileges are saved. If Global Controller Address(es) is configured, iDRAC continues to query the Global Catalog.
Single Sign-On SSO login fails on Windows Server 2008 R2 x64. What are the settings required to resolve this? 1. Run the technet.microsoft.com/en-us/library/dd560670(WS.10).aspx for the domain controller and domain policy. 2. Configure the computers to use the DES-CBC-MD5 cipher suite. These settings may affect compatibility with client computers or services and applications in your environment.
12. Close the Registry Editor window. You can now log in to iDRAC using SSO. If you have enabled SSO for iDRAC and you are using Internet Explorer to log in to iDRAC, SSO fails and you are prompted to enter your user name and password. How to resolve this? Make sure that the iDRAC IP address is listed in the Tools → Internet Options → Security → Trusted sites. If it is not listed, SSO fails and you are prompted to enter your user name and password. Click Cancel and proceed.
Can the local user also turn off or turn on the video? When the local console is disabled, the local user cannot turn off or turn on the video. Does switching off the local video also switch off the local keyboard and mouse? No. Does turning off the local console turn off the video on the remote console session? No, turning the local video on or off is independent of the remote console session.
Can a keyboard or mouse be used while installing a Microsoft operating system remotely through the Virtual Console? No. When you remotely install a supported Microsoft operating system on a system with Virtual Console enabled in the BIOS, an EMS Connection Message is sent that requires that you select OK remotely. You must either select OK on the local system or restart the remotely managed server, reinstall, and then turn off the Virtual Console in BIOS.
When starting a Virtual Console session from iDRAC Web interface, why is an ActiveX security popup displayed? iDRAC may not be in the trusted site list. To prevent the security popup from appearing every time you begin a Virtual Console session, add iDRAC to the trusted site list in the client browser: 1. Click Tools → Internet Options → Security → Trusted sites. 2. Click Sites and enter the IP address or the DNS name of iDRAC 3. Click Add. 4. Click Custom Level. 5.
3. Press Ctrl + Alt +Print Screen. 4. Release only Print Screen. 5. Press Print Screen+Ctrl+Alt. NOTE: The SysRq feature is currently not supported with Internet Explorer and Java. Why is the "Link Interrupted" message displayed at the bottom of the Virtual Console? When using the shared network port during a server reboot, iDRAC is disconnected while BIOS is resetting the network card.
• 1.44 Floppy disk or floppy image • A USB key that is recognized by the operating system as a removable disk • A USB key image How to make the USB key a bootable device? You can also boot with a Windows 98 startup disk and copy system files from the startup disk to the USB key. For example, from the DOS prompt, type the following command: sys a: x: /s where, x: is the USB key that is required to be set as a bootable device. The Virtual Media is attached and connected to the remote floppy.
where: /dev/sdx is the device name found in step 4 and /mnt/floppy is the mount point. Why are the virtual drives attached the server removed after performing a remote firmware update using the iDRAC Web interface? Firmware updates cause the iDRAC to reset, drop the remote connection, and unmount the virtual drives. The drives reappear when iDRAC reset is complete.
The vFlash SD card is locked when an operation is in-progress. For example, during an initialize operation. SNMP Authentication Why is the message 'Remote Access: SNMP Authentication Failure' displayed? As part of discovery, IT Assistant attempts to verify the get and set community names of the device. In IT Assistant, you have the get community name = public and the set community name = private. By default, the SNMP agent community name for iDRAC agent is public.
• Click Start → Control Panel → Programs and Features. The version of the installed iDRAC Service Module is listed in the Version tab. • Go to My Computer → Uninstall or change a program. What is the minimum permission level required to install the iDRAC Service Module? To install the iDRAC Service Module, you must have administrator level privileges. While installing the iDRAC Service Module, it displays an error message This is not a supported server.
mode. After the uninstallation, the virtual switch vSwitchiDRACvusb and the port group iDRAC Network are not deleted. To delete it manually, perform one of the following steps: • Go to vSphere Client Configuration wizard and delete the entries.
Clear the ARP table on your system. Remote RACADM fails to connect to iDRAC from SUSE Linux Enterprise Server (SLES) 11 SP1. Make sure that the official openssl and libopenssl versions are installed. Run the following command to install the RPM packages: rpm -ivh --force < filename > where, filename is the openssl or libopenssl rpm package file. For example: rpm -ivh --force openssl-0.9.8h-30.22.21.1.x86_64.rpm rpm -ivh --force libopenssl0_9_8-0.9.8h-30.22.21.1.x86_64.
IP Address Subnet Mask Gateway = 192.168.0.1 = 255.255.255.0 = 192.168.0.1 Using LCD: On the Main Menu, highlight the Server and press the check button and select the required server and press the check button. How to find the CMC IP address related to the blade server? From iDRAC Web interface: Click Overview → iDRAC Settings → CMC . The CMC Summary page displays the CMC IP address. From the Virtual Console: Select the "Dell CMC" console in the OSCAR to log in to CMC through a local serial connection.
• Make sure that NIC settings, IPv4 and IPv6 settings and either Static or DHCP is enabled for your network. Inserted the blade server into the chassis and pressed the power switch, but it did not power on. • iDRAC requires up to two minutes to initialize before the server can power on. • Check CMC power budget. The chassis power budget may have exceeded. How to retieve an iDRAC administrative user name and password? You must restore iDRAC to its default settings.
Use Case Scenarios 25 This section helps you in navigating to specific sections in the guide to perform typical use case scenarios. Troubleshooting An Inaccessible Managed System After receiving alerts from OpenManage Essentials, Dell Management Console, or a local trap collector, five servers in a data center are not accessible with issues such as hanging operating system or server. Need to identify the cause to troubleshoot and bring up the server using iDRAC.
Using iDRAC Service Module Obtaining System Information and Assess System Health To obtain system information and assess system health: • In iDRAC Web interface, go to Overview → Server → System Summary to view the system information and access various links on this page to asses system health. For example, you can check the health of the chassis fan. • You can also configure the chassis locator LED and based on the color, assess the system health.
• Lifecycle Controller–Remote Services • Lifecycle Controller • Dell Remote Access Configuration Tool (DRACT) Performing Graceful Shutdown To perform graceful shutdown, in iDRAC Web interface, go to one of the following locations: • Overview → Server → Power/Thermal → Power Configuration → Power Control. The Power Control page is displayed. Select Graceful Shutdown and click Apply. • Overview → Server → Power/Thermal → Power Monitoring.
Managing Rack Density Suppose two servers are installed in a rack. To add two additional servers, need to determine how much capacity is left in the rack. To assess the capacity of a rack to add additional servers: 1. View the current power consumption data and historical power consumption data for the servers. 2. Based on the data, power infrastructure and cooling system limitations, enable the power cap policy and set the power cap values.
