Release Notes

• Support for AMD Abu Dhabi CPU for M915, M910.
Fixes
• The getconfig RACADM command output is not reflecting changes made to cfgServerFirstBootDevice object
properly.
• In the iDRAC Web interface, the About page does not display the correct iDRAC firmware version.
• M610 with an Amulet DX4000 Mezzanine card reboots the blade server after iDRAC firmware upgrade or downgrade.
• In the iDRAC6 Web interface, the SNMP Community string does not accepting an underscore character (_).
• The Address Resolution Protocol (ARP) request is invalid.
• Changes to IPMI over LAN setting in Lifecycle Controller (USC) is not displayed in the iDRAC6 Web interface.
• For the closessn RACADM command, a and i options does not close the remote RACADM sessions.
• The config RACADM command accepts special characters for Group name for Standard Schema. But the getconfig
RACADM command does not display all the specified special characters.
• Single Sign On authentication does not work with non GMT time zone.
Important Notes
• You must disable the Enhanced Security Mode in Internet Explorer for the Java-based virtual console and virtual
media plug-in to function properly. Else, specify the ActiveX plug-in in the iDRAC6 configuration instead of Java. In
addition, you must add the iDRAC6 Web URL to the Intranet security zone only. Also, this zone settings must be
Medium-Low or lesser, for the control to function properly.
• To successfully launch Virtual Media, make sure that you have installed a 64-bit JRE version on a 64-bit operating
system with 64-bit browser or a 32-bit JRE version on a 32-bit operating system with 32-bit browser. iDRAC6 does
not support 64-bit ActiveX versions. Also, make sure that for Linux, the compat-libstdc++-33-3.2.3-61 related
package is installed for launching Virtual Media. On Windows, the package may be included in the .NET framework
package.
• To use Virtual Console with Java plug-in, the supported JRE version is 1.6.0_20 or higher.
• For Remote Enablement auto-discovery, make sure that the user ID on the provisioning server does not contain any
spaces, as iDRAC6 user IDs may not contain spaces. If a user ID containing spaces is configured on the provisioning
server, the auto-discovery process may be successful, but the resulting iDRAC6 account is not be usable.
• The iDRAC6 can be updated using the DOS utility when DOS is booted using PXE. However, the new firmware image
has to be on a local media on the system for this to work properly. Local media can be a RAMDISK, HD, or a USB
key on the server. When the image is stored on non-local devices like a network drive, PXE server drive, and so on,
the iDRAC6 update on multiple systems must be sequenced that is, it should be done one system after the other.
After the first system completes the update, the second system starts the update. After the second system
completes the update, the third system starts the update and so on.
• On systems running Windows operating systems, the Explorer window(s) for any media does not close
automatically if you remove the media. You must close the window(s) after you remove the media. On systems
running Linux operating systems, the file browser window(s) for any media closes automatically if you remove the
media.
• iDRAC6 Linux DUPs do not support VMware ESX 4.0 operating systems. If the Linux DUP for iDRAC6 is run on
VMware ESX 4.0, the DUP fails. You can update iDRAC6 using one of the following interfaces:
o Chassis Management Controller Web interface
o iDRAC6 Web interface
o Remote RACADM
• If the message "A webpage is not responding on the following website" is displayed in Internet Explorer 8.0, see:
o //blogs.msdn.com/ie/archive/2009/05/04/ie8-in-windows-7-rc-reliability-and-telemetry.aspx
o //support.microsoft.com/?kbid=970858
• To execute iDRAC DUPs in XenServer 5.6, you must install the procmail package. You can install the procmail RPM
in CentOS 5.4 i386, which can be downloaded from any public site that hosts CentOS packages. However, it is
recommended not to install any RPMs manually on XenServer, instead download and install the OpenManage