Unsolved

This post is more than 5 years old

1 Rookie

 • 

23 Posts

44324

June 15th, 2017 07:00

Firmware Update from Dell's repo failed

Hello All!

I've just tried to update a Diagnostics component in iDRAC directly from Dell's repo (downloads.dell.com) via HTTP protocol and using our proxy-server. I was able to get a list of available updates but the Diagnostics component (it seems for me its update should be the safest one to try) update fails with an error message "RED006: Unable to download Update Package".

I wonder if anyone could successfully performed any update from Dell's repository (just to make sure that a source of the problem is on our side)?

1 Rookie

 • 

23 Posts

June 16th, 2017 00:00

Robert, thanks a lot for a prompt reply!

The only proper URL to catalog.xml.gz file I was able to find is downloads.dell.com/.../catalog.xml.gz.

So I put the following values in iDRAC Update and Rollback form:

HTTP Address: downloads.dell.com

Catalog Location (optional): Catalog

Catalog Filename (optional): catalog.xml.gz

http://downloads.dell.com/Catalog/ in a browser let me see a list of files. But I get 404 "File or directory not found" error in a browser if I enter http://downloads.dell.com/catalog.xml.gz. So it seems for me a proper URL is downloads.dell.com/.../catalog.xml.gz.

1 Rookie

 • 

23 Posts

June 16th, 2017 12:00

Robert, so if options below are correct

HTTP Address: downloads.dell.com

Catalog Location (optional): Catalog

Catalog Filename (optional): catalog.xml.gz

but I get an error "RED006: Unable to download Update Package" does that mean something is wrong with proxy server? I've tried two of them and both have given me the mentioned error.

Can anyone confirm he was able successfully update firmware from Dell repo directly?

1 Rookie

 • 

23 Posts

June 16th, 2017 14:00

Robert, thanks a lot indeed for quick replies!

I am getting the following error in the web interface of LifeCycle Controller

    
LC023: Cannot access network share. Check network share access credentials (IP address, user name, password, share type, and so on). Refer to Lifecycle Controller Profile documentation for more details.

if I specify the following options:

HTTP Address: downloads.dell.com

Catalog Location (optional): catalog

Catalog Filename (optional): catalog.cab

So I am not even able to get a list of available update whereas Catalog/catalog.xml.gz gives me such one.

Although I am able to download http://downloads.dell.com/catalog/catalog.cab from my PC's web browser but our iDRAC network interfaces are in a separate network in contrast to my PC what I work with iDRAC web interface from. So one can assume that our proxy blocks cab-files but our network guys says there is no such limitation on our proxy server. I am our of ideas what can be wrong.

1 Rookie

 • 

23 Posts

June 21st, 2017 08:00

Robert, thanks a lot for taking time to do some research!

Do I understand right that specifying  as below

HTTP Address: downloads.dell.com

Catalog Location (optional):

Catalog Filename (optional): catalog.xml.gz

I should be able to update selected component?

Because right now I am getting an error "RED006: Unable to download Update Package".

1 Rookie

 • 

23 Posts

June 22nd, 2017 01:00

Robert, as I wrote in my previous post it doesn't work for me:

I am getting an error "RED006: Unable to download Update Package". If it works for you then I have to double check with our network guys if there is some limitation on their equipment.

1 Rookie

 • 

23 Posts

June 28th, 2017 01:00

What I am experiencing right now it the following:

There is a GET http-request in /var/log/squid/access.log on the proxy-server running squid:

1498633016.526    152 TCP_HIT/200 1174203 GET downloads.dell.com/catalog.xml.gz - NONE/- application/x-gzip

and tcpdump running on proxy server shows network activity from iDRAC's IP which corresponds to the query of the list of available updates, But as soon as I choose a certain update from the list of updates and press Install button the job for that update is created but there is no queries in squid's log and tcpdump shows no activity from the iDRAC's IP.

Iptables was off on proxy server during my tests.

1 Rookie

 • 

23 Posts

October 3rd, 2017 08:00

I've just updated from locally downloaded file iDRAC on one of my Dell PowerEdge R630 servers.
Now iDRAC firmware version is 2.50.50.50. But I am experiencing the same issue as described above, i.e. I am getting exactly the error "RED006: Unable to download Update Package".

So I wonder if someone was able successfully to perform firmware update from remote Dell repo?

5 Posts

June 26th, 2018 02:00

Hi, 

I'm trying to update firmware from iDRAC and using http proxy. Catalog values using default empty values, downloads update list. When trying to download update it ends with

 

2018-06-26 11:22:40 SYS261 Unable to transfer the file, FOLDER04867034M/1/Network_Firmware_VX6DW_WN64_18.5.17_A00.EXE, because initial network connection to the remote host server is not successfully started.

5 Posts

June 26th, 2018 04:00

It seems download job which is created ignores proxy settings entered (=not using proxy), resulting to download failure. What a **bleep**!

5 Posts

July 11th, 2018 00:00

So update: Opened case will Dell support. They have replicated issue in lab and we also confirmed it worked in old version 3.11. It should be fixed in some next release of iDRAC

 

5 Posts

October 2nd, 2018 00:00

The issue is fixed in iDRAC version 3.21.23.22.

February 15th, 2019 08:00

I'm having the same issue, even with the newest version of iDRAC 7 I can have - 2.61.60.60. It worked when it was on 1.35 (the firmware I received the server at), and nothing changed besides the iDRAC update. Worked on 1.35, failed on 2.60.60.60 and up.

What version iDRAC did you have?

1 Message

February 24th, 2019 09:00

RED006: Unable to download Update Package

So dumb.  Been messing with this for 2 hours to no avail.  Basic stuff.  Switching to HP servers.  

March 7th, 2019 06:00

I'm having exactly the same issue with iDRAC/LCC version 2.60.60.60 (latest at the moment).

Neither HTTP nor FTP Firmware Update methods work in Lifecycle Controller.

LLC can download the catalog using FTP, but instead of ftp.dell.com I have to enter a IP address of ftp.dell.com or else the error about unresolvable name appears. DNS is correctly configured and working fine.

LLC can't access the files from FTP because it tries to download them from nonexisting path, for example:
ftp://143.166.147.76//downloads.dell.com/FOLDER03762355M/1/Diagnostics_Application_4DVC2_WN64_2.1_A00.EXE

The same is with HTTP:
http://23.64.233.21/downloads.dell.com/FOLDER03762355M/1/Diagnostics_Application_4DVC2_WN64_2.1_A00.EXE

URLs get the same downloads.dell.com in-between the host name (IP) and path which breaks it.

Also, when using HTTP, the CDN web server requires the requests to be made with host name downloads.dell.com, but LLC converts the name to IP address and sends the request using IP address instead of downloads.dell.com so the web server responds with error.

The issue might be related to catalog.xml, which contains:

Instead of using "downloads.dell.com" as a host name, it seems to be prepended to path.

I managed to update the firmware with LLC by installing a proxy server and rewriting the requests on the fly.

1 Rookie

 • 

16 Posts

March 21st, 2019 17:00

@rockedeller 

since you are smarter than Dell, can you post more details to how you did this or share a link to a blog that has the details.

Top