Release Notes

• If the instant messenger is launched in the Virtual Console viewer with ActiveX native plug-in and another
application is started (example Notepad, WordPad, and so on) without minimizing the Virtual Console, the
instant messenger box also pops-up on other applications. This does not happen with Java plug-in.
• When a system is in POST, it is not possible to attach a vFlash partition as the first boot device.
• Virtual Console Viewer from iDRAC8 Web interface terminates when the managed system is restarted.
• A pop-up message is not displayed to confirm if test emails are successfully sent or not.
• For iDRAC8 Enterprise, when the Virtual Console is disabled and Virtual Media is disabled and/or detached,
the console port (default: 5900) remains open. For iDRAC8 Express (no Virtual Console or Virtual Media)
the console port is open.
• If auto-negotiation is enabled while setting iDRAC8 network, 1 Gbps is not supported and you cannot
manually select it.
• A USB device mounted through Virtual Media in floppy emulation mode for a Linux operating system
shows as a removable volume.
• During system power operations, if the video mode changes, the message "Out of range" may appear for a
short while on the Virtual Console.
• When using the Virtual Console in native console mode with
Pass all keystrokes to server
disabled in
Internet Explorer versions 8 and 9, if an F1/F2 prompt is encountered, pressing F1 displays the Virtual
Console online help pop-up in addition to continuing with the system boot.
• When any of the storage enclosure components are removed, the corresponding details are not displayed.
Only the name and status attributes are displayed.
• When certain RAID operations are requested using WS-MAN on non-RAID cards such as, the Dell SAS
6Gbs HBA or the Internal Tape Adapter, the operation succeeds, however the job fails with the error
message "Unable to locate device in current configuration".
• If the iDRAC8 network is configured to use a shared LOM and the spanning tree is enabled on the LOM
port, WS-MAN and remote service commands may time-out in the following scenarios:
- At system reboot
- When CSIOR is running
- While entering SSM
The connectivity lost is variable. In typical cases, it is approximately:
- 40 seconds at system reboot and varies per NIC or link speed
- 20 seconds when CSIOR is running
- 40-60 seconds while entering SSM
• The reason is that when spanning tree is enabled, the switch does not allow the link to re-establish the
connection after a reset until it completes checking for network loops. Server reboots reset the NIC and
disconnects the link.
Note
: This does not occur while using dedicated NIC because server reboots do not affect the dedicated
NIC.
• When logging in to iDRAC8 web interface using Internet Explorer 9 and IPv6 address, the connection may
not succeed. To resolve this, make sure that in
Internet Explorer
->
Tools
->
Internet Options
->
Connections
->
LAN Settings
, the
Use automatic configuration script
option is cleared.
• On PowerEdge systems with cabled power supply units installed (that is, PSUs which do not provide
PMBus support), power values may still be displayed in the iDRAC8 web and LCD interfaces. Due to lack of
PMBus support in the PSUs, the power values displayed on the GUI pages, including the
Overview
->
Hardware
->
Front Panel
page, may not be correct.
• Due to the independent nature of the alert processes (e-mail, SMTP, remote syslog), when changing the
licenses that affect alert features (example, email alerts for Express or remote syslog for Enterprise) there is
no guarantee of the timing of the features being activated or deactivated when the license changes.
• In the iDRAC web interface, when the
System Inventory
page is accessed for the first time, it takes up to
two minutes for the inventory data to be collected. After the data collection is complete, refresh the page
to display the inventory data.