iDRAC9 Version 7.00.00.174 Release Notes
Rev. A00, November 2024
Overview
This release includes fixes that improve iDRAC stability and security.
- Current Release Version: 7.00.00.174
- Previous Release Version: 7.00.00.173
- Release Type: Minor (MI)
Topics
- Revision History
- Product Description
- New and enhanced features
- Resolved issues
- Known issues
- Limitations
- Environmental and system requirements
- Installation and upgrade considerations
- Where to get help
Revision History
- 6.00.02.00
- 6.00.30.00
- 6.00.30.15
- 6.00.30.25
- 6.10.00.00
- 6.00.30.27
- 6.10.30.00
- 6.10.30.20
- 6.10.80.00
- 7.00.00.00
- 7.00.00.171
- 7.00.00.172
- 7.00.00.173
NOTE: The list of previous iDRAC versions that are supported may vary depending on the server model. To see the supported previous versions for a specific server:
- Go to Dell Support page.
- In the Enter a Service Tag, Serial Number... field, type the Service Tag or the model number of your server, and press Enter or click the search icon.
- On the product support page, click Drivers & downloads.
- From the list, locate and expand the iDRAC entry and click Older versions.
List of all previous versions supported is displayed along with the download link and the release date.
Product Description
The Integrated Dell Remote Access Controller (iDRAC) is designed to make server administrators more productive and improve the overall availability of Dell servers. iDRAC alerts administrators to server issues, helps them perform remote server management, and reduces the need for physical access to the server. Additionally, iDRAC enables administrators to deploy, monitor, manage, configure, update, and troubleshoot Dell servers from any location without using any agents. It accomplishes this regardless of the operating system or hypervisor presence or state.
iDRAC also provides an out-of-band mechanism for configuring the platform, applying firmware updates, saving or restoring a system backup, or deploying an operating system, either by using a GUI or a remote scripting language, such as Redfish or RACADM.
Release date
November 2024
Priority and recommendations
Recommended: Dell Technologies recommends applying this update during your next scheduled update cycle. The update contains feature enhancements or changes that will help keep your system software current and compatible with other system modules (firmware, BIOS, drivers, and software).
Minimum version
N/A
NOTE: This release only supports 14th generation servers.
NOTE: For details about the previous releases, if applicable, or to determine the most recent release for your platform, and for the latest documentation version, see KB article 00178115 available at Integrated Dell Remote Access Controller 9 Versions and Release Notes.
New and enhanced features
N/A
Deprecated features
The following table displays the features that are listed as deprecated*, Removed**, and To be Removed***:
Table 1. Deprecated Features
Features |
iDRAC9 for 14th-Generation PowerEdge Rx4xx/Cx4xx |
iDRAC9 for 15th-Generation PowerEdge Rx5xx/ Cx5xx |
iDRAC9 for 16th-Generation PowerEdge Rx6xx/Cx6xx |
SM-CLP |
Removed |
Removed |
Removed |
VM CLI |
Removed |
Removed |
Removed |
vFlash |
Deprecated |
Removed |
Removed |
Backup and Restore |
Removed |
Removed |
Removed |
iDRAC9 for 14th-Generation PowerEdge Rx4xx/Cx4xx |
Removed |
Removed |
Removed |
RBAP and Simple Identity profiles |
Removed |
Removed |
Removed |
WSMan |
Deprecated |
Deprecated |
Deprecated |
DCIM_account profile |
Removed |
Removed |
Removed |
Telnet and TLS 1.0 |
Removed |
Removed |
Removed |
SHA1 |
Removed |
Removed |
Removed |
Java, ActiveX, and HTML5 plugins for vConsole, vMedia, and RFS access |
Removed |
Removed |
Removed |
SupportAssist direct upload, scheduling, and register |
Removed |
Removed |
Removed |
NOTE: Alternatively, use the Server Configuration Profiles (SCP) feature to import or export server configuration settings and firmware updates.
NOTE: Attaching virtual external device using Java client is supported.
NOTE: Alternatively, use Secure Connect Gateway or OpenManage Enterprise Services plug-in for automatic case creation.
NOTE: In iDRAC release version 7.00.00.00 and later versions, Dell Tech Support no longer accepts automatic uploads of SupportAssist Collections.
Deprecated* - No longer being updated or new features added.
Removed** - Code has been removed, this feature is no longer functional.
To be Removed*** - Expected to be removed from iDRAC code in an upcoming release.
Resolved issues
iDRAC Firmware
- 314856: iDRAC sends TCG traffic to Self-Encrypting drives (SEDs) managed by the Host OS.
Security
- CVE-2022-48858 fix.
- CVE-2023-52340 fix.
- CVE-2024-38664 fix.
- CVE-2024-39494 fix.
- CVE-2024-42154 fix.
- CVE-2024-24790 fix.
Storage
- 309722: Unable to see all the drives present on the system.
Known issues
iDRAC firmware
Table 2. Firmware update failure for specific components
Details |
|
Description |
The firmware update for certain components may encounter issues. |
Workaround |
Reboot the iDRAC and initiate the firmware update again. |
Systems Affected |
All systems supported by this release. |
Tracking number |
279474 |
Table 3. PDR8 and PDR5 disk removal and insertion logs during enclosure firmware updates
Details |
|
Description |
During the firmware update process for enclosures like PowerVault MD 2412, PowerVault MD 2424, or PowerVault MD 2460, there are observations of PDR8 and PDR5 disk removal and insertion logs. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release and connected to PowerVault MD 2412, PowerVault MD 2424, or PowerVault MD 2460 enclosure through an HBA controller. |
Tracking number |
275053 |
Table 4. Smart Card certificate revocation list (CRL) checks fail
Details |
|
Description |
iDRAC fails to support local user Smart Card certificate revocation list (CRL) checks. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release. |
Tracking number |
299611 |
Monitoring and alerting
Table 5. Template deployment logs virtual address configuration failure messages
Details |
|
Description |
When deploying templates on sleds within the OMEM framework, the Lifecycle (LC) logs report a failure in configuring virtual addresses for a subset of partitions, despite the configuration being successfully applied. |
Workaround |
No workaround is required as the virtual MAC address configuration is applied without issues. |
Systems Affected |
All modular systems supported by this release. |
Tracking number |
276928 |
Table 6. Intermittent warning message on storage summary page for max configuration systems
Details |
|
Description |
On occasional host cold boots, the Lifecycle(LC) Log and SEL log may display the message "SWC9016 Unable to authenticate CPLD either because of unsuccessful cryptographic authentication or integrity issue." This error results in the server front panel's Amber light being activated and the health status changing to 'critical.' |
Workaround |
See other iDRAC GUI storage pages such as Physical disks and Enclosures page to view the Physical disks details. |
Systems Affected |
All systems supported by this release configured with an increased quantity of physical disks, for example, 240. |
Tracking number |
274630 |
Table 7. PDR8 and PDR5 disk removal and insertion logs during enclosure firmware updates
Details |
|
Description |
During the firmware update process for enclosures like PowerVault MD 2412, PowerVault MD 2424, or PowerVault MD 2460, there are observations of PDR8 and PDR5 disk removal and insertion logs. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release and connected to PowerVault MD 2412, PowerVault MD 2424, or PowerVault MD 2460 enclosure through an HBA controller. |
Tracking number |
275053 |
Table 8. Intermittent SWC9016 Error Triggering Front Panel Amber Light
Details |
|
Description |
On occasional host cold boots, the Lifecycle(LC) Log and SEL log may display the message "SWC9016 Unable to authenticate CPLD either because of unsuccessful cryptographic authentication or integrity issue." This error results in the server front panel's Amber light being activated and the health status changing to 'critical.' |
Workaround |
This log error does not have a functional impact, and it can be cleared by performing an AC power cycle. |
Systems Affected |
All systems supported by this release. |
Tracking number |
276462 |
Table 9. Issue with StorageDiskSMARTData and ReportSequence reports
Details |
|
Description |
Despite multiple recurrence intervals passing since enabling the report, StorageDiskSMARTData is still showing zero metric count and a ReportSequence of one. |
Workaround |
To obtain the latest telemetry details, perform an iDRAC reset. |
Systems Affected |
All systems supported by this release. |
Tracking number |
278027 |
Table 10. Job status pending
Details |
|
Description |
When real-time firmware updates are performed, the job status remains at "Completed Virtual AC pending" even after performing an AC power cycle through the Redfish URI or physical power cycle. |
Workaround |
Perform a cold boot after the AC power cycle to ensure that the job status is correctly displayed as completed. |
Systems Affected |
All systems supported by this release. |
Tracking number |
277870 |
Table 11. Incomplete management module log collection during iDRAC TSR Log retrieval
Details |
|
Description |
There is a possibility that the operation for collecting Management Module logs may not successfully complete when gathering iDRAC TSR logs. |
Workaround |
Directly collect EC Logs from OMEM. |
Systems Affected |
All modular systems supported by this release. |
Tracking number |
276780 |
Table 12. PWR2284 event logs
Details |
|
Description |
iDRAC may intermittently display PWR2284 messages in Lifecycle logs during an AC power cycle stress test. |
Workaround |
Perform an iDRAC reset. |
Systems Affected |
All DCS systems supported by this release. |
Tracking number |
269853 |
Table 13. PR1 & PR10 Lifecycle logs displayed during Retire and Repurpose operation
Details |
|
Description |
PR1 & PR10 logs are displayed in Lifecycle logs for PSUs when Retire and Repurpose operation is executed. This doesn't impact server functionality. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release. |
Tracking number |
186119 |
Table 14. Repetitive PR7 messages related to PSU in LC logs after a system erase operation
Details |
|
Description |
When the system is powered on manually after performing a system erase on LC data, several messages are displayed in LC logs for PSU stating “PR7 New device detected: POWER SUPPLY (PSU.Slot.X)”. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release. |
Tracking number |
129440 |
Networking and IO
Table 15. Latest NIC firmware version not displaying in iDRAC
Details |
|
Description |
When performing a real-time NIC firmware update without requiring a host reboot, if the update job is successful without requesting the host to reboot, the latest firmware version may not reflect in any of the iDRAC interfaces. |
Workaround |
Perform an iDRAC reset or reboot the host system. |
Systems Affected |
All systems supported by this release. |
Tracking number |
277745 |
Table 16. Failure of network and base band management controller firmware update by RACADM
Details |
|
Description |
Firmware updates for the network and base band management controllers are encountering failures when performed using RACADM CLI commands. |
Workaround |
Update firmware from the iDRAC GUI. |
Systems Affected |
All systems supported system by this release with Smart NIC configuration. |
Tracking number |
276045 |
Table 17. Network firmware update job failing
Details |
|
Description |
Unable to create a network firmware update job after running the "racadm systemerase reinstallfw" command immediately after performing "racadm systemerase Icdata" command. |
Workaround |
Update or rollback the network firmware and then try the "racadm systemerase reinstallfw" command. |
Systems Affected |
All systems supported by this release. |
Tracking number |
263013 |
Table 18. Unable to add iDRAC Static IP
Details |
|
Description |
After setting iDrac static IP using IPV4 group (IPv4.1.Address, IPv4.1.Gateway,IPv4.1.Netmask) using Redfish or RACADM interface, a new IP address may not apply and system may become inaccessible. |
Workaround |
Use the IPV4Static group (IPv4Static.1.Address, IPv4Static.1.Gateway,IPv4Static.1.Netmask) to set static IP address. |
Systems Affected |
All systems supported by this release. |
Tracking number |
185458 |
Table 19. Partial information displayed for Mellanox Cards
Details |
|
Description |
iDRAC interfaces only display partial information for the Mellanox network cards, such as, in InfiniBand mode the card is displayed as a NIC device. Also, no board manufacturer and version is available. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release. |
Tracking number |
179265 |
Table 20. NIC or FC device slot listed in hardware inventory even when disabled in BIOS
Details |
|
Description |
For some NIC or FC cards, even if the device slot is disabled in BIOS, the slot may still get listed in the hardware inventory. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release. |
Tracking number |
104535 |
Table 21. iDRAC Network Disruption Post-Reboot Issue
Details |
|
Description |
After an iDRAC reboot, iDRAC may lose network connectivity when configured with LOM1 failover to another shared LOM, especially if LOM1 experiences a link loss during the reboot process. |
Workaround |
To address this issue, restore the network connection to LOM1. |
Systems Affected |
All systems supported by this release. |
Tracking number |
285467 |
Table 22. RAC0508 error while uploading signed CSR certificate
Details |
|
Description |
"RAC0508 Unexpected error" may occur while uploading signed CSR certificate. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release. |
Tracking number |
299294 |
Automation — API and CLI
Table 23. Issue with POST operation for SystemErase action
Details |
|
Description |
Encountering a failure in the POST operation for DellLCService.SystemErase action when ComponentBitmap is specified in the payload, such as {"ComponentBitmap": 1}. URI: /redfish/v1/Managers/<Manager-Id>/Oem/Dell/DellLCService/Actions/DellLCService.SystemErase |
Workaround |
To address this issue, replace ComponentBitmap with Component in the payload. For example: {"Component": ["BIOS"]}. |
Systems Affected |
All systems supported by this release. |
Tracking number |
282020 |
Table 24. Drive property not displayed
Details |
|
Description |
In Redfish API, properties of some Samsung drives are displayed as unknown in the GET operation response. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release. |
Tracking number |
266130 |
Table 25. Expand query parameter issue
Details |
|
Description |
Performing a GET method on ComponentIntegrity instance with Expand query parameter may fail to expand some of properties or links. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release. |
Tracking number |
263837/272326 |
Table 26. Server reboots while applying device firmware update
Details |
|
Description |
While applying firmware update through Redfish interface for a device that does not require a reboot for the update, setting @Redfish.OperationApplyTime property to Immediate in the request body may cause the server to reboot. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release |
Tracking number |
233764 |
Table 27. GET method on Port collection returning incorrect information
Details |
|
Description |
GET method on the Ports collection URI with a filter query parameter that includes "ne" operator returns incorrect details. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release |
Tracking number |
261094 |
Table 28. Redfish Validator error
Details |
|
Description |
Running schema validator to check schema conformance may display an error about NetworkAttributeRegistry instance that the JSON does not match the required URIs in Schema of AttributeRegistry. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release |
Tracking number |
268459 |
Table 29. RLCE reports Incorrect value for fan sensor
Details |
|
Description |
Redfish Life Cycle Events may report incorrect data for fan sensor URI after a hot pluggable fan is removed. |
Workaround |
Restart the host system. |
Systems Affected |
All systems supported by this release. |
Tracking number |
193777 |
Table 30. Service Validator reporting errors for Redfish API services
Details |
|
Description |
To continue support firmware backward compatible, you may get errors for Redfish API services in the Service Validator. They do not have any functional impact on the system and may be ignored. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release. |
Tracking number |
183321 |
Table 31. Performing GET with Top query parameter returns no error
Details |
|
Description |
Top query on a Parity URI instance returns complete response instead of an error code. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release. |
Tracking number |
175801 |
Table 32. Uploaded firmware link not available in SoftwareImages property
Details |
|
Description |
While performing GET method on BIOS or Manager Schema through Redfish, the SoftwareImages property may not display the uploaded firmware link. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release. |
Tracking number |
156737 |
Table 33. Attributes for CNA cards not displayed through Redfish or RACADM interface
Details |
|
Description |
If the partitions are disabled on FCoE capable CNA cards, few Hll attributes values for WWN, VirtWWN, WWPN, VirtWWPN are displayed in the iDRAC GUI's Network page. However, the same data is not displayed when Get commands are performed in Redfish and RACADM interfaces. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release. |
Tracking number |
151560 |
Storage
Table 34. Unable to create a recurring job after same job was completed
Details |
|
Description |
Creating a recurring job will fail if the same job was completed recently and its Task ID still exists. |
Workaround |
Wait for ten minutes for the Task ID to be deleted. |
Systems Affected |
All systems supported by this release. |
Tracking number |
147501 |
Table 35. Get operation not displaying model or serial number for PCIe devices
Details |
|
Description |
If you perform a Get operation for a PCIe device using Redfish API, the response may not display the model and serial number of the device. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release. |
Tracking number |
111564 |
Table 36. Abnormal display of storage status page in iDRAC GUI
Details |
|
Description |
The Storage status page is observed to exhibit abnormal behavior in the iDRAC GUI when configured with C2-9 settings. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release with front and rear backplanes containing various drive form factors. |
Tracking number |
279637 |
Table 37. Drive slots empty
Details |
|
Description |
Following an enclosure firmware update, the iDRAC indicates that the drive slots associated with the enclosure's physical disks appear empty. |
Workaround |
Perform an iDRAC reset. |
Systems Affected |
All systems that supported by this release with PowerVault MD 2412 or PowerVault MD 2424, or PowerVault MD 2460 connected through HBA 355e. |
Tracking number |
273389 |
Table 38. Crypto erase job failure in KIOXIA CM6 FIPs drive
Details |
|
Description |
The Crypto Erase job failing in the KIOXIA CM6 FIPs drive, and as a result, the drive remains secured. The operation encountered an error with the code TCGR_METHOD_NOT_AUTHORIZED. |
Workaround |
Replace the drive. |
Systems Affected |
All systems supported by this release with KIOXIA CM6 FIPs drive. |
Tracking number |
262524 |
Table 39. Disk conversion job failure
Details |
|
Description |
The iDRAC GUI's Storage page may erroneously permit the creation of a job to convert a locked SED drive from 'Ready' to 'Non-Raid' status, despite this action not being supported. The created job fails without offering any specific reason for the failure. |
Workaround |
N/A |
Systems Affected |
All systems supported by this release. |
Tracking number |
271620 |
Table 40. 254 Drive Slots Displayed in PowerVault MD2412
Details |
|
Description |
An issue has been noticed where 254 drive slots are displayed in the PowerVault MD 2412 Enclosure's slot details instead of 12. |
Workaround |
Perform an iDRAC reset. |
Systems Affected |
All systems supported by this release configured with PowerVault MD 2412 Enclosure. |
Tracking number |
277676 |
Table 41. Errors in SCP Import Job
Details |
|
Description |
During the SCP import job, errors are encountered when attempting to erase drives and disable controller security. |
Workaround |
Disable Boss security through alternative interfaces such as RACADM, IDRAC GUI, or Redfish API, and then retry the import. |
Systems Affected |
All systems supported by this release and with BOSS configurations. |
Tracking number |
277805 |
Table 42. Issue creating a VD by iDRAC GUI advanced configuration
Details |
|
Description |
Unable to create the VD from iDRAC GUI using Advanced Configuration. |
Workaround |
Use the RACADM interface or Redfish API, or the basic option in iDRAC GUI to create the VD. |
Systems Affected |
All systems supporting by this release that have JBODs with 4U60 configurations and maximum physical disks. |
Tracking number |
278458 |
Table 43. Intermittent absence of controller driver version
Details |
|
Description |
The Controller Driver version may not be displayed in the iDRAC GUI Storage tab after a host reboot. |
Workaround |
A cold or warm reboot is recommended. |
Systems Affected |
All systems supporting by this release. |
Tracking number |
278645 |
Miscellaneous
Table 57. PSU Type issue
Details |
|
Description |
Servers equipped with 1400W power supply units (PSUs) of distinct hardware revisions, such as A01 and A02, exhibit a disparity in the iDRAC GUI. Specifically, the A02 PSU is presented as AC Type, while the A01 is indicated as DC Type. |
Workaround |
Use PSUs of the same A02 version. |
Systems Affected |
All systems supported by this release. |
Tracking number |
281279 |
Table 58. Server host powering off following PSU part replacement update
Details |
|
Description |
When using NFS/HTTP/HTTPS shares, the mapping of .IMG images though RFS in "Read-Write" mode is encountering issues. |
Workaround |
Perform an iDRAC reset and power on the host. |
Systems Affected |
All system supported by this release with AMD chipset. |
Tracking number |
277484 |
Table 59. BBU update issue
Details |
|
Description |
When scheduling a Battery Backup Unit (BBU) firmware update concurrently with other updates, such as a BIOS update, the system may be held in an S5 state, preventing the host from powering on and initiating the update jobs. |
Workaround |
Perform the BBU firmware update as a standalone operation and avoid combining or scheduling it with any other firmware updates. |
Systems Affected |
All systems supported by this release with BBU. |
Tracking number |
275222 |
Table 60. Failure in mapping images through RFS
Details |
|
Description |
When using NFS/HTTP/HTTPS shares, the mapping of .IMG images though RFS in "Read-Write" mode is encountering issues. |
Workaround |
Either use a CIFS share or opt for a lower version of NFS/HTTPS share to connect .IMG files using RFS in Read-Write mode. Note that, NFS version 4.1 and HTTPS with IIS version 10.0 for Windows are known to work for connecting .IMG files in Read-Write mode. |
Systems Affected |
All systems supported by this release. |
Tracking number |
277169 |
Table 61. VMAC reapplication issue after network card and BIOS updates
Details |
|
Description |
The VMAC fails to be reapplied following updates to the network card and BIOS. |
Workaround |
Perform the following:
For systems not in a failed state:
1. Run the command racadm set iDRAC.PCIeVDM.Enable disabled.
2. Perform a cold boot.
3. Proceed with the required BIOS/NIC firmware upgrades.
For systems already in a failed state (i.e., without the PCIeVDM disabled-triggered firmware upgrade):
1. Run the command racadm set iDRAC.PCIeVDM.Enable disabled.
2. Perform a cold boot.
3. Once again, perform a cold boot. |
Systems Affected |
All systems supported by this release. |
Tracking number |
278034 |
Table 62. Rebootless firmware fails through SCP
Details |
|
Description |
Performing rebootless firmware update using SCP import may fail with the SCP import file that also includes updates for other configurations that require a host reboot. |
Workaround |
Retry the operation with an SCP Import file that only includes the firmware update changes. |
Systems Affected |
All systems supported by this release. |
Tracking number |
270392 |
Table 63. Firmware update through iDRAC Group Manager failing
Details |
|
Description |
iDRAC firmware update for Identity Module installed systems from iDRAC Group Manager fails with an error "Firmware is invalid for this platform". |
Workaround |
Use other iDRAC interfaces to update the firmware. |
Systems Affected |
All systems supported by this release. |
Tracking number |
274746 |
Table 64. Few Virtual Keyboard keys not working for other languages
Details |
|
Description |
Some keys or key combination may not provide the correct output for languages other than English. |
Workaround |
Use the physical keyboard or Windows On-Screen Keyboard. |
Systems Affected |
All systems supported by this release. |
Tracking number |
181505 |
Important notes
Authentication
- Ensure that you use digest authentication for HTTP/HTTPs share for all iDRAC and LC features, basic authentication is no longer supported and is blocked by iDRAC due to security risks.
- 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.
BIOS and UEFI
- 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.
- If the BIOS date and time are set incorrectly while resetting iDRAC to default settings, the iDRAC's IP address may be lost. Reset iDRAC or AC power cycling the server to recover iDRAC IP.
iDRAC firmware
- In iDRAC, attaching a folder that is in an NFS share hosted by a Linux-based operating system is not supported.
- In Lifecycle (LC) interface, It is recommended to avoid performing any operations on media that is mounted as RFS through iDRAC GUI/RACADM/Redfish.
- Updating iDRAC firmware to version 6.xx or later changes the static IPv4 or IPv6 DNS settings. Ensure that you reconfigure the network settings after the upgrade is complete.
- Firmware update using an FTP fails if the HTTP proxy is used without any authentication. Ensure that you change the proxy configuration to allow the CONNECT method to use non-SSL ports. For example, while using a squid proxy, remove the line "http_access deny CONNECT !SSL_ports" that restricts from using the CONNECT method on non-SSL ports.
- To apply a firmware update that is scheduled and awaiting a host reboot, ensure that you perform a cold reboot instead of a warm reboot.
- For catalog updates through downloads.dell.com, adding catalog location or name is not required. Adding downloads.dell.com as HTTPS Address enables iDRAC to find the appropriate catalog file.
- If Lifecycle controller logs display RED057 message during a component update, then run the command systemerase Icdata through RACADM interface and then retry the operation.
- While performing a PSU firmware update through the host OS in the 15 th or later Generations of PowerEdge servers, ensure that you perform a cold reboot to apply the update.
- During OS deployment through SCP, if the SCP configuration file includes the attribute "OSD.1#AnswerFileName" then a virtual USB device OEMDRV is attached to the server that contains the file with responses for an unattended OS installation. This device will be available for the duration as specified in the optional attribute "OSD.1#ExposeDuration" in the template and if the attribute is not specified, it remains attached for about 18 hours. After the OS installation is complete, detaching the ISO and the driver pack also unmounts the OEMDRV device.
- Before updating PSU firmware on PowerEdge C series systems, ensure that all the blades are powered off in the chassis first. If any of the blades are powered on, the PSU firmware update process may fail, and Lifecycle Controller (LC) logs report the failure.
- Adding an iDRAC system with firmware version 4.4x or later to a group manager of systems with iDRAC versions earlier than 3.xx, 4.0x, 4.1x, 4.2x, or 4.3x is not supported. Ensure that all the systems have the latest iDRAC firmware version 4.4x or any later versions.
- While performing a firmware update or rollback through LifeCycle controller(LC) GUI, the component information displayed in the table listing the available updates may be truncated if it exceeds the table column or row width.
- 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.
- 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.
- After updating the iDRAC license to Data Center license, ensure that you reboot the iDRAC for Idle server detection feature related attributes to function.
- In LifeCycle Controller GUI, use the mouse to browse files or folders. Browsing files using keyboard is not supported.
- iDRAC GUI search output points to a GUI page where the search keywords are missing within the page. These are typical false positives like any other search engine that may be ignored.
- If a single DUP is used to update firmware for multiple devices, and if any update fails then the firmware for the subsequent cards may display an incorrect version. Update the firmware for all the failed devices again.
- When node initiated discovery or Group Manager is enabled, iDRAC uses mDNS to communicate through port 5353. Turn off the Group Manager and node initiated discovery to disable mDNS.
- After iDRAC is upgraded to version 4.xx or later, you may stop receiving encrypted email alerts from iDRAC, if the external email server does not support encryption. iDRAC firmware version 4.xx or later includes a user-selectable encryption option and the default protocol is StartTLS. To start receiving email messages again, disable the email encryption by using the following RACADM command: racadm set idrac.RemoteHosts.ConnectionEncryption None
- 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
- 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:
- You cannot update any DUP.
- LC cannot involve CSIOR.
However, if a server AC power cycle or iDRAC reboot is performed, the OEMDRV drive is automatically detached.
- 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.
- Firmware rollback is not supported for CPLD, NVDIMM, SAS/SATA drives, and PSU (on modular systems).
- 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.
- 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.
Environmental and system requirements
License Requirements
iDRAC features are available based on the purchased license.
- iDRAC Express—Available by default on all blade servers, and rack or tower servers of 600 or higher series
- iDRAC Enterprise-Available on all servers as an upgrade
- iDRAC Datacenter-Available on all servers as an upgrade.
- iDRAC Secure Enterprise Key Manager(SEKM)—Available on all servers as an upgrade.
NOTE: IDRAC Secure Enterprise Key Manager(SEKM) with PERC is not supported on MX series blade servers.
NOTE: BMC - Available only on Dell PowerEdge C series servers.
For more information about the features available for a license, see the iDRAC licenses section in the iDRAC User's Guide available at dell.com/idracmanuals.
NOTE: To manage new and existing licenses, go to the Dell Digital Locker.
Supported systems
Table 65. Supported systems
14th Generation of PowerEdge Servers |
PowerEdge C4140 |
PowerEdge C6420 |
PowerEdge FC640 |
PowerEdge M640 |
PowerEdge M640 (for PE VRTX) |
PowerEdge MX740c |
PowerEdge MX840c |
PowerEdge MX7000 |
PowerEdge R240 |
PowerEdge R340 |
PowerEdge R440 |
PowerEdge R540 |
PowerEdge R640 |
PowerEdge R740 |
PowerEdge R740xd |
PowerEdge R740xd2 |
PowerEdge R840 |
PowerEdge R940 |
PowerEdge R940xa |
PowerEdge R6415 |
PowerEdge R7415 |
PowerEdge R7425 |
PowerEdge T40 |
PowerEdge T140 |
PowerEdge T340 |
PowerEdge T440 |
PowerEdge T640 |
PowerEdge XE7420 |
PowerEdge XE7440 |
PowerEdge XR2 |
Dell EMC XC Core XC940 System |
Dell EMC XC Series XC940 Appliance |
Precision 7920 Rack |
Precision 7920 XL Rack |
Supported managed server operating systems and hypervisors
- Microsoft Windows
- Server 2022 Standard
- Server 2022 Datacenter
- Server 2019 Standard (Downgrade only)
- Server 2019 Datacenter (Downgrade only)
- WinPE 5.0 64-bit
- WinPE 10
- Microsoft Azure Stack HCI v2 and v3
- Linux
- RHEL 9.1 and RT
- RHEL 8.7 and RT
- SLES
- Ubuntu
- VMware
Supported web browsers
- Microsoft EDGE
- Safari 15.4
- Mozilla Firefox 121
- Mozilla Firefox 120
- Google Chrome 116
- Google Chrome 115
Supported software
Java
OpenSource tools
- OpenJDK 8u202
- Adopt Open JDK
- You may utilize an open source version of AdoptOpenJDK or OpenJDK (“Adopt Open JDK”) subject to the terms and conditions of the Adopt Open JDK community at the link below.
- You use Adopt Open JDK at your own risk. Adopt Open JDK may not meet your requirements or expectations. It could include quality, technical or other mistakes, inaccuracies or typographical errors.
- Dell does not provide support or maintenance for Adopt Open JDK.
- Dell makes no express warranties, and disclaims all implied warranties, including merchantability, fitness for a particular purpose, title, and non-infringement as well as any warranty arising by statute, operation of law, course of dealing or performance or usage of trade regarding Adopt Open JDK.
- Dell has no liability to you for any damage that arise out of or relate to your use of Adopt Open JDK.
iDRAC Service Module (iSM)
iSM version 5.1.0.0 or later
iDRAC tools
This version of iDRAC requires the following tools based on the operating system:
- Dell iDRAC Tools for Microsoft Windows Server(R), v11.1.0.0
- Dell iDRAC Tools for Linux, v11.1.0.0
- Dell iDRAC Tools for VMware ESXi (R), v11.1.0.0
This version contains:
- Remote/Local RACADM on Windows or Linux or ESXi
- IPMI Tool on Windows or Linux
Download the DRAC tools from the Drivers & downloads page for your system at Dell Support page.
Before installing iDRAC tools from OM 9.5.0, you must uninstall any older versions of DRAC tools. For more information about uninstalling applications, see the documentation for your operating system.
Secured Component Verification (SCV)
SCV version 1.8
Supported Key Management Server (KMS) for Secured Enterprise Key Manager (SEKM)
- Cipher Trust Manager version 2.11.1
- IBM Security Guardium Key Lifecycle Manager version 4.1.1.0
- Utimaco Enterprise Secure Key Manager version 8.4.0
- KeySecure Classic version 8.12.5
- Thales Data Security Manager (DSM) version 6.4.9
Installation and upgrade considerations
Downloading iDRAC firmware installation file
NOTE: For information about updating iDRAC firmware using various interfaces, see the iDRAC User's Guide available at iDRAC Manuals.
- Go to Dell Support page.
- In the Enter a Service Tag, Serial Number... field, type the Service Tag or the model number of your server, and press Enter or click the search icon.
- On the product support page, click Drivers & downloads.
- Select the appropriate operating system.
- From the list, locate the iDRAC entry and click the download icon.
Updating iDRAC firmware from host OS
From the host operating system, execute the installation package that you downloaded and follow the instructions of the update wizard.
For more information about opening executable files on your system, see the operating system's documentation.
Updating iDRAC remotely using iDRAC web interface
You can remotely update the firmware from the management stations using the iDRAC web interface.
- Extract the self-extracting installation package to the management station.
- Access the iDRAC web interface using a supported web browser.
- Log in as an administrator.
- Click Maintenance > System Update.
The Manual Update page is displayed.
- Select Local to upload the firmware image from the local system.
- Click Browse, select the .d9 file that you extracted or the Dell Update Package for Windows, and click Upload.
- Wait for the upload to complete. After the upload is complete, the Update Details section displays the uploaded file and the status.
- Select the firmware file and click Install. The message RAC0603: Updating Job Queue is displayed.
- To view the status of the firmware update, click Job Queue. After the update is complete, iDRAC restarts automatically.
Resources and support
For more information about the features of this release, see the documentation for iDRAC 7.xx.
Latest Release Notes
To access the latest Release Notes for this version of iDRAC:
- Go to iDRAC manuals page.
- Click the link for the generation and then click the firmware series of iDRAC.
- Click DOCUMENTATION.
- Click MANUALS AND DOCUMENTS.
Accessing documents using direct links
You can directly access the documents using the following links:
Table 66. Direct links for documents
URL |
Product |
iDRAC Manuals |
iDRAC and Lifecycle Controller |
CMC Manuals |
Chassis Management Controller (CMC) |
ESM Manuals |
Enterprise System Management |
Software Serviceability Tools |
Serviceability Tools |
Client System Management Manuals |
Client System Management |
Accessing documents using the product search
- Go to Dell Technologies Support site.
- In the Enter a Service Tag, Serial Number... search box, type the product name. For example, PowerEdge or iDRAC. A list of matching products is displayed.
- Select your product and click the search icon or press enter.
- Click DOCUMENTATION.
- Click MANUALS AND DOCUMENTS.
Accessing documents using product selector
You can also access documents by selecting your product.
- Go to Dell Technologies Support site.
- Click Browse all products.
- Click the desired product category, such as Servers, Software, Storage, and so on.
- Click the desired product and then click the desired version if applicable.
NOTE: For some products, you may need to navigate through the subcategories.
- Click DOCUMENTATION.
- Click MANUALS AND DOCUMENTS.
Lifecycle Controller (LC) Remote Services — client tools
Redfish API
For information about Redfish, see the DMTF website DMTF Redfish. This website provides access to schema files, white papers, technical notes, and so on.
For iDRAC Redfish API guide, go to Dell Developer Portal.
IDRAC SNMP MIB Files
The iDRAC SNMP MIB files are now available for download along with the iDRAC firmware and can be accessed on the Dell Support page. To download the files:
- Go to Dell Support page.
- In the Enter a Service Tag, Serial Number... field, type the Service Tag or the model number of your server, and press Enter or click the search icon.
- On the product support page, click Drivers & downloads.
- From the list, locate the iDRAC entry and click the iDRAC firmware version to expand for more information.
- Click View full driver details.
- Locate the iDRAC MIB file and click Download.
Where to get help
The Dell Technologies Support site contains important information about products and services including drivers, installation packages, product documentation, knowledge base articles, and advisories.
A valid support contract and account might be required to access all the available information about a specific Dell Technologies product or service.