Release Notes

Limitations
• iDRAC features cannot access CIFS or Samba shares when only SMBv1 protocol is enabled. All iDRAC features work with SMBv2/
SMBv3 protocol. For information on enabling SMBv2/SMBv3 protocol, see the documentation for your operating system.
• The behavior of an LC log export to a remote share is not dened when the path specied (-l option) in racadm command contains
special characters. Please use the conventional characters in naming the remote share directory. The special characters like @#$
%^&*()+! are not advisable to be used for naming directories or folders.
• 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. Go to General > Network Settings.
• Lifecycle Controller may go into an innite loop when a network operation is tried with an incorrect NFS share name. Restart Lifecycle
Controller and retry the operation with the correct NFS share name details.
• If NPAR is enabled, LC might show unexpected behavior when conguring network settings. Disable NPAR option and execute the
network setting congurations. To disable the NPAR option, go to
System Setup > 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 nd 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.
• If you enumerate the enclosure view's WSMan command on a system while one PSU-cable is removed, the primary status of the
enclosure view is reported as Healthy instead of Warning.
• After iDRAC reset or rmware update, the ServerPoweredOnTime (a property in RACADM and WS-MAN) may not be populated until
the host server is restarted.
• On performing warm boots, occasionally a message is displayed by BIOS indicating that there is a KCS failure (error code UEFI0039).
No action required for this error. Rebooting the host restores normal boot behavior.
• Upon execution of racadm swinventory or racadm hwinventory command via a local RACADM interface, the inventory details are not
fetched if all the OS drives (A-Z) are mapped. Unmap an existing OS drive to resolve this issue.
• Using local RACADM proxy, if you congure a CMC user name that consists of a space, the command does not successfully create the
user name. Use CMC RACADM, Remote RACADM, or Remote RACADM proxy interface.
• Redsh response contains a HTTP header named Allow, when the HTTP response code is 405. The list may contain PATCH, DELETE,
POST, GET, HEAD values, but all of them may not be supported.
• If a requested resource is not present, HTTP response status code may not be always 404.
• Scrolling-down using the mouse does not work in VNC server.
• When a new PCIe SSD drive is hot plugged in an empty drive bay slot, PrepareToRemove or SecureErase features on that drive fail
unless the host is rebooted and it completes the CSIOR cycle.
• Sometimes, iDRAC logs the following message to the Lifecycle Controller log: PWR2262: "The Intel Management Engine has
reported an internal system error." Also, it logs the following message within the next few minutes: PWR2264: "The Intel
Management Engine has reported normal system operation." No action is required. All Dell PowerEdge systems with iDRAC7 and
iDRAC8 are aected.
7
Limitations 11