###################################################################### Integrated DELL(TM) REMOTE ACCESS CONTROLLER 6 (iDRAC6) Version 1.20 ###################################################################### Version 1.20 Release Date: August 2009 This readme contains updated information about the Integrated Dell Remote Access Controller 6 (iDRAC6). For more information about iDRAC6, including installation and configuration information, see the "Integrated Dell Remote Access Controller 6 (iDRAC6) Version 1.2 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\manuals". ###################################################################### TABLE OF CONTENTS ###################################################################### This file contains the following sections: * Criticality * Minimum Requirements * Release Highlights * Known Issues for iDRAC6 v1.20 * Known Issues for Documentation ###################################################################### CRITICALITY ###################################################################### 1 - Critical ###################################################################### MINIMUM REQUIREMENTS ###################################################################### The following subsections list operating systems that are compatible with the iDRAC6. ====================================================================== SUPPORTED SYSTEMS ====================================================================== iDRAC6 is supported on the following Dell PowerEdge(TM) and PowerVault(TM) systems: *PowerEdge T710 *PowerEdge R710 *PowerEdge T610 *PowerEdge R610 *PowerEdge T410 *PowerEdge R410 ====================================================================== SUPPORTED MANAGED SERVER OPERATING SYSTEMS ====================================================================== The iDRAC6 is supported by the following operating systems: * Microsoft(R) Windows Server(R) 2003 family The Windows Server 2003 family includes - Windows Server 2003 R2 (Web, Standard and Enterprise Editions) with SP2 (x86). - Windows Server 2003 R2 (Standard, Enterprise and DataCenter Editions) with SP2 (x64). - Windows Server 2003 (SBS, Standard, and Premium Editions) with SP2. * Microsoft Windows Server 2008 with core (Web, Standard, and Enterprise Editions) (x86) * Microsoft Windows Server 2008 with core (Standard, Enterprise, and DataCenter Editions) (x64) * Microsoft Windows Server 2008 SBS, EBS, Standard, and Premium Editions * SUSE(R) Linux Enterprise Server (SLES) 10 SP2 * SUSE(R) Linux Enterprise Server (SLES) 11 SP2 * Red Hat(R) Enterprise Linux (RHEL) 4.7 (x86_32, x86_64) * RHEL 5 Update 3 (x86_32, x86_64) * VMware(R) ESX 3.5 Update 4 * VMware ESXi 3.5 Update 4 Flash * VMware(R) ESX 4.0 * VMware ESXi 4.0 Update 4 Flash ====================================================================== SUPPORTED WEB BROWSERS ====================================================================== * Microsoft Internet Explorer 6.0 with SP2 for Microsoft Windows(R) XP, Windows 2000 Sever, Windows 2000 Pro, Windows 2003 Server Gold, Windows 2003 Server SP1, and Windows 2003 Server SP2 * Microsoft Internet Explorer 7.0 for Windows 2003 Server Gold, Windows 2003 Server SP1, Windows 2003 Server SP2, Windows Server 2008, and Windows Vista(R) * Mozilla Firefox 2.0 on SLES 10 SP1 * Mozilla Firefox 3.0 on Windows 2003 Server Gold, Windows 2003 Server SP1, Windows 2003 Server SP2, Windows 2000 Pro, Windows XP, Windows Server 2008, Windows Vista, RHEL 4, RHEL 5, SLES 9, SLES 10, SLES 11, and SLES 10 SP1 ============================================= FIRMWARE VERSIONS ============================================= * iDRAC6 Firmware Version: 1.20 ###################################################################### RELEASE HIGHLIGHTS (FIRMWARE VERSION 1.20) ###################################################################### * Defect Fixes • Linux DUP is fails to update iDRAC6 firmware on ESX 4.0 • iDRAC6 not sending hostname to DHCP database • iDRAC6 serial mux switching fails to switch modes after iDRAC6 reset ###################################################################### RELEASE HIGHLIGHTS (FIRMWARE VERSION 1.20) ###################################################################### iDRAC6 Management Features for the release include: * Support for Lifecycle Controller 1.2, consisting of Operating System Deployment(OSD) and Auto-Discovery & Handshake (AD&H). Auto-Discovery and Handshake The Auto-Discovery and Handshake feature enables automated discovery of unprovisioned systems on the network; further, it securely establishes initial credentials so that these discovered systems can be managed. This feature enables the iDRAC6 to locate the provisioning server. The iDRAC6 and provisioning service server mutually authenticate each other. The provisioning server then provisions the iDRAC6 with initial login credentials using secure handshake methodology. The iDRAC6 is now "known" and can be managed through its newly installed credentials to perform operations such as remote operating system deployment. Remote Operating System Deployment The remote operating system deployment feature enables the provision web services to generate the list of supported operating systems on the new system, request drivers for a specific operating system to be installed either locally on a server or on a share for the console to copy and finally transfer a pre-operating system ISO image on the server and boot to it. ###################################################################### KNOWN ISSUES FOR iDRAC6 v1.20 ###################################################################### This section provides additional information about known issues with the iDRAC6 firmware version 1.20. * Configuring iDRAC6 to use Static IP using "syscfg" utility Given below is the method to use the syscfg utility to set the iDRAC6 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 operating system installation requirement when using "virtual floppy" When using Virtual Media to install an operating system, the following is required to allow the Installation to complete successfully: When installing drivers using a floppy disk, ensure that the Virtual floppy device is set as the first device in the Boot sequence in the System BIOS (F2). This will allow the operating system to see the required mass storage device drivers on the floppy to complete the installation. This way, the drivers in the floppy can be used to install the storage drivers and complete the Windows and other installation. * Configuring the "Host Name String" using the iDRAC6 Configuration Utility with Server Administrator (OMSA) installed - OMSA takes precedence. OMSA sets the "Host Name String" every time it starts up. Given above, even if "Host Name String" is set using the iDRAC6 Configuration Utility, it will be overwritten by OMSA when it starts up. With OMSA not installed - The iDRAC6 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. * Using the VMCLI tool from within a system running Windows Vista To use VMCLI from within a system running Windows Vista - The user has to start up the 'cmd' with 'Run as Administrator'. (VMCLI requires that the user has 'administrator' privileges when it is used.) Note: User can log in as a non-admin user, but when using VMCLI, the user has to start 'cmd' with 'Run as Administrator' privilege thereby giving them admin privileges to enable using VMCLI. * Uploading images from multiple management systems to the virtual flash at the same time has to be avoided in order to prevent image corruption. * The name of the firmware image file for iDRAC6 is firmimg.d6 * If the network cable to iDRAC6 is disconnected and then connected again, iDRAC6 will not negotiate a new IP address until the current lease expires. * Remote Racadm and VMCLI utilities are not supported with IPv6 in this release. * If iDRAC6 firmware update is interrupted for any reason, a wait of up to 30 minutes may be required before another firmware update operation is again allowed. * The Diagnostic tab on the GUI page is not operational if iDRAC6 Enterprise card is not installed. * Enabling Virtual Flash from iDRAC6 Configuration Utility will not take effect if the SD card is not formatted. Format the SD card from iDRAC6 GUI or using "racadm vmkey reset" command before enabling it. * In SM-CLP start or stop on the target /system1/ sp1/adsvc1 displays an error “*-* yyerror: syntax error, unexpected ZTOK_PARAMVALUE, expecting XTOK_VALUE or XTOK_VALUEARRAY or XTOK_VALUEREFERENCE” and hangs the telnet/ssh session. It recovers only when the session times out or is restarted. This target is not supported with iDRAC6 firmware version 1.20. * You must close an open POST boot capture log video before you play another one. You cannot play two logs simultaneously. * The status for System Board Riser1 Pres and System Board Riser2 Pres sensors is reported incorrectly as unknown instead of good on R710 and R610 servers. * VMDeploy script, and vmdeploy.sh, does not work correctly on all supported Linux versions. To fix the issue, modify the following lines in vmdeply.sh using a Linux editor like vi: - Line 198: Replace if [ "`grep \"RAW RSP (0 bytes)\" ipmitool_log`" != "RAW RSP (0 bytes)" ] with grep "RAW RSP (0 bytes)" ipmitool_log if [ "$?" != 0 ] - Line 230: Replace if [ "`grep \"not supported\" ipmitool_log`" != "not supported" ] with grep "not supported" ipmitool_log if [ "$?" != 0 ] *On SLES 64 bit operating systems, if you try to attach an ISO file through Virtual Media Command Line Interface (VMCLI), an error message is displayed "Unable to connect to the server". 1. Get the installed libssl.so version by executing the following command: #ldd /usr/bin/openssl Output: ... libssl.so.0.9.8 => /usr/lib/libssl.so.0.9.8 ... 2. Create new symbolic link by executing the following command: #ln -s /usr/lib/libssl.so.0.9.8 /usr/lib/libssl.so.0.9.7 NOTE: Specify the path /usr/lib/libssl.so.0.9.8 in the command as displayed in step 1. 3. Execute the VMCLI command. 4. Once you complete the execution, remove the symbolic link by executing the following command: #rm /usr/lib/libssl.so.0.9.7 * Two Factor Authentication(TFA) and Single Sign On(SSO) features are not supported on Firefox browser. * The Smart Card based Two Factor Authentication (TFA) and the Single Sign-On (SSO) features are not supported if the Active Directory is configured for Extended Schema. * Operating system information may not be displayed in the iDRAC6 GUI “System Summary” page if Dell OpenManage Server Administrator is not installed. * To attach a .iso file using VMCLI, ensure that there is no blank spaces in the .iso filename. * To install a 32-bit Firefox browser on SUSE Linux Enterprise Server 11 operating systems, ensure that you use a 32-bit media. ###################################################################### KNOWN ISSUES FOR DOCUMENTATION ###################################################################### This section provides additional information about known issues with the iDRAC6 Firmware version 1.2 User's Guide. None ###################################################################### Information in this document is subject to change without notice. (C) 2009 Dell Inc. All rights reserved. Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden. Trademarks used in this text: "Dell", "OpenManage", "PowerEdge" and "PowerVault" are trademarks of Dell Inc.; "Microsoft", "Windows", "Windows Server", "Active Directory", and "Windows Vista" are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries; "Intel" is a trademark of Intel Corporation in the United States and other countries; "SUSE" is a registered trademark of Novell, Inc.; "Red Hat" is a registered trademark of Red Hat, Inc. in the United States and other countries; VMware is a registered trademark of VMware, Inc. in the United States and/or other jurisdictions. 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 2009