Release Notes
•
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.
LC GUI - Important Notes
•
This release note is the latest and overrides the release note available on the LC GUI.
•
The drivers exposed by Lifecycle Controller are present in a read-only hard disk drive, labeled OEMDRV,
which are active for 18 hours. During this period:
o
You cannot update any DUP.
o
Lifecycle Controller cannot invoke CSIOR.
However, if an AC power cycle (cold boot) is performed, the OEMDRV drive is automatically deleted.
•
To log the update events in the Lifecycle Log, make sure that the installed versions of Lifecycle Controller and
iDRAC are from the same release.
•
If Lifecycle Controller and iDRAC are not from the same release, the Lifecycle Log displays blank messages
and messages with a “~” character.
•
CPLD firmware update has no impact on Trusted Platform Module enablement.
•
On the basis of virtual storage device type attached through iDRAC, that is, USB drive or CD/.ISO file,
Lifecycle Controller will display Virtual Floppy or Virtual CD respectively.
•
If Test Network Connection fails for a valid address, try configuring the network settings again. If the issue
persists, restart the system and retry the operation.
•
When you reset or update iDRAC, you must reboot Lifecycle Controller if it is launched already. If you fail
to reboot, Lifecycle Controller displays an unexpected behavior.
•
On PowerEdge FC630, PowerEdge FC830, and PowerEdge FC430 systems, part replacement is not supported
if a single PERC (FD332) is replaced with a dual PERC (FD332) or vice versa.
•
After performing firmware update or rollback operations using Lifecycle Controller the host is rebooted by
default, reboot the host server again to display the updated firmware versions in the Hardware Configuration
wizard.
•
While installing the operating system on the Dell 12th generation PowerEdge servers using Lifecycle
Controller, ensure that the virtual media is connected to the server before booting in to the BIOS.