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: http://support.microsoft.com/kb/3140245/EN-US
2. 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 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 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.
6. If Test Network Connection fails for a valid address in LC, try configuring the network settings again. If the issue persists, restart the
system and retry the operation.
7. You must reboot an already launched instance of LC while you reset or update iDRAC. 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 (which is connected to Top of Rack switch) receives LLDP packets. Thus, the
iDRAC network port (dedicated mode) LLDP information is not available in the blades whose CMC is not the first 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 an NVMe drive reports a 'Failed' status due to any of the controller SMART errors, it should be treated as a predictive failure. 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.
13. 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 complete the memory tuning:
a. Update to this version of iDRAC.
b. At the next possible maintenance cycle, or before any power operations are performed, turn off the host.
c. Wait for 2 minutes for iDRAC to reset and tune the memory parameters.
d. Power on the host.
14. 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 complete the memory tuning:
a. Update to this version of iDRAC.
b. At the next possible maintenance cycle, perform a virtual reseat.
15. After updating iDRAC Firmware directly to 3.30.30.30 or later from a previous version, the first inventory collection after system
reboot may display both PR7 (New Device Detected) and PR8 (Device not detected) messages. A change in the slot number display
format causes this behavior, which is expected.
16. Ensure that the SSH client is updated to the latest version. Following SSH configurations are no longer available on iDRAC:
5
10 Important notes