Release Notes

• 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.
• USB NIC IP address must always be assigned Link Local address. Assigning IP address other than Link Local
IP address or conflicting IP address of other network interface may cause network related issues.
• iDRAC Virtual NIC driver is not loaded when Windows 2008 SP2 (64-bit) installation has completed.
• When Virtual Console is in Lifecycle Controller, if
Next Boot
is set to
BIOS Setup
, rebooting the system
boots to Lifecycle Controller instead of BIOS Setup.
• If the http or https service port is set to 1 or 65535, and if you launch the iDRAC8 web interface using the
Google Chrome browser, it does not launch iDRAC8. This is because of a limitation in the Google Chrome
browser. The resolution is to use Internet Explorer or Mozilla Firefox browsers.
• You cannot start iDRAC after updating the NIC firmware because the update process resets NDC. To
resolve this issue, reset iDRAC after updating the NIC firmware.
• When iDRAC NIC is in shared mode and the host system is power cycled, the network connection is lost
for a few seconds. During this time, if you perform any action in the active VNC client, the VNC session
may close. You must wait for time out (value configured for the VNC Server settings in the Services page in
iDRAC Web interface) and then re-establish the VNC connection.
• The ports 6000-6063 are reserved for x-server display. Hence, any service configured with these ports on
iDRAC is unsuccessful. Use ports other than 6000 to 6063 to configure the service.
• For servers with higher configuration (more enclosures and RAID components), remote racadm may not
provide the output for hwinventory or swinventory commands. In such cases, try using firmware racadm
(SSH).
LC GUI - Fixes
None.