iDRAC9 Version 7.10.70.00 Release Notes

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.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.30.00
• 7.00.60.00
• 7.10.30.00
• 7.10.50.00

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:

1. Go to Dell Support page.
2. 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.
3. On the product support page, click Drivers & downloads.
4. 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

September 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 Dell PowerEdge 15th and 16th generation servers. This release does not support Dell PowerEdge 14th (14G) generation servers. The last release that supported 14G servers is iDRAC9 version 7.00.00.173.

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

iDRAC firmware

• Support for Universal Base Board (UBB) FRU.
• Support for AMD MI300X GPU FRU.
• Enhanced manual catalog updates with Additional Filter Options, Apply Same Version and Apply Downgrade Versions.

NOTE: When either or both parameters are selected, the highest firmware version available in the repository is listed or applied.

Automation — API and CLI

• Support to crypto-erase all drives in a single action through a Redfish API for drives under BOSS-N1 controller.

Monitoring and alerting

• Added Alert Liquid Cooling System Default Action Power Off, which facilitates a graceful shutdown if a GPU liquid leak is detected.
• Improved machine check errors and CPU messages.

Security

• Support for SNMPv3 with AES-256.

Deprecated features

The following table displays the features that are listed as deprecated*, Removed**, and To be 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

• 307277/296749: Resolved issue where server status was incorrectly displayed as "Not ready" while the server was in an idle state.
• 292698: Fixed an issue where iDRAC erroneously reported duplicate ports.

Networking and I/O

• 289309: Resolved the issue where the Fibre Channel over Ethernet (FCOE) attributes reported by iDRAC were incorrect.
• 295565: Fixed an issue where iDRAC incorrectly displayed either the NIC or InfiniBand device based on the mode selected, leading to a misrepresentation of the network configuration.

Security

• 296775: Resolved issue where two-factor authentication (TFA) failed when the user certificate path exceeded two levels.

Monitoring and alerting

• 289725: Resolved the discrepancy in the "DeviceNumber" and "FunctionNumber" values between the Network device and PCI network device on the iDRAC Hardware Inventory page.
• 291869: Resolved the issue of HWC9053 (device communication lost) and HWC9054 (device communication issue resolved) events reported in LC logs when initiating warm boot cycles with intervals of less than four minutes.
• 292617: Resolved the issue where a Drive insertion log (PDR1000) was observed for all 36 drives in the Lifecycle (LC) logs and SEL, after an iDRAC update.
• 294454: Resolved the issue where a critical leak detected on LSC_SIG5 was incorrectly indicated as multiple leaks in the SEL log instead of specifying the LSC_SIG5 cable.
• 294652: Resolved the issue where servers with older SCV certificates display a profile version mismatch as an overall mismatch when performing Secure Component Verification (SCV) with the latest firmware, despite matching inventory.
• 292106, 294267, 294279: The issue where certain attributes for sensors that are related to CPU, Fan, or GPU were either absent or duplicated in the iDRAC GUI under the System page, is resolved.
• 295922: Resolved an issue where the HealthRollupStatus would incorrectly show as critical when the PowerEdge R750 server is powered off.
• 297567/290922: Fixed an issue where the Lifecycle Controller (LC) logs displayed the message "The iDRAC firmware was rebooted with the following reason: watchdog." This was also occasionally observed during server reboot failures.

Storage

• 293863: The issue causing an enclosure-connector position mismatch during a cold or warm boot on a system experiencing an EMM failure is resolved.
• 282234: Fixed the issue that was causing the BOSS security configuration job to encounter a failure when the system is under stress.

Miscellaneous

