Firmware automatic update Failed due to Error: Download failed
Applies to
- ONTAP 9
- Automatic Update Feature on System Manager
Issue
- After enabling the Automatic Update Feature the firmware download is failing:
download failed for url [https://support-sg-nawest.netapp.com/au__BMC_FW.13.10P1.zip.tgz_...]
- EMS reports:
Thu Jan 18 10:47:43 +0900 [Nodename: mgwd: auto.update.action:notice]: Automatic update: Applied the action "install" to package: SP/BMC FW revision 13.10P1.
Thu Jan 18 10:47:51 +0900 [Nodename: mgwd: auto.update.failure:error]: Automatic update: Failed update for package: SP/BMC FW revision 13.10P1. Error: Download failed.
or
Thu Aug 10 14:19:16 -0500 [netapp-1: mgwd: auto.update.received:notice]: Automatic update: Received update for package: Shelf FW revision 0310 for shelf model IOM12.
Thu Aug 10 14:19:16 -0500 [netapp-1: mgwd: auto.update.received:notice]: Automatic update: Received update for package: Shelf FW revision 0250 for shelf model IOM12E.
Thu Aug 10 14:20:17 -0500 [netapp-1: mgwd: auto.update.failure:error]: Automatic update: Failed update for package: Shelf FW revision 0310 for shelf model IOM12. Error: Download failed.
Thu Aug 10 14:20:33 -0500 [netapp-1: mgwd: auto.update.failure:error]: Automatic update: Failed update for package: Shelf FW revision 0250 for shelf model IOM12E. Error: Download failed.
- Errors seen in mgwd:
Thu Aug 10 2023 14:19:51 -05:00 [kern_mgwd:info:2302] ERR: au_downloader_libcurl: do_download:src/core/downloader_impl_libcurl.cc:109 download failed after 1259 ms, trans_id {e0190fe0-37b2-11ee-8249-00a098e2c38f} retry needed: no, curl (22) http (404) (HTTP response code said error : The requested URL returned error: 404)
or
Thu Jan 18 2024 10:47:49 +09:00 [kern_mgwd:info:2346]ERR: au_downloader_libcurl: do_download:src/core/downloader_impl_libcurl.cc:109 download failed after 3811 ms, trans_id {93c845a2-b5a3-11ee-8aee-d039ea940a54} retry needed: no, curl (22) http (403) (HTTP response code said error : The requested URL returned error: 403 Forbidden)
- Network configuration has been confirmed to be correct and no issues with firewall settings.