- Notes, cautions, and warnings
- Release summary
- Compatibility
- New and enhanced features
- Fixes
- Deprecated features
- Important notes
- Known issues — To be fixed in future releases
- LC logs display incorrect version change for disks
- Blue screen while deploying OS through Lifecycle Controller
- Server stops responding during POST with Config Error
- OME-M Deployment and Configuration Job Fails with Error LC063
- Unable to generate CSR through Redfish
- vFlash detaching after iDRAC firmware update
- MAC identities displayed in RESERVED state
- SEL events may not be correctly displayed in the earlier versions of iDRAC
- CMC firmware update fails
- Telemetry data Disabled without confirmation
- WWN details for the Mezz cards displayed randomly in the WWN/MAC GUI page
- CPU information missing under Hardware Inventory
- Storage Devices displayed in gray text
- Backplane Rollback contents not populating in iDRAC
- Test network connection fails
- MetricReport output does not match the DMTF schema
- Service Validator reporting errors for Redfish API services
- Lifecycle Controller fails to resolve IPv6 DNS addresses
- Performing GET with Top query parameter returns no error
- Server Configuration Profile import job fails
- Unable to add iDRAC Static IP
- Creating virtual media image takes longer on safari browser
- iDRAC displays warning message for different plug-in selection.
- Read-only user Virtual Console session disconnects
- iDRAC Virtual Console entering Connecting Viewer state
- PR1 & PR10 Lifecycle logs displayed during Retire and Repurpose operation
- CPU PPIN in Hardware inventory in IDRAC GUI shows as “Not Supported”
- Performing GET method on chassis PCIe slots displays all PCIe slots
- Virtual Media performance is degraded with QLogic 25G OCP
- iDRAC time fails to synchronize when Server Configuration Profile is imported with SNTP settings
- Virtual console display in iDRAC GUI is blurred
- iDRAC unable to obtain the current time after reboot
- Firmware version change displayed multiple times in Lifecycle log for PCIe SSDs
- Few Virtual Keyboard keys not working for other languages
- DellCertificateCollection URI response not according to DMTF standards
- Disabling local server video attribute in iDRAC virtual console not supported on C6400 and C6525
- Field required displayed in Internet Explorer browser
- Firmware update using pud method failing
- Uploaded firmware link not available in the SoftwareImages property in Redfish
- PCIe types and lanes information not getting populated using Redfish
- iDRAC reboots while collecting SupportAssist logs
- Webserver restarts after remote presence port number is updated
- Getting an error SWC0018 during OS installation
- WSMan query with space between attributes fails
- Attributes for CNA cards not displayed through Redfish or RACADM interface
- Unable to create a recurring job after same recurring job was completed
- SCP Import Job completes with error due to HddSeq error
- iDRAC LC Log shows reset cause as ‘Internal Error’
- Access to serial interface fails.
- LC log created after going to Virtual media page in iDRAC GUI
- Boot mode error during OS deployment
- Repetitive PR7 messages related to PSU in LC logs after a system erase operation
- After a warm reboot, LC logs display Disk Inserted
- iDRAC DUP update fails in Linux operating systems when secure boot is enabled
- Limitations
- Updating iDRAC firmware
- Lifecycle Controller Remote Services — client tools
- Resources and support
- Contacting Dell EMC
iDRAC9 Version 4.40.55.00 Release Notes
Server stops responding during POST with Config Error
- Description
- Server may stop responding during POST after a Lifecycle Controller System Erase job with the message- The System Configuration Check operation resulted in the following issue: Config Error: CPU 1 and CPU ID.
- Workaround
- iDRAC reset.
- Systems affected
- PowerEdge R7525 with EPYC 7003-generation processors and x24 Expander or x4 Rear backplanes.
- Tracking number
- 196985
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\