Integrated Dell Remote Access Controller 8 (iDRAC8) Version 2.05.05.
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. NOTE: 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.................................................................................................................................... 14 Benefits of Using iDRAC With Lifecycle Controller......................................................................................................... 14 Key Features.........................................................................................................................................................................
Setting Up iDRAC IP Using CMC Web Interface...................................................................................................... 38 Enabling Auto-discovery............................................................................................................................................... 39 Configuring Servers and Server Components Using Auto Config.......................................................................... 39 Using Hash Passwords for Improved Security..............
Modifying Network Settings Using Web Interface................................................................................................... 68 Modifying Network Settings Using Local RACADM................................................................................................. 68 Configuring IP Filtering................................................................................................................................................. 68 Configuring Services........................
Checking the System for Fresh Air Compliance..............................................................................................................92 Viewing Historical Temperature Data............................................................................................................................... 92 Viewing Historical Temperature Data Using iDRAC Web Interface........................................................................ 92 Viewing Historical Temperature Data Using RACADM....
Configuring Extended Schema Active Directory..................................................................................................... 122 Testing Active Directory Settings.............................................................................................................................. 130 Configuring Generic LDAP Users.....................................................................................................................................
Viewing System Event Log...............................................................................................................................................149 Viewing System Event Log Using Web Interface.................................................................................................... 149 Viewing System Event Log Using RACADM............................................................................................................
Understanding RAID Concepts........................................................................................................................................ 166 What Is RAID?.............................................................................................................................................................. 166 Organizing Data Storage For Availability And Performance................................................................................... 167 Choosing RAID Levels ...
Storage Devices — Apply Operation Scenarios............................................................................................................ 198 Blinking or Unblinking Component LEDs.........................................................................................................................199 Blinking or Unblinking Component LEDs Using Web Interface.............................................................................. 199 Blinking or Unblinking Component LEDs Using RACADM....
17 Managing vFlash SD Card......................................................................................................... 221 Configuring vFlash SD Card..............................................................................................................................................221 Viewing vFlash SD Card Properties........................................................................................................................... 221 Enabling or Disabling vFlash Functionality.
Configuring iDRAC Quick Sync Settings Using iDRAC Settings Utility................................................................ 248 Using Mobile Device to View iDRAC Information..........................................................................................................248 22 Deploying Operating Systems.................................................................................................. 249 Deploying Operating System Using VMCLI ..................................................
SNMP Authentication....................................................................................................................................................... 272 Storage Devices.................................................................................................................................................................272 iDRAC Service Module.........................................................................................................................................
1 Overview 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.
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. For information on the features available for a license, see Managing Licenses. Inventory and Monitoring • • • • • • • • • • • View managed server health.
• • • Set the backplane mode (unified or split mode). Blink or unblink component LEDs. Apply the device settings immediately, at next system reboot, at a scheduled time, or as a pending operation to be applied as a batch as part of the single job. Update • • • • • • • Manage iDRAC licenses. Update BIOS and device firmware for devices supported by Lifecycle Controller. Update or rollback iDRAC firmware and lifecycle controller firmware using a single firmware image. Manage staged updates.
• • • Login failure limits per IP address, with login blocking from that IP address when the limit is exceeded. Limited IP address range for clients connecting to iDRAC. Dedicated Gigabit Ethernet adapter available on rack and tower servers (additional hardware may be required).
Acquiring Licenses Use any of the following methods to acquire the licenses: • • • 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.
License/ Component state or condition Import Export Delete Replace Learn More Expired license No Yes Yes Yes Yes License installed but component missing No Yes Yes No Yes NOTE: In the iDRAC Web interface, on the Licenses page, expand the device to view the Replace option in the dropdown menu. Managing Licenses Using iDRAC Web Interface To manage the licenses using the iDRAC Web interface, go to Overview > Server > Licenses .
Feature iDRAC8 Basic iDRAC8 Express iDRAC8 Express for Blades iDRAC8 Enterprise IPv6 Yes Yes Yes Yes DHCP Yes Yes Yes Yes Dynamic DNS Yes Yes Yes Yes OS pass-through Yes Yes Yes Yes Front panel USB Yes Yes Yes Yes Role-based authority Yes Yes Yes Yes Local users Yes Yes Yes Yes SSL encryption Yes Yes Yes Yes IP blocking No Yes Yes Yes Directory services (AD, LDAP) No No No Yes Two-factor authentication (smart card) No No No Yes Single sign-on (kerb
Feature iDRAC8 Basic iDRAC8 Express iDRAC8 Express for Blades iDRAC8 Enterprise Power thresholds and alerts (includes headroom) No Yes Yes Yes Real-time power graphing No Yes Yes Yes Historical power counters No Yes Yes Yes Power capping No No No Yes Power Center integration No No No Yes Temperature monitoring Yes Yes Yes Yes Temperature graphing No Yes Yes Yes Full agent-free monitoring Yes Yes Yes Yes Predictive failure monitoring Yes Yes Yes Yes SNMPv1, v
Feature iDRAC8 Basic iDRAC8 Express iDRAC8 Express for Blades iDRAC8 Enterprise Embedded configuration tools (iDRAC Settings Utility) Yes Yes Yes Yes Embedded configuration wizards (Lifecycle Controller wizards) 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 Zero-touch configurat
Feature iDRAC8 Basic iDRAC8 Express iDRAC8 Express for Blades iDRAC8 Enterprise Lifecycle Log Yes Yes Yes Yes Work notes Yes Yes Yes Yes Remote Syslog No No No Yes License management Yes Yes Yes Yes [1] Not available with blade servers. [2] 500 series and lower rack and tower servers require a hardware card to enable this feature; this hardware is offered at additional cost. [3] Requires vFlash SD card media.
Interface or Protocol Description CMC Web Interface In addition to monitoring and managing the chassis, use the CMC Web interface to: • • • • • • View the status of a managed system Update iDRAC firmware Configure iDRAC network settings Log in to iDRAC Web interface Start, stop, or reset the managed system Update BIOS, PERC, and supported network adapters Lifecycle Controller Use Lifecycle Controller to perform iDRAC configurations.
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.
• • • • • • • • • • • • • • The iDRAC Online Help provides detailed information about the fields available on the iDRAC Web interface and the descriptions for the same. You can access the online help after you install iDRAC. The iDRAC8 RACADM Command Line Interface Reference Guide provides information about the RACADM sub-commands, supported interfaces, and iDRAC property database groups and object definitions.
4. Select the appropriate service or support link based on your need. Accessing documents from Dell support site You can access the required documents in one of the following ways: • Using the following links: • • • • • For all Enterprise Systems Management documents — dell.com/softwaresecuritymanuals For Enterprise Systems Management documents — dell.com/openmanagemanuals For Remote Enterprise Systems Management documents — dell.
2 Logging into iDRAC 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.
4. For an Active Directory user, in the Username and Password fields, enter the Active Directory user name and password. If you have specified the domain name as a part of the username, select This iDRAC from the drop-down menu. The format of the user name can be: \, /, or @. For example, dell.com\john_doe, or JOHN_DOE@DELL.COM. If the domain is not specified in the user name, select the Active Directory domain from the Domain drop-down menu. 5.
Related concepts Enabling or Disabling Smart Card Login Related tasks Configuring iDRAC Smart Card Login for Local Users Logging Into iDRAC as an Active Directory User Using Smart Card Before you log in as a Active Directory user using Smart Card, make sure to: • • • • Upload a Trusted Certificate Authority (CA) certificate (CA-signed Active Directory certificate) to iDRAC. Configure the DNS server. Enable Active Directory login. Enable Smart Card login.
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. name) and [port number] is the HTTPS port number. NOTE: If you use IP address instead of FQDN, SSO fails. iDRAC logs you in with appropriate Microsoft Active Directory privileges, using your credentials that were cached in the operating system when you logged in using a valid Active Directory account.
Accessing iDRAC Using Firmware RACADM You can use SSH or Telnet interfaces to access iDRAC and run firmware RACADM commands. For more information, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/manuals. Accessing iDRAC Using SMCLP SMCLP is the default command line prompt when you log in to iDRAC using Telnet or SSH. For more information, see Using SMCLP.
• • • You log in to iDRAC with Configure User privilege. Default password warning feature is enabled. Credentials for any currently enabled account are root/calvin. A warning message is also displayed when you log in to iDRAC using SSH, Telnet, remote RACADM, or the Web interface. For Web interface, SSH, and Telnet, a single warning message is displayed for each session. For remote RACADM, the warning message is displayed for each command.
Enabling or Disabling Default Password Warning Message Using Web Interface To enable or disable the display of the default password warning message after logging in to iDRAC: 1. Go to Overview > iDRAC Settings > User Authentication > Local Users . The Users page is displayed. 2. In the Default Password Warning section, select Enable, and then click Apply to enable the display of the Default Password Warning page when you log in to iDRAC. Else, select Disable.
3 Setting Up Managed System and Management Station 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.
• • Chassis or Server LCD panel (see the system’s Hardware Owner’s Manual) 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.
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).
IPv6 Settings Alternately, based on the infrastructure setup, you can use IPv6 address protocol. To configure the IPv6 settings: 1. Select Enabled option under Enable IPv6. 2. For the DHCPv6 server to automatically assign the IP address, gateway, and subnet mask to iDRAC, select Enabled option under Enable Auto-configuration. If enabled, the static values are disabled. Else, proceed to the next step to configure using the static IP address. 3. In the Static IP Address 1 box, enter the static IPv6 address.
7. To save the network information, click Apply. For more information, see the Chassis Management Controller User’s Guide available at dell.com/support/manuals. Enabling Auto-discovery The auto-discovery feature allows newly installed servers to automatically discover the remote management console that hosts the provisioning server. The provisioning server provides custom administrative user credentials to iDRAC, so that the unprovisioned server can be discovered and managed from the management console.
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.
Configuring Option 43 on Windows To configure option 43 on Windows: 1. On the DHCP server, go to Start > Administration Tools > DHCP to open the DHCP server administration tool. 2. Find the server and expand all items under it. 3. Right-click on Scope Options and select Configure Options. The Scope Options dialog box is displayed. 4. Scroll down and select 043 Vendor Specific Info. 5.
For example, option myname code 43 = text; subnet 192.168.0.0 netmask 255.255.0.0 { #default gateway option routers 192.168.0.1; option subnet-mask 255.255.255.0; option nis-domain "domain.org"; option domain-name "domain.org"; option domain-name-servers 192.168.1.1; option time-offset -18000; # Eastern Standard Time # option ntp-servers 192.168.1.1; # option netbios-name-servers 192.168.1.1; # --- Selects point-to-point node (default is hybrid).
You must have Server Control privileges to include and export hash passwords. If access to all accounts is lost, use iDRAC Settings Utility or local RACADM and perform reset iDRAC to default task. If the iDRAC user account’s password is set with the SHA256 password hash only and not the other hashes (SHA1v3Key or MD5v3Key), then authentication through SNMP v3 and IPMI is not available. Hash Password Using RACADM Use the following objects with the set racadm sub command to set hash passwords: • • iDRAC.
Related tasks Configuring Supported Web Browsers Accessing iDRAC Remotely To remotely access iDRAC Web interface from a management station, make sure that the management station is in the same network as iDRAC. For example: • • 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.
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.
• This option allows the system fans speeds to change such that the exhaust temperature does not exceed the selected exhaust temperature limit. This cannot always be guaranteed under all system operating conditions due to dependency on system load and system cooling capability. Fan Speed Offset — Selecting this option allows additional cooling to the server. In case hardware is added (example, new PCIe cards), it may require additional cooling.
Object Description Usage • • FanSpeedHighOffsetVal • • • FanSpeedLowOffsetVal • • • FanSpeedMaxOffsetVal • • • FanSpeedMediumOffsetVal • • • FanSpeedOffset • • 4 - Indica 255 - Ind Getting this variable reads the fan speed offset value in %PWM for High Fan Speed Offset setting. This value depends on the system. Use FanSpeedOffset object to set this value using index value 1. Values from Getting this variable reads the fan speed offset value in %PWM for Low Fan Speed Offset setting.
Object Description Usage • • • • • The index value decides the offset that is applied and the FanSpeedLowOffsetVal, FanSpeedMaxOffsetVal, FanSpeedHighOffsetVal, and FanSpeedMediumOffsetVal objects (defined earlier) are the values at which the offsets are applied.
3. Click Custom Level, select Medium-Low, and click Reset. Click OK to confirm. Click Custom Level to open the dialog. 4. Scroll down to the section labeled ActiveX controls and plug-ins and set the following: NOTE: The settings in the Medium-Low state depend on the IE version.
• • • • • Use SSL 3.0: selected Use TLS 1.0: selected Warn about invalid site certificates: selected Warn if changing between secure and not secure mode: selected Warn if forms submittal is being redirected: selected NOTE: To modify the settings, it is recommended that you learn and understand the consequences. For example, if you block pop-ups, parts of iDRAC Web interface may not function properly. 7. Click Apply, and then click OK. 8. Click the Connections tab. 9.
4. In the Preferences Name column, locate xpinstall.enabled. Make sure that Value is true. If not, double-click xpinstall.enabled to set Value to true. Viewing Localized Versions of Web Interface iDRAC Web interface is supported in the following languages: • • • • • • English (en-us) French (fr) German (de) Spanish (es) Japanese (ja) Simplified Chinese (zh-cn) The ISO identifiers in parentheses denote the supported language variants.
Table 6.
Updating Firmware Using iDRAC Web Interface You can update the device firmware using firmware images available on the local system, from a repository on a network share (CIFS or NFS), or from FTP. Updating Single Device Firmware Before updating the firmware using single device update method, make sure that you have downloaded the firmware image to a location on the local system. To update single device firmware using iDRAC Web interface: 1. Go to Overview > iDRAC Settings > Update and Rollback .
4. Click Check for Update. The Update Details section displays a comparison report showing the current firmware versions and the firmware versions available in the repository. NOTE: Any update in the repository that is not applicable to the system or the installed hardware or not supported is not included in the comparison report. 5. Select the required updates and do one of the following: • • • For firmware images that do not require a host system reboot, click Install. For example, .d7 firmware file.
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.
• • • For firmware images that do not require a host system reboot, click Install. For example, .d7 firmware file. For firmware images that require a host system reboot, click Install and Reboot or Install Next Reboot. To cancel the firmware update, click Cancel. When you click Install, Install and Reboot or Install Next Reboot, the message Updating Job Queue is displayed. 7.
3. Select the Enable Automatic Update option. 4. Select any of the following options to specify if a system reboot is required after the updates are staged: • • Schedule Updates — Stage the firmware updates but do not reboot the server. Schedule Updates and reboot Server — Enables server reboot after the firmware updates are staged. 5. Select any of the following to specify the location of the firmware images: • • Network — Use the catalog file from a network share (CIFS or NFS).
Updating Firmware Using CMC Web Interface You can update iDRAC firmware for blade servers using the CMC Web interface. To update iDRAC firmware using the CMC Web interface: 1. Log in to CMC Web interface. 2. Go to Server > Overview > . The Server Status page is displayed. 3. Click Launch iDRAC Web interface and perform iDRAC Firmware Update.
Updating Firmware Using Lifecycle Controller Remote Services For information to update the firmware using Lifecycle Controller–Remote Services, see Lifecycle Controller Remote Services Quick Start Guide available at dell.com/support/manuals. Updating CMC Firmware From iDRAC In FX2/FX2s chassis, you can update the firmware for the Chassis Management Controller and any component that can be updated by CMC and shared by the servers from iDRAC.
Viewing and Managing Staged Updates Using RACADM To view the staged updates using RACADM, use jobqueue subcommand. For more information, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/manuals. Rolling Back Device Firmware You can rollback the firmware for iDRAC or any device that is supported by Lifecycle Controller even if the update was previously performed using another interface.
• While in rollback mode, the rollback process continues in the background even if you navigate away from this page. • If iDRAC configuration is reset to default values, the iDRAC IP address is reset to 192.168.0.120. You can access iDRAC using this IP, or reconfigure the iDRAC address using local RACADM or F2 (remote RACADM requires network access).
• • • • • • System Health and Identify LED is flashed at ~1/2 second rate. (LED is located on the back of a rack and tower servers and on the front of a blade server.) Bootloader is now polling the SD card slot. Format an SD card with FAT using a Windows operating system, or EXT3 using a Linux operating system. Copy firmimg.d7 to the SD card. Insert the SD card into the server. Bootloader detects the SD card, turns the flashing LED to solid amber, reads the firmimg.
• • Network to save the backup file image on a CIFS or NFS share. vFlash to save the backup file image on the vFlash card. 3. Enter the backup file name and encryption passphrase (optional). 4. If Network is selected as the file location, enter the network settings. 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. 5.
Scheduling Automatic Backup Server Profile Using RACADM To enable automatic backup use the command: racadm set lifecyclecontroller.lcattributes.
• • Network vFlash 3. Enter the backup file name and decryption passphrase (optional). 4. If Network is selected as the file location, enter the network settings. 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. 5.
4 Configuring iDRAC 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.
Managing vFlash SD Card Setting First Boot Device Enabling or Disabling OS to iDRAC Pass-through Related tasks Configuring iDRAC to Send Alerts Topics: • • • • • • • • • • • Viewing iDRAC Information Modifying Network Settings Configuring Services Using VNC Client to Manage Remote Server Configuring Front Panel Display Configuring Time Zone and NTP Setting First Boot Device Enabling or Disabling OS to iDRAC Pass-through Obtaining Certificates Configuring Multiple iDRACs Using RACADM Disabling Access to Mo
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.
• • IP filtering limits the IP address range of the clients accessing iDRAC. It compares the IP address of an incoming login to the specified range and allows iDRAC access only from a management station whose IP address is within the range. All other login requests are denied. When repeated login failures occur from a particular IP address, it prevents the address from logging in to iDRAC for a preselected time span.
• Using set command: racadm set iDRAC.IPBlocking.RangeEnable 1 racadm set iDRAC.IPBlocking.RangeAddr 192.168.0.57 racadm set iDRAC.IPBlocking.RangeMask 255.255.255.255 • To restrict logins to a set of four adjacent IP addresses (for example, 192.168.0.212 through 192.168.0.215), select all but the lowest two bits in the mask: • Using set command: racadm set iDRAC.IPBlocking.RangeEnable 1 racadm set iDRAC.IPBlocking.RangeAddr 192.168.0.212 racadm set iDRAC.IPBlocking.RangeMask 255.255.255.
• • cfgOobSnmpAgentEnable • cfgOobSnmpAgentCommunity Use the objects in the following object groups with the set command: • • • • • • • iDRAC.LocalSecurity iDRAC.LocalSecurity iDRAC.SSH iDRAC.Webserver iDRAC.Telnet iDRAC.Racadm iDRAC.SNMP For more information about these objects, see iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/ support/manuals.
wait for timeout (value configured for the VNC Server settings in the Services page in iDRAC Web interface) and then re-establish the VNC connection. • If the VNC client window is minimized for more than 60 seconds, the client window closes. You must open a new VNC session. If you maximize the VNC client window within 60 seconds, you can continue to use it. Configuring VNC Server Using iDRAC Web Interface To configure the VNC server settings: 1.
Related concepts Configuring LCD Setting Configuring System ID LED Setting Configuring LCD Setting You can set and display a default string such as iDRAC name, IP, and so on or a user-defined string on the LCD front panel of the managed system. Configuring LCD Setting Using Web Interface To configure the server LCD front panel display: 1. In iDRAC Web interface, go to Overview > Hardware > Front Panel. 2.
Configuring System ID LED Setting Using Web Interface To configure the System ID LED display: 1. In iDRAC Web interface, go to Overview > Hardware > Front Panel. The Front Panel page is displayed. 2. In System ID LED Settings section, select any of the following options to enable or disable LED blinking: • • • • • Blink Off Blink On Blink On 1 Day Timeout Blink On 1 Week Timeout Blink On 1 Month Timeout 3. Click Apply. The LED blinking on the front panel is configured.
• • • • • Virtual CD/DVD/ISO Local SD Card vFlash Lifecycle Controller 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.
racadm config -g cfgRacTuning -o cfgRacTuneAsrEnable 1 5. Enable Automated System Recovery Agent. To do this, go to Overview > iDRAC Settings > Network > Services, select Enabled and click Apply.
Category Manufacturer Type • • • 57800S QP rNDC (10G SFP+ + 1G BASE-T) 57840 4x10G KR 57840 rNDC Intel • • • i540 QP rNDC (10G BASE-T + 1G BASE-T) i350 QP rNDC 1G BASE-T x520/i350 rNDC 1GB Qlogic QMD8262 Blade NDC In-built LOM cards also support the OS to iDRAC pass-through feature. The following cards do not support the OS to iDRAC Pass-through feature: • • • • Intel 10 GB NDC. Intel rNDC with two controllers – 10G controllers does not support.
• • • • Configure the USB NIC interface using Network Manager tool. Navigate to System > Administrator > Network > Devices > New > Ethernet Connection and select Dell computer corp.iDRAC Virtual NIC USB Device. Click the Activate icon to activate the device. For more information, see the RHEL 5.9 documentation. Create corresponding interface’s config file as ifcfg-ethX in /etc/sysconfig/network-script/ directory. Add the basic entries DEVICE, BOOTPROTO, HWADDR, ONBOOT.
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. Active Directory user login Trusted CA certificate This certificate is issued by a CA. SHA-2 certificates are also supported. Local User login SSL Certificate Generate a CSR and get it signed from a trusted CA NOTE: iDRAC ships with a default self-signed SSL server certificate. The iDRAC Web server, Virtual Media, and Virtual Console use this certificate. SHA-2 certificates are also supported.
Related concepts Generating a New Certificate Signing Request Uploading Server Certificate Viewing Server Certificate Uploading Custom Signing Certificate Downloading Custom SSL Certificate Signing Certificate Deleting Custom SSL Certificate Signing Certificate Generating a New Certificate Signing Request A CSR is a digital request to a Certificate Authority (CA) for a SSL server certificate.
1. In the iDRAC Web interface, go to Overview > iDRAC Settings > Network > SSL, select Upload Server Certificate and click Next. The Certificate Upload page is displayed. 2. Under File Path, click Browse and select the certificate on the management station. 3. Click Apply. The SSL server certificate is uploaded to iDRAC. 4. 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.
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. Click Reset iDRAC or Reset iDRAC Later as required. After iDRAC resets, 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.
Configuring Multiple iDRACs Using RACADM You can configure one or more iDRACs with identical properties using RACADM. When you query a specific iDRAC using its group ID and object ID, RACADM creates the .cfg configuration file from the retrieved information. File name is user specified. Import the file to other iDRACs to identically configure them. NOTE: • The configuration file contains information that is applicable for the particular server. The information is organized under various object groups.
• If you have used the getconfig command: [cfgUserAdmin] # cfgUserAdminIndex=11 cfgUserAdminUserName= # cfgUserAdminPassword=******** (Write-Only) cfgUserAdminEnable=0 cfgUserAdminPrivilege=0x00000000 cfgUserAdminIpmiLanPrivilege=15 cfgUserAdminIpmiSerialPrivilege=15 cfgUserAdminSolEnable=0 • If you have used the get command: [idrac.users.
The racadm getconfig -f .cfg command places a comment in front of index objects, allowing the user to see the included comments. To view the contents of an indexed group, use the following command: • racadm getconfig -g -i For indexed groups the object anchor must be the first object after the "[ ]" pair. The following are examples of the current indexed groups: [cfgUserAdmin] cfgUserAdminIndex=11 If you type racadm getconfig -f < myexample >.cfg, the command builds a .
NOTE: If access is disabled, you cannot use Server Administrator or IPMITool to perform iDRAC configurations. However, you can use IPMI Over LAN.
5 Viewing iDRAC and Managed System Information 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 Channel Backplane Enclosure PCIe SSDs When
• • • If IDSDM redundancy is initially disabled when the system is powered on or after an iDRAC reset, the IDSDM SD1 sensor status is displayed only after a card is inserted. • If IDSDM redundancy is enabled with two SD cards present in the IDSDM, and the status of one SD card is online while the status of the other card is offline. A system reboot is required to restore redundancy between the two SD cards in the IDSDM.
measure the cumulative utilization of each of these system resources that is read from the iDRAC using existing inter-communication mechanisms to provide these vital data through out-of-band management interfaces. Since Intel sensor representation of performance parameters and index values are for complete physical system, performance data representation on the interfaces is for the complete physical system, even if the system is virtualized and hosting multiple virtual hosts.
Monitoring Performance Index for of CPU, Memory, and I/O Modules Using RACADM Use the SystemPerfStatistics sub command to monitor performance index for CPU, memory, and I/O modules. For more information, see the iDRAC RACADM Command Line Reference Guide available at dell.com/esmmanuals. Checking the System for Fresh Air Compliance Fresh air cooling directly uses outside air to cool systems in the data center.
NOTE: After an iDRAC firmware update or iDRAC reset, some temperature data may not be displayed in the graph. Viewing Historical Temperature Data Using RACADM To view historical data using RACADM, use the inlettemphistory subcommand. For more information, see the iDRAC8 RACADM Command Line Reference Guide. Configuring Warning Threshold for Inlet Temperature You can modify the minimum and maximum warning threshold values for the system board inlet temperature sensor.
The corresponding device page is displayed from the Hardware > Network Devicessection, where you can view the device details. For information about the properties, see the iDRAC Online Help. 4. For each network device, click the icon to display the additional details. Similarly, you can view the host OS network interface information associated with a network device from the Hardware > Network Devices page. Click View Host OS Network Interfaces.
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. For more information about these commands, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/ support/manuals.
6 Setting Up iDRAC Communication 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.
Enabling or Disabling Remote RACADM Disabling Local RACADM Enabling IPMI on Managed System Configuring Linux for Serial Console During Boot Supported SSH Cryptography Schemes Topics: • • • • • • • • • Communicating With iDRAC Through Serial Connection Using DB9 Cable Switching Between RAC Serial and Serial Console While Using DB9 Cable Communicating With iDRAC Using IPMI SOL Communicating With iDRAC Using IPMI Over LAN Enabling or Disabling Remote RACADM Disabling Local RACADM Enabling IPMI on Managed Sys
6. Press to exit System Setup. Enabling RAC Serial Connection After configuring serial connection in BIOS, enable RAC serial in iDRAC. NOTE: This is applicable only for iDRAC on rack and tower servers. Enabling RAC Serial Connection Using Web Interface To enable RAC serial connection: 1. In the iDRAC Web interface, go to Overview > iDRAC Settings > Network > Serial. The Serial page is displayed. 2. Under RAC Serial, select Enabled and specify the values for the attributes. 3. Click Apply.
• Usingconfig command: racadm config -g cfgSerial -o cfgSerialConsoleEnable 0 racadm config -g cfgIpmiSerial -o cfgIpmiSerialConnectionMode < 0 • or 1> where, 0 indicates Terminal mode and 1 indicates Basic mode. Using set command: racadm set iDRAC.Serial.Enable 0 racadm set iDRAC.IPMISerial.ConnectionMode < 0 or 1> where, 0 indicates Terminal mode and 1 indicates Basic mode.
For information about the options, see the iDRAC Online Help. 5. Click Apply. The terminal mode settings are configured. 6. Make sure that the serial MUX (external serial connector) is set correctly to the remote access device in the BIOS Setup program to configure BIOS for serial connection.
Configuring BIOS For Serial Connection To configure BIOS for Serial Connection: 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.
3. Update the IPMI SOL baud rate: • • Using config command: racadm config -g cfgIpmiSol -o cfgIpmiSolBaudRate Using set command: racadm set iDRAC.IPMISol.BaudRate where is 9600, 19200, 57600, or 115200 bps. NOTE: To redirect the serial console over LAN, make sure that the SOL baud rate is identical to the managed system’s baud rate. 4.
An RMCP+ connection to iDRAC must be encrypted using the encryption Key (Key Generator (KG)Key). You can configure the encryption key using the iDRAC Web interface or iDRAC Settings utility. To start SOL session using IPMItool from a management station: NOTE: If required, you can change the default SOL time-out at Overview > iDRAC Settings > Network > Services. 1. Install IPMITool from the Dell Systems Management Tools and Documentation DVD.
• In Windows, if the Emergency Management System (EMS) console is opened immediately after a host reboot, the Special Admin Console (SAC) terminal may get corrupted. Quit the SOL session, close the terminal, open another terminal, and start the SOL session using the same command.
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. Open a command prompt window (if required). 2. If you are not running a Telnet session, type telnet. If you are running a Telnet session, press <]>. 3. At the prompt, type set bsasdel. The message Backspace will be sent as delete is displayed.
• • Using config command: racadm config -g cfgIpmiLan -o cfgIpmiLanPrivilegeLimit Using set command: racadm set iDRAC.IPMILan.PrivLimit where is one of the following: 2 (User), 3 (Operator) or 4 (Administrator) 3. Set the IPMI LAN channel encryption key (if required): • • Using config command: racadm config -g cfgIpmiLan -o cfgIpmiEncryptionKey Using set command: racadm set iDRAC.IPMILan.
NOTE: When you configure the client VT100 emulation window, set the window or application that is displaying the redirected Virtual Console to 25 rows x 80 columns to make sure the correct text displays. Else, some text screens may be garbled. Edit the /etc/grub.conf file as follows: 1. Locate the General Setting sections in the file and add the following: serial --unit=1 --speed=57600 terminal --timeout=10 serial 2. Append two options to the kernel line: kernel .............
l0:0:wait:/etc/rc.d/rc 0 l1:1:wait:/etc/rc.d/rc 1 l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.d/rc 4 l5:5:wait:/etc/rc.d/rc 5 l6:6:wait:/etc/rc.d/rc 6 #Things to run in every runlevel. ud::once:/sbin/update ud::once:/sbin/update #Trap CTRL-ALT-DELETE ca::ctrlaltdel:/sbin/shutdown -t3 -r now #When our UPS tells us power has failed, assume we have a few #minutes of power left. Schedule a shutdown for 2 minutes from now.
Supported SSH Cryptography Schemes To communicate with iDRAC using SSH protocol, it supports multiple cryptography schemes listed in the following table. Table 11.
4. You can modify the key comment field. 5. Enter a passphrase to secure the key. 6. Save the public and private key. Generating Public Keys for Linux To use the ssh-keygen application to create the basic key, open a terminal window and at the shell prompt, enter ssh-keygen –t rsa –b 1024 –C testing where: • • • -t is either dsa or rsa. –b specifies the bit encryption size between 768 and 4096. –C allows modifying the public key comment and is optional. NOTE: The options are case-sensitive.
Viewing SSH Keys You can view the keys that are uploaded to iDRAC. Viewing SSH Keys Using Web Interface To view the SSH keys: 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 is displayed with the key details.
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.
You can configure single or multiple iDRAC users using RACADM. To configure multiple iDRAC users with identical configuration settings, perform one of the following procedures: • • Use the RACADM examples in this section as a guide to create a batch file of RACADM commands and then execute the batch file on each managed system. Create the iDRAC configuration file and execute the racadm config or racadm set subcommand on each managed system using the same configuration file.
The following example describes how to add a new user named "John" with a "123456" password and LOGIN privileges to the RAC.
Table 12. iDRAC Roles Current Generation Prior Generation Privileges Administrator Administrator Login, Configure, Configure Users, Logs, System Control, Access Virtual Console, Access Virtual Media, System Operations, Debug Operator Power User Login, Configure, System Control, Access Virtual Console, Access Virtual Media, System Operations, Debug Read Only Guest User Login None None None Table 13.
Enabling SSL on Domain Controller When iDRAC authenticates users with an Active Directory domain controller, it starts an SSL session with the domain controller. At this time, the domain controller must publish a certificate signed by the Certificate Authority (CA)—the root certificate of which is also uploaded into iDRAC.
NOTE: If iDRAC firmware SSL certificate is CA-signed and the certificate of that CA is already in the domain controller's Trusted Root Certificate Authority list, do not perform the steps in this section. To import iDRAC firmware SSL certificate to all domain controller trusted certificate lists: 1. Download iDRAC SSL certificate using the following RACADM command: racadm sslcertdownload -t 0x1 -f 2.
Table 14.
4. Click Next. The Active Directory Configuration and Management Step 2 of 4 page is displayed. 5. Enable Active Directory and specify the location information about Active Directory servers and user accounts. Also, specify the time iDRAC must wait for responses from Active Directory during iDRAC login. NOTE: If certificate validation is enabled, specify the Domain Controller Server addresses and the Global Catalog FQDN. Make sure that DNS is configured correctly under Overview > iDRAC Settings > Network.
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. With Standard Schema, these are the addresses of the domain controllers where the user accounts and the role groups are located.
database. Some example user class attributes can include the user’s first name, last name, phone number, and so on. You can extend the Active Directory database by adding your own unique attributes and classes for specific requirements. Dell has extended the schema to include the necessary changes to support remote management authentication and authorization using Active Directory. Each attribute or class that is added to an existing Active Directory Schema must be defined with a unique ID.
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.
NOTE: Make sure to use the schema extension for this product is different from the previous generations of RAC products. The earlier schema does not work with this product. NOTE: Extending the new schema has no impact on previous versions of the product. You can extend your schema using one of the following methods: • • Dell Schema Extender utility LDIF script file If you use the LDIF script file, the Dell organizational unit is not added to the schema.
OID 1.2.840.113556.1.8000.1280.1.7.1.1 Attributes dellSchemaVersion dellRacType Table 17. delliDRACAssociationObject Class OID 1.2.840.113556.1.8000.1280.1.7.1.2 Description Represents the Dell Association Object. The Association Object provides the connection between the users and the devices. Class Type Structural Class SuperClasses Group Attributes dellProductMembers dellPrivilegeMember Table 18. dellRAC4Privileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.
OID 1.2.840.113556.1.8000.1280.1.1.1.5 Class Type Structural Class SuperClasses Computer Attributes dellAssociationMembers 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.
Attribute Name/Description Assigned OID/Syntax Object Identifier TRUE if the user has Debug Command Admin rights on the device. Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.7) dellSchemaVersion 1.2.840.113556.1.8000.1280.1.1.2.12 The Current Schema Version is used to update the schema. Case Ignore String (LDAPTYPE_CASEIGNORESTRING 1.2.840.113556.1.4.905) dellRacType 1.2.840.113556.1.8000.1280.1.1.2.
1. In the MMC Console Root window, right-click a container. 2. Select New > Dell Remote Management Object Advanced. The New Object window is displayed. 3. Enter a name for the new object. The name must be identical to iDRAC name that you enter while configuring Active Directory properties using iDRAC Web interface. 4. Select iDRAC Device Object and click OK. Creating Privilege Object To create prvivlege object: NOTE: You must create a privilege object in the same domain as the related association object.
Adding Users or User Groups To add users or user groups: 1. Right-click the Association Object and select Properties. 2. Select the Users tab and click Add. 3. Enter the user or user group name and click OK. Adding Privileges To add privileges: 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. 1.
Configuring Active Directory With Extended Schema Using RACADM To configure Active Directory with Extended Schema using the RACADM: 1.
• Using set command: racadm set iDRAC.IPv4.DNSFromDHCP 0 racadm set iDRAC.IPv4.DNSFromDHCP.DNS1 racadm set iDRAC.IPv4.DNSFromDHCP.DNS2 4.
Configuring Generic LDAP Directory Service Using iDRAC Web-Based Interface To configure the generic LDAP directory service using Web interface: NOTE: For information about the various fields, see the iDRAC Online Help. 1. In the iDRAC Web interface, go to Overview > iDRAC Settings > User Authentication > Directory Services > Generic LDAP Directory Service. The Generic LDAP Configuration and Management page displays the current generic LDAP settings. 2. Click Configure Generic LDAP. 3.
2. Click Test Settings. 3. Enter the user name and password of a directory user that is chosen to test the LDAP settings. The format depends on the Attribute of User Login is used and the user name entered must match the value of the chosen attribute. NOTE: When testing LDAP settings with Enable Certificate Validation checked, iDRAC requires that the LDAP server be identified by the FQDN and not an IP address.
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.
4. Add the preceding SSO user (login user) to the device object. 5. Provide access privilege to Authenticated Users for accessing the created association object. Related concepts Adding iDRAC Users and Privileges to Active Directory Configuring Browser to Enable Active Directory SSO This section provides the browser settings for Internet Explorer and Firefox to enable Active Directory SSO. NOTE: Google Chrome and Safari do not support Active Directory for SSO login.
NOTE: For information about the options, see the iDRAC Online Help. 1. Verify whether the iDRAC DNS name matches the iDRAC Fully Qualified Domain Name. To do this, in iDRAC Web interface, go to Overview > iDRAC Settings > Network > Network and see the DNS Domain Name property. 2.
Uploading Smart Card User Certificate Using RACADM To upload smart card user certificate, use the usercertupload object. For more information, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/manuals. Uploading Trusted CA Certificate For Smart Card Before you upload the CA certificate, make sure that you have a CA-signed certificate.
Enabling or Disabling Smart Card Login Before enabling or disabling smart card login for iDRAC, make sure that: • • You have configure iDRAC permissions. iDRAC local user configuration or Active Directory user configuration with the appropriate certificates is complete. NOTE: If smart card login is enabled, then SSH, Telnet, IPMI Over LAN, Serial Over LAN, and remote RACADM are disabled. Again, if you disable smart card login, the interfaces are not enabled automatically.
9 Configuring iDRAC to Send Alerts 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.
2. Under Alerts section: • • Select Enable to enable alert generation or perform an event action. Select Disable to disable alert generation or disable an event action. 3. 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.
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 Event Alerts You can set event alerts such as e-mail alerts, IPMI alerts, SNMP traps, remote system logs, operating system logs, and WS events to be sent to configured destinations.
1. In the iDRAC Web interface, go to Overview > Server > Alerts > Alert Recurrence. The Alert Recurrence page is displayed. 2. In the Recurrence column, enter the alert frequency value for the required category, alert, and severity type(s). For more information, see the iDRAC Online help. 3. Click Apply. The alert recurrence settings are saved. Setting Alert Recurrence Events Using RACADM To set the alert recurrence event using RACADM, use the eventfilters subcommand.
Related concepts Configuring IP Alert Destinations Configuring Email Alert Settings Configuring IP Alert Destinations You can configure the IPv6 or IPv4 addresses to receive the IPMI alerts or SNMP traps. For information about the iDRAC MIBs required to monitor the servers using SNMP, see the SNMP Reference Guide for iDRAC8 available at dell.com/support/manuals. Configuring IP Alert Destinations Using Web Interface To configure alert destination settings using Web interface: 1.
3. Configure the SNMP community name string: racadm config -g cfgIpmiLan -o cfgIpmiPetCommunityName [name] where [name] is the SNMP Community Name. 4. To configure SNMP destination: • To set the SNMP trap destination for SNMPv3: racadm set idrac.SNMP.Alert.[index].DestAddr [Ip address] For example, racadm set idrac.SNMP.Alert.1.DestAddr 1.2.3.4 • To set SNMPv3 users for trap destinations: racadm set idrac.SNMP.Alert.1.SNMPv3Username root • To enable SNMPv3 for a user: racadm set idrac.users.2.
3. Click Send under Test Email to test the configured email alert settings. 4. Click Apply. Configuring Email Alert Settings Using RACADM To configure the email alert settings: 1. To enable email alert: • Using config command: racadm config -g cfgEmailAlert -o cfgEmailAlertEnable -i [index] [0|1] 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.
Configuring SMTP Email Server Address Settings You must configure the SMTP server address for email alerts to be sent to specified destinations. Configuring SMTP Email Server Address Settings Using iDRAC Web Interface To configure the SMTP server address: 1. In iDRAC Web interface, go to Overview > Server > Alerts > SNMP and E-mail Settings. 2. Enter the valid IP address or fully qualified domain name (FQDN) of the SMTP server to be used in the configuration. 3.
Message ID Description CPU Processor CPUA Proc Absent CTL Storage Contr DH Cert Mgmt 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
Message ID Description 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 VME Virtual Media VRM Virtual Console WR
10 Managing Logs 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.
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. In the iDRAC Settings Utililty, go to System Event Log. The iDRAC Settings.
• • • • Select the Log Type from the drop-down list. Select the severity level from the Severity drop-down list. Enter a keyword. Specify the date range. 2. Click Apply. The filtered log entries are displayed in Log Results. Adding Comments to Lifecycle Logs To add comments to the lifecycle logs: 1. In the Lifecycle Log page, click the + icon for the required log entry. The Message ID details are displayed. 2. Enter the comments for the log entry in the Comment box.
NOTE: It is recommended not to use too many special characters. 3. Click Add. The work note is added to the log. For more information, see the iDRAC Online Help. Configuring Remote System Logging You can send lifecycle logs to a remote system. Before doing this, make sure that: • • There is network connectivity between iDRAC and the remote system. The remote system and iDRAC is on the same network. Configuring Remote System Logging Using Web Interface To configure the remote syslog server settings: 1.
11 Monitoring and Managing Power 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.
Setting Warning Threshold for Power Consumption You can set the warning threshold value for the power consumption sensor in the rack and tower systems. The warning/critical power threshold for rack and tower systems may change on system power cycle based on PSU capacity and redundancy policy. However, the warning threshold must not exceed the critical threshold even if Power Supply Unit capacity of the redundancy policy is changed.
Power Capping You can view the power threshold limits that covers the range of AC and DC power consumption that a system under heavy workload presents to the datacenter. This is a licensed feature. Power Capping in Blade Servers Before a blade server powers up, iDRAC provides CMC with its power requirements. It is higher than the actual power that the blade can consume and is calculated based on limited hardware inventory information.
• • cfgServerPowerCapBTUhr • cfgServerPowerCapPercent • cfgServerPowerCapEnable Using the following objects with the set subcommand: • • • • System.Power.Cap.Enable System.Power.Cap.Watts System.Power.Cap.Btuhr System.Power.Cap.Percent For more information, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.com/support/manuals. Configuring Power Cap Policy Using iDRAC Settings Utility To view and configure power policies: 1.
• • System.Power.Hotspare.PrimaryPSU 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.
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 concepts Inventory and Monitoring FC HBA Devices Dynamic Configuration of Virtual Addresses, Initiator, and Storage Target Settings Topics: • • • Inventory and Monitoring Network Devices Inventory
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.
Supported BIOS Version for I/O Identity Optimization Supported NIC Firmware Versions for I/O Identity Optimization Enabling or Disabling I/O Identity Optimization Configuring Persistence Policy Settings Supported Cards for I/O Identity Optimization The following table provides the cards that support the I/O Identity Optimization feature.
Dell PowerEdge 12th Generation Server Minimum Supported BIOS Version R720, R720xd, R620, T620, and M620 2.1.0 R820 2.0.15 R520, R320, R420, T420, T320, M520, and M420 2.0.19 M820 1.7.0 Supported NIC Firmware Versions for I/O Identity Optimization In 13th generation Dell PowerEdge servers, the required NIC firmware is available by default. The following table provides the NIC firmware versions for the I/O identity optimization feature.
• • You have the Login, Configure, and System Control privileges. BIOS, iDRAC, and network cards are updated to the latest firmware. For information on the supported versions, see Supported BIOS Version For I/O Identity Optimization and Supported NIC Firmware Version for I/O Identity Optimization. After enabling I/O Identity Optimization feature, export the XML configuration file from iDRAC, modify the required I/O Identity attributes in the XML configuration file, and import the file back to iDRAC.
Default Values for Persistence Policy Persistence Policy AC Power Loss Cold Boot Warm Boot Virtual Address: Auxiliary Powered Devices Not selected Selected Selected Virtual Address: Non-Auxiliary Powered Devices Not selected Not selected Selected Initiator Selected Selected Selected Storage Target Selected Selected Selected Related concepts Enabling or Disabling I/O Identity Optimization Configuring Persistence Policy Settings Using iDRAC Web Interface To configure the persistence polic
iSCSI Initiator Default Values in IPv4 mode Default Values in IP IscsiInitiatorIpv6Gateway :: :: IscsiInitiatorPrimDns 0.0.0.0 :: IscsiInitiatorIpv4PrimDns 0.0.0.0 0.0.0.0 IscsiInitiatorIpv6PrimDns :: :: IscsiInitiatorSecDns 0.0.0.0 :: IscsiInitiatorIpv4SecDns 0.0.0.0 0.0.0.0 IscsiInitiatorIpv6SecDns :: :: IscsiInitiatorName Value Cleared Value Cleared IscsiInitiatorChapId Value Cleared Value Cleared IscsiInitiatorChapPwd Value Cleared Value Cleared IPVer Ipv4 Table 24.
13 Managing Storage Devices 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.
PERC Capability CEM configuration Capable Controller (PERC 9.1 or later) CEM configuration Non-capable Controller (PERC 9.0 and lower) at run-time. Run-time or real-time means, a reboot is not required. Staged If all the set operations are staged, the configuration is staged and applied after reboot or it is applied at real-time.
read/write performance, data protection, and storage capacity. Not all RAID levels maintain redundant data, which means for some RAID levels lost data cannot be restored. The RAID level you choose depends on whether your priority is performance, protection, or storage capacity. NOTE: The RAID Advisory Board (RAB) defines the specifications used to implement RAID. Although RAB defines the RAID levels, commercial implementation of RAID levels by different vendors may vary from the actual RAID specifications.
• • • • Performance — Read and write performance can be increased or decreased depending on the RAID level you choose. Some RAID levels may be more appropriate for particular applications. Cost efficiency — Maintaining the redundant data or parity information associated with RAID volumes requires additional disk space. In situations where the data is temporary, easily reproduced, or non-essential, the increased cost of data redundancy may not be justified.
RAID Level 1 (Mirroring) RAID 1 is the simplest form of maintaining redundant data. In RAID 1, data is mirrored or duplicated on one or more physical disks. If a physical disk fails, data can be rebuilt using the data from the other side of the mirror. 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.
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 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. Two disks per span are required for parity.
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 Performance Write Performance Rebuild Performance Minimum Disks Required Suggested Uses data intensive uses. RAID 6 Excellent Sequential reads: good. Transactional reads: Very good Fair, unless using writeback cache Poor N + 2 (N = at least two disks) Critical information. Databases and other read intensive transactional uses. RAID 60 Excellent Very Good Fair Poor X x (N + 2) (N = at least 2) Critical information.
Feature Name PERC 9 Controllers H830 H730P H730 Assign or unassign physical disk as a global hot spare Realtime Realtime Create virtual disks Realtime Edit virtual disks cache policies PERC 8 Controllers H330 H710P H710 H310 Real-time Real-time Staged Staged Staged Staged Not applicable Realtime Real-time Real-time Staged Staged Staged Staged Not applicable Realtime Realtime Real-time Real-time Staged Staged Staged Staged Not applicable Check virtual disk consistency Realtim
Feature Name PERC 9 Controllers H830 H730P H730 Clear foreign configuration Realtime Realtime Reset controller configuration Realtime Create or change security keys Realtime PERC 8 Controllers H330 H810 PCIe SSD H710P H710 H310 Real-time Real-time Staged Staged Staged Staged Not applicable Realtime Real-time Real-time Staged Staged Staged Staged Not applicable Realtime Real-time Real-time Staged Staged Staged Staged Not applicable Inventory and remotely Not monitor the healt
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.
If you have assigned a physical disk as a global hot spare in Add to Pending Operation mode, the pending operation is created but a job is not created. Then, if you try to unassign the same disk as global hot spare, the assign global hot spare pending operation is cleared. If you have unassigned a physical disk as a global hot spare in Add to Pending Operation mode, the pending operation is created but a job is not created.
• • • • • • • Edit policies Initialize Check consistency Cancel check consistency Encrypt virtual disks Assign or unassign dedicated hot spares Blink and unblink virtual disks Related concepts Creating Virtual Disks Editing Virtual Disk Cache Policies Deleting Virtual Disks Checking Virtual Disk Consistency Initializing Virtual Disks Encrypting Virtual Disks Assigning or Unassigning Dedicated Hot Spares Managing Virtual Disks Using Web Interface Managing Virtual Disks Using RACADM Creating Virtual Disks
• Cannot create virtual disks on PCIe SSDs. Creating Virtual Disks Using Web interface To create virtual disk: 1. In the iDRAC Web interface, go to Overview > Storage > Virtual Disks > Create. The Create Virtual Disk page is displayed. 2. In the Settings section, do the following: a) Enter the name for the virtual disk. 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.
The Disk Cache policy apply to readings on a specific virtual disk. These settings do not affect the read-ahead policy. NOTE: • Controller non-volatile cache and battery backup of controller cache affects the read-policy or the write policy that a controller can support. All PERCs do not have battery and cache. • Read ahead and write back requires cache. Therefore, if the controller does not have cache, it does not allow you to set the policy value.
A fast initialization on a virtual disk overwrites the first and last 8 MB of the virtual disk, clearing any boot records or partition information. The operation takes only 2-3 seconds to complete and is recommended when you are recreating virtual disks. A background initialization starts five minutes after the Fast Initialization is completed. Full or Slow Initialization The full initialization (also called slow initialize) operation initializes all physical disks included in the virtual disk.
• • 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.
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 read mode is manual Patrol read unconfigured areas Check consistency mode Copyback mode Load balance mode Check consistency rate Rebuild rate BGI rate Reconstruct rate Enhanced auto import foreign configuration Create or change security keys NOTE: You can configure the Patrol Read Unconfigured Areas property using the
Check Consistency The Check Consistency task verifies the accuracy of the redundant (parity) information. This task only applies to redundant virtual disks. When necessary, the Check Consistency task rebuilds the redundant data. If the virtual disk is in a Failed Redundancy state, running a check consistency may be able to return the virtual disk to a Ready state.
• 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.
Importing Foreign Configuration Using Web Interface To import foreign configuration: 1. In the iDRAC Web interface, go to Overview > Storage > Controllers > Setup. The Setup Controllers page is displayed. 2. In the Foreign Configuration section, from the Controller drop-down menu, select the controller that you want to configure. 3. From the Apply Operation Mode drop-down menu, select when you want to import. 4. Click Import Foreign Configuration.
You may recreate the exact same configuration without an initialize operation which may result in the data being recovered. You must have server control privilege. NOTE: Resetting the controller configuration does not remove a foreign configuration. To remove a foreign configuration, perform clear configuration operation. Resetting Controller Configuration Using Web Interface To reset the controller configuration: 1. In the iDRAC Web interface, go to Overview > Storage > Controllers > Troubleshooting.
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.
• • Securely erase the data Blink or unblink the device LED Related concepts Inventory and Monitoring PCIe SSDs Preparing to Remove PCIe SSD Erasing PCIe SSD Device Data Inventory and Monitoring PCIe SSDs In staged or real-time, the following inventory and monitoring information is available for PCIe SSDs: • Hardware information: • • PCIe SSD Extender card • PCIe SSD Backplane Software inventory includes only the firmware version for the PCIe SSD.
Before preparing the PCIe SSD for removal, make sure that: • • • iDRAC Service Module is installed. Lifecycle Controller is enabled. You have Server Control and Login privileges Preparing to Remove PCIe SSD Using Web Interface To prepare the PCIe SSD for removal: 1. In the iDRAC Web interface, go to Overview > Storage > Physical Disks > Setup. The Setup Physical Disk page is displayed. 2. From the Controller drop-down menu, select the extender to view the associated PCIe SSDs. 3.
Erasing PCIe SSD Device Data Using Web Interface To erase the data on the PCIe SSD device: 1. In the iDRAC Web interface, go to Overview > Storage > Physical Disks > Setup. The Setup Physical Disk page is displayed. 2. From the Controller drop-down menu, select the controller to view the associated PCIe SSDs. 3. From the drop-down menus, select Secure Erase for one or more PCIe SSDs.
Related concepts Summary of Supported Features for Storage Devices Supported Enclosures Configuring Backplane Mode 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.
1. At the RACADM command prompt, run the following command to view the current backplane mode: get storage.enclosure.1.backplanecurrentmode The output is: BackplaneCurrentMode=UnifiedMode 2. Run the following command to view the requested mode: get storage.enclosure.1.backplanerequestedmode The output is: BackplaneRequestedMode=None 3. Run the following command to set the requested backplane mode to split mode: set storage.enclosure.1.backplanerequestedmode "splitmode" The successful message is displayed.
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. Run the following command and verify that only 0–11 drives are displayed: storage get pdisks For more information about the racadm command, see the iDRAC8 RACADM Command Line Interface Reference Guide available at dell.
Choosing Operation Mode to Apply Settings While creating and managing virtual disks, setting up physical disks, controllers, and enclosures or resetting controllers, before you apply the various settings, you must select the operation mode. That is, specify when you want to apply the settings: • • • • Immediately During the next system reboot At a scheduled time As a pending operation to be applied as a batch as part of a single job.
Viewing and Applying Pending Operations You can view and commit all pending operations for the storage controller. All the settings are either applied at once, during the next reboot, or at a scheduled time based on the selected options. You can delete all the pending operations for a controller. You cannot delete individual pending operations. Pending Operations are created on the selected components (controllers, enclosures, physical disks, and virtual disks).
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.
Case 4: Selected Add to Pending Operations and there are prior existing pending operations If you have selected Add to Pending Operations and then clicked Apply, first the pending operation is created for the selected storage configuration operation. • If the pending operation is created successfully and if there are existing pending operations, then an information message is displayed: • • Click OK to remain on the page to perform more storage configuration operations.
• • Select or deselect all virtual disks — Select the Select/Deselect All option and click Blink to start blinking the LEDs for all the virtual disks. Similarly, click Unblink to stop blinking the LEDs. Select or deselect individual virtual disks — Select one or more virtual disks and click Blink to start blinking the LEDs for the virtual disks. Similarly, click Unblink to stop blinking the LEDs. If the blink or unblink operation is not successful, error messages are displayed.
14 Configuring and Using Virtual Console 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.
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. Press at the iDRAC Virtual Console to switch Linux to a text console. Configuring Web Browsers to Use Virtual Console To use Virtual Console on your management station: 1.
2. Add iDRAC IP or hostname to the Trusted Sites list. 3. Reset the custom settings to Medium-low or change the settings to allow installation of signed ActiveX plug-ins. 4. Enable the browser to download encrypted content and to enable third-party browser extensions. To do this, go to Tools > Internet Options > Advanced, clear the Do not save encrypted pages to disk option, and select the Enable third-party browser extensions option.
4. Delete the Video Viewer add-on. Clearing Earlier ActiveX Versions in IE8 To clear earlier versions of Active-X viewer for IE8, do the following: 1. Close the Video Viewer and Internet Explorer browser. 2. Open the Internet Explorer browser again and go to Internet Explorer > Tools > Manage Add-ons and click Enable or Disable Add-ons. The Manage Add-ons window is displayed. 3. Select All Add-ons from the Show drop-down menu. 4. Select the Video Viewer add-on and click the More Information link. 5.
4. Copy the renamed CA certificate to your home directory. For example, C:\Documents and Settings\ directory. Configuring Virtual Console Before configuring the Virtual Console, make sure that the management station is configured. You can configure the virtual console using iDRAC Web interface or RACADM command line interface.
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. If the Virtual Console is configured to use ActiveX plug-in, it may not launch the first time. This is because of the slow network connection and the temporary credentials (that Virtual Console uses to connect) timeout is two minutes. The ActiveX client plug-in download time may exceed this time.
Disabling Warning Messages While Launching Virtual Console Or Virtual Media Using Java or ActiveX Plug-in You can disable the warning messages while launching the Virtual Console or Virtual Media using Java plug-in. 1. Initially, when you launch Virtual Console or Virtual Media using Java plug-in, the prompt to verify the publisher is displayed. Click Yes. A certificate warning message is displayed indicating that a trusted certificate is not found.
NOTE: This is not applicable for managed systems running Windows operating system since they support Absolute Positioning. When using the Virtual Console to connect to a managed system with a recent Linux distribution operating system installed, you may experience mouse synchronization problems. This may be due to the Predictable Pointer Acceleration feature of the GNOME desktop. For correct mouse synchronization in the iDRAC Virtual Console, this feature must be disabled.
• • • Browser Stop Key • Browser Search Key • Browser Favorites key • Browser Start and Home key • Volume mute key • Volume down key • Volume up key • Next track key • Previous track key • Stop Media key • Play/Pause media key • Start mail key • Select media key • Start Application 1 key • Start Application 2 key All the individual keys (not a combination of different keys, but a single key stroke) are always sent to the managed system.
2. After the server boots to the operating system, the localhost.localdomain login prompt appears. Log in using the operating system user name and password. 3. If SysRq is not enabled, enable using echo 1 >/proc/sys/kernel/sysrq. 4. Run break sequence ~B. 5. Use the SysRq magic key to enable the SysRq function.
15 Managing Virtual Media 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. It is available by default for blade servers.
Table 27. Supported Drives and Devices Drive Supported Storage Media Virtual Optical Drives • • • • • Legacy 1.44 floppy drive with a 1.
Table 28. Attached Media State and System Response Attached Media State System Response Detach Cannot map an image to the system. Attach Media is mapped even when Client View is closed. Auto-attach Media is mapped when Client View is opened and unmapped when Client View is closed. Server Settings For Viewing Virtual Devices in Virtual Media You must configure the following settings in the management station to allow visibility of empty drives.
Launching Virtual Media Without Using Virtual Console Before you launch Virtual Media when the Virtual Console is disabled, make sure that • • Virtual Media is in Attach state. System is configured to unhide empty drives. To do this, in Windows Explorer, navigate to Folder Options, clear the Hide empty drives in the Computer folder option, and click OK. To launch Virtual Media when Virtual Console is disabled: 1. In the iDRAC Web Interface, go to Overview > Server > Virtual Console.
Viewing Virtual Device Details To view the virtual device details, in the Virtual Console Viewer, click Tools > Stats. In the Stats window, the Virtual Media section displays the mapped virtual devices and the read/write activity for each device. If Virtual Media is connected, this information is displayed. If Virtual Media is not connected, the “Virtual Media is not connected” message is displayed.
After the device/file is mapped, the name of its Virtual Media menu item changes to indicate the device name. For example, if the CD/DVD device is mapped to an image file named foo.iso, then the CD/DVD menu item on the Virtual Media menu is named foo.iso mapped to CD/DVD. A check mark for that menu item indicates that it is mapped.
Before you enable the boot once option, make sure that: • • • You have Configure User privilege. Map the local or virtual drives (CD/DVD, Floppy, or USB flash device) with the bootable media or image using the Virtual Media options Virtual Media is in Attached state for the virtual drives to appear in the boot sequence. To enable the boot once option and boot the managed system from the Virtual Media: 1. In the iDRAC Web interface, go to Overview > Server > Attached Media. 2.
16 Installing and Using VMCLI Utility 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 -i — Enables an interactive method of starting VMCLI. It ensures that the user name and password are not visible when processes are examined by other users. vmcli -r -S -u -p c {< device-name > | < image-file >} — Indicates whether the iDRAC CA certificate is valid. If the certificate is not valid, a warning message is displayed when you run this command.
For example, under a Linux operating system, the ampersand character (&) following the command causes the program to be spawned as a new background process. This technique is useful in script programs, as it allows the script to proceed after a new process is started for the VMCLI command (otherwise, the script blocks until the VMCLI program is terminated). When multiple VMCLI sessions are started, use the operating system-specific facilities for listing and terminating processes.
17 Managing vFlash SD Card 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 RACADM To view the vFlash SD card properties using RACADM, use one of the following: • Use the cfgvFlashSD object with the getconfig command. The following read-only properties are displayed: • • cfgVFlashSDSize • cfgVFlashSDLicensed • cfgVFlashSDAvailableSize • cfgVFlashSDHealth • cfgVFlashSDEnable • cfgVFlashSDWriteProtect • cfgVFlashSDInitialized Use the following objects with the get command: • • • • • iDRAC.vflashsd.AvailableSize iDRAC.vflashsd.Health iDRAC.
NOTE: The RACADM command functions only if a vFlash SD card is present. If a card is not present, the following message is displayed: ERROR: SD Card not present. Enabling or Disabling vFlash Functionality Using iDRAC Settings Utility To enable or disable the vFlash functionality: 1. In the iDRAC Settings utility, go to Media and USB Port Settings. The iDRAC Settings . Media and USB Port Settings page is displayed. 2.
2. Enter the command: racadm vFlashsd status The status of commands sent to the SD card is displayed. 3. To get the last status of all the vflash partitions, use the command:racadm vflashpartition status -a 4. To get the last status of a particular partition, use command:racadm vflashpartition status -i (index) NOTE: If iDRAC is reset, the status of the last partition operation is lost.
1. Open a telnet, SSH, or Serial console to the system and log in. 2. Enter the command: racadm vflashpartition create -i 1 -o drive1 -t empty -e HDD -f fat16 -s 20 A 20 MB empty partition in FAT16 format is created. By default, an empty partition is created as read-write. 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 (.
Before creating an partition from an image file, make sure that: • • • • You have Access Virtual Media privilege. The card is initialized. The card is not write-protected. An initialize operation is not being performed on the card. To format vFlash partition: 1. In iDRAC Web interface, go to Overview > Server > vFlash > Format. The Format Partition page is displayed. 2. Enter the required information and click Apply. For information about the options, see the iDRAC Online Help.
2. In the Read-Only column: • • Select the checkbox for the partition(s) and click Apply to change to read-only. Clear the checkbox for the partition(s) and click Apply to change to read-write. The partitions are changed to read-only or read-write, based on the selections. NOTE: If the partition is of type CD, the state is read-only. You cannot change the state to read-write. If the partition is attached, the check box is grayed-out.
1. Open a telnet, SSH, or Serial console to the system and log in. 2. Use any one of the following: • • Using config command: • To attach a partition: • racadm config –g cfgvflashpartition –i 1 –o cfgvflashPartitionAttachState 1 To detach a partition: racadm config –g cfgvflashpartition –i 1 –o cfgvflashPartitionAttachState 0 Using set command: • To attach a partition: • racadm set iDRAC.vflashpartition..AttachState 1 To detach a partition: racadm set iDRAC.vflashpartition..
Downloading Partition Contents You can download the contents of a vFlash partition in the .img or .iso format to the: • • Managed system (where iDRAC is operated from) Network location mapped to a management station. 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.
18 Using SMCLP 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.
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. iDRAC SMCLP Syntax The iDRAC SMCLP uses the concept of verbs and targets to provide systems management capabilities through the CLI. The verb indicates the operation to perform, and the target determines the entity (or object) that runs the operation.
Target Definitions admin1/system1/logs1 admin1/system1/logs1/log1 admin1/system1/logs1/log1/record* admin1/system1/settings1 admin1/system1/capacities1 admin1/system1/consoles1 admin1/system1/sp1 admin1/system1/sp1/timesvc1 admin1/system1/sp1/capabilities1 admin1/system1/sp1/capabilities1/clpcap1 admin1/system1/sp1/capabilities1/pwrmgtcap1 admin1/system1/sp1/capabilities1/acctmgtcap* admin1/system1/sp1/capabilities1/rolemgtcap* admin1/system1/sp1/capabilities/ PwrutilmgtCap1 admin1/system1/sp1/capabilitie
Target admin1/system1/sp1/jobq1 admin1/system1/sp1/jobq1/job* admin1/system1/sp1/pwrmgtsvc1 admin1/system1/sp1/account1-16 admin1/sysetm1/sp1/account1-16/identity1 admin1/sysetm1/sp1/account1-16/identity2 admin1/sysetm1/sp1/account1-16/identity3 admin1/sysetm1/sp1/account1-16/identity4 admin1/system1/sp1/acctsvc1 admin1/system1/sp1/acctsvc2 admin1/system1/sp1/acctsvc3 admin1/system1/sp1/rolesvc1 admin1/system1/sp1/rolesvc1/Role1-16 admin1/system1/sp1/rolesvc1/Role1-16/ privilege1 admin1/system1/sp1/rolesvc2
Related concepts 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. The root target is represented by a slash (/) or a backslash (\). It is the default starting point when you log in to iDRAC.
• • SEL Management MAP Target Navigation Server Power Management The following examples show how to use SMCLP to perform power management operations on a managed system.
Commands: cd 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.
exit Using SMCLP 237
19 Using iDRAC Service Module 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.
• Prepare to Remove NVMe PCIe SSD. For more information, see iDRACUG_Preparing to Remove NVMe PCIe SSD. NOTE: The features such as Windows Management Instrumentation Providers, Prepare to Remove NVMe PCIe SDD through iDRAC, Automating Technical Support Report OS collection are supported only on 13th generation Dell PowerEdge servers with minimum firmware version 2.00.00.00 or later.
CIM Interface Enumerate instances of a class Get a specific instance of a class Get associated instances of an instance Get references of an instance WinRM WMIC PowerShell winrm e wmi/root/ cimv2/dcim/ dcim_account wmic /namespace:\ \root\cimv2\dcim PATH dcim_account Get-WmiObject dcim_account namespace root/ cimv2/dcim winrm g wmi/root/ cimv2/dcim/ DCIM_Account? CreationClassName=DC IM_Account +Name=iDRAC.Embedded .1#Users.
Using iDRAC Service Module From iDRAC Web Interface To use the iDRAC Service Module from the iDRAC Web interface: 1. Go to Overview > Server > Service Module. The iDRAC Service Module Setup page is displayed. 2. You can view the following: • • Installed iDRAC Service Module version on the host operating system Connection status of the iDRAC Service Module with iDRAC. 3.
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. This port is not available in a few of the 200-500 model variations without the LCD panel.
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. NOTE: PowerEdge systems that do not have the LCD and the LED panel does not support the USB key.
The Configure USB Management Port page is displayed. 2. From the USB Management Port Mode drop-down menu, select any of the following options: • • • 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. 3.
Importing Server Configuration Profile From USB Device Make sure to create a directory in root of the USB device called System_Configuration_XML which contains both the config.xml and control.xml files.: • • Server Configuration Profile is in the System_Configuration_XML sub-directory under the USB device root directory. This file includes all the attribute-value pairs of the server. This includes attributes of iDRAC, PERC, RAID, and BIOS. You can edit this file to configure any attribute on the server.
2. 3. 4. 5. Applying — When the job is in-progress. Completed — When the job has completed successfully. Completed with errors — When the job has completed with errors. Failed — When the job has failed. For more details, see the results file on the USB device. LED Blinking Behavior If the USB LED is present, it indicates the following: • • • Solid green – When the server configuration profile is being copied from the USB device. Blinking green – When the job is in-progress.
21 Using iDRAC Quick Sync A few 13th generation Dell PowerEdge servers have the Quick Sync bezel that supports the Quick Sync feature. This feature enables atthe-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 Settings Using Web Interface To configure iDRAC Quick Sync: 1. In the iDRAC Web interface, go to Overview > Hardware > Front Panel. 2. In the iDRAC Quick Sync section, from the Access drop-down menu, select one of the following to provide access to the Andriod mobile device: • • • Read-write Read-only Disabled 3. Enable the Timer. 4. Specify the Timeout value. For more information about the fields, see the iDRAC Online Help. 5. Click Apply to apply the settings.
22 Deploying Operating Systems 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 tasks Deploying Operating System Using VMCLI Deploying Operating System Using Remote File Share Deploying Operating System Using Virtual Media Topics: • • • • Deploying Operating System Using VMCLI Deploying Operating System Using Remote File Share Deploying Operating System Using Virtual
NOTE: The vmdeploy script processes the -r option slightly differently than the vmcli -r option. If the argument to the -r option is the name of an existing file, the script reads iDRAC IPv4 or IPv6 addresses from the specified file and runs the utility once for each line. If the argument to the -r option is not a filename, then it should a single iDRAC address. In this case, the -r works as described for the VMCLI utility. The following table describes the vmdeploy command parameters. Table 32.
4. Select the Boot Once option to enable the managed system to reboot using the image file for the next instance only. 5. Click Apply. 6. Reboot the managed system and follow the on-screen instructions to complete the deployment.
The following characters are supported for image file path, user name and password: • • • • • Uppercase characters Lowercase characters Digits from 0–9 _, -, ?, <, >, /, \, :, *, |, @ Whitespace 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. 4. Click Apply and then click Connect. After the connection is established, the Connection Status displays Connected.
1. Do one of the following: • • Insert the operating system installation CD or DVD into the management station CD or DVD drive. Attach the operating system image. 2. Select the drive on the management station with the required image to map it. 3. Use one of the following methods to boot to the required device: • • Set the boot order to boot once from Virtual Floppy or Virtual CD/DVD/ISO using the iDRAC Web interface.
About IDSDM Internal Dual SD Module (IDSDM) is available only on applicable platforms. IDSDM provides redundancy on the hypervisor SD card by using another SD card that mirrors the first SD card’s content. Either of the two SD cards can be the master. For example, if two new SD cards are installed in the IDSDM, SD1 is active (master) card and SD2 is the standby card. The data is written on both the cards, but the data is read from SD1.
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 tasks 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 Har
2. In the Command text box, enter a command and click Submit. For information about the commands, see the iDRAC Online Help. The results are displayed on the same page. Scheduling Remote Automated Diagnostics You can remotely invoke automated offline diagnostics on a server as a one-time event and return the results. If the diagnostics require a reboot, you can reboot immediately or stage it for a subsequent reboot or maintenance cycle (similar to updates).
Viewing Post Codes Post codes are progress indicators from the system BIOS, indicating various stages of the boot sequence from power-on-reset, and allows you to diagnose any faults related to system boot-up. The Post Codes page displays the last system post code prior to booting the operating system. To view the Post Codes, go to Overview > Server > Troubleshooting > Post Code. The Post Code page displays the system health indicator, a hexadecimal code, and a description of the code.
Viewing Front Panel Status The Front Panel on the managed system summarizes the status of the following components in the system: • • • • • • • Batteries Fans Intrusion Power Supplies Removable Flash Media Temperatures Voltages You can view the status of the front panel of the managed system: • • For rack and tower servers: LCD front panel and system ID LED status or LED front panel and system ID LED status. For blade servers: Only system ID LEDs.
Based on the problem, use the following methods to correct the problem: • • • • Reseat the module or component and restart the system In case of a blade server, insert the module into a different bay in the chassis Replace hard drives or USB flash drives Reconnect or replace the power and network cables If problem persists, see the Hardware Owner’s Manual for specific troubleshooting information about the hardware device.
After the report is generated, you can view the report. It contains a bunch of XML files and log files. The report must be shared with tech support to troubleshoot the issue. Each time the data collection is performed, an event is recorded in the Lifecycle Controller log. The event includes information such as the interface used, the date and time of export, and iDRAC user name.
operating system from the server OS to collect and transfer the data to iDRAC. You can then export the report to a local or network shared location. In 13th generation Dell PowerEdge systems, the OS collector DUP is installed in factory. However, if you determine that OS Collector is not present in iDRAC, then you can download the DUP file from the Dell support site and then upload the file to iDRAC using the Firmware Update process.
3. Click Attach OS Collector. You are directed to access the host OS. A message asking you to launch Virtual Console is displayed. 4. After you launch the Virtual Console, click the pop-up message to run and use the OS Collector tool to collect the data. 5. Navigate to the DRACRW virtual USB device that is presented to the system by the iDRAC. 6. Invoke the OS Collector file appropriate for the host operating system: • • For Windows, run Windows_OSCollector_Startup.bat.
• • You have iDRAC Server Control privilege. Lifecycle Controller is enabled. 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.
24 Frequently Asked Questions 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 Topics: • • • • • • • • • • • • • System Event Log Network Security Active Directory Single Sign-On Smart Card Login Virtual Console Virtual Media vFlash SD Card SNMP Authenticat
iDRAC includes a default iDRAC server certificate to ensure network security while accessing through the Web-based interface and remote RACADM. This certificate is not issued by a trusted CA. To resolve this, 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.
Check the Subject or Subject Alternative Name field of your domain controller certificate. Normally, Active Directory uses the host name and not the IP address of the domain controller in the Subject or Subject Alternative Name field of the domain controller certificate. To resolve this, do any of the following: • • • Configure the host name (FQDN) of the domain controller as the domain controller address(es) on iDRAC to match the Subject or Subject Alternative Name of the server certificate.
3. 4. 5. 6. Make sure that the domain clients have the updated GPO. At the command line, type gpupdate /force and delete the old key tab with klist purge command. After the GPO is updated, create the new keytab. Upload the keytab to iDRAC. You can now log in to iDRAC using SSO. Why does SSO login fail with Active Directory users on Windows 7 and Windows Server 2008 R2? You must enable the encryption types for Windows 7 and Windows Server 2008 R2. To enable the encryption types: 1. 2. 3. 4. 5. 6.
Yes. Why does it take 15 seconds to turn off the local video on the server after requesting to turn off the local video? It gives a local user an opportunity to take any action before the video is switched off. Is there a time delay when turning on the local video? No, after a local video turn ON request is received by iDRAC, the video is turned on instantly. 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.
If a Virtual Console session is in-progress and a local user accesses the managed server, does the first user receive a warning message? No. If a local user accesses the system, both have control of the system. How much bandwidth is required to run a Virtual Console session? It is recommended to have a 5 MBPS connection for good performance. A 1 MBPS connection is required for minimal performance.
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. This duration is longer on 10 Gb cards, and is also exceptionally long if the connected network switch has Spanning Tree Protocol (STP) enabled.
3. At the Linux prompt, run the following command: grep "hh:mm:ss" /var/log/messages where, hh:mm:ss is the time stamp of the message returned by grep in step 1. 4. In step 3, read the result of the grep command and locate the device name that is given to the Virtual Floppy. 5. Make sure that you are attached and connected to the virtual floppy drive. 6.
Why is an error message displayed when trying to connect a DVD/USB through virtual media even though the virtual media is currently not in use? The error message is displayed if Remote File Share (RFS) feature is also in use. At a time, you can use RFS or Virtual Media and not both. vFlash SD Card When is the vFlash SD card locked? The vFlash SD card is locked when an operation is in-progress. For example, during an initialize operation.
The following message is displayed in the OS log, even when the OS to iDRAC Pass-through over USBNIC is configured properly. Why? The iDRAC Service Module is unable to communicate with iDRAC using the OS to iDRAC Pass-through channel iDRAC Service Module uses the OS to iDRAC pass-through over USB NIC feature to establish the communication with iDRAC. Sometimes, the communication is not established though the USB NIC interface is configured with the correct IP endpoints.
RACADM After performing an iDRAC reset (using the racadm racreset command), if any command is issued, the following message is displayed. What does this indicate? ERROR: Unable to connect to RAC at specified IP address The message indicates that you must wait until the iDRAC completes the reset before issuing another command. When using RACADM commands and subcommands, some errors are not clear.
Subnet Mask Gateway = 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.
When attempting to boot the managed server, the power indicator is green, but there is no POST or no video. This happens due to any of the following conditions: • • • Memory is not installed or is inaccessible. CPU is not installed or is inaccessible Video riser card is missing or not connected properly. Also, see error messages in iDRAC log using iDRAC Web interface or from the server LCD.
25 Use Case Scenarios This section helps you in navigating to specific sections in the guide to perform typical use case scenarios.
Inventory and Monitoring Storage Devices 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.
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. From the Power Control drop-down menu, select Graceful Shutdown and click Apply. For more information, see the iDRAC Online Help.
Installing New Electronic License See License Operations for more information. Applying I/O Identity Configuration Settings for Multiple Network Cards in Single Host System Reboot If you have multiple network cards in a server that is part of a Storage Area Network (SAN) environment and you want to apply different virtual addresses, initiator and target configuration settings to those cards, use the I/O Identity Optimization feature to reduce the time in configuring the settings. To do this: 1.
