Firmware download fails

Hello

The file location in the catalog looks correct.

https://downloads.dell.com/FOLDER05268089M/1/BIOS_5KNGY_WN64_1.5.6.EXE

I tested downloading the file through a browser and by creating a repository and exporting it. I had no issues creating an SUU with BIOS package 5KNGY for the R740.

This may be a network security issue or a folder permission issue. I suggest checking OpenManage Enterprise documentation regarding ports that need to be open.

http://www.dell.com/openmanagemanuals/

Thanks

I agree, logging is very limited in OMEn. It is something that will hopefully change with a future update.

https://www.dell.com/community/Dell-OpenManage-Enterprise/Dell-openamanage-job-execution-details/m-p/6233291

Ports are fine, I can download the image from a machine in the same VLAN as OME without any issues. Downloading firmware on OME worked just fine when I tried it a few weeks ago, but fails since this week.

I ran tcpdump on the firewall and I can see OME establishing an SSL connection to a close-by Akamai Node. TLS handshake looks good, a bit of data is exchanged, nothing more to see due to SSL.

When I go through a proxy

1544733458.264  60505 2001:xxx:0:104::a9c:a3b TCP_TUNNEL/200 1963199 CONNECT downloads.dell.com:443 - HIER_DIRECT/2a02:26f0:64:4ae::1c -
1544733625.232     87 2001:xxx:0:104::a9c:a3b TCP_TUNNEL/200 3758 CONNECT [2a02:26f0:10c:290::1c]:443 - HIER_DIRECT/2a02:26f0:10c:290::1c -
1544733625.451     87 2001:xxx:0:104::a9c:a3b TCP_TUNNEL/200 3758 CONNECT [2a02:26f0:10c:290::1c]:443 - HIER_DIRECT/2a02:26f0:10c:290::1c -

First hit was the Catalog Update which went fine (as far as I can tell). The other two lines are the download of two firmware files that failed (after 87ms)

I guess the literal IPv6 address COULD point to an issue, but it is hard to tell because there simply is no log of OME trying to download the file (what file, what URL, what was the error encountered)

I'm not complaining about the error, I'm complaining about the total lack of debugging information when an error occurs.

Getting same issue here, was able to update fine 2 months ago, now 30 of our M630 blades fail to update, they also fail to obtain the update when attempting via the DRAC which also used to work. The only way i can update now is downloading each update manually and uploading to the DRAC.

Edit - I'll try disabling ipv6 to see if that helps.

Edit 2: Nope, same error.

Severity Date and Time Message ID Summary Comment
2019-02-27T05:33:39-0600 RED006
Unable to download Update Package.

2019-02-27T05:32:38-0600 RED100
iDRAC initiated the download update package files operation. Wait for a few minutes.

2019-02-27T05:32:37-0600 JCP027
The (installation or configuration) job JID_512671576777 is successfully created on iDRAC.

2019-02-27T05:32:15-0600 JCP037
The (installation or configuration) job JID_512670610688 is successfully completed.

2019-02-27T05:32:14-0600 RED036
Firmware updates are available : QLogic QME2662 16Gb FC Adapter - 2001000E1EE9CCF8.

2019-02-27T05:32:14-0600 RED036
Firmware updates are available : QLogic 577xx/578xx 10 Gb Ethernet BCM57810 - F4:E9:D4:AD:8B:70.

2019-02-27T05:32:14-0600 RED036
Firmware updates are available : Dell OS Driver Pack, 17.08.10, A00.

2019-02-27T05:31:26-0600 RED002
Package successfully downloaded.

2019-02-27T05:31:26-0600 RED111
Successfully downloaded the update package details 0.782469 MB in 23.1342 secs at 0.0338231 MBps (0.270585 Mbps) [Catalog.xml.gz].

From the DRAC Logs.

2019-02-22T01:01:59-0600 RED068
Unable to successfully complete JID_508180167719: The network file transfer of an update package was not successful.

2019-02-22T01:01:59-0600 RED051
The network file transfer of an update package was not successful.

I have the same error.

I started to work with OM Enterprise last week. I use usually OM Essentials and it looks that OM Enterprise can't replace it because OM Enterprise don't provide driver updates. But for my Linux colleagues OM Enterprise could be a solution. So I test it but it don't work for the moment.

Greetings Barbara

Hi @bernilrz ,

I am seeing the same error for few servers. Any idea about the solution?

Thanks,

NJ

Hi,

You need to enable smb v1 on the appliance to be able to update older servers.

Thomas, thank you! I was having the same issue and your solution fixed it for me.

SMB v1 was already enabled for me, yet I still get the error.  Other than a recent firewall change (unlikely), I'm at a loss for why this is failing for us.

I know this thread is a bit dated, but I also get this error on various IDRACs.
Ive tried feeding the update manually after extracting the download package and using online repo.
SMB1 i have enabled for testing, it did not improve the situation.
Manually updating the IDRAC via the web-interface works so the file isn'z a problem.

It keeps failing on my IDRACs with signature errors:

Messages:
Running
Starting communication with the device.
Checking LC-Service state
Checking Remote Services availability
Remote Service is ready.
Initiated Update Job for DCIM:INSTALLED#iDRAC.Embedded.1-1#IDRACinfo with JobId (JID_972323903184)
Job status for JID_972323903184 is Failed
Message: Unable to verify Update Package signature.
Message ID: RED007
System state check initiated.
iDrac state check.
Checking LC-Service state
Checking Remote Services availability
Remote Service is ready.
Deleting the job queue
Delete Job Queue was successful
Deleted Job Id:JID_972323903184
Task Failed. Completed With Errors.