###################################################################### Integrated DELL(TM) REMOTE ACCESS CONTROLLER (iDRAC) Version 1.20 ###################################################################### This document contains updated information about the Integrated Dell Remote Access Controller (iDRAC). For more information about iDRAC, including installation and configuration information, see the "Integrated Dell Remote Access Controller User's Guide" and the "Dell OpenManage(TM) Server Administrator User's Guide." These documents are located on the Dell SUpport site at "support.dell.com". ###################################################################### TABLE OF CONTENTS ###################################################################### This file contains the following sections: * Criticality * Minimum Requirements * Release Highlights * Known Issues for iDRAC v1.20 * Known Issues for Documentation ###################################################################### CRITICALITY ###################################################################### 1 - Urgent ###################################################################### MINIMUM REQUIREMENTS ###################################################################### The following subsections list operating systems that are compatible with the iDRAC. ====================================================================== SUPPORTED SYSTEMS ====================================================================== iDRAC is supported on the following Dell PowerEdge(TM) systems in the Dell PowerEdge M1000e system enclosure: * Dell PowerEdge M600 * Dell PowerEdge M605 * Dell PowerEdge M805 * Dell PowerEdge M905 ====================================================================== SUPPORTED MANAGED SERVER OPERATING SYSTEMS ====================================================================== The iDRAC is supported by the following operating systems: * Microsoft(R) Windows Server(R) 2003 family The Windows Server 2003 family includes - Windows Server 2003 R2 (Enterprise and Standard Editions) with SP2 (32-bit). - Windows Server 2003 (Web Edition) with SP2 (32-bit). - Windows Server 2003 R2 Standard and Enterprise Edition with SP2 (32-bit, x86_64). - Windows Server 2003 Standard and Enterprise Editions x64 Editions with SP2. - Windows Storage Server 2003 R2 Express and Workgroup x64 Editions (x86_64). * Microsoft Windows Server 2008 Web, Standard, and Enterprise Editions (32-bit x86) * Microsoft Windows Server 2008 Web, Standard, Enterprise and Datacenter (x86_64) Editions NOTE: When installing Windows Server 2003 with SP1, be aware of changes to DCOM security settings. For more information, see article 903220 from the Microsoft Support website at support.microsoft.com/kb/903220. * Red Hat(R) Enterprise Linux WS, ES, and AS (version 4) (x86 and x86_64). * Red Hat(R) Enterprise Linux 5 (x86 and x86_64). * SUSE(R) Linux Enterprise Server 9 with Update 3 (x86_64). * SUSE Linux Enterprise Server 10 (x86_64) Gold. ====================================================================== SUPPORTED WEB BROWSERS ====================================================================== * Microsoft Internet Explorer 6.0 (32-bit) with SP2 for Windows XP and Windows 2003 R2 SP2 only. NOTE: There are known issues with IE6 on the 64-bit version of Windows XP Professional. Upgrade to Internet Explorer 7 for best results. * Microsoft Internet Explorer 7.0 (32- or 64-bit) for Windows 2008 (Longhorn), Vista, Windows XP, and Windows 2003 R2 SP2 only. * Mozilla Firefox 1.5 (32-bit) on SUSE Linux (version 10) only. * Mozilla Firefox 2.0 (32- and 64-bit) on RHEL4, 5 and Windows XP, Windows 2003 R2 SP2, Windows 2008, and Windows Vista. ============================================= FIRMWARE VERSIONS ============================================= * iDRAC Firmware Version: 1.20 ###################################################################### RELEASE HIGHLIGHTS (FIRMWARE VERSION 1.20) ###################################################################### iDRAC ver. 1.20 has critical security enhancements, new operating system and browser support, and new features like Boot Capture Replay and improved health status visibility. Fixes and Enhancements in 1.20 ---------------------------------------------- * Windows Server 2008 (Longhorn),ESX (latest version), W2K3-R2 & RHEL5 operating system support as managed server OSes * Added support for 64-bit Firefox and IE browsers * Generate a default Self Signed SSL certificate. * An option to disable access to iDRAC configuration by any user or local RACADM. * SSL 2.0 is no longer supported due to security risks in SSL 2.0.iDRAC will negotiate to use SSL 3.0 if both (SSL 2.0 and SSL 3.0 )are present * Expanded Health Error Reporting Tree * Java Runtime Engine and Java Development Support updated to Version 6 Update 7 (JRE1.6u7) * Two Concurrent KVM Sessions are now supported (from different clients) to the same iDRAC * iDRAC Console Viewer now supports Mouse Scrolling * iDRAC Web Interface will list the MAC/WWN present on the server and support the persistent MAC functionality of FlexAddress * iDRAC Web Interface will list Storage Daughter card and I/O Mezzanine Card population. * Boot Capture console replay for last three boot sequences. * Improved Power Usage Reporting * Improved support for non-US-ASCII keyboards ###################################################################### KNOWN ISSUES FOR iDRAC ###################################################################### This section provides additional information about known issues with the iDRAC Firmware version 1.20. * Microsoft(R) Internet Explorer Security Settings Recent updates to IE 6 and IE 7 have more stringent security settings, and simply setting the overall security level to 'medium' is no longer sufficient. Please read the iDRAC User's Guide v1.20 to determine the settings that need to be enabled for the iDRAC Web Interface to function correctly. * Clear Browser Caches After Firmware Update It is important to flush the browser caches after performing a firmware update operation. Please read the User's Guide for instruction on how to accomplish this. * Issues with flash When flashing to an earlier version of iDRAC firmware, it is imperative that only DUP or other firmware packages specfic to the affected server are used. Do not attempt to downgrade M805 and M905 to any version {unsupported} earlier than 1.20. Doing so will curropt the firmware which can only be recovered via Chassis Management controller * Link Tuning Errors after Server Power Cycle During a server module power cycle, iDRAC may log a link tuning error that will cause an amber LED and a red “X” on the iDRAC health page. To determine if a link tuning error has occurred, review the iDRAC’s SEL log for the following entry: LinkT/FlexAddr: Link tuning sensor failed to get link tuning or flex address data from BMC/iDRAC To correct this issue, perform a server module power cycle. * Using virtual devices on VMware ESX Console, after an iDRAC Update Please reboot the managed server running VMware ESX 3.x one time after an iDRAC update is completed. This will ensure that VMware ESX re-enumerates the virtual devices and enables virtual floppy and virtual CDROM features of the iDRAC. After that reboot, virtual devices including Virtual Floppy work fine. * Disabling Local Configuration Access In order for the disabling of local configuration access to work at the iDRAC COnfiguration Utility level (Ctrl-E at bootup), the BIOS in your system needs to be at least at the following level: PowerEdge M600 - BIOS version 2.1.2 PowerEdge M605 - BIOS version 4.0.0 PowerEdge M805/M905 - BIOS version 0.2.3 * Possible Active Sessions vs. Current Active Sessions in OMSA In Dell Open Manage Server Administrator, the number of "Current Active Sessions" displayed for iDRAC refers only to the number of current IPMI transaction sessions active, and does not include web GUI or ssh/SM-CLP sessions. * Using special keys in "keyboard passthrough" mode Special keys such as the Windows key, CTRL-Prnt Scrn, and ALT-Function key combinations in keyboard passthrough mode will be problematic, as some combinations are sent to the Viewer itself and might produce undesireable behavior. Special provision is made in the Java and ActiveX viewers for macros under the Keyboard menu pulldown which allow the user to send such combinations and special keys directly to the managed server. * Configuring iDRAC to use Static IP using 'syscfg' utility Given below is the method to use the syscfg utility to set the iDRAC to use a static IP address. It has to be done in 2 steps. Step 1: "syscfg lcp --ipaddrsrc=static" Wait at least 5 seconds. After this time, the change to static IP will be in effect and the next syscfg command will succeed. Step 2: "syscfg lcp --gateway=(gateway IP) --ipaddress=(valid IP address) --subnetmask=255.255.255.0" * Manual OS Installation REQUIREMENT when using 'virtual floppy' Using vMedia to do a Windows / Other installation, there is one thing REQUIRED to enable completing the installation. When there is a need to install drivers using a floppy disk - ENSURE the 'Virtual Floppy' device is the FIRST device in the 'Boot Sequence'. Use BIOS Setup screens to ensure this. This way, the drivers in the floppy can be used to install the storage etc drivers and complete the Windows / Other installation. * Configuring the 'Host Name String' using the iDRAC Configuration Utility With OMSA installed - OMSA takes precendence. OMSA sets the 'Host Name String' every time it starts up. Given above, even if 'Host Name String' is set using the iDRAC Configuration Utility', it will be overwritten by OMSA when it starts up. With OMSA NOT installed - The iDRAC Configuration Utility can be used to configure the 'Host Name String'. * Accessing remote floppy disks and CD-ROMs from (VMWare) VMs Accessing remote floppy disks and CD-ROMs from (VMWare) VMs is NOT supported. Only devices directly connected to an ESX server or a floppy or CD-ROM ISO image present in the ESX Service Console can be made accessible to the VM. Avoid this issue by creating an image of the floppy or CD-ROM and copying it to the Service Console. * Updating iDRAC using DOS update utility, from a PXE network setup The iDRAC can be updated using the DOS utility when DOS is booted using PXE. However, the new FW image has to be on a local media on the server for this to work properly. Local media can be a RAMDISK, HD or USB key on the server. Alternatively, the update of iDRACs on multiple servers has to be sequenced, i.e. done one server after the other, with the 1st completing update and the 2nd starting update and so on to 3rd after 2nd is done, 4th after 3rd is done etc. * Usage of virtual CD-ROM in SLES 9 Use the auto-attach checkbox in the vMedia area of the Web GUI of the iDRAC when using CD-ROM devices in SLES9. Another way to do the same when using SM-CLP is to set the /system1/sp1/oemdell_vmservice1 enabledstate to VMEDIA_AUTO_ATTACH. * Setting of iDRAC time, after an iDRAC FW update New behavior in iDRAC 1.20 is that the CMC automatically sets the iDRAC time after a firmware update. * RACADM restore default configuration behavior The racresetcfg command in RACADM restores all properties except cfgDNSRacName in the cfgLanNetworking group to their default values. * Configuring iDRAC using RACADM config The actual time the user needs to wait after executing the racresetcfg command within racadm may vary depending on the network speed. * iDRAC Media Redirection using floppy disks on Vista management station with IE7 and ActiveX The iDRAC's IP address needs to be added to the 'Trusted Sites' list, before launching the Console Redirection session on a management station running Vista with IE7. 1 Click Tools-> Internet Options-> Security-> Trusted sites. 2 Click Sites and enter the IP address or DNS name of the iDRAC. 3 Click Add. * Configuring specific DNS parameters using 'racadm config -f ' DHCP has to be enabled on the iDRAC for the following two DNS parameters to be configurable, using 'racadm config -f ' - 1) cfgDNSServersFromDHCP, 2) cfgDNSDomainNameFromDHCP. * Behavior of the iDRAC Virtual Media functionality, when the media is removed On Windows - Once the media is removed, the Explorer window(s) for this media do not close by themselves. User action IS required. Please close the Explorer window(s), once the media is removed. On Linux - Once the media is removed, the file browser window(s) for this media do close by themselves. User action is NOT required. * Using the iVMCLI tool from within a system running Windows Vista To use iVMCLI from within a system running Windows Vista - The user has to start up the 'cmd' with 'Run as Administrator'. (iVMCLI requires the user has 'administrator' privileges when it is used.) Aside - User can log in as a non-admin user, but when using iVMCLI, the user has to start 'cmd' with 'Run as Administrator' thereby giving them admin privileges to enable using iVMCLI. ###################################################################### KNOWN ISSUES FOR DOCUMENTATION ###################################################################### This section provides additional information about known issues with the iDRAC Firmware version 1.20 User's Guide. * Firefox 2+ window and tab behavior The User's Guide for iDRAC v1.20 incorrectly states that Firefox 2 behavior is the same as that of the Internet Explorer. Firefox 2 tabs and windows are not new sessions. The last user that logs into the device will have the same privileges for all windows and tabs. Internet Explorer 7 tabs will work the same. If any of these windows or tabs are closed or the user is logged out, then all sessions will expire. This is different than each new Internet Explorer 7 window; they will work like new sessions for the same device and are not affected if a user is logged out. ###################################################################### Information in this document is subject to change without notice. (C) 2008 Dell Inc. All rights reserved. Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden. Trademarks used in this text: "Dell", "Dell OpenManage", and "PowerEdge" are trademarks of Dell Inc.; "Microsoft", "Windows", "Windows Server" and "Active Directory" are trademarks or registered trademarks of Microsoft Corporation; "Intel" is a trademark of Intel Corporation; "SUSE" is a registered trademark of Novell, Inc.; "Red Hat" is a registered trademark of Red Hat, Inc. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own. August 2008