iDRAC9 Version 7.00.00.172 Release Notes
This release includes fixes and enhancements that improve iDRAC stability.
Current Release Version: 7.00.00.172
Previous Release Version: 7.00.00.171
Release Type: Minor (MI)
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
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: June 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
Security
- Support for virtual media certificate validation.
- Support for certificate validation for iDRAC as client.
Deprecated features
The following table displays the features that are listed as deprecated*, Removed**, and To be Removed***:
Table 1. Deprecated FeaturesFeatures | 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 |
NOTE: Alternatively, use the Server Configuration Profiles (SCP) feature to import or export server configuration settings and firmware updates. |
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 |
NOTE: Attaching virtual external device using Java client is supported. |
SupportAssist direct upload, scheduling, and register | Removed | Removed | Removed |
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
- 292137: Unable to login to iDRAC due to LDAP bind failure.
- 291072: Performing SystemErase with only BIOS repurpose option resets all iDRAC settings to factory default.
Security
- 295875: Secure Boot Bypass due to Root Block Vulnerability.
- CVE-2024-25943 fix.
Networking and IO
- 291088: iDRAC IPv6 Redfish requests get blocked when the HostHeaderCheck is enabled on the iDRAC webserver configuration.
- 291118: Remote file share ISO boot fails frequently.
- 296775: Two Factor Authentication fails when user certificate depth is more than 2.
Known issues
iDRAC firmware
Table 2. Firmware update failure for specific componentsDetails | |
---|
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 updatesDetails | |
---|
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 failDetails | |
---|
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 messagesDetails | |
---|
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. LC Message on System Power Cycle: New PSU DetectedDetails | |
---|
Description | When performing a system power cycle, an LC message may be displayed, indicating that a new PSU has been detected, along with an error message "Firmware update file not found (PR10)." |
Workaround | Ignore the message. |
Systems Affected | PowerEdge XE8545, PowerEdge XE9680, PowerEdge XE8640 (4 or 6 PSU systems) |
Tracking number | 272772 |
Table 7. Multiple job queue entries for exporting SPDM certificateDetails | |
---|
Description | The Job queue may display multiple entries for "Export SPDM Certificate: SPDMHWCert_download.pem." These jobs are logged when either the host or iDRAC is rebooted for each SPDM-enabled device. If both the host and iDRAC goes through a reboot, then two separate jobs are recorded. |
Workaround | Ignore the jobs as these are internal jobs that are triggered during an inventory collection. |
Systems Affected | All systems supported with this release configured with an external PERC 12.1 and Fiber Channel with SPDM enabled. |
Tracking number | 272001 |
Table 8. Intermittent warning message on storage summary page for max configuration systemsDetails | |
---|
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 9. PDR8 and PDR5 disk removal and insertion logs during enclosure firmware updatesDetails | |
---|
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 10. Intermittent SWC9016 Error Triggering Front Panel Amber LightDetails | |
---|
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.' This log error does not have a functional impact, and it can be cleared by performing an AC power cycle. |
Workaround | Perform an iDRAC reset. |
Systems Affected | All systems supported by this release. |
Tracking number | 276462 |
Table 11. Issue with StorageDiskSMARTData and ReportSequence reportsDetails | |
---|
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 12. Job status pendingDetails | |
---|
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 13. Incomplete management module log collection during iDRAC TSR Log retrievalDetails | |
---|
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 14. PWR2284 event logsDetails | |
---|
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 15. SEL events may not be correctly displayed in the earlier versions of iDRACDetails | |
---|
Description | New SEL events were introduced in iDRAC versions 4.4x. If iDRAC is rolled back to an earlier version, then new events logged in the version of iDRAC before it was rolled back may be displayed as an unknown event. |
Workaround | N/A |
Systems Affected | All PowerEdge Rx5x5 or Cx5x5 series servers supported by this release. |
Tracking number | 186384 |
Table 16. PR1 & PR10 Lifecycle logs displayed during Retire and Repurpose operationDetails | |
---|
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 17. After a warm reboot, LC logs display Disk InsertedDetails | |
---|
Description | Following a warm reboot of the server, iDRAC may report "Disk Inserted" in the LC logs for drives behind HBA or PERC12 controllers. |
Workaround | Ignore the log entry. |
Systems Affected | All systems supported by this release. |
Tracking number | 144819/141414/278145 |
Table 18. Repetitive PR7 messages related to PSU in LC logs after a system erase operationDetails | |
---|
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 19. Latest NIC firmware version not displaying in iDRACDetails | |
---|
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 20. Failure of network and base band management controller firmware update by RACADMDetails | |
---|
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 21. LOM Auto recovery failsDetails | |
---|
Description | If the LOM image is corrupted, then LOM Auto recovery after an AC power cycle may fail. |
Workaround | Recover the LOM image manually by running the RACADM command "racadm recover <fqdd>" or perform a host cold boot. |
Systems Affected | PowerEdge XE9640 |
Tracking number | 275366 |
Table 22. Network firmware update job failingDetails | |
---|
Description | Unable to create a network firmware update job after running the "racadm systemerase reinstallfw" command immediately after performing "racadm systemerase lcdata" 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 23. HWC8010 error after installing a DPU cardDetails | |
---|
Description | Server may report the error "HWC8010: Configuration error: Add-in card in slot x" after the server is restarted post a DPU card installation. |
Workaround | Ensure that the DPU card is installed in the PCIe Slot 1 in PowerEdge R650 and in Slot 2 in PowerEdge R750. |
Systems Affected | PowerEdge R650 and PowerEdge R750 |
Tracking number | 232953 |
Table 24. Unable to add iDRAC Static IPDetails | |
---|
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 25. Partial information displayed for Mellanox CardsDetails | |
---|
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 26. NIC or FC device slot listed in hardware inventory even when disabled in BIOSDetails | |
---|
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 27. iDRAC Network Disruption Post-Reboot IssueDetails | |
---|
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 28. RAC0508 error while uploading signed CSR certificateDetails | |
---|
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 29. Issue with POST operation for SystemErase actionDetails | |
---|
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 30. Drive property not displayedDetails | |
---|
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 31. Expand query parameter issueDetails | |
---|
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 32. Server reboots while applying device firmware updateDetails | |
---|
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 33. GET method on Port collection returning incorrect informationDetails | |
---|
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 34. Redfish Validator errorDetails | |
---|
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 35. RLCE reports Incorrect value for fan sensorDetails | |
---|
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 36. Service Validator reporting errors for Redfish API servicesDetails | |
---|
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 37. Performing GET with Top query parameter returns no errorDetails | |
---|
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 38. Uploaded firmware link not available in SoftwareImages propertyDetails | |
---|
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 39. Attributes for CNA cards not displayed through Redfish or RACADM interfaceDetails | |
---|
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 |
Table 40. Unable to create a recurring job after same job was completedDetails | |
---|
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 41. Get operation not displaying model or serial number for PCIe devicesDetails | |
---|
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 |
Storage
Table 42. Abnormal display of storage status page in iDRAC GUIDetails | |
---|
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 43. Drive slots emptyDetails | |
---|
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 44. Crypto erase job failure in KIOXIA CM6 FIPs driveDetails | |
---|
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 45. Disk conversion job failureDetails | |
---|
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 46. iDRAC update fails to discover PERC12Details | |
---|
Description | During the iDRAC update process initiated from the Host OS, in rare instances, the PERC12 controller may not be detected even after a successful firmware update. In the iDRAC GUI, the storage components may display the PERC 12 card and its associated Physical Disks (PD), Virtual Disks (VD), and Enclosures as "Unknown." |
Workaround | Perform an iDRAC reset. |
Systems Affected | All systems supported by this release. |
Tracking number | 278102 |
Table 47. 254 Drive Slots Displayed in PowerVault MD2412Details | |
---|
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 48. Errors in SCP Import JobDetails | |
---|
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 49. Issue creating a VD by iDRAC GUI advanced configurationDetails | |
---|
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 50. Intermittent absence of controller driver versionDetails | |
---|
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 |
Table 51. VOSS Drive Encryption Capability IssueDetails | |
---|
Description | When SDPM is enabled, and the iDRAC security status is disabled, the security status of VOSS drives fails to automatically change to "Encryption Capable." |
Workaround | To update the security status of VOSS drives, perform a cold reboot of the system. |
Systems Affected | All systems supporting by this release. |
Tracking number | 279378 |
Table 52. VOSS Drive Security Issue with SDPMDetails | |
---|
Description | When SDPM is enabled, VOSS drives do not secure automatically. |
Workaround | To address this, perform any one of the following options:- Enable Autosecure before enabling SEKM/ILKM.
- Perform a cold server reboot.
- Manually enable security for the VOSS drive using any iDRAC interface.
|
Systems Affected | All systems supporting by this release. |
Tracking number | 279248 |
Table 53. Drive part number not displayedDetails | |
---|
Description | If a faulty drive is hot-inserted into the BOSS controller, the Part Number of the drive is not shown in the PDR3 Lifecycle logs. |
Workaround | Go to the Storage overview page to check the part number of the drive. |
Systems Affected | All systems supporting by this release. |
Tracking number | 270642 |
Table 54. Drive Security IssueDetails | |
---|
Description | Drive security status may incorrectly appear as unsecured or encryption capable while SEKM080 message was displayed in the Lifecycle logs about successful drive encryption. |
Workaround | Perform an additional cold reboot to ensure that the drives are properly secured. |
Systems Affected | All systems supporting by this release. |
Tracking number | 270281 |
Table 55. VD blink operation failingDetails | |
---|
Description | For JBODs that are connected through PERC H965e, the VD blink operation fails with an error. |
Workaround | N/A |
Systems Affected | All systems supporting by this release. |
Tracking number | 269683 |
Table 56. PERC H965i missing from iDRACDetails | |
---|
Description | PERC H965i controller not listed in iDRAC after flashing iDRAC firmware is updated. |
Workaround | Perform a cold boot or warm boot or AC power cycle or an iDRAC reset. |
Systems Affected | All systems supporting by this release. |
Tracking number | 273349 |
Table 57. Expanding VD capacity jobs fails intermittentlyDetails | |
---|
Description | After a VD capacity expansion job is initiated, the expansion completes while iDRAC reports the job as failed. Similarly, the delete job for the same VD job may fail. |
Workaround | Retry the operation. |
Systems Affected | PowerEdge XE8640 |
Tracking number | 272248 |
Table 58. Unblink operation not workingDetails | |
---|
Description | Unblink operation on drives that are installed in the enclosures including PowerVault MD 2412, PowerVault MD 2424, or PowerVault MD 2460 fails. |
Workaround | Try the unblink operation using the PERC CLI tool. |
Systems Affected | All systems supported by this release. |
Tracking number | 264210 |
Table 59. Unable to update external enclosuresDetails | |
---|
Description | Changing external enclosure element (EMM/PSU/Fan/TempProbes) inventory/monitoring and Enclosure Asset Tag and AssetName may fail for PowerVault MD 2412, PowerVault MD 2424, or PowerVault MD 2460 that is connected to the server through PERC H840. |
Workaround | N/A |
Systems Affected | All systems that supported by this release with PERC H840 connected to SAS4 JBODs on PowerVault MD 2412 or PowerVault MD 2424, or PowerVault MD 2460. |
Tracking number | 260963, 260401, 257318 |
Table 60. LC logs display incorrect version change for disksDetails | |
---|
Description | After a disk firmware upgrade, LC logs may report it as a firmware downgrade with PR36 message. |
Workaround | Restart the host system. |
Systems Affected | All systems supported by this release. |
Tracking number | 197049 |
Table 61. Storage components display incorrect status after warm reboot stressDetails | |
---|
Description | After a system warm reboot, iDRAC storage components (Controller/Physical Disk/Enclosure/Virtual Disk) may display health status as "unknown". |
Workaround | Perform a cold system reboot or iDRAC reboot. |
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 | 283580 |
Table 62. Enclosure components missing in GUI after warm bootDetails | |
---|
Description | After a system warm reboot, iDRAC GUI displays some enclosure components like Fan, Temperature Probe, EMM as missing for the enclosures PowerVault MD 2412, PowerVault MD 2424, or PowerVault MD 2460. |
Workaround | Perform an iDRAC reset. |
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 | 283805 |
Table 63. Incorrect status in GUI after EMM removal and insertionDetails | |
---|
Description | After removal and insertion of EMM for the enclosures PowerVault MD 2412, PowerVault MD 2424, or PowerVault MD 2460, the Enclosure page may display incorrect EMM status. |
Workaround | Perform a cold reboot or warm reboot or iDRAC reset. |
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 | 284232 |
Table 64. Storage components display incorrect status after frequent warm rebootDetails | |
---|
Description | iDRAC may display health status of storage components (Controller/Enclosure/PhysicalDisk/VirtualDisk) as "Unknown" following frequent warm reboot triggered within a short interval. |
Workaround | Perform an iDRAC reboot. |
Systems Affected | All systems supported by this release with PERC controllers. |
Tracking number | 279452 |
Miscellaneous
Table 65. PSU Type issueDetails | |
---|
Description | Servers equipped with the 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 66. Server host powering off following PSU part replacement updateDetails | |
---|
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 67. BBU update issueDetails | |
---|
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 68. Failure in mapping images through RFSDetails | |
---|
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 69. VMAC reapplication issue after network card and BIOS updatesDetails | |
---|
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:
- Run the command
racadm set iDRAC.PCIeVDM.Enable disabled . - Perform a cold boot.
- Proceed with the required BIOS/NIC firmware upgrades.
- For systems already in a failed state (i.e., without the PCIeVDM disabled-triggered firmware upgrade):
- Run the command
racadm set iDRAC.PCIEVDM.Enable disabled . - Perform a cold boot.
- Once again, perform a cold boot.
|
Systems Affected | All systems supported by this release. |
Tracking number | 278034 |
Table 70. Rebootless firmware fails through SCPDetails | |
---|
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 71. Firmware update through iDRAC Group Manager failingDetails | |
---|
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 72. Few Virtual Keyboard keys not working for other languagesDetails | |
---|
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 ¡DRAC 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 15th 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. - CPLD firmware update has no impact on Trusted Platform Module enablement.
- Ensure that the SSH client is updated to the latest version. Following SSH configurations are no longer available on iDRAC:
- KEX algorithms: diffie-hellman-group14-sha1
- MAC: umac-64, umac-64-etm@openssh.com
- In the software inventory, the hash value for iDRAC firmware is displayed as NA instead of hash.
- Install SEKM license before you update the iDRAC to SEKM supported version 4.00.00.00 or later. If you install the SEKM license after updating the iDRAC to SEKM supported version, you have to reapply SEKM supported iDRAC firmware.
- If you are configuring a Gemalto based KeySecure SEKM Server with iDRAC, and to get the redundancy feature functional, copy the certificates manually from primary Gemalto KeySecure cluster to secondary Gemalto SEKM KeySecure cluster. The redundance feature works after the iDRAC is set up for SSL certificate-based authentication.
- When FCP is enabled, 'Default Password Warning' setting is disabled after the default user password is changed.
- For enhanced security, keyboard interactive authentication is enabled on the iDRAC SSH Server. SSH clients now require keyboard interactive authentication before logging in a user in to iDRAC.
- After upgrading or downgrading the iDRAC firmware, ensure that you review the version of the TLS protocol that is selected in the Web Server Settings page.
Storage
- Servers with NVMe drives with different firmware versions and configured through a PERC may display PR36 messages in Lifecycle logs during the boot process.
- Reports about the drives that are not certified by Dell may not be included in the Telemetry reports.
- PatrolReadRate property is deprecated and not supported from iDRAC firmware version 5.10.25.00 and the later releases. Setting PatrolReadRate using SCP is not supported.
- While encrypting VDs through Lifecycle controller, ensure that the first VD in the list is selected. Selecting a VD that is already secured does not affect the existing encryption of the VD.
- Before performing SecureErase on a vFlash, ensure that the partitions on the vFlash are detached.
- Intel ColdStream NVMe devices do not support cryptographic erase. For more information, see Intel's documentation for the specific device.
- 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.
- Before deleting a VD that hosts the OS, ensure that you uninstall iSM. If a VD is deleted without uninstalling iSM, LC log may display the error: "ISM0007 The iDRAC Service Module Communication has ended with iDRAC".
- 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.
- SMART monitoring is disabled for a hard drive while it is set to Non-Raid mode.
- 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.
- 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.
- If any of the NVMe drives report a 'Failed' status (Red LED) due to any of NVMe controller SMART errors (critical warning bits set), it should be treated as a predictive failure (Blinking amber LED). These errors include SMART errors such as:
- Available spare threshold
- Reliability degraded
- Read-only mode
- Virtual memory backup failed, and so on.
- For improved support on drives and operating system deployment, it is recommended to use the UEFI BIOS boot mode.
- To create a virtual disk or deploy an operating system, ensure that you use the Dell supported SATA, SAS, or NVMe drives. For more information, see the documentation for BIOS, controller, and drive.
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
Table 73. Supported systems14th Generation of PowerEdge Servers |
---|
PowerEdge C4140 |
PowerEdge C6420 |
PowerEdge FC640 |
PowerEdge M640 |
PowerEdge M640 (for PE VRTX) |
PowerEdge MX740c |
PowerEdge MX840c |
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 T140 |
PowerEdge T340 |
PowerEdge T440 |
PowerEdge T640 |
PowerEdge XE2420 |
PowerEdge XE7420 |
PowerEdge XE7440 |
Dell EMC XC Core XCXR2 |
Dell EMC XC Core XC640 System |
Dell EMC XC Series XC640 Appliance |
Dell EMC XC Series XC6420 Appliance |
Dell EMC XC Core XC740xd2 |
Dell EMC XC Core XC940 System |
Dell EMC XC Series XC940 Appliance |
DSS 8440 |
DSS 9600 |
DSS 9620 |
DSS 9630 |
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)
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 74. Direct links for documentsURL | 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.
iDRAC Attribute Registry
For information about iDRAC attributes, go to Dell QRL Site,
- Click Look Up,
- Select iDRAC Attributes,
- Select the appropriate attribute group.
- Enter the attribute name.
- Select the attribute from the suggested list for quick access to relevant details.
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.
Models: iDRAC9 Integrated Remote Access Controller, iDRAC9, Integrated Remote Access Controller, Remote Access Controller, Access Controller, Controller