Release Notes

iDRAC - Limitations
• If floppy emulation is enabled when a bootable USB key is mounted as a Virtual Media from the Virtual
Console and if you try to delete any file from the mounted USB key (floppy), the blue screen appears
immediately.
•
Web server session time-out is not exact. It is either 10% more or 15 seconds more, whichever is greater.
•
WinRM and RACADM commands may become unresponsive during BIOS update or when setting BIOS,
NIC, or RAID attributes through Lifecycle Controller.
• If invalid credentials are used for the maximum login attempts, the IP is blocked for the duration of the IP
Blocking Penalty Time and a message is not displayed.
•
If Internet Explorer (IE) 64-bit browser is used to log in to iDRAC8 Web interface and when viewing the
power usage graph, the X and Y axis labels appear too small to read. This is a known limitation for IE 64-bit
only. The labels appear correctly in IE 32-bit browser.
•
On Linux management stations, if Firefox is launched from the root user, a USB key is mapped in Virtual
Media successfully. If Firefox is launched from any user other than the root user, a USB key is not shown for
mapping because the user must have root privileges to access all the low-level drives.
• Alert notification for battery events does not work.
•
Operating system information on the System Summary page does not display after rebooting iDRAC8 until
the operating system is rebooted.
•
iDRAC8 users with user names containing a semi-colon (;) cannot log in to iDRAC8 through SSH.
•
In the iDRAC8 web interface, the power consumption sensor reading may have a rounding error of up to 13
Watts depending on the actual power reading. This is an IPMI limitation. The power cap, power graphs,
cumulative power, and peak power are not affected by this inaccuracy. However, the power values shown in
the power graphs are average values over a period of time and should not be used to calculate instantaneous
power.
•
Virtual Console uses self-signed certificates. Due to this, when launching Virtual Console from some
management stations with Windows operating systems, a certificate warning appears.
• Virtual Console in dual monitor mode is not supported and hence the behavior is undefined, especially using
Java plug-in. The primary console is used as the target console.
•
The email address specified in iDRAC8 web interface -> Overview -> iDRAC Settings -> Network -> SSL
->
Generate Certificate Signing Request (CSR) page is not validated.
•
On a Linux management station with Matrox drivers, from the Virtual Console Viewer if you access the
iDRAC Chat window, the mouse appears flickering inside the chat window.
• Work notes can display up to 255 characters. If any of the characters are special characters or non-alpha
numeric characters, then the total number of characters displayed is less than 255 to accommodate overriding
special characters.
•
Performing a graceful shutdown from the iDRAC8 web interface or updating the BIOS or the firmware using
the iDRAC8 update method:
o
For SLES 11 SP2:
A prompt appears for the Super user password in the operating system console. Provide the root
password and proceed with the graceful shutdown or firmware/BIOS update.
o
For Windows OS in screen lock state:
Graceful shutdown does not happen because, Windows operating system has a policy setting to
disable shutdown while in locked state. Make sure that this policy is enabled.
If it is not enabled, then it proceeds with ungraceful shutdown. This is equivalent to losing power.
After the server resets, multiple options are displayed to start Windows. Select Start Windows
Normally
and then check the System Event Log file. You can see that an event is logged in for the
ungraceful shutdown.
•
In the iDRAC web interface > Overview > Server > Lifecycle Log page, when the filter criteria results in
nothing found, the
Log Results section does not display any user-friendly information and it is blank instead.
•
VNC disconnects after host reboot on Wyse PocketCloud.
•
Encrypted VNC does not work through Real VNC client.
• VNC does not work through mobile when encryption is enabled.
•
OS to iDRAC communication through the USB NIC interface is not supported on RHEV – H (hypervisor)
system.