Release Notes

Important notes
1. Creating RAID using the selected controller is not supported through Lifecycle Controller interface. Use iDRAC GUI to create
the virtual disk, then relaunch Lifecycle Controller and retry the deployment operation.
2. A new storage GUI has been introduced with this release. The old storage GUI is still accessible but would be deprecated in a
future iDRAC release.
3. For Telemetry reports through subscription, if there are more than two subscriptions, it is recommended to update the
Metric Report Recurrence interval to above 60 seconds.
4. There is a change in the URI for BIOS HTTP Certificates from iDRAC version 4.40.00.00 and later versions. To perform
BIOS HTTP certificate related operations use the following Certificates URI:/redfish/v1/Systems/{ComputerSystemId}/
Boot/Certificates
5. IPMItool interface does not report non-communicative PSU status for PowerEdge Rx4xx/Cx4xx servers.
6. In Redfish API, all BIOS certificate related operations are now supported using the new URI: /redfish/v1/Systems/
{ComputerSystemId}/Boot/Certificates
7. Adding an iDRAC system with firmware version 4.40.00.00 to a group manager with systems having iDRAC versions earlier
than 3.xx, 4.0x, 4.1x, 4.2x, or 4.3x is not supported, ensure all the systems have the latest iDRAC firmware version 4.4x or
any later versions.
8. Arrow keys on virtual keyboard of the iDRAC Virtual Console with eHTML5 plug-in do not respond inside BIOS boot manager
after the system reboots. Close and reopen the eHTML5 Virtual console session.
9. Before deleting a VD that hosts the OS, ensure uninstalling the iSM. If VD is deleted without uninstalling iSM, LC log may
display the following error: "ISM0007 The iDRAC Service Module Communication has ended with iDRAC".
10. If an Active Directory user is configured for SSO with RSA token authentication, then the RSA token is bypassed and user
can log in directly. This is because RSA is not applicable for AD-SSO, Active Directory smart card, and local user smart card
logins.
11. While performing any method (GET/POST and so on) on an incorrect resource URI, a proper extended error message
specifying that "Resource URI is incorrect" is not provided in the response body.
12. When auto negotiation is disabled while iDRAC in Shared LOM mode, the speed and duplex values shown in the GUI and
racadm output may not accurately show the actual speed and duplex on the link.
13. While performing a firmware update or rollback through LifeCycle controller GUI, the component information displayed in the
table listing the available updates may be truncated if it exceeds the table column or row width.
14. If SOL session is active for a long duration or if the system is rebooted multiple times, the SOL session gets terminated
automatically.
15. Critical event PDR1016 will not be generated when M.2 drives from the BOSS-S2 controller are removed since M.2 drives are
directly attached to BOSS controller and not connected to the backplane.
16. While performing BIOS Recovery operation all iDRAC resets are blocked and if a iDRAC reset to default operation is
performed, it causes iDRAC to be set to factory defaults and iDRAC will not reset. The condition is expected and a manual
iDRAC reset is recommended.
17. After an iDRAC reboot, the iDRAC GUI may take some time to initialize causing some information to be unavailable or some
options to be disabled.
18. Unlike RAID 10 configured via iDRAC, OMSA or PERCCLI with all disks on a single span, a RAID 10 VD created in the
Lifecycle Controller only supports two disks per span. Therefore, expansion of RAID 10 VD created in the LC is not
permissible.
19. AD/LDAP diagnostic results will display Not Run or Not Applicable for Ping Directory Server Tests. ICMP ping tests are no
longer performed while running AD/LDAP diagnostics.
20. While generating Server Configuration Profile templates using the Clone or Replace option, ensure that the template is
updated using a password that complies with the restrictions set on the target iDRAC, or use the 'Include Password Hash'
option.
21. While clearing the Job queue using RACADM, WSMAN, or Redfish interface, it is recommended to use JID_CLEARALL
instead of JID_CLEARALL_FORCE . Use JID_CLEARALL_FORCE only to recover iDRAC Lifecycle controller from a failed
state to avoid an iDRAC restart.
22. For Dell online catalog update, downloads.dell.com only supports https protocol.
23. After updating the iDRAC license to Data Center license, ensure that you reboot the iDRAC for Idle server detection feature
related attributes to function.
24. Updating firmware from version 3.30.30.30/3.34.34.34/3.36.36.36 to 4.00.00.00 or later using http/https/ftp share may fail
if you use default file name. Ensure to rename the file name before you proceed with the firmware update.
6
Important notes 13