Release Notes
Limitations
• After an iDRAC reset or firmware update operation, the ServerPoweredOnTime (a property in RACADM and WSMan) may not be
populated until the host server is restarted.
•
Sometimes, when using WSMan, an Internal SSL Error is reported and the WSMan command fails. If this happens, retry the
command.
• Due to known limitations in OpenSource (SFCB), query filtering with long integers and lengthy strings may not work as expected.
• If the LCD display is blank, press any one of the 3 LCD buttons to turn on the LCD before inserting a USB storage device.
• If Flex Address is enabled on Chassis Management Controllers (CMC), iDRAC and LC do not display the same MAC addresses. To
view the chassis-assigned MAC address, use the iDRAC web interface or the CMC web interface.
• Windows operating system deployment may intermittently fail with the following error message: A required CD/DVD drive
device driver is missing. If you have a driver floppy disk, CD, DVD, or USB drive, please
insert it now. Reboot to LC and retry until the operating system is successfully deployed.
• Some of the supported components may not be displayed on the Firmware Update > View Current Versions page. To update this
list, restart the system.
• While performing any network operation, LC may go into an infinite loop if there are network glitches, leaks, or packet loss. Restart LC
and retry the operation with the correct NFS share name details.
• You may be unable to scroll using the keyboard. Use the mouse to scroll.
• If NPAR is enabled, LC might show unexpected behavior when configuring network settings. Disable NPAR and execute the network
setting configurations. To disable the NPAR option, go to System Setup > Device Setting.
• When NPAR is enabled, the port numbers displayed on the LC Network Settings page (Settings > Network Settings) do not match
the port numbers displayed on the Device Settings page (
System Setup > Advanced Hardware Configuration > Device
Settings).
• When Virtualization Mode is set to NPAR for Network Adapter that support the partitioning feature, PartitionState attribute can
only be used for checking the state of partitions created for base partition in WSMan enumeration. You can see the states of all the
partitions by pressing F2 during POST and going to Device Setting.
• The process of retrieving IPv6 address from the DHCP server with VLAN connection takes a few minutes. Wait for a few minutes and
check the Network Settings page to view the assigned IPv6 address.
• Deployment of Windows Server operating systems (OS) using LC may fail with one of the following message:
• Windows installation cannot continue because a required driver could not be installed.
• Product key required.
• Windows cannot find the software license terms.
This happens when the Windows setup copies the driver to the scratch space (X: drive) and the scratch space becomes full. To
resolve this issue, do any of the following:
• Remove all the installed add-on devices before starting the OS installation. After the OS installation is complete, connect the add-
on devices and manually install the remaining drivers using Dell Update Packages (DUPs).
• To avoid physically removing the hardware, disable the PCle slots in the BIOS.
• Increase scratch space size beyond 32 MB using DISM set-scratchspace command when creating customized deployment.
For more details, see Microsoft's documentation.
• LC supports the following characters for username and password:
Alphabets
a-z, A-Z
Numbers 0-9
Special characters - _ .
• If the iDRAC firmware update is interrupted, you may have to wait up to 30 minutes before attempting another firmware update.
• Firmware update is supported only for LAN on Motherboards (LoM), Network Daughter Cards (NDC), and network adapters from
Broadcom, QLogic, and Intel, and some of the QLogic and Emulex fiber channel cards. For the list of supported fiber channel cards,
see the Lifecycle Controller 3.00.00.00 User’s Guide available at www.dell.com/idracmanuals.
• After the CPLD firmware is updated on modular systems, the firmware update date is displayed as 2000-01-01 on the View Current
Versions page. The update date and time is displayed according to the time zone configured on the server.
• On some modular systems, after a firmware update, the Lifecycle Log displays the time-stamp as 1999-12-31 instead of the date on
which the firmware update was performed
7
12 Limitations