iDRAC9 with Lifecycle Controller Version 3.11.11.11 Release Notes

Important notes

1. Windows Server 2012, Windows Server 2008 R2, and Windows 7 do not support TLS 1.2 and TLS 1.1. Install the following update to enable TLS 1.2 and TLS 1.1 as a default secure protocols in WinHTTP in Windows:

   support.microsoft.com/kb/3140245

2. The drivers exposed by LC are present in a read-only drive labeled OEMDRV and the drive is active for 18 hours. During this period:
   • You cannot update any DUP.
   • LC cannot involve CSIOR.

   However, if an AC power cycle (cold boot) is performed, the OEMDRV drive is automatically deleted.

3. CPLD firmware update has no impact on Trusted Platform Module enablement.
4. 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.
5. If the network is not configured and you try to perform a network operation, a warning message is displayed. When you navigate to the network settings page from this message, the left navigation panel on network settings page may not be displayed.
6. 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.
7. 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.
8. 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.
9. 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.
10. Rollback is not supported for CPLD.
11. 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 (only in the case of 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.

12. 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). This includes SMART errors such as:
    • Available spare threshold
    • Reliability degraded
    • Read-only mode
    • Virtual memory backup failed, and so on