• 292136: Fixed the issue where performing multiple Battery Backup Units (BBU) firmware rollbacks only applied the rollback process to one BBU.
• 288896: Fixed the issue where combining staged and direct updates in the same SCP catalog import that resulted in staged jobs that failed to update.
• 298771: The issue causing errors in the process of exporting GPU debug log in the Technical Support Report (TSR) has been resolved.
• 286001: Resolved the issue that caused the AMD GPU firmware updates to fail, resulting in the iDRAC showing firmware versions as 00.00.00.00 on the iDRAC firmware inventory page.
• 277169: Fixed the issue with mapping .IMG images through RFS in "Read-Write" mode when using NFS/HTTP/HTTPS shares.
• 294394: Resolved an issue where AC power recovery failed to power the sleds back on after an AC power loss.
• 285650: Resolved an issue where applying the same SCP template to multiple servers through the iDRAC GUI resulted in inconsistent outcomes. Despite identical hardware and firmware versions, the Lifecycle Controller displayed SYS033 and SYS035 messages without showing any failures or errors.

Known issues

iDRAC firmware

Networking and IO

Storage

Automation — API and CLI

Monitoring and alerting

Miscellaneous

Important notes

Authentication

1. 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.
2. 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

1. 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.
2. 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

1. The software inventory for Chassis Manager (CM) firmware is available on all SLEDs, allowing updates to be initiated from any SLED. However, if a CM update is started from one SLED, any attempt to initiate another CM update from a different SLED fails, indicating that an update is already in progress.
2. If attributes that need a staged job for modification are changed using a Server Configuration Profile (SCP) import while the host is in power off state, a manual server reboot is necessary to finalize the attribute update. Additionally, to perform a compliance check using the OpenManage Enterprise (OME) template, ensure that the system is powered on before initiating the check.
3. In iDRAC, attaching a folder that is in an NFS share hosted by a Linux-based operating system is not supported.
4. In Lifecycle (LC) interface, It is recommended to avoid performing any operations on media that is mounted as RFS through ¡DRAC GUI/RACADM/Redfish.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. During OS deployment from LCUI, unmounting OEMDRV through the LC UI or Host OS is not supported. To unmount OEMDRV, either exit LCUI (F10) or wait for automatic unmounting after 18 hours.
13. 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.
14. 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.
15. 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.
16. 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.
17. 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.
18. After updating the iDRAC license to Data Center license, ensure that you reboot the iDRAC for Idle server detection feature related attributes to function.
19. In LifeCycle Controller GUI, use the mouse to browse files or folders. Browsing files using keyboard is not supported.
20. 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.
21. 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.
22. 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.
23. 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
24. 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
25. 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.
26. 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.
27. Firmware rollback is not supported for CPLD, NVDIMM, SAS/SATA drives, and PSU (on modular systems).
28. 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.
29. When you get an error while performing SupportAssist collection through RACADM using HTTPS share, use the following commands to perform the collection: a. Racadm SupportAssist collect. b. Racadm SupportAssist exportlastcollection
30. When upgrading iDRAC firmware from a version earlier than 7.10.70.00, ensure to delete the old PowerMetric MetricReportDefinition (MRD) using DELETE method on the URI (/redfish/v1/TelemetryService/MetricReportDefinitions/PowerMetrics) or perform a racadm racresetcfg to update the PowerMetrics MRD.
31. Telemetry service may experience a brief disruption (up to 60 s) during a server host reboot, whether initiated manually or as part of a device firmware update.
32. In LC GUI, the checkbox for Telemetry Reports in SupportAssist remains active and is not disabled even when the Telemetry Data Stream is turned off.
33. Updating "Tpm2Algorithm" and "inteltxt" attributes through a single job is not supported using RACADM interface. Either update the Tpm2Algorithm and then update inteltxt through separate jobs or use the Server Configuration Profile (SCP) to update both the attributes in a single job.
34. The display of Intel IPU card's PartNumber and SerialNumber in the PCIeDevice instance URI may vary with Redfish, as Redfish interface does not support this card.
35. A compliance error in the Bios AttributeRegistry is flagged due to a deviation from the schema to accommodate Value Level dependencies of BIOS attributes in the implementation. This can be disregarded as there is no impact on functionality.
36. For Redfish OEM actions ExportLCLog and ExportHWInventory, the final job status message is not consistent across all supported network share protocols. When using NFS or CIFS share, final job status message is " was successful" and while using HTTP or HTTPS, final job status message is "The command was successful". To view what operation was performed, see the JobType property in the job ID JSON output results.
37. For Telemetry reports, if the RecurrenceInterval is set to a value lower than the metric SensingInterval a few extra reports may be generated when no data is available at the source. Ensure that RecurrenceInterval is greater than and a multiple of SensingInterval.
38. During an iDRAC stress test, if the number of user sessions exceed eight, then iDRAC may display unexpected failures for Redfish operations.
39. Values for some properties may not reflect the same across different iDRAC interfaces, as there can be a delay in data refresh.
40. If you get 400 status code while performing Redfish MultipartUpload for firmware updates, wait for five minutes and retry the operation again.
41. When streaming alerts using Remote Syslog or Redfish event listener, not every message ID/message gets streamed. To confirm which message ID/messages can be streamed, see the EEMI guide.
42. While accessing iDRAC GUI and Redfish through the same browser, if the webserver times out, then RedfishService may prompt you to enter the login credentials to create a session. Select Cancel to clear the Redfish login prompt and proceed to the iDRAC login page.

