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

A 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.

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?

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.

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".

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.

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.

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?

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

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

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