Lifecycle controller FTP Firmware update failing

Hello

I would try updating the iDRAC/LCC manually. If you are using an iDRAC7 or later then you can use Windows 32-bit Dell Update Packages. If you go to the update and rollback section of the iDRAC web page you can upload the DUP from your computer through the browser. If you are using an iDRAC6 you will need to use the image file, I think the extension is .d7 for the iDRAC. The LCC should have a repair package that is .usc file extension.

You can also try downloads.dell.com instead of ftp.dell.com. Also, our FTP site no longer works with 11th generation or older systems.

http://www.dell.com/idracmanuals/

Thanks

But that's a 12 Gen System.

I'm having the same issue with 12th, 13 and 14 Gen. This worked last month. Is it going to be fixed anytime soon or there is no fix to this?

---

@geniefiasco wrote:

But that's a 12 Gen System.

I'm having the same issue with 12th, 13 and 14 Gen. This worked last month. Is it going to be fixed anytime soon or there is no fix to this?

 

 

---

Glad to see it's not just us - same issue here - unable to apply any updates via FTP/HTTP/OME anymore, all fail to download, have to download manually and push them to update anything. Worked last month for us also.

Glad to see it's not just us - same issue here - unable to apply any updates via FTP/HTTP/OME anymore, all fail to download, have to download manually and push them to update anything. 

is it not true most FTP servers are being shut down

due to new security rules?

I can't speak for Dell but many sites world wide that had FTP and now dead

we ask and get that answer.

is it related to GDPR? rules new, spring 2018?

I see these pages

http://downloads.dell.com/published/pages/poweredge-r710.html

but FTP I dont know.\

but this don't fly,  ftp.dell.com now.

404

http://ftp.dell.com/Browse_for_Drivers/Servers,%20Storage%20and%20Networking/PowerEdge/

one post here said

I think some of the confusion is to blame on the other DNS names the FTP can be reached at, such as.
downloads.dell.com
ftp1.us.dell.com
ftp2.us.dell.com
ftp.us.dell.com

my guess is this is why.

you don't need FTP, especially since the SSH daemon has its own FTP module for accomplishing SFTP through a tunnel.(the new FTP)secure.

https://www.dell.com/community/Systems-Management-General/ftp-dell-com-system-management-download-issues/m-p/7250847

---

@DELL-Daniel My wrote:

https://www.dell.com/community/Systems-Management-General/ftp-dell-com-system-management-download-issues/m-p/7250847

---

Thanks Daniel - https didn't work - however "downloads.dell.com" worked.

We're having the same issue,  it's a shame that Dell just says "we don't support FTP anymore" and leave their users to just "deal with it."  Short of installing each patch manually I've exhausted every way to check/install firmware updates.  I'm trying now to use the "Dell Repository Manager" and "rufas" to create a bootable USB key to update the firmware.  (I'll post if I succeed or not.) 

What used to take an hour or so per server every quarter is now taking me days to complete.  

BTW, I've tried following the suggested documents, "ftp.dell.com",  "downloads.dell.com", etc etc etc  (and as the previous poster stated you can't put "https://" in the line that asks for the FTP address.)  

What makes this even worse is that I'm still under maintenance and support and now I have a product that I can't update (easily).  

Thanks again, Dell, for standing by your products!

Paul

I'm in the same boat.

Just under two years into a three year Dell SMB contract and I'm back to updating with USBs or DVD/CD.  Sadly, I know the procedure...it's how I did things back when it was floppies.  Think about that.

Has anyone tried a local FTP?  For one or two servers that might not make sense, or if they are all physically local.  But for a multi-site it might make more sense.  Still, that's more $$$ that needs to be factored vs a competitor when calculating TCO.

Hi all, I was having the same issue updating with LCC on an R520. I had no such problems when I last updated this server in Dec 2018, so firmware shouldn't be too far out of date.

I tried the ftp.dell.com repo first: downloads catalog successfully, but each update fails to download.

Tried HTTP repo, downloads.dell.com: network tests OK, fails to connect with various errors. says credentials are wrong, or invalid catalog, etc.

I happened to give it a shot from the iDRAC web panel and it looks like the updates are applying successfully. If you're stuck trying to update with LCC maybe give it a shot from the iDRAC panel. "Update and Rollback" worked with the HTTP repo in iDRAC 7.

Hope this helps somebody.

Found FTP always fails now.

I updated to 2.63.60.62 (.61 was the one that was buggy) and then used 'http' with 'downloads.dell.com' and the share name 'Catalog' (which seems to be case sensitive). on R420/R720/R720xd

https for some reason didn't work.

Update the idrac firmware with this file "iDRAC-With-Lifecycle-Controller_Firmware_T35W2_WN64_2.63.60.62_A00" via usb and then it will update through the FTP server.

Updating is now a horrible chore, as the previous post in this thread show. I made my own thread regarding this, "LifeCycle Controller updates", but basically my tl;dr solution is:

Download the LCC update image, either the windows .exe or linux .bin, doesn't matter. currently "iDRAC with Lifecycle Controller v. 2.63.60.62". Don't run the exe, but open it with an archive manager like WinZip, as it is a self extracting archive. Inside you should find a "payload" directory, containing "firmimg.d7".

Extract this file. Access the iDRAC Web UI, and use the update/rollback, "local file" "single update" etc procedure (may be different depending on the currently installed firmware), but load in the .d7 file as the update file.

The iDRAC will receive this, reflash itself to upgrade, the iDRAC will restart, and after you login you should have HTTPS support, at which point you can either use the LCC or via the iDRAC do the updates, using https://downloads.dell.com as the update server, and you should know be able to install all the updates.

Loading the .d7 file directly bypasses the issue that the bin file is signed using a hash algorithm that old LCC versions are unable to handle, causing it to reject the update, as it cannot verify it is authentic.

Hey

I tried what you wrote on my R820 but still been running into the same issue of it unable to verify the digital signature and that is with the .exe. With the .bin file it wont even bother just says needs to be a .exe extension.

I tried to do a rollback to see if it will see that .d7 file but it doesn't launch the wizard.

Any ideas for the digital signature issue I'm running into

Current version is 1.57.57

Thanks in advance