Unsolved
1 Rookie
•
3 Posts
0
1861
September 22nd, 2021 08:00
Firmware updating doesn't work via latest Lifecycle Controller (2.81.81.81)
Hi,
we try to update several PowerEdge R730xd via Lifecycle Controller. First we updated iDRAC/Lifecycle Controller to the latest version (2.81.81.81). Then we followed this article 000177916 and after the catalog was downloaded it said that "Lifecycle Controller currently doesn't import SSL certificates -- click OK to continue" (translated), we clicked OK and now it hangs on this screen (progress bar not moving) for ever.
No Events found!


DELL-Chris H
7 Practitioner
•
9.7K Posts
•
48K Points
0
September 22nd, 2021 13:00
Kschlimme,
Would you confirm what version the BIOS is, as well as if it was updated prior to the iDrac update?
Also, what version was the iDrac / LCC at before the update?
Lastly, if the update is run from the Platform Specific Bootable ISO, does it progress normally?
kschlimme
1 Rookie
•
3 Posts
0
September 23rd, 2021 01:00
Ah, sorry. I forgot to mention that we used the Platform Specific Bootable ISO to update the system without any issues before we updated the iDRAC/Lifecycle Controller to the latest version and tried the update via Lifecycle Controller (HTTPS). Therefore the BIOS version now is 2.12.1 (via bootable ISO). Unfortunately I can't say what BIOS version it was before.
So now we try to update via Lifecycle Controller 2.81.81.81/BIOS 2.12.1 via HTTPS (downloads.dell.com) and have the described problem.
But we have another R730xd with Lifecycle Controller 2.75.100.75/BIOS 2.12.1 that has the same problem. Here is a screen capture: https://youtu.be/zabdzgD1tac
DELL-Shine K
6 Operator
•
3K Posts
0
September 23rd, 2021 02:00
Can you try updating server using iDRAC? For this you can login to iDRAC GUI and traverse to "iDRAC Settings -> Update and Rollback" page and select HTTPS option
kschlimme
1 Rookie
•
3 Posts
0
September 28th, 2021 02:00
Thank you for your help! Update via iDRAC worked with all of our machines. Unfortunately it was a lot of work, because our iDRAC interfaces were all in a subnet without internet access.