Integrated Dell Remote Access Controller 7 (iDRAC7) Version 1.40.
Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2013 Dell Inc.
Contents 1 Overview.....................................................................................................................................13 Benefits of Using iDRAC7 With Lifecycle Controller...............................................................................................13 Key Features........................................................................................................................................................... 14 New In This Release...................
Enabling or Disabling Default Password Warning Message Using Web Interface.........................................33 Enabling or Disabling Warning Message to Change Default Login Password Using RACADM......................33 3 Setting Up Managed System and Management Station.................................................... 35 Setting Up iDRAC7 IP Address................................................................................................................................
Restore Operation Sequence...........................................................................................................................53 Monitoring iDRAC7 Using Other Systems Management Tools...............................................................................53 4 Configuring iDRAC7...................................................................................................................55 Viewing iDRAC7 Information...........................................................
5 Viewing iDRAC7 and Managed System Information...........................................................77 Viewing Managed System Health and Properties..................................................................................................77 Viewing System Inventory...................................................................................................................................... 77 Viewing Sensor Information......................................................................
Disabling Local RACADM....................................................................................................................................... 97 Enabling IPMI on Managed System....................................................................................................................... 97 Configuring Linux for Serial Console During Boot..................................................................................................
9 Configuring iDRAC7 to Send Alerts...................................................................................... 137 Enabling or Disabling Alerts................................................................................................................................. 137 Enabling or Disabling Alerts Using Web Interface.........................................................................................137 Enabling or Disabling Alerts Using RACADM..........................................
Executing Power Control Operations Using Web Interface...........................................................................152 Executing Power Control Operations Using RACADM...................................................................................152 Power Capping..................................................................................................................................................... 152 Power Capping in Blade Servers................................................
Mapping Virtual Drive.................................................................................................................................... 171 Unmapping Virtual Drive................................................................................................................................ 172 Setting Boot Order Through BIOS........................................................................................................................ 172 Enabling Boot Once for Virtual Media......
17 Deploying Operating Systems.............................................................................................197 Deploying Operating System Using VMCLI ..........................................................................................................197 Deploying Operating System Using Remote File Share........................................................................................198 Managing Remote File Share....................................................................
RACADM...............................................................................................................................................................219 Miscellaneous...................................................................................................................................................... 220 20 Use Case Scenarios..............................................................................................................
Overview 1 The Integrated Dell Remote Access Controller 7 (iDRAC7) is designed to make server administrators more productive and improve the overall availability of Dell servers. iDRAC7 alerts administrators to server issues, helps them perform remote server management, and reduces the need for physical access to the server. iDRAC7 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 iDRAC7 include: NOTE: Some of the features are available only with iDRAC7 Enterprise license. For information on the features available for a license, see Managing Licenses. Inventory and Monitoring • View managed server health.
• No dependency on Server Administrator for generation of alerts. • Log event data: Lifecycle and RAC logs. • Set email alerts, IPMI alerts, remote system logs, WS eventing logs, and SNMP traps (v1 and v2c) for events and improved email alert notification. • Capture last system crash image. • View boot and crash capture videos. Secure Connectivity Securing access to critical network resources is a priority.
• For the 12th generation PowerEdge systems shipping with eMMC 2 GB card that has JEDEC 4.5 standard, the minimum supported version of iDRAC supported is 1.40.40.
iDRAC7 license management and firmware update functionality is available through iDRAC7 Web interface and RACADM. Types of Licenses The types of licenses offered are: • 30 day evaluation and extension — The license expires after 30 days and can be extended for 30 days. Evaluation licenses are duration based, and the timer runs when power is applied to the system. • Perpetual — The license is bound to the service tag and is permanent.
For one-to-many license deployment, you can use Dell License Manager. For more information, see the Dell License Manager User’s Guide available at dell.com/support/manuals. Importing License After Replacing Motherboard You can use the Local iDRAC7 Enterprise License Installation Tool if you have recently replaced the motherboard and need to reinstall the iDRAC7 Enterprise license locally (with no network connectivity) and activate the dedicated NIC.
Feature Basic Management with IPMI iDRAC7 Express (Rack and Tower Servers) iDRAC7 iDRAC7 Express (for Enterprise Blade Servers) WS-MAN Yes Yes Yes Yes SMASH-CLP (SSH) No Yes Yes Yes RACADM (SSH, Local, and Remote) [1] No Yes Yes Yes Telnet No Yes Yes Yes Shared or Failover Network Yes Modes (rack and tower servers only) Yes No Yes Dedicated NIC No No Yes [ 2] Yes [2,6] DNS Yes Yes Yes Yes VLAN Tagging Yes Yes Yes Yes IPv4 Yes Yes Yes Yes IPv6 No Yes Yes Ye
Feature Basic Management with IPMI iDRAC7 Express (Rack and Tower Servers) iDRAC7 iDRAC7 Express (for Enterprise Blade Servers) Remote File Share No No No Yes vFlash [6] No No No Yes vFlash Partitions [6] No- No No Yes Auto-discovery No Yes Yes Yes Backup Server Profile No No No Yes Parts Replacement [8] No Yes Yes Yes Network Time Protocol (NTP) No Yes Yes Yes Sensor monitoring and alerting Yes Yes Yes Yes Device Monitoring No Yes Yes Yes Storage Monitoring
Interfaces and Protocols to Access iDRAC7 The following table lists the interfaces to access iDRAC7. NOTE: Using more than one interface at the same time may generate unexpected results. Table 3. Interfaces and Protocols to Access iDRAC7 Interface or Protocol Description iDRAC Settings Utility Use the iDRAC Settings utility to perform pre-OS operations. It has a subset of the features that are available in iDRAC7 Web interface along with other features.
Interface or Protocol Description • Update BIOS, PERC, and supported network adapters Lifecycle Controller Use Lifecycle Controller to perform iDRAC7 configurations. To access Lifecycle Controller, press during boot and go to System Setup → Advanced Hardware Configuration → iDRAC Settings . For more information, see Lifecycle Controller User’s Guide available at dell.com/support/manuals. Telnet Use Telnet to access iDRAC7 where you can run RACADM and SMCLP commands.
iDRAC7 Port Information The following ports are required to remotely access iDRAC7 through firewalls. These are the default ports iDRAC7 listens to for connections. Optionally, you can modify most of the ports. To do this, see Configuring Services. Table 4.
• The Dell Lifecycle Controller Remote Services Quick Start Guide provides an overview of the Remote Services capabilities, information on getting started with Remote Services, Lifecycle Controller API, and provides references to various resources on Dell Tech Center.
3. Verify your country or region in the Choose a Country/Region drop-down menu at the top of page. 4. Select the appropriate service or support link based on your need. Accessing Documents From Dell Support Site To access the documents from Dell Support site: 1. Go to dell.com/support/manuals. 2. In the Tell us about your Dell system section, under No, select Choose from a list of all Dell products and click Continue. 3. In the Select your product type section, click Software and Security. 4.
Logging into iDRAC7 2 You can log in to iDRAC7 as an iDRAC7 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 iDRAC7.
5. For an LDAP user, in the Username and Password fields, enter your LDAP user name and password. Domain name is not required for LDAP login. By default, This iDRAC is selected in the drop-down menu. 6. Click Submit. You are logged into iDRAC7 with the required user privileges. If you log in with Configure Users privileges and the default account credentials, and if the default password warning feature is enabled, the Default Password Warning page is displayed allowing you to easily change the password.
NOTE: If you are a local user for whom Enable CRL check for Smart Card Logon is enabled, iDRAC7 attempts to download the CRL and checks the CRL for the user's certificate. The login fails if the certificate is listed as revoked in the CRL or if the CRL cannot be downloaded for some reason.
To login to iDRAC7 using Web interface: 1. Log in to your management station using a valid Active Directory account. 2. In a Web browser, type https://[FQDN address] NOTE: If the default HTTPS port number (port 443) has been changed, type: https://[FQDN address]: [port number] where, [FQDN address] is the iDRAC7 FQDN (iDRAC7dnsname.domain. name) and [port number] is the HTTPS port number. NOTE: If you use IP address instead of FQDN, SSO fails.
4. Generate and upload the server certificate to iDRAC7. Accessing iDRAC7 Using Local RACADM For information to access iDRAC7 using local RACADM, see the RACADM Command Line Reference Guide for iDRAC7 and CMC available at dell.com/support/manuals. Accessing iDRAC7 Using Firmware RACADM You can use SSH or Telnet interfaces to access iDRAC7 and run firmware RACADM commands. For more information, see the RACADM Command Line Reference Guide for iDRAC7 and CMC available at dell.com/support/manuals.
Interface Number of Sessions Serial - 1 Changing Default Login Password The warning message that allows you to change the default password is displayed if: • You log in to iDRAC7 with Configure Users privilege. • Default password warning feature is enabled. • Credentials for any currently enabled account are root/calvin. The same warning message is displayed if you log in using Active Directory or LDAP.
For more information, see the RACADM Command Line Reference Guide for iDRAC7 and CMC. Changing Default Login Password Using iDRAC Settings Utility To change the default login password using iDRAC Settings Utility: 1. In the iDRAC Settings utility, go to User Configuration. The iDRAC Settings.User Configuration page is displayed. 2. In the Change Password field, enter the new password. 3. Click Back, click Finish, and then click Yes. The details are saved.
Setting Up Managed System and Management Station 3 To perform out-of-band systems management using iDRAC7, you must configure iDRAC7 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.
In case of blade servers, the iDRAC7 network interface is disabled by default. After you configure iDRAC7 IP address: • Make sure to change the default user name and password after setting up the iDRAC7 IP address. • Access it through any of the following interfaces: – iDRAC7 Web interface using a supported browser (Internet Explorer, Firefox, Chrome, or Safari) – Secure Shell (SSH) — Requires a client such as PuTTY on Windows.
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).
IPv4 Settings To configure the IPv4 settings: 1. Select Enabled option under Enable IPv4 . 2. Select Enabled option under Enable DHCP , so that DHCP can automatically assign the IP address, gateway, and subnet mask to iDRAC7. Else, select Disabled and enter the values for: 3. – Static IP Address – Static Gateway – Static Subnet Mask Optionally, enable Use DHCP to obtain DNS server address, so that the DHCP server can assign the Static Preferred DNS Server and Static Alternate DNS Server.
NOTE: You must have Chassis Configuration Administrator privilege to set up iDRAC7 network settings from CMC. 1. Log in to CMC Web interface. 2. Go to Server Overview → Setup → iDRAC. The Deploy iDRAC page is displayed. 3. Under iDRAC Network Settings, select Enable LAN and other network parameters as per requirements. For more information, see CMC online help. 4. For additional network settings specific to each blade server, go to Server Overview → . The Server Status page is displayed.
4. Click Network. The iDRAC Settings Network page is displayed. 5. Enable NIC. 6. Enable IPv4. NOTE: IPv6 is not supported for auto-discovery. 7. Enable DHCP and get the domain name, DNS server address, and DNS domain name from DHCP. NOTE: Step 7 is optional if the provisioning server IP address (step 3) is provided. Setting Up Management Station A management station is a computer used for accessing iDRAC7 interfaces to remotely monitor and manage the PowerEdge server(s).
Network Settings Setting Up Managed System If you need to run local RACADM or enable Last Crash Screen capture, install the following from the Dell Systems Management Tools and Documentation DVD: • Local RACADM • Server Administrator For more information about Server Administrator, see Dell OpenManage Server Administrator User’s Guide available at dell.com/support/manuals.
Setting Up Managed System Location Using iDRAC Settings Utility To specify the system location details: 1. In the iDRAC Settings utility, go to System Location. The iDRAC Settings System Location page is displayed. 2. Enter the location details of the managed system in the data center. For information about the options, see the iDRAC Settings Utility Online Help. 3. Click Back, click Finish, and then click Yes. The details are saved.
– 3. Fan Speed Offset (Default = None) – Specify the fan speed offset when increased thermal margin is required for custom high-power PCIe cards or for reducing system exhaust temperatures for adjacent equipment such as switches. A fan speed offset causes fan speeds to increase (by the offset % value) over baseline fan speeds calculated by the Thermal Control algorithm. By default, the value is None. You can select: * Low Fan Speed Offset - Drives fan speeds to a moderate fan speed (approx.
Under Scripting: – Active scripting: Enable – Allow paste operations via script: Enable – Scripting of Java applets: Enable 4. Go to Tools → Internet Options → Advanced . 5.
9. If the Use a proxy server box is selected, select the Bypass proxy server for local addresses box. 10. Click OK twice. 11. Close and restart your browser to make sure all changes take effect.
• German (de) • Spanish (es) • Japanese (ja) • Simplified Chinese (zh-cn) The ISO identifiers in parentheses denote the supported language variants. For some supported languages, resizing the browser window to 1024 pixels wide is required to view all features. iDRAC7 Web interface is designed to work with localized keyboards for the supported language variants. Some features of iDRAC7 Web interface, such as Virtual Console, may require additional steps to access certain functions or letters.
Downloading Device Firmware The image file format that you download depends on the method of update: • iDRAC7 Web interface — Download the binary image packaged as a self-extracting archive. The default firmware image file is firmimg.d7. NOTE: The same file format is used to recover iDRAC7 using CMC Web interface. • Managed System — Download the operating system-specific Dell Update Package (DUP). The file extensions are .bin for Linux Operating systems and .exe for Windows operating systems.
To update iDRAC7 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.
– Using update command: racadm -r -u -p update —f For more information, see fwupdate command in the RACADM Command Line Reference Guide for iDRAC7 and CMC available at dell.com/support/manuals. 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.
Rollback Firmware Using Lifecycle Controller-Remote Services Rollback Firmware Using iDRAC7 Web Interface To roll back firmware using iDRAC7 Web interface: NOTE: Currently, rollback for only iDRAC7 firmware is supported and is not supported for any other device firmware. 1. In the iDRAC7 Web interface, go to Overview → iDRAC Settings → Update and Rollback → Rollback . The Rollback page displays the current and previous firmware versions. 2. Click Next. The iDRAC7 reboots after the rollback is applied.
Rollback Firmware Using Lifecycle Controller-Remote Services For information, see Lifecycle Controller Remote Services Quick Start Guide available at dell.com/support/manuals. Recovering iDRAC7 iDRAC7 supports two operating system images to make sure a bootable iDRAC7. In the event of an unforeseen catastrophic error and you lose both boot paths: • iDRAC7 bootloader detects that there is no bootable image. • System Health and Identify LED is flashed at ~1/2 second rate.
as captured in the backup file. If components are different or not in the same location, they are not modified and restore failures is logged to the Lifecycle Log. Backing Up Server Profile Using iDRAC7 Web Interface To back up the server profile using iDRAC7 Web interface: 1. Go to Overview → iDRAC Settings → Backup and Restore . The Backup and Restore Server Profile page is displayed. 2. Select Backup. 3. Select one of the following to save the backup file image: 4. 5.
Restoring Server Profile Using RACADM To restore the server profile using RACADM, use systemconfig restore command. For more information, see the RACADM Command Line Reference Guide for iDRAC7 and CMC available at dell.com/support/manuals. Restore Operation Sequence The restore operation sequence is: 1. Host system shuts down. 2. Backup file information is used to restore the Lifecycle Controller. 3. Host system turns on. 4. Firmware and configuration restore process for the devices is completed.
Configuring iDRAC7 4 iDRAC7 enables you to configure iDRAC7 properties, set up users, and set up alerts to perform remote management tasks. Before you configure iDRAC7, make sure that the iDRAC7 network settings and a supported browser is configured, and the required licenses are updated. For more information about the licensable feature in iDRAC7, see Managing Licenses.
Configuring Services Configuring Front Panel Display Setting Up Managed System Location Configuring Time Zone and NTP Setting Up iDRAC7 Communication Configuring User Accounts and Privileges Monitoring and Managing Power Enabling Last Crash Screen Configuring and Using Virtual Console Managing Virtual Media Managing vFlash SD Card Setting First Boot Device Enabling or Disabling OS to iDRAC Pass-through Configuring iDRAC7 to Send Alerts Viewing iDRAC7 Information You can view the basic properties of iDRAC7.
To modify the network settings using iDRAC7 Web interface or RACADM, you must have Configure privileges. NOTE: Changing the network settings may terminate the current network connections to iDRAC7. Modifying Network Settings Using Web Interface To modify the iDRAC7 network settings: 1. In the iDRAC7 Web interface, go to Overview → iDRAC Settings → Network. 2. Specify the network settings, common settings, IPv4, IPv6, IPMI, and/or VLAN settings as per your requirement and click Apply.
racadm racadm racadm racadm racadm racadm racadm set set set set set set set iDRAC.IPv4.DNSFromDHCP 0 iDRAC.IPv4.DNS1 192.168.0.5 iDRAC.IPv4.DNS2 192.168.0.6 iDRAC.Nic.DNSRegister 1 iDRAC.Nic.DNSRacName RAC-EK00002 iDRAC.Nic.DNSDomainFromDHCP 0 iDRAC.Nic.DNSDomainName MYDOMAIN NOTE: If cfgNicEnable or iDRAC.Nic.Enable is set to 0, the iDRAC7 LAN is disabled even if DHCP is enabled.
• – cfgRacTuneIpRangeAddr – cfgRacTuneIpRangeMask – cfgRacTuneIpBlkEnable – cfgRacTuneIpBlkFailCount – cfgRacTuneIpBlkFailWindow With set command, use the objects in the iDRAC.IPBlocking group: – RangeEnable – RangeAddr – RangeMask – BlockEnable – FailCount – FailWindow – PenaltyTime The cfgRacTuneIpRangeMask or the RangeMask property is applied to both the incoming IP address and to the cfgRacTuneIpRangeAddr or RangeAddr property.
• – Using config command: racadm config -g cfgRacTuning -o cfgRacTuneIpRangeEnable 1 racadm config -g cfgRacTuning -o cfgRacTuneIpBlkFailCount 5 racadm config -g cfgRacTuning -o cfgRacTuneIpBlkFailWindow 60 – Using set command: racadm set iDRAC.IPBlocking.RangeEnable 1 racadm set iDRAC.IPBlocking.FailCount 5 racadm set iDRAC.IPBlocking.
• Use the following objects with the config command: – • cfgRacTuneLocalConfigDisable – cfgRacTuneCtrlEConfigDisable – cfgSerialSshEnable – cfgRacTuneSshPort – cfgSsnMgtSshIdleTimeout – cfgSerialTelnetEnable – cfgRacTuneTelnetPort – cfgSsnMgtTelnetIdleTimeout – cfgRacTuneWebserverEnable – cfgSsnMgtWebserverTimeout – cfgRacTuneHttpPort – cfgRacTuneHttpsPort – cfgRacTuneRemoteRacadmEnable – cfgSsnMgtRacadmTimeout – cfgOobSnmpAgentEnable – cfgOobSnmpAgentCommunity Use the obje
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 iDRAC7 Web interface, go to Overview → Hardware → Front Panel. 2.
5. Click Back, click Finish, and then click Yes. Configuring System ID LED Setting To identify a server, enable or disable System ID LED blinking on the managed system. Configuring System ID LED Setting Using Web Interface To configure the System ID LED display: 1. In iDRAC7 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: 3.
Setting First Boot Device You can set the first boot device for the next boot only or for all subsequent reboots. Based on this selection, you can set the first boot device for the system. The system boots from the selected device on the next and subsequent reboots and remains as the first boot device in the BIOS boot order, until it is changed again either from the iDRAC7 Web interface or from the BIOS boot sequence.
To set the first boot device using Virtual Console: 1. Launch Virtual Console. 2. In the Virtual Console Viewer, from the Next Boot menu, set the required device as the first boot device. Enabling Last Crash Screen To troubleshoot the cause of managed system crash, you can capture the system crash image using iDRAC7. To enable the last crash screen: From the Dell Systems Management Tools and Documentation DVD, install Server Administrator on the managed system. 1.
Before enabling OS to iDRAC Pass-through, make sure that: • Host operating system and iDRAC7 are in the same subnet. • Host operating system IP address is configured. • You have Configure privilege. When you enable this feature: • In shared mode, the host operating system's IP address is auto-populated. • In dedicated mode, you must provide a valid IP address of the host operating system. If more than one LOM is active, enter the first LOM’s IP address.
Category Manufacturer Type Intel PCIe • 5719 QP 1G ADAPTER • • • • X540 DP 10G BASE-T ADAPTER I350 DP 1G ADAPTER I350 QP 1G ADAPTER X520 DP 10G SFP+ ADAPTER QLogic DP 10Gb SFP+/DA CNA ADAPTER Emulex LPe16000 Qlogic • • • • QLE2660 FC16 QLE2662 FC16 QLE2560 FC8 QLE2562 FC8 The following cards do not support the OS to iDRAC Pass-through feature: • Intel 10 Gig bNDC. • Intel rNDC (Elk Flat rNDC) with two controllers – 10G controllers does not support. • Qlogic bNDC Part # D90TX.
3. Click Back, click Finish, and then click Yes. The details are saved. Obtaining Certificates The following table lists the types of certificates based on the login type. Table 8.
For each iDRAC to be trusted by the management station, that iDRAC’s SSL certificate must be placed in the management station’s certificate store. Once the SSL certificate is installed on the management stations, supported browsers can access iDRAC without certificate warnings. You can also upload a custom signing certificate to sign the SSL certificate, rather than relying on the default signing certificate for this function.
Generating CSR Using RACADM To generate a CSR using RACADM, use the objects in the cfgRacSecurity group with the config command or use the objects in the iDRAC.Security group with the set command, and then use the sslcsrgen command to generate the CSR. For more information, see the RACADM Command Line Reference Guide for iDRAC7 and CMC available at dell.com/ support/manuals. Uploading Server Certificate After generating a CSR, you can upload the signed SSL server certificate to the iDRAC7 firmware.
Uploading Custom Signing Certificate Using Web Interface To upload the custom signing certificate using iDRAC7 Web interface: 1. Go to Overview → iDRAC Settings → Network → SSL. The SSL page is displayed. 2. Under Custom SSL Certificate Signing Certificate, select Upload Custom SSL Certificate Signing Certificate and click Next. The Upload Custom SSL Certificate Signing Certificate page is displayed. 3. Click Browse and select the custom SSL certificate signing certificate file.
The SSL page is displayed. 2. Under Custom SSL Certificate Signing Certificate, select Delete Custom SSL Certificate Signing Certificate and click Next. The custom signing certificate is deleted from iDRAC. iDRAC resets to use the default self-signed SSL certificate auto-generated by the Web server. iDRAC is not available during reset. Deleting Custom SSL Certificate Signing Certificate Using RACADM To delete the custom SSL certificate signing certificate using RACADM, use the sslcertdelete subcommand.
• Created • Obtained from racadm getconfig -f .cfg command or racadm get -f .cfg • Obtained from racadm getconfig -f .cfg command or racadm get -f .cfg, and then edited For information about the getconfig and get commands, see the RACADM Command Line Reference Guide for iDRAC7 and CMC available at dell.com/support/manuals . The .cfg file is first parsed to verify that valid group and object names are present and the basic syntax rules are being followed.
Parsing Rules • All lines that start with '#' are treated as comments. A comment line must start in column one. A '#' character in any other column is treated as a '#' character. Some modem parameters may include # characters in its string. An escape character is not required. You may want to generate a .cfg from a racadm getconfig -f .cfg command, and then perform a racadm config -f .cfg command to a different iDRAC7, without adding escape characters.
cfgNicGateway=10.35.10.1 This file is updated as follows: # # Object Group "cfgLanNetworking" # [cfgLanNetworking] cfgNicIpAddress=10.35.9.143 # comment, the rest of this line is ignored cfgNicGateway=10.35.9.1 The command racadm config -f myfile.cfg parses the file and identifies any errors by line number. A correct file updates the proper entries. Additionally, you can use the same getconfig command from the previous example to confirm the update.
Viewing iDRAC7 and Managed System Information 5 You can view iDRAC7 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.
• DIMMs • HDDs • NICs (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 When you replace any hardware component or
• Intrusion— Provides information about the chassis. • Power Supplies (available only for rack and tower servers) — Provides information about the power supplies and the power supply redundancy status. NOTE: If there is only one power supply in the system, the power supply redundancy is set to Disabled. • Removable Flash Media — Provides information about the Internal SD Modules—vFlash and Internal Dual SD Module (IDSDM).
View Sensor Information For Using Web Interface Voltage Overview → Server → Power/ Thermal → Voltages Using RACADM Checking the System for Fresh Air Compliance Fresh air cooling directly uses outside air to cool systems in the data center. Fresh air compliant systems can operate above its normal ambient operating range (temperatures up to 113 °F (45 °C)). NOTE: Fresh air configuration is not supported for 135W CPUs, PCIe SSD, GPU cards, and LR DIMMs.
You can also configure iDRAC to generate additional events. For more information, see the Setting Alert Recurrence Event section. Viewing Historical Temperature Data Using iDRAC7 Web Interface To view historical temperature data: 1. In the iDRAC7 Web interface, go to Overview → Server → Power / Thermal → Temperatures. The Temperatures page is displayed. 2.
• Go to Overview → Storage → Physical Disks to view physical disk information. The Physical Disks page is displayed. • Go to Overview → Storage → Virtual Disks to view virtual disks information. The Virtual Disks page is displayed. • Go to Overview → Storage → Controllers to view the RAID controller information. The Controllers page is displayed. • Go to Overview → Storage → Enclosures to view the enclosure information. The Enclosures page is displayed.
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.
CAUTION: With FlexAddress enabled, if you switch from a server–assigned MAC address to a chassis–assigned MAC address and vice–versa, iDRAC7 IP address also changes. Viewing or Terminating iDRAC7 Sessions You can view the number of users currently logged in to iDRAC7 and terminate the user sessions. Terminating iDRAC7 Sessions Using Web Interface The users who do not have administrative privileges must have Configure iDRAC7 privilege to terminate iDRAC7 sessions using iDRAC7 Web interface.
6 Setting Up iDRAC7 Communication You can communicate with iDRAC7 using any of the following modes: • iDRAC7 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.
Communicating With iDRAC7 Using IPMI SOL Communicating With iDRAC7 Using IPMI Over LAN Enabling or Disabling Remote RACADM Disabling Local RACADM Enabling IPMI on Managed System Configuring Linux for Serial Console During Boot Supported SSH Cryptography Schemes Communicating With iDRAC7 Through Serial Connection Using DB9 Cable You can use any of the following communication methods to perform systems management tasks through serial connection to rack and tower servers: • RAC Serial • IPMI Serial — Direc
6. Press to exit System Setup. Enabling RAC Serial Connection After configuring serial connection in BIOS, enable RAC serial in iDRAC7. NOTE: This is applicable only for iDRAC7 on rack and tower servers. Enabling RAC Serial Connection Using Web Interface To enable RAC serial connection: 1. In the iDRAC7 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.
Enabling Serial Connection IPMI Mode Using RACADM To configure the IPMI mode, disable the RAC serial interface and then enable the IPMI mode using any of the following: • 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.
The Serial page is displayed. 2. Enable IPMI serial. 3. Click Terminal Mode Settings. The Terminal Mode Settings page is displayed. 4. Specify the following values: – Line editing – Delete control – Echo Control – Handshaking control – New line sequence – Input new line sequences For information about the options, see the iDRAC7 Online Help. 5. Click Apply. The terminal mode settings are configured. 6.
Communicating With iDRAC7 Using IPMI SOL IPMI Serial Over LAN (SOL) allows a managed system’s text-based console serial data to be redirected over iDRAC7’s dedicated or shared out-of-band ethernet management network. Using SOL you can: • Remotely access operating systems with no time-out. • Diagnose host systems on Emergency Management Services (EMS) or Special Administrator Console (SAC) for Windows or Linux shell. • View the progress of a servers during POST and reconfigure the BIOS setup program.
Configuring iDRAC7 to Use SOL Using iDRAC7 Web Interface To configure IPMI Serial over LAN (SOL): 1. In the iDRAC7 Web interface, go to Overview → iDRAC Settings → Network → Serial Over LAN. The Serial over LAN page is displayed. 2. Enable SOL, specify the values, and click Apply. The IPMI SOL settings are configured. 3. To set the character accumulate interval and the character send threshold, select Advanced Settings. The Serial Over LAN Advanced Settings page is displayed. 4.
Enabling Supported Protocol The supported protocols are IPMI, SSH, and Telnet. Enabling Supported Protocol Using Web Interface To enable SSH or Telnet, go to Overview → iDRAC Settings → Network → Services and select Enabled for SSH or Telnet, respectively. To enable IPMI, go to Overview → iDRAC Settings → Network and select Enable IPMI Over LAN. Make sure that the Encryption Key value is all zeroes or press the backspace key to clear and change the value to NULL characters.
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. For installation instructions, see the Software Quick Installation Guide. 2.
NOTE: The port number is optional. It is required only when the port number is reassigned. 2. Run the command console com2 or connect to start SOL and boot the managed system. A SOL session from the management station to the managed system using the SSH or Telnet protocol is opened. To access the iDRAC7 command line console, follow the ESC key sequence.
Disconnecting SOL Session in iDRAC7 Command Line Console Using Telnet Virtual Console Some Telnet clients on the Microsoft operating systems may not display the BIOS setup screen correctly when BIOS Virtual Console is set for VT100/VT220 emulation. If this issue occurs, change the BIOS console to ANSI mode to update the display. To perform this procedure in the BIOS setup menu, select Virtual Console → Remote Terminal Type → ANSI.
Configuring IPMI Over LAN Using Web Interface To configure IPMI over LAN: 1. In the iDRAC7 Web interface, go to Overview → iDRAC Settings → Network. The Network page is displayed. 2. Under IPMI Settings, specify the values for the attributes and click Apply. For information about the options, see the iDRAC7 Online Help. The IPMI over LAN settings are configured. Configuring IPMI Over LAN Using iDRAC Settings Utility To configure IPMI over LAN: 1. In the iDRAC Settings Utility, go to Network.
Enabling or Disabling Remote RACADM You can enable or disable remote RACADM using the iDRAC7 Web interface or RACADM. You can run up to five remote RACADM sessions in parallel. Enabling or Disabling Remote RACADM Using Web Interface To enable or disable remote RACADM: 1. In iDRAC7 Web interface, go to Overview → iDRAC Settings → Network → Services. The Services page is displayed. 2. Under Remote RACADM, select Enabled. Else, select Disabled. 3. Click Apply.
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 ............. console=ttyS1,115200n8r console=tty1 3. Disable GRUB's graphical interface and use the text-based interface. Else, the GRUB screen is not displayed in RAC Virtual Console. To disable the graphical interface, comment-out the line starting with splashimage.
#System initialization. si::sysinit:/etc/rc.d/rc.sysinit 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.
tty10 tty11 ttyS1 Supported SSH Cryptography Schemes To communicate with iDRAC7 using SSH protocol, it supports multiple cryptography schemes listed in the following table. Table 11.
CAUTION: The capability to upload, view, and/ or delete SSH keys is based on the ’Configure Users’ user privilege. This privilege allows user(s) to configure another user's SSH key. You should grant this privilege carefully. Generating Public Keys for Windows To use the PuTTY Key Generator application to create the basic key: 1. Start the application and select either SSH-2 RSA or SSH-2 DSA for the type of key to generate. (SSH-1 is not supported).
The Upload SSH Key(s) page is displayed. 4. Upload the SSH keys in one of the following ways: – Upload the key file. – Copy the contents of the key file into the text box For more information, see iDRAC7 Online Help. 5. Click Apply. Uploading SSH Keys Using RACADM To upload the SSH keys, run the following command: NOTE: You cannot upload and copy a key at the same time.
The Users Main Menu page is displayed. 3. Under SSH Key Configurations, select View/Remove SSH Key(s) and click Next. The View/Remove SSH Key(s) page displays the key details. 4. Select Remove for the key(s) you want to delete, and click Apply. The selected key(s) is deleted.
Configuring User Accounts and Privileges 7 You can setup user accounts with specific privileges (role-based authority) to manage your system using iDRAC7 and maintain system security. By default iDRAC7 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 iDRAC7.
Configuring Local Users Using RACADM NOTE: You must be logged in as user root to execute RACADM commands on a remote Linux system. You can configure single or multiple iDRAC7 users using RACADM. To configure multiple iDRAC7 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.
Adding iDRAC7 User Using RACADM To add a new user to the RAC configuration, perform the following: 1. Set the user name. 2. Set the password. 3. Set the following user privileges: 4. – iDRAC7 – LAN – Serial Port – Serial Over LAN Enable the user. Example: The following example describes how to add a new user named "John" with a "123456" password and LOGIN privileges to the RAC.
NOTE: For a list of valid bit mask values for specific user privileges, see the RACADM Command Line Reference Guide for iDRAC7 and CMC available at dell.com/support/manuals. The default privilege value is 0, which indicates the user has no privileges enabled.
Prerequisites for Using Active Directory Authentication for iDRAC7 Supported Active Directory Authentication Mechanisms Prerequisites for Using Active Directory Authentication for iDRAC7 To use the Active Directory authentication feature of iDRAC7, make sure that you have: • Deployed an Active Directory infrastructure. See the Microsoft website for more information. • Integrated PKI into the Active Directory infrastructure.
To export the domain controller root CA certificate to iDRAC7: 1. Locate the domain controller that is running the Microsoft Enterprise CA service. 2. Click Start → Run. 3. Enter mmc and click OK. 4. In the Console 1 (MMC) window, click File (or Console on Windows 2000 systems) and select Add/Remove Snap-in. 5. In the Add/Remove Snap-In window, click Add. 6. In the Standalone Snap-In window, select Certificates and click Add. 7. Select Computer and click Next. 8.
• • Standard schema solution, which uses Microsoft’s default Active Directory group objects only. Extended schema solution, which has customized Active Directory objects. All the access control objects are maintained in Active Directory. It provides maximum flexibility to configure user access on different iDRAC7s with varying privilege levels.
Role Groups Default Privilege Level Permissions Granted Bit Mask Virtual Media, Test Alerts, Execute Diagnostic Commands Role Group 3 None Login to iDRAC 0x00000001 Role Group 4 None No assigned permissions 0x00000000 Role Group 5 None No assigned permissions 0x00000000 NOTE: The Bit Mask values are used only when setting Standard Schema with the RACADM.
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. 6. Click Next. The Active Directory Configuration and Management Step 3 of 4 page is displayed. 7. Select Standard Schema and click Next. The Active Directory Configuration and Management Step 4a of 4 page is displayed. 8.
racadm set iDRAC.ActiveDirectory.GlobalCatalog3 For Bit Mask values for specific Role Group permissions, see Default Role Group Privileges. Enter the FQDN of the domain controller, not the FQDN of the domain. For example, enter servername.dell.com instead of dell.com. At least one of the three addresses is required to be configured.
4. If you want to configure a list of user domains so that you only need to enter the user name when logging in to the Web interface, enter the following command: – Using config command: racadm config -g cfgUserDomain -o cfgUserDomainName -i – Using set command: racadm set iDRAC.UserDomain..
Figure 2. Typical Setup for Active Directory Objects You can create as many or as few association objects as required. However, you must create at least one Association Object, and you must have one iDRAC7 Device Object for each iDRAC7 device on the network that you want to integrate with Active Directory for Authentication and Authorization with iDRAC7. The Association Object allows for as many or as few users and/or groups as well as iDRAC7 Device Objects.
Figure 3. Privilege Accumulation for a User The figure shows two Association Objects—A01 and A02. User1 is associated to iDRAC72 through both association objects. Extended Schema Authentication accumulates privileges to allow the user the maximum set of privileges possible considering the assigned privileges of the different privilege objects associated to the same user. In this example, User1 has both Priv1 and Priv2 privileges on iDRAC72. User1 has Priv1 privileges on iDRAC71 only.
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. The LDIF files and Dell Schema Extender are located on your Dell Systems Management Tools and Documentation DVD in the following respective directories: • DVDdrive:\SYSMGMT\ManagementStation\support\OMActiveDirectory_Tools
OID 1.2.840.113556.1.8000.1280.1.7.1.1 Directory Access Protocol (LDAP) queries to Active Directory. Class Type Structural Class SuperClasses dellProduct 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.
Table 20. dellProduct Class OID 1.2.840.113556.1.8000.1280.1.1.1.5 Description The main class from which all Dell products are derived. 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 List of dellPrivilege Objects that belong to this Attribute. 1.2.840.113556.1.8000.1280.1.1.2.
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 The Current Schema Version is used to update the schema. 1.2.840.113556.1.8000.1280.1.1.2.12 Case Ignore String (LDAPTYPE_CASEIGNORESTRING 1.2.840.113556.1.4.
Creating iDRAC7 Device Object To create iDRAC7 device object: 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 iDRAC7 name that you enter while configuring Active Directory properties using iDRAC7 Web interface. 4. Select iDRAC Device Object and click OK.
Adding Objects to Association Object Using the Association Object Properties window, you can associate users or user groups, privilege objects, and iDRAC7 devices or iDRAC7 device groups. You can add groups of users and iDRAC7 devices. Related Links Adding Users or User Groups Adding Privileges Adding iDRAC7 Devices or iDRAC7 Device Groups 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.
The Active Directory Configuration and Management Step 2 of 4 page is displayed. 5. Specify the location information about Active Directory (AD) servers and user accounts. Also, specify the time iDRAC7 must wait for responses from AD during login process. NOTE: If certificate validation is enabled, specify the Domain Controller Server addresses and the FQDN. Make sure that DNS is configured correctly under Overview → iDRAC Settings → Network. 6. Click Next.
– Using config command: racadm config -g cfgActiveDirectory -o cfgADCertValidationEnable 1 – Using set command: racadm set iDRAC.ActiveDirectory.CertValidationEnable 1 In this case, you must upload a CA certificate: racadm sslcertupload -t 0x2 -f NOTE: If certificate validation is enabled, specify the Domain Controller Server addresses and the FQDN. Make sure that DNS is configured correctly under Overview → iDRAC Settings → Network.
The Active Directory summary page is displayed. 2. Click Test Settings. 3. Enter a test user's name (for example, username@domain.com) and password and click Start Test. A detailed test results and the test log displays. If there is a failure in any step, examine the details in the test log to identify the problem and a possible solution.
NOTE: If certificate validation is enabled, specify the LDAP Server’s FQDN and make sure that DNS is configured correctly under Overview → iDRAC Settings → Network . NOTE: In this release, nested group is not supported. The firmware searches for the direct member of the group to match the user DN. Also, only single domain is supported. Cross domain is not supported. 6. Click Next. The Generic LDAP Configuration and Management Step 3a of 3 page is displayed. 7. Click Role Group.
The test results and the test log are displayed. Testing LDAP Directory Service Settings Using RACADM To test the LDAP directory service settings, use the testfeature command. For more information, see the RACADM Command Line Reference Guide for iDRAC7 and CMC available at dell.com/support/manuals.
Configuring iDRAC7 for Single Sign-On or Smart Card Login 8 This section provides information to configure iDRAC7 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. iDRAC7 supports Kerberos based Active Directory authentication to support Smart Card and SSO logins. For information on Kerberos, see the Microsoft website.
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. For more information about the options, see the iDRAC7 Online Help.
Creating Active Directory Objects and Providing Privileges Perform the following steps for Active Directory Extended schema based SSO login: 1. Create the device object, privilege object, and association object in the Active Directory server. 2. Set access privileges to the created privilege object. It is recommended not to provide administrator privileges as this could bypass some security checks. 3. Associate the device object and privilege object using the association object. 4.
Configuring Active Directory With Standard Schema Using RACADM Configuring Active Directory With Extended Schema Using iDRAC7 Web Interface Configuring Active Directory With Extended Schema Using RACADM Configuring iDRAC7 SSO Login for Active Directory Users Using Web Interface To configure iDRAC7 for Active Directory SSO login: NOTE: For information about the options, see the iDRAC7 Online Help. 1. Verify whether the iDRAC7 DNS name matches the iDRAC7 Fully Qualified Domain Name.
Uploading Smart Card User Certificate Using Web Interface To upload smart card user certificate: 1. In iDRAC7 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 Smart Card Configurations, select Upload User Certificate and click Next. The User Certificate Upload page is displayed. 4.
– Upload a trusted CA-signed certificate. – Upload the keytab file. Enable smart card login. For information about the options, see the iDRAC7 Online Help. 2.
Enabling or Disabling Smart Card Login Using iDRAC Settings Utility To enable or disable the Smart Card logon feature: 1. In the iDRAC Settings utility, go to Smart Card. The iDRAC Settings Smart Card page is displayed. 2. Select Enabled to enable smart card logon. Else, select Disabled. For more information about the options, see iDRAC Settings Utility Online Help. 3. Click Back, click Finish, and then click Yes. The smart card logon feature is enabled or disabled based on the selection.
Configuring iDRAC7 to Send Alerts 9 You can set alerts and actions for certain events that occur on the managed system. An event occurs when the status of a system component is greater than the pre-defined condition. If an event matches an event filter and you have configured this filter to generate an alert (e-mail, SNMP trap, IPMI alert, remote system logs, or WS events), then an alert is sent to one or more configured destinations.
– 3. Select Disable to disable alert generation or disable an event action. Click Apply to save the setting. Enabling or Disabling Alerts Using RACADM To enable or disable generating alerts or event actions using config command: racadm config -g cfgIpmiLan -o cfgIpmiLanAlertEnable 1 To enable or disable generating alerts or event actions using set command: racadm set iDRAC.IPMILan.
– 4. Critical Click Apply. The Alert Results section displays the results based on the selected category and severity. Filtering Alerts Using RACADM To filter the alerts, use the eventfilters command. For more information, see the RACADM Command Line Reference Guide for iDRAC7 and CMC 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, and WS events to be sent to configured destinations.
Setting Alert Recurrence Event You can configure iDRAC to generate additional events at specific intervals if the system continues to operate at a temperature which is greater than the inlet temperature threshold limit. The default interval is 30 days. The valid range is 0 to 365 days. A value of ‘0’ indicates that the event recurrence is disabled. NOTE: You must have Configure iDRAC privilege to set the alert recurrence value.
Setting Event Actions Using RACADM To configure an event action, use one of the following: • eventfilters command. • cfgIpmiPefAction object with config command. For more information, see the RACADM Command Line Reference Guide for iDRAC7 and CMC available at dell.com/ support/manuals. Configuring Email Alert, SNMP Trap, or IPMI Trap Settings The management station uses Simple Network Management Protocol (SNMP) and Intelligent Platform Management Interface (IPMI) traps to receive data from iDRAC7.
6. In the SNMP Trap Format section, select the protocol version to be used to send the traps on the trap destination(s) — SNMP v1 or SNMP v2 and click Apply. NOTE: The SNMP Trap Format option applies only for SNMP Traps and not for IPMI Traps. IPMI Traps are always sent in SNMP v1 format and is not based on the configured SNMP Trap Format option. The SNMP trap format is configured. Configuring IP Alert Destinations Using RACADM To configure the trap alert settings: 1.
Configuring Email Alert Settings You can configure the email address to receive the email alerts. Also, configure the SMTP server address settings. NOTE: If your mail server is Microsoft Exchange Server 2007, make sure that iDRAC7 domain name is configured for the mail server to receive the email alerts from iDRAC7. NOTE: Email alerts support both IPv4 and IPv6 addresses. The DRAC DNS Domain Name must be specified when using IPv6.
3. To configure a custom message: – Using config command: racadm config -g cfgEmailAlert -o cfgEmailAlertCustomMsg -i [index] [custom-message] where [index] is the email destination index and [custom-message] is the custom message. – Using set command: racadm set iDRAC.EmailAlert.CustomMsg.[index] [custom-message] where [index] is the email destination index and[custom-message] is the custom message. 4.
Alerts Message IDs The following table provides the list of message IDs that are displayed for the alerts. Table 22.
Message ID Description PSU Power Supply PSUA PSU Absent PWR Power Usage RAC RAC Event RDU Redundancy RED FW Download RFL IDSDM Media RFLA IDSDM Absent RFM FlexAddress SD RRDU IDSDM Redundancy RSI Remote Service SEC Security Event SEL Sys Event Log SRD Software RAID SSD PCIe SSD STOR Storage SUP FW Update Job SWC Software Config SWU Software Change SYS System Info TMP Temperature TST Test Alert UEFI UEFI Event USR User Tracking VDR Virtual Disk VF vFlash S
Managing Logs 10 iDRAC7 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 iDRAC7 Web interface, RACADM, and WS-MAN interface. When the size of the lifecycle log reaches 800 KB, the logs are compressed and archived.
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.System Event Log displays the Total Number of Records. 2. To clear the records, select Yes. Else, select No. 3. Click Back, click Finish, and then click Yes.
Exporting Lifecycle Log Results To export the lifecycle log results, in the Lifecycle Log page, in the Log Results section, click Export. A dialog box is displayed that allows you to save the log entries in an XML format to a location of your choice. 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.
3. Click Apply. The settings are saved. All logs written to the lifecycle log are also simultaneously written to configured remote server(s). Configuring Remote System Logging Using RACADM To configure the remote syslog server settings, use one of the following: • Objects in the cfgRemoteHosts group with the config command. • Objects in the iDRAC.SysLog group with the set command. For more information, see the RACADM Command Line Reference Guide for iDRAC7 and CMC available at dell.
Monitoring and Managing Power 11 You can use iDRAC7 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.
Executing Power Control Operations iDRAC7 enables you to remotely perform a power-on, power off, reset, graceful shutdown, Non-Masking Interrupt (NMI), or power cycle using the Web interface or RACADM. You can also perform these operations using Lifecycle Controller Remote Services or WS-Management. For more information, see the Lifecycle Controller Remote Services Quick Start Guide available at dell.com/support/manuals and the Dell Power State Management profile document available at delltechcenter.com.
CMC reclaims any unused power from lower priority servers and subsequently allocates the reclaimed power to a higher priority infrastructure module or a server. If there is not enough power allocated, the blade server does not power on. If the blade has been allocated enough power, the iDRAC7 turns on the system power. Viewing and Configuring Power Cap Policy When power cap policy is enabled, it enforces user-defined power limits for the system.
– System.Power.Cap.Watts – System.Power.Cap.Btuhr – System.Power.Cap.Percent For more information, see the RACADM Command Line Reference Guide for iDRAC7 and CMC available at dell.com/ support/manuals. Configuring Power Cap Policy Using iDRAC Settings Utility To view and configure power policies: 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.
• System.Power.Hotspare.Enable • System.Power.Hotspare.PrimaryPSU • System.Power.PFC.Enable For more information, see the RACADM Command Line Reference Guide for iDRAC7 and CMC 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.
Configuring and Using Virtual Console 12 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 four 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 iDRAC7 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.
To configure IE to use ActiveX plug-in: 1. Clear the browser’s cache. 2. Add iDRAC7 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.
Clearing Earlier ActiveX Versions in IE7 To clear earlier versions of Active-X viewer for IE7, 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 Add-ons that have been used by Internet Explorer from the Show drop-down menu. 4. Delete the Video Viewer add-on.
Importing CA Certificate to ActiveX Trusted Certificate Store You must use the OpenSSL command line tool to create the certificate Hash using Secure Hash Algorithm (SHA). It is recommended to use OpenSSL tool 1.0.x and later since it uses SHA by default. The CA certificate must be in Base64 encoded PEM format. This is one-time process to import each CA certificate. To import the CA certificate to the ActiveX trusted certificate store: 1. Open the OpenSSL command prompt. 2.
Previewing Virtual Console Before launching the Virtual Console, you can preview the state of the Virtual Console on the System → Properties → System Summary page. The Virtual Console Preview section displays an image showing the state of the Virtual Console. The image is refreshed every 30 seconds. This is a licensed feature. NOTE: The Virtual Console image is available only if you have enabled Virtual Console.
The Virtual Console Viewer displays the remote system’s desktop. Using this viewer, you can control the remote system’s mouse and keyboard functions from your management station. Multiple message boxes may appear after you launch the application. To prevent unauthorized access to the application, navigate through these message boxes within three minutes. Otherwise, you are prompted to relaunch the application. If one or more Security Alert windows appear while launching the viewer, click Yes to continue.
Sometimes the Virtual Console Viewer may display low quality video. This is due to slow network connectivity that leads to loss of one or two video frames when you start the Virtual Console session. To transmit all the video frames and improve the subsequent video quality, do any of the following: • In the System Summary page, under Virtual Console Preview section, click Refresh. • In the Virtual Console Viewer, under Performance tab, set the slider to Maximum Video Quality.
The behavior of the Pass all keystrokes to server feature depends on the: • Plug-in type (Java or ActiveX) based on which Virtual Console session is launched. For the Java client, the native library must be loaded for Pass all keystrokes to server and Single Cursor mode to function. If the native libraries are not loaded, the Pass all keystrokes to server and Single Cursor options are deselected.
• All the individual keys (not a combination of different keys, but a single key stroke) are always sent to the managed system. This includes all the Function keys, Shift, Alt, Ctrl key and Menu keys. Some of these keys affect both management station and managed system.
Managing Virtual Media 13 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.
Supported Drives and Devices The following table lists the drives supported through virtual media. Table 24. Supported Drives and Devices Drive Supported Storage Media Virtual Optical Drives Virtual floppy drives USB flash drives • • • • • Legacy 1.44 floppy drive with a 1.
Configuring Virtual Media Using iDRAC Settings Utility You can attach, detach, or auto-attach virtual media using the iDRAC Settings utility. To do this: 1. In the iDRAC Settings utility, go to Virtual Media. The iDRAC Settings Virtual Media page is displayed. 2. Select Detach, Attach, or Auto attach based on the requirement. For more information about the options, see iDRAC Settings Utility Online Help. 3. Click Back, click Finish, and then click Yes. The Virtual Media settings are configured.
The Virtual Media Client View window is displayed listing the devices available for mapping NOTE: The Virtual Console Viewer window must remain active while you access the Virtual Media. . Related Links Configuring Web Browsers to Use Virtual Console Configuring Virtual Media 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.
the added folder is being used. However, the .iso file can be removed after the relevant entry is first deselected and then removed using the Remove Image to remove the entry. Removing Virtual Media Images To remove the image, in the Virtual Media Client View window, select the required mapped image and click Remove Image. The selected image is removed from the list of devices in the Client View window.
Displaying Correct Virtual Drives For Mapping On a Linux-based management station, the Virtual Media Client window may display removable disks and floppy disks that are not part of the management station. To make sure that the correct virtual drives are available to map, you must enable the port setting for the connected SATA hard drive. To do this: 1. Reboot the operating system on the management station. During POST, press or to enter System Setup. 2. Go to SATA settings.
• 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 iDRAC7 Web interface, go to Overview → Server → Attached Media. 2. Under Virtual Media, select the Enable Boot Once and click Apply. 3.
Installing and Using VMCLI Utility 14 The Virtual Media Command Line Interface (VMCLI) utility is an interface that provides virtual media features from the management station to iDRAC7 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.
The parameter enables VMCLI to connect to the specified server, access iDRAC7, and map to the specified virtual media. NOTE: VMCLI syntax is case-sensitive. To ensure security, it is recommended to use the following VMCLI parameters: • vmcli -i — Enables an interactive method of starting VMCLI. It ensures that the user name and password are not visible when processes are examined by other users.
VMCLI Operating System Shell Options VMCLI uses shell options to enable the following operating system features: • stderr/stdout redirection — Redirects any printed utility output to a file. For example, using the greater-than character (>) followed by a filename overwrites the specified file with the printed output of the VMCLI utility. NOTE: The VMCLI utility does not read from standard input (stdin). Hence, stdin redirection is not required.
Managing vFlash SD Card 15 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 iDRAC7 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: 1. Open a telnet, SSH, or Serial console to the system and log in. 2.
Enabling or Disabling vFlash Functionality Using iDRAC Settings Utility To enable or disable the vFlash functionality: 1. In the iDRAC Settings utility, go to vFlash Media. The iDRAC Settings vFlash Media page is displayed. 2. Select Enabled to enable vFlash functionality or select Disabled to disable the vFlash functionality. 3. Click Back, click Finish, and then click Yes. The vFlash functionality is enabled or disabled based on the selection.
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 iDRAC7 is reset, the status of the last partition operation is lost. Managing vFlash Partitions You can perform the following using the iDRAC7 Web interface or RACADM: NOTE: An administrator can perform all operations on the vFlash partitions.
– The card is write-protected. – The label name matches the label of an existing partition. – A non-integer value is entered for the partition size, the value exceeds the available space on the card, or the partition size is greater than 4 GB. – An initialize operation is being performed on the card. Creating an Empty Partition Using RACADM To create a 20 MB empty partition: 1. Open a telnet, SSH, or Serial console to the system and log in. 2.
Creating a Partition From an Image File Using RACADM To create a partition from an image file using RACADM: 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 –e HDD –t image – l //myserver/sharedfolder/foo.iso –u root –p mypassword A new partition is created. By default, the created partition is read-only. This command is case sensitive for the image file name extension.
Viewing Available Partitions Using RACADM To view the available partitions and their properties using RACADM: 1. Open a Telnet, SSH, or Serial console to the system and log in. 2.
racadm config –g cfgvflashpartition –i 1 –o cfgvflashPartitionAccessType 0 Attaching or Detaching Partitions When you attach one or more partitions, they are visible to the operating system and BIOS as USB mass storage devices. When you attach multiple partitions, based on the assigned index, they are listed in an ascending order in the operating system and the BIOS boot order menu. If you detach a partition, it is not visible in the operating system and the BIOS boot order menu.
• The vFlash partition label is different from the volume name of the file system on the emulated USB device. You can change the volume name of the emulated USB device from the operating system. However, it does not change the partition label name stored in iDRAC7. Deleting Existing Partitions Before deleting existing partition(s), make sure that: • The vFlash functionality is enabled. • The card is not write-protected. • The partition is not attached.
The Download Partition page is displayed. 2. From the Label drop-down menu, select a partition that you want to download and click Download. NOTE: All existing partitions (except attached partitions) are displayed in the list. The first partition is selected by default. 3. Specify the location to save the file. The contents of the selected partition are downloaded to the specified location.
Using SMCLP 16 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.
• yx2x blade, rack, and tower servers use admin->. where, y is a alpha-numeric character such as M (for blade servers), R (for rack servers), and T (for tower servers) and x is a number. This indicates the generation of Dell PowerEdge servers. NOTE: Scripts using -$ can use these for yx1x systems, but starting with yx2x systems one script with admin-> can be used for blade, rack, and tower servers.
Target Definitions admin1/system1/logs1/log1 System Event Log (SEL) record entry admin1/system1/logs1/log1/record* An individual SEL record instance on the managed system admin1/system1/settings1 Managed system SMASH collection settings admin1/system1/capacities1 Managed system capacities SMASH collection admin1/system1/consoles1 Managed system consoles SMASH collection admin1/system1/sp1 Service Processor admin1/system1/sp1/timesvc1 Service Processor time service admin1/system1/sp1/capabili
Target Definitions admin1/sysetm1/sp1/account1-16/ identity2 IPMI identity (LAN) account admin1/sysetm1/sp1/account1-16/ identity3 IPMI identity (Serial) account admin1/sysetm1/sp1/account1-16/ identity4 CLP identity account admin1/system1/sp1/acctsvc1 Local user account management service admin1/system1/sp1/acctsvc2 IPMI account management service admin1/system1/sp1/acctsvc3 CLP account management service admin1/system1/sp1/rolesvc1 Local Role Base Authorization (RBA) service admin1/system1
Using Show Verb To learn more about a target use the show verb. This verb displays the target’s properties, sub-targets, associations, and a list of the SM-CLP verbs that are allowed at that location. Using the -display Option The show –display option allows you to limit the output of the command to one or more of properties, targets, associations, and verbs.
system1 has been stopped successfully • To switch on the server: start /system1 The following message is displayed: system1 has been started successfully • To reboot the server: reset /system1 The following message is displayed: system1 has been reset successfully SEL Management The following examples show how to use the SMCLP to perform SEL-related operations on the managed system.
/system1/logs1/log1/record4 Properties: LogCreationClassName= CIM_RecordLog CreationClassName= CIM_LogRecord LogName= IPMI SEL RecordID= 1 MessageTimeStamp= 20050620100512.
Deploying Operating Systems 17 You can use any of the following utilities to deploy operating systems to managed systems: • Virtual Media Command Line Interface (CLI) • Virtual Media Console • Remote File Share Related Links Deploying Operating System Using VMCLI Deploying Operating System Using Remote File Share Deploying Operating System Using Virtual Media Deploying Operating System Using VMCLI Before you deploy the operating system using the vmdeploy script, make sure that: • VMCLI utility is
vmdeploy.bat -r -u -p [ -f { | < device-name>} | -c { |} ] [-i ] NOTE: vmdeploy does not support IPv6, since IPv6 does not support the IPMI tool. NOTE: The vmdeploy script processes the -r option slightly differently than the vmcli -r option.
To deploy an operating system using RFS: 1. Using Remote File Share (RFS), mount the ISO or IMG image file to the managed system through NFS or CIFS. 2. Go to Overview → Setup → First Boot Device . 3. Set the boot order in the First Boot Device drop-down list to Remote File Share. 4. 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.
3. Click Apply and then click Connect. After the connection is established, the Connection Status displays Connected. NOTE: Even if you have configured remote file sharing, the Web interface does not display user credential information due to security reasons. For Linux distributions, this feature may require a manual mount command when operating at runlevel init 3.
To deploy an operating system using Virtual Media: 1. Do one of the following: – Insert the operating system installation CD or DVD into the management station CD or DVD drive. 2. – Attach the operating system image. 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: 4. – Set the boot order through System Setup → System BIOS Settings by pressing during boot.
7. Click Yes to save the settings and press to exit System Setup. 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.
18 Troubleshooting Managed System Using iDRAC7 You can diagnose and troubleshoot a remote managed system using: • Diagnostic console • Post code • Boot and crash capture videos • Last system crash screen • System event logs • Lifecycle logs • Front panel status • Trouble indicators • System health Related Links Using Diagnostic Console Viewing Post Codes Viewing Boot and Crash Capture Videos Viewing Logs Viewing Last System Crash Screen Viewing Front Panel Status Hardware Trouble Indicato
Viewing Boot and Crash Capture Videos You can view the video recordings of: • Last three boot cycles — A boot cycle video logs the sequence of events for a boot cycle. The boot cycle videos are arranged in the order of latest to oldest. • Last crash video — A crash video logs the sequence of events leading to the failure. This is a licensed feature. iDRAC7 records fifty frames during boot time. Playback of the boot screens occur at a rate of 1 frame per second.
• 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. Viewing System Front Panel LCD Status To view the LCD front panel status for applicable rack and tower servers, in iDRAC7 Web interface, go to Overview → Hardware → Front Panel . The Front Panel page displays. The Live Front Panel Feed section displays the live feed of the messages currently being displayed on the LCD front panel.
• 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. CAUTION: You should only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by online or telephone service and support team. Damage due to servicing that is not authorized by Dell is not covered by your warranty.
• Soft restart — Using iDRAC7 Web interface or RACADM. Resetting iDRAC7 Using iDRAC7 Web Interface To restart iDRAC7, do one of the following in the iDRAC7 Web interface: • Go to Overview → Server → Summary. Under Quick Launch Tasks, click Reset iDRAC. • Go to Overview → Server → Troubleshooting → Diagnostics. Click Reset iDRAC. Resetting iDRAC7 Using RACADM To restart iDRAC7, use the racreset command. For more information, see the RACADM Reference Guide for iDRAC7 and CMC available at dell.
Frequently Asked Questions 19 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 • RACADM • Miscellaneous System Event Log While using iDRAC7 Web interface through Internet Explorer, why does SEL not save using the Save As option? This is due to a browser setting. To resolve this: 1.
When accessing the iDRAC7 Web-based interface, a security warning is displayed stating that the SSL certificate host name does not match the iDRAC7 host name. iDRAC7 includes a default iDRAC7 server certificate to ensure network security while accessing through the Web-based interface and remote RACADM. When this certificate is used, the Web browser displays a security warning because the default certificate that is issued to iDRAC7 does not match the iDRAC7 host name (for example, the IP address).
• • iDRAC7 date is not within the validity period of the server certificate or CA certificate. Check the iDRAC7 time and the validity period of your certificate. The domain controller addresses configured in iDRAC7 does not match the Subject or Subject Alternative Name of the directory server certificate. If you are using an IP address, read the next question. If you are using FQDN, make sure you are using the FQDN of the domain controller and not the domain. For example, servername.example.
The Active Directory is configured for a domain present in Windows Server 2008 Active Directory. A child or sub domain is present for the domain, the user and group is present in the same child domain, and the user is a member of that group. When trying to log in to iDRAC7 using the user present in the child domain, Active Directory Single Sign-On login fails. This may be because of the an incorrect group type.
9. Name the new key as SuppressExtendedProtection. 10. Right-click SuppressExtendedProtection and click Modify. 11. In the Value data field, type 1 and click OK. 12. Close the Registry Editor window. You can now log in to iDRAC7 using SSO. If you have enabled SSO for iDRAC7 and you are using Internet Explorer to log in to iDRAC7, SSO fails and you are prompted to enter your user name and password.
Any user with iDRAC7 configuration privileges can turn on or turn off the local console. How to get the current status of the local server video? The status is displayed on the Virtual Console page. Use the RACADM command racadm getconfig –g cfgRacTuning to display the status in the object cfgRacTuneLocalServerVideo. Or, use the following RACADM command from a Telnet, SSH, or a remote session: racadm -r (iDRAC IP) -u -p getconfig -g cfgRacTuning The status is also seen on the Virtual Console OSCAR display.
It is recommended to have a 5 MBPS connection for good performance. A 1 MBPS connection is required for minimal performance. What are the minimum system requirements for the management station to run Virtual Console? The management station requires an Intel Pentium III 500 MHz processor with at least 256 MB of RAM. Why doe Virtual Console Viewer window sometimes displays No Signal message? You may see this message because the iDRAC7 Virtual Console plug-in is not receiving the remote server desktop video.
The Linux SysRq key behavior is different when using Virtual Console from Internet Explorer. To send the SysRq key, press the Print Screen key and release while holding the Ctrl and Alt keys. To send the SysRq key to a remote Linux server though iDRAC7, while using Internet Explorer: 1. Activate the magic key function on the remote Linux server. You can use the following command to activate it on the Linux terminal: echo 1 > /proc/sys/kernel/sysrq 2.
• A USB key image How to make the USB key a bootable device? Search support.dell.com for the Dell Boot Utility You can also boot with a Windows 98 startup disk and copy system files from the startup disk to the USB key. For example, from the DOS prompt, type the following command: sys a: x: /s where, x: is the USB key that is required to be set as a bootable device. The Virtual Media is attached and connected to the remote floppy.
Virtual media devices and vFlash devices are connected as a composite USB device to the Host USB BUS, and they share a common USB port. Whenever any virtual media or vFlash USB device is connected to or disconnected from the host USB bus, all the Virtual Media and vFlash devices are disconnected momentarily from the host USB bus, and then they are re-connected. If the host operating system uses a virtual media device, do not attach or detach one or more virtual media or vFlash devices.
Storage Devices Information for all the storage devices connected to the system are not displayed and OpenManage Storage Management displays more storage devices that iDRAC7. Why? iDRAC7 displays information for only the Comprehensive Embedded Management (CEM) supported devices. RACADM After performing an iDRAC7 reset (using the racadm racreset command), if any command is issued, the following message is displayed.
This occurs because the create partition operation is in-progress. However, the partition is deleted after sometime and a message that the partition is deleted is displayed. If not, wait until the create partition operation is completed and then delete the partition. Miscellaneous How to find an iDRAC IP address for a blade server? You can find the iDRAC IP address using any of the following methods: Using CMC Web interface: Go to Chassis → Servers → Setup → Deploy.
iDRAC7 network connection is not working. For blade servers: • Make sure that the LAN cable is connected to CMC. • Make sure that NIC settings, IPv4 or IPv6 settings, and either Static or DHCP is enabled for your network. For rack and tower servers: • In shared mode, make sure the LAN cable is connected to the NIC port where the wrench symbol is present. • In Dedicated mode, make sure the LAN cable is connected to the iDRAC LAN port.
Use Case Scenarios 20 This section helps you in navigating to specific sections in the guide to perform typical use case scenarios. Troubleshooting An Inaccessible Managed System After receiving alerts from OpenManage Essentials, Dell Management Console, or a local trap collector, five servers in a data center are not accessible with issues such as hanging operating system or server. Need to identify the cause to troubleshoot and bring up the server using iDRAC7.
Setting Up Alerts and Configuring Email Alerts To set up alerts and configure email alerts: 1. Enable alerts. 2. Configure the email alert and check the ports. 3. Perform a reboot, power off, or power cycle the managed system. 4. Send test alert. Viewing and Exporting Lifecycle Log and System Event Log To view and export lifecycle log and system event log (SEL): 1. In iDRAC7 Web interface, go to Overview → Server → Logs to view SEL and Overview → Server → Logs → Lifecycle Log to view lifecycle log.
• Configuring Local Users • Configuring Active Directory Users • Configuring Generic LDAP Users Launching Server's Remote Console and Mounting a USB Drive To launch the remote console and mount a USB drive: 1. Connect a USB flash drive (with the required image) to the management station. 2. Use one the following methods to launch virtual console through the iDRAC7 Web Interface: – Go to Overview → Server → Console and click Launch Virtual Console.
