I have a LtAP mini with the Mikrotik R11eL-EC200A-EU modem on which I can’t update the firmware. I have updated RouterOS and the Routerboard firmware but can’t make the modem update. It can’t actually do the firmware check. I have a SIM card in the device and can get internet access via the LTE modem.
When I try to do a check I see this:
[admin@MikroTik] > /interface lte firmware-upgrade lte1
installed: EC200AAUHAR01A10M16_01.200.01.200
status: error: Fetch failed with status 404 (6)
I have another one of these deployed in the field with he same modem and it works fine:
There are a few "me too" in this thread, but I'm not sure all are the same issue.... I stand by it's critical to start with some recent version like "stable" and ensure /system/routerboard firmware matches RouterOS release. If those don't align, that is the first thing to try to fix any LTE problem.
@jstepnicka seem to be at 7.21rc6. So I probably get everything to stable and/or try "testing" channel. Often some LTE issue creeps in some point release for specific modems/models, then get fixed, and many release later the cycle repeats again... But if there is a bug, you avoid MikroTik telling you to "try stable", or "testing", as the first response. And trying different version of RouterOS+RouterBOOT is 5 minutes exercise.
On the EC200A, firmware update used to require a working LTE connection to do upgrade. But, that changed in 7.18 (from docs) where it can use any RouterOS internet upstream. So perhaps some issue in the new logic, perhaps particular older LTE firmware to latest don't work, but IDK.
Now @jstepnicka seems to have a [relatively] recent version (although an "rc"), matching RouterBOOT firmware, and connected/valid LTE interface... and the "upgrade check" works, so internet works...so LTE upgrade should work. Thus I'm at the "hoping it's fixed in another version" option may be worthwhile troubleshooting step... And I'd also recommend a hard power cycle since the modem capacitor will keep modem running during a normal reboot. It pretty quick to upgrade/downgrade everything to see if some version does work... than perhaps wait for support case to resolve.
Alternatively to the "try another version"... you can enable more logging on what you got to see if reports any thing. So some /system/logging add topics=lte will get you perhaps too many logs, but if you enable just before trying upgrade and disable after "failure", you should have a reasonable set of logs to see what's going on. And topics=lte,!packet and/or =lte,!raw etc could be used narrow LTE logging..
If you get the same error, generate a supout.rif and save that and open a ticket. The higher LTE logging will be included in supout for MikroTik take a look at... So if the problem is not clear from your review of logs, MikroTik have a full set of data to look at.
