Release Notes

• 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).
•
On a system with a non-PERC RAID controller, the available virtual or physical disk(s) may not be displayed
in the virtual or physical disks tab in the iDRAC web interface.
•
In the iDRAC web interface, you can upload the same firmware DUP multiple times.
•
Historical Peak Value is available using the get and set RACADM commands. However, this option is not
available using the iDRAC web interface.
• Systems with PERC H330 RAID controller may display an empty slot on the Storage enclosure page in the
iDRAC web interface.
•
Since power supplies are not available on the PowerEdge C6320, power supply attributes display a 0 instead
of N/A in the get command
• Virtual console preview in the iDRAC web interface may display No Signal however, you can connect to the
console.
•
The System Event Log in the iDRAC web interface displays an Unknown Event after performing a system
erase using the Repurpose and Retire feature in Lifecycle Controller.
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.
• 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.