Article Number: 000177187
This article provides steps to resolve PowerEdge Server get a UEFI0315 Error when the Secure boot is enabled and during update iDRAC firmware.
After downgrading iDRAC8 firmware from 184.108.40.206 release, Dell EMC PowerEdge 13G servers may stop at POST with an UEFI0315 Error Banner. The error persists on each HOST reboot/ power-on.
UEFI0315: Unable to process an iDRAC request to configure Secure Boot keys because of a communication error between BIOS and iDRAC…
Example of Lifecycle Controller Logs:
Unable to process an iDRAC request to configure Secure Boot keys because of a communication error between BIOS and iDRAC.
This error banner is displayed when BIOS fails to receive an expected Secure Boot setting value during the Power-On Self-Test (POST) sequence. When iDRAC8 is downgraded from 220.127.116.11, this reading fails regardless of Secure Boot settings within server BIOS.
The Lifecycle Controller Logs of the iDRAC8 will record if the iDRAC8 firmware has changed. Searching for the event "PR36" will show the history of firmware updates that are applied to the server.
Version change detected for Lifecycle Controller firmware. Previous version:18.104.22.168, Current version:22.214.171.124
iDRAC8 firmware 126.96.36.199 resolved an issue that was leading to this sighting randomly. Downgrading from the iDRAC8 188.8.131.52 is persistently causing the error to return. If the iDRAC8 firmware is confirmed to have been downgraded, this error is not an indication of faulty hardware.
Use one of the following methods to clear the condition from impacted servers.
Option 1: Update iDRAC8 to 184.108.40.206
Reinstalling iDRAC8 to firmware version 220.127.116.11 will restore the fix that corrects this condition. The server will need to be warm rebooted after the iDRAC firmware update completes.
iDRAC8 18.104.22.168 is available for download here.
Option 2: Reset Secure Boot Keys via Redfish API
If the server needs to remain on downgraded iDRAC8 firmware, the Secure Boot Keys of the system BIOS need to be reset. Redfish API is the only method to modify this setting. Follow the instructions below to modify the /redfish/v1/Systems/System.Embedded.1/SecureBoot/Actions/SecureBoot.ResetKeys value.
Secure Boot Policy setting needs to be set to Custom attempting to reset Secure Boot Keys. Secure Boot can either be Enable or Disabled.
F2 System Setup >> System BIOS >> System Security >> Secure Boot:
Postman App was used in the following examples. Define the following fields in the application before sending the Redfish POST command.
Post URL Bar:
If the Redfish post command was successful, Postman will show similar messaging in the Response field:
"Message": "Successfully Completed Request",
"Message": "The operation successfully completed.",
"Resolution": "No response action is required.",
iDRAC7/8 with Lifecycle Controller Version 22.214.171.124, iDRAC8 with Lifecycle Controller version 126.96.36.199
29 Nov 2021