Monitoring and alerting

1. Optimizing fan control algorithms to reduce system power consumption may increase GPU temperatures. This change maintains GPU performance across both maximum performance and minimum power thermal profiles.
2. When an older version of iDRAC firmware (older than version 7.10.30.00) is installed on the PowerEdge 16G XR series servers, then an error message is observed in the iDRAC Lifecycle (LC) log stating "HWC8010 - The System Configuration Check operation resulted in the following issue: Config Error: Sig Pwr Cable 0".
3. SCV validation is not supported when accessing the iDRAC GUI over HTTP. Ensure that the HTTPS protocol is used for logging into the iDRAC GUI to enable SCV validation.
4. During continuous reboot cycles, SYS336 may occasionally appear in the Lifecycle (LC) logs. This is merely an informational entry and does not affect functionality.
5. The reporting format in SCV application version 1.92 has undergone a redesign. The iDRAC GUI reporting format is in alignment with SCV application version 1.91. Therefore, there may be variations in comparisons between SCV application reporting and iDRAC GUI.
6. When servers with SPDM-enabled components undergo an AC power cycle stress or a host reboot stress (cold or warm boot), the LC logs may show errors related to SPDM export issues. To address this, it is recommended to incorporate appropriate time intervals between consecutive power cycles. The time required for iDRAC readiness may differ based on the server configuration. The objective of these necessary time gaps is to ensure the full functionality of iDRAC and the completion of the Secured Component Verification (SCV) inventory before commencing the next stress cycle.

Networking and IO

1. When bifurcation is disabled (set to platform default) for a NIC devices in the PCI slot, the PCI lanes allocated to the device will display as x16 instead of x4.
2. In the iDRAC GUI, NVIDIA BlueField-3 DPUs that are configured in InfiniBand (IB) mode, are classified under the NIC Devices and InfiniBand Devices.
3. During a DPU (Smart NIC) firmware update, SUP0516 message about firmware update is logged in Lifecycle (LC) Logs before the system restart log (SYS1000). The actual firmware update is applied at Post while the host system is powering on.
4. Firmware version for DPU cards on iDRAC Overview page (Network Devices section) may vary with the version that is displayed on the Firmware Inventory page. Use the version that is displayed on the Firmware Inventory page.
5. iDRAC may display some unsupported attributes such as PCleOfflineOnlineFQDDList, SerialNumber, PermanentMACAddress, CSP Mode and DPUOSDeployment TaskState for DPUs when GET is performed on the iDRAC attribute registry. These attributes are expected to be removed from the iDRAC code in an upcoming release.
6. iDRAC IPv6 auto-generated addresses change to stable-privacy assigned addressing when iDRAC is upgraded to firmware version 5.10.00.00 (or later) from any previous iDRAC versions.
7. In a SCP import job for enabling NPAR on a network port, if all partitions are not required then ensure that you apply the SCP import twice. Once to enable the NPAR on the port and the second time to disable the partitions that are not required.
8. For partition enabled COMMs adapter, a PR6 Lifecycle Log message may be displayed as partition-1 even though the values are configured as other than first partition.
9. When auto negotiation is disabled while iDRAC is 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.
10. In systems with network adapters without internal temperature sensors, for some adapters the NIC temperature sensors metric value is reported as 0.
11. After iDRAC is upgraded to versions 4.xx or later for the first time, there may be a change in network settings option including IPv4 and IPv6. Reconfigure the network settings to resolve this.
12. 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.
13. 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.
14. 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.
15. If SMBv2 share fails in Lifecycle GUI, ensure that: The Digitally sign communications option is disabled. Permissions to access the folder or file is granted. folder/file name does not have a space. Share contains fewer files and folders.
16. While iDRAC is initializing, all communications with iDRAC may fail. For any service requests, wait until the initialization process is complete.
17. In iDRAC, if there is no link that is detected in the selected iDRAC port then the iDRAC IP is displayed as 0.0.0.0.
18. FRU objects or properties for Network adapters that are embedded on the motherboard are not available through any of the iDRAC interfaces.
19. The iDRAC feature “Topology LLDP” is not supported on 1 GbE controllers and on selected 10 GbE controllers (Intel X520, QLogic 578xx).

