Release Notes
Table Of Contents
- iDRAC9 Version 4.20.20.20 Release Notes
- Release summary
- Compatibility
- New and enhanced features
- Fixes
- Deprecated features
- Important notes
- Known issues — To be fixed in future releases
- OpenManage fails to determine iDRAC license type
- iDRAC DUP update fails in Linux operating systems when secure boot is enabled
- iDRAC service module displaying incorrect iSM status
- Device based deployment of WWN attribute of FC remains unchanged
- iDRAC loses communication with OME-Modular
- During POST, the host system is temporarily unable to communicate with iDRAC
- Uploaded firmware link not available in the SoftwareImages property in Redfish
- PCIe types and lanes information not getting populated using Redfish
- iDRAC reboots while collecting SupportAssist logs
- System Setup iDRAC Power Configuration Menu prompts to save changes unexpectedly
- iDRAC and iSM Communication failure
- SupportAssist collection failing
- Cooling fans displaying N/A status
- CMC firmware update fails from iDRAC
- Joining iDRAC to Group Manager fails on VLAN network
- CPU information not available in hardware inventory
- Intel Coldstream NVMe drives appearing as cryptographic erase capable
- Missing Qlogic NIC Partitions in iDRAC GUI
- SupportAssist collection job creation fails
- System configuration profile NIC job completes with errors
- iDRAC Firmware Update page not responding
- IDSDM controller listed in iDRAC without an IDSDM installed
- Webserver restarts after remote presence port number is updated
- Getting an error SWC0018 during OS installation
- WSMan query with space between attributes fails
- Attributes for CNA cards not displayed through Redfish or RACADM interface
- Rollback firmware Version is not displayed for NVDIMMs
- Get method not displaying certificates after all certificates are deleted
- iDRAC dashboard page in IE displays an expanded progress bar
- Unable to create a recurring job after same recurring job was completed
- Unable to create virtual disk through Redfish
- SCP Import Job completes with error due to HddSeq error
- iDRAC LC Log shows reset cause as ‘watchdog’
- Integrated/Embedded NIC displaying status as Unknown
- No errors when the selected component and the selected device firmware do not match
- PCIe SSD Backplane 2 is displayed as unknown
- Firmware update operation not scheduled through WSMan
- Access to serial interface fails.
- Remote File Share (RFS) does not stay connected after downgrading iDRAC
- LC log created after going to Virtual media page in iDRAC GUI
- Firmware update for a replaced PSU failing
- Device description and type not displayed
- Get method on UefiTargetBootSourceOverride attribute shows null value
- Sluggishness in Virtual Console
- Blank boot capture file generated
- Unable to export factory shipped inventory
- NIC or FC device slot listed in hardware inventory even when disabled in BIOS
- Get operation not displaying model or serial number for PCIe devices
- Boot mode error during OS deployment
- Repetitive PR7 messages related to PSU in LC logs after a system erase operation
- After a warm reboot, LC logs display Disk Inserted
- Limitations
- Updating iDRAC firmware
- Lifecycle Controller Remote Services — client tools
- Resources and support
- Contacting Dell EMC
26. The drivers that LC exposes are present in a read-only drive that is labeled OEMDRV and the drive is active for 18 hours.
During this period:
a. You cannot update any DUP.
b. LC cannot involve CSIOR.
However, if a server AC power cycle or iDRAC reboot is performed, the OEMDRV drive is automatically detached.
27. CPLD firmware update has no impact on Trusted Platform Module enablement.
28. Depending on the virtual storage device attached through iDRAC, that is, USB drive or CD/DVD .ISO file, LC displays Virtual
Floppy or Virtual CD respectively.
29. If the network is not configured and you try to perform a network operation in LC, a warning message is displayed. When you
go to the network settings page from this message, the left navigation panel on network settings page may not be displayed.
30. If a network operation fails for a valid address, try configuring the network settings again. If the issue persists, restart the
system and retry the operation.
31. When you reset or update the iDRAC, you must reboot LC if it is launched already. If you do not reboot, LC may show
unexpected behavior.
32. Fibre-channel NIC cards with dual or four ports are displayed as a single port card in LC. However, all ports are updated
when a firmware update is performed.
33. The option to enable or disable the disk cache policy for SWRAID controllers are supported only on SWRAID controller driver
version 4.1.0-0025 or later.
34. Rollback is not supported for CPLD and HBA controllers.
35. When CMCs are daisy chained, only the first CMC (CMC which is connected to Top of Rack switch) receives LLDP packets.
Other CMCs do not receive LLDP packets. So, the iDRAC network port (dedicated mode) LLDP information is not available
in the blades whose corresponding CMC is not the first CMC in the daisy chain. The LLDP information is also not available
for every CMC in the daisy chain that is not connected to TOR switch directly.
36. If any of the NVMe drives report a 'Failed' status (Red LED) due to any of NVMe controller SMART errors (critical warning
bits set), it should be treated as a predictive failure (Blinking amber LED). These errors include SMART errors such as:
a. Available spare threshold
b. Reliability degraded
c. Read-only mode
d. Virtual memory backup failed, and so on.
37. This note is applicable only to PowerEdge C6420, DCS9650, DCS9670, and DCS9690 systems. If you update iDRAC to this
version from version 3.02.x.x or earlier, you must perform a power cycle of the system before performing any power-related
operations. The power cycle is required to tune the memory parameters without affecting the host. iDRAC tunes the
memory parameters at the first power cycle after a firmware update. To allow the memory tuning to be completed:
a. Update to this version of iDRAC.
b. At the next possible maintenance cycle, or before any power operations are performed, power off the host.
c. Wait for 2 minutes to allow iDRAC to reset and tune the memory parameters.
d. Power on the host.
38. This note is applicable only to PowerEdge M640 and FC640. If you update iDRAC to this version, you must perform a virtual
reseat of the system from CMC. Reseat is required to tune the memory parameters and to resolve issues that may lead to
the watchdog timer causing iDRAC to be reset. To allow the memory tuning to be completed:
a. Update to this version of iDRAC.
b. At the next possible maintenance cycle, perform a virtual reseat.
39. After updating iDRAC Firmware to 3.30.30.30 from a previous version, the first inventory collection after system reboot may
display both PR7 (New Device Detected) and PR8 (Device not detected) messages. This is an expected behavior that is
caused by a change in the slot number display format.
40. Ensure that the SSH client is updated to the latest version. Following SSH configurations are no longer available on iDRAC:
KEX algorithms:
a. diffie-hellman-group14-sha1
MAC:
a. umac-64
b. umac-64-etm@openssh.com
41. This note is applicable only to PowerEdge M640 and FC640. When performing BIOS Recovery operation, host may not turn
on. To recover from this condition, do a virtual/physical reseat operation of the blade server.
42. After updating the iDRAC firmware, LC logs may display Message ID PR36 that "Version change detected for PCIe SSD
firmware. Previous version:X.X.X, Current version:X.X.X." This is due to a change in the naming convention. Ignore the log
entry.
43. After downgrading the iDRAC firmware to any previous versions, storage page and drives may display warnings. To resolve
the issue, reset iDRAC using the 'racreset' command.
Important notes
15