OS deployment

1. Operating system installation fails when the OS media volume name (label) is blank. Recommendation is to add a valid volume name for OS media (USB drive, DVD, and so on) before starting the OS installation.
2. While installing an operating system, a media verification warning message may be displayed. This has no impact on the installation, to proceed, click Yes.
3. Windows operating system deployment may intermittently fail with the following error message: A required CD/DVD drive device driver is missing. If you have a driver floppy disk, CD, DVD, or USB drive, please insert it now. Reboot to LC and retry until the operating system is successfully deployed.
4. Deployment of Windows Server operating systems (OS) using LC may fail with one of the following messages: Windows installation cannot continue because a required driver could not be installed Product key required Windows cannot find the software license terms This issue occurs when the Windows setup copies the driver to the scratch space (X: drive) and the scratch space becomes full. To resolve this issue, do any of the following: Remove all the installed add-on devices before starting the OS installation. After the OS installation is complete, connect the add-on devices, and manually install the remaining drivers using Dell Update Packages (DUPs). To avoid physically removing the hardware, disable the PCIe slots in the BIOS. Increase scratch space size beyond 32 MB using DISM set-scratchspace command when creating customized deployment. For more details, see Microsoft's documentation.
5. LC may display multiple drive names for some CDs or DVDs, such as the ones containing operating systems.
6. If the operating system (OS) selected for installation and the OS on the media used are different, LC displays a warning message. However, while installing Windows OS, the warning message is displayed only when the bit count (x86 or x64) of the OS does not match. For example, if Windows Server 2008 x64 is selected for installation and Windows Server 2008 x86 media is used, the warning is displayed.
7. In Windows10, HTML5 plug-in does not support Virtual media connection on the following versions of Edge browsers: a. Microsoft Edge 44.17763.1.0 b. Microsoft EdgeHTML 18.17763

Security

1. Cryptographic Erase operation is not supported for hot-plugged NVMe disks. Cold reboot (power cycle) the server before starting the operation. If the operation continues to fail, ensure that CSIOR is enabled and that the NVMe disk is qualified by Dell.
2. iDRAC9 does not support Personal Identity Verification (PIV) or Common Access Card (CAC) smart card users on a child or subdomain in a forest or collection of domains. To overcome this limitation, it is recommended to deploy all smart card users on the root domain instead of the child domains within the forest.

Storage

1. iDRAC interfaces do not support slicing RAID volumes through software RAID controllers. To configure sliced RAID volumes, use F2 Device settings.
2. Part number for Predictive failure message "PDR16" for NVMe drive may appear as "Not Available" immediately after the cold reboot. Allow some time after the cold reboot for iDRAC to initialize the inventory.
3. While renaming a virtual disk (VD), using a . (period) is not allowed in the VD name.
4. If your system has a PERC card configured in Enhanced HBA mode and you downgrade iDRAC to an older version, the SET commands for storage configuration may fail. To resolve the issue, ensure that a Collect System Inventory On Reboot (CSIOR) is performed after the downgrade. To perform a CSIOR, use the following methods: a. Completely turn off the system and then turn it on again. b. Ensure that CSIOR is enabled before turning off the system. c. Use the following RACADM command: racadm serveraction powercycle
5. Few legacy drives do not support the SMART ID #245 "Remaining Rated Write Endurance". In such cases, iDRAC interfaces may display the "Remaining Rated Write Endurance" attribute as unavailable.
6. If a M.2 SATA drive attached to BOSS-S2 controller is removed, performing a blink operation may not fail for the removed drive.
7. The standard erase procedure for non-ISE drives is notably time-consuming, particularly for larger drives, potentially spanning hours or days, with the added risk of job failure. A workaround is to conduct the erase on each disk individually while other drives are uninstalled.

SupportAssist and parts replacement

1. Part-replacement of BOSS-S1 controller is not detected by Lifecycle Controller. After replacing the controller, follow the instructions in the controller's documentation.

Firmware and driver update

1. In PowerEdge systems with AMD configuration, if a PSU firmware update is initiated from LCUI, host goes into powered-off state and Job is Completed with status 0%. Ensure that you power on the system using any iDRAC interface to start the PSU firmware update.
2. CMC server component update does not support the iDRAC9 firmware packages. Use iDRAC GUI, RACADM interface, or OpenManage Enterprise Modular to perform any out-of-band updates of iDRAC9 firmware.
3. After an iDRAC reset or firmware update operation, the ServerPoweredOnTime—a property in RACADM and WSMan—may not be populated until the host server is restarted.
4. Some of the supported components may not be displayed on the Firmware Update > View Current Versions page. To update this list, restart the system.
5. If the iDRAC firmware update is interrupted, you may have to wait up to 30 minutes before attempting another firmware update.
6. Firmware update is supported only for LAN on Motherboards (LoM), Network Daughter Cards (NDC), and network adapters from Broadcom, QLogic, and Intel, and some of the QLogic and Emulex fiber channel cards. For the list of supported fiber channel cards, see the Lifecycle Controller User's Guide available at iDRAC Manuals.
7. After the CPLD firmware is updated on modular systems, the firmware update date is displayed as 2000-01-01 on the View Current Versions page. The update date and time is displayed according to the time zone configured on the server.
8. On some modular systems, after a firmware update, the Lifecycle Log displays the timestamp as 1999-12-31 instead of the date on which the firmware update was performed.
9. It is not recommended to perform CPLD update along with other updates. If a CPLD update is uploaded and updated along with other updates using iDRAC web interface, CPLD update completes successfully but the other updates do not take effect. To complete the iDRAC updates, reinitiate the updates.

Miscellaneous

1. When the attribute USBMux0Hmc0Lock is enabled, the iDRAC displays only limited information for GPU inventory data. Specifically, the Name, Product Name, Status, State, and Slot Number are displayed.
2. You may be unable to scroll using the keyboard. Use the mouse to scroll.
3. Due to a limitation of Google Chrome browser, HTML5 virtual console intermittently displays the following error message: Chrome ran out of memory while trying to display the webpage.
4. When accessing the iDRAC web interface for the first time using Google Chrome version 59.0, the mouse pointer may not be visible. To display the mouse pointer, refresh the page or use Google Chrome version 61.0 or later.
5. If you use the HTML5 plug-in on Chrome version 61.0 to access Virtual Console, you cannot connect to Virtual Media. To connect to Virtual Media using the HTML5 plug-in, use Chrome version 63 or later.
6. Launching Virtual Console with Java plug-in fails after the iDRAC firmware is updated. Delete the Java cache and then launch the virtual console.
7. A Serial-On-Lan (SOL) session that has been active for more than five days or multiple reboots may get terminated automatically. If the session terminates, you must reinitiate the session.
8. Due to an issue with Safari, if an ipv6 literal address is used to log into the Web GUI, Safari is not able to launch the HTML5 based vConsole. Alternative options are to use Java based vConsole, or HTML5 vConsole by using the corresponding DNS name or by using an alternate browser in Mac OS.
9. iDRAC login page does not allow password entry using Firefox browser in Ubuntu management OS.
10. iDRAC and LC features cannot access CIFS or Samba shares when only SMBv1 protocol is enabled. All iDRAC features work with SMBv2 protocol. For information on enabling SMBv2 protocol, see the documentation for your operating system.
11. In Lifecycle Controller GUI, using keyboard to browse folders and files is not supported. Use the mouse to navigate through files and folders.
12. When accessing iDRAC through a Safari web browser version 14.0.3 and later versions, if a page refresh is attempted using the browser refresh option, then the iDRAC session may get cleared and you may get redirected to the iDRAC dashboard page. To refresh the page, use the Refresh option available on the iDRAC console.

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.

• 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

Supported managed server operating systems and hypervisors

• Microsoft Windows
  • Server 2025
  • Server 2022 Standard
  • Server 2022 Datacenter
  • Server 2019 Standard (Downgrade only)
  • Server 2016 Datacenter (Downgrade only)
  • WinPE 10
  • Microsoft Azure Stack HCI 23H2
  • Microsoft Azure Stack HCI 21H2
• Linux
  • RHEL 9.4
  • RHEL 8.10
  • SLES
• VMware
  • ESXi 8.0 U3
  • ESXi 7.0 U3

Supported web browsers

• Microsoft EDGE
• Safari 16.6
• Safari 17.x
• Mozilla Firefox 128
• Mozilla Firefox 129
• Mozilla Firefox 130
• Google Chrome 137
• Google Chrome 138

Supported software

Java

• Java - Oracle version

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.

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
• Fortanix Data Security Manager version 4.23.2324

NOTE: Thales ended support and reached end-of-life for the Gemalto SafeNet KeySecure key management server (k150v) on December 31, 2023. Also, Thales discontinued the support for the Data Security Manager (DSM).

Chassis Manager and iDRAC firmware alignment

Ensuring alignment between the Chassis Manager (CM) firmware version and the iDRAC firmware version is important for optimal performance and compatibility within Dell PowerEdge C-series servers.

Mismatched firmware versions can lead to functionality issues, security vulnerabilities, and potential system instability. The following table provides a general guideline for ensuring compatibility between CMC and iDRAC firmware versions.

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.

1. Go to Dell Support page.
2. 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.
3. On the product support page, click Drivers & downloads.
4. Select the appropriate operating system.
5. 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.

1. Extract the self-extracting installation package to the management station.
2. Access the iDRAC web interface using a supported web browser.
3. Log in as an administrator.
4. Click Maintenance > System Update. The Manual Update page is displayed.
5. Select Local to upload the firmware image from the local system.
6. Click Browse, select the .d9 file that you extracted or the Dell Update Package for Windows, and click Upload.
7. Wait for the upload to complete. After the upload is complete, the Update Details section displays the uploaded file and the status.
8. Select the firmware file and click Install. The message RAC0603: Updating Job Queue is displayed.
9. 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:

1. Go to iDRAC manuals page.
2. Click the link for the generation and then click the firmware series of iDRAC.
3. Click DOCUMENTATION.
4. Click MANUALS AND DOCUMENTS.

Accessing documents using direct links

You can directly access the documents using the following links:

Accessing documents using the product search

1. Go to Dell Technologies Support site.
2. 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.
3. Select your product and click the search icon or press enter.
4. Click DOCUMENTATION.
5. Click MANUALS AND DOCUMENTS.

Accessing documents using product selector

You can also access documents by selecting your product.

1. Go to Dell Technologies Support site.
2. Click Browse all products.
3. Click the desired product category, such as Servers, Software, Storage, and so on.
4. Click the desired product and then click the desired version if applicable.

   NOTE: For some products, you may need to navigate through the subcategories.

5. Click DOCUMENTATION.
6. 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:

1. Go to Dell Support page.
2. 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.
3. On the product support page, click Drivers & downloads.
4. From the list, locate the iDRAC entry and click the iDRAC firmware version to expand for more information.
5. Click View full driver details.
6. 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.

Notes, cautions, and warnings

NOTE: A NOTE indicates important information that helps you make better use of your product.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.