EAP653v1 US update firmware fails on SDN controller 5.13.30.8
EAP653v1 US running stock firmware as shipped. 1.0.6
Controller is running on ubuntu 24.04
Notification from controller that there is an available firmware update to version 1.0.14 for these EAP653 APs.
Attempt to upgrade inside controller and fails with error message:
Upgrade Results
Failed (1)
98-25-4A-xx-xx-xx upgrade failed: The upgrade file is invalid. Please select a correct file.
This is my 1st Omada SDN setup and no I'm not unfamiliar with how this works. I've tested the things I need to work VLANS, captive portal, client isolation, etc. The usual stuff. It looks and smells a lot like UI setup which I have many years of experience.
Now this should be pretty straightforward stuff. Controller checks mothership for FW updates according to known AP models being used, download FW and offer update.
So now what? Do I need to find the correct FW file for this model and upload it to the controller so the offered FW is the correct one?
thanks,
Jeff
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I got it sorted out. I stopped the controller and renamed each directory in the device-firmware directory to *.bak then restarted the controller. Waited a bit then went back to the controller management page and chose upgrade. In few seconds and new directory was created with same name as before "569176d68e945ba2fc6ec3d08d5c64cc" and the upgrade proceeded properly.
Of interest is that there where 3 directories in the device-firmware directory with 3 apparently different firmwares but note that two of them had the same size bin file. Whether that is due to regulatory domains, don't know. Anyway below is before renaming of directories.
root@localhost:/opt/tplink/EAPController/data/device-firmware# ls -la
total 20
drwxr-xr-x 5 omada omada 4096 Jul 12 21:57 .
drwxrwxr-x 8 omada omada 4096 Jul 12 22:01 ..
drwxr-xr-x 2 omada omada 4096 Jul 10 20:34 569176d68e945ba2fc6ec3d08d5c64cc
drwxr-xr-x 2 omada omada 4096 Jul 12 21:57 74b041412db16c9ff64d64a513e308ba
drwxr-xr-x 2 omada omada 4096 Jul 12 21:49 e207aa3c17ca140add09c89549ed3070
root@localhost:/opt/tplink/EAPController/data/device-firmware# cd 569176d68e945ba2fc6ec3d08d5c64cc/
root@localhost:/opt/tplink/EAPController/data/device-firmware/569176d68e945ba2fc6ec3d08d5c64cc# ls -la
total 16528
drwxr-xr-x 2 omada omada 4096 Jul 10 20:34 .
drwxr-xr-x 5 omada omada 4096 Jul 12 21:57 ..
-rw-r--r-- 1 omada omada 16914744 Jul 10 20:34 569176d68e945ba2fc6ec3d08d5c64cc.bin
root@localhost:/opt/tplink/EAPController/data/device-firmware/569176d68e945ba2fc6ec3d08d5c64cc# cd ../74b041412db16c9ff64d64a513e308ba/
root@localhost:/opt/tplink/EAPController/data/device-firmware/74b041412db16c9ff64d64a513e308ba# ls -la
total 16528
drwxr-xr-x 2 omada omada 4096 Jul 12 21:57 .
drwxr-xr-x 5 omada omada 4096 Jul 12 21:57 ..
-rw-r--r-- 1 omada omada 16914713 Jul 12 21:57 74b041412db16c9ff64d64a513e308ba.bin
root@localhost:/opt/tplink/EAPController/data/device-firmware/74b041412db16c9ff64d64a513e308ba# cd ../e207aa3c17ca140add09c89549ed3070/
root@localhost:/opt/tplink/EAPController/data/device-firmware/e207aa3c17ca140add09c89549ed3070# ls -la
total 16528
drwxr-xr-x 2 omada omada 4096 Jul 12 21:49 .
drwxr-xr-x 5 omada omada 4096 Jul 12 21:57 ..
-rw-r--r-- 1 omada omada 16914713 Jul 12 21:49 e207aa3c17ca140add09c89549ed3070.bin
Below is after stopping controller and renaming the directories (firmwares) downloaded, then restarting controller and selecting upgrade.
root@localhost:/opt/tplink/EAPController/data/device-firmware# ls -la
total 24
drwxr-xr-x 6 omada omada 4096 Jul 16 00:01 .
drwxrwxr-x 8 omada omada 4096 Jul 15 23:54 ..
drwxr-xr-x 2 omada omada 4096 Jul 16 00:01 569176d68e945ba2fc6ec3d08d5c64cc
drwxr-xr-x 2 omada omada 4096 Jul 10 20:34 569176d68e945ba2fc6ec3d08d5c64cc.bak
drwxr-xr-x 2 omada omada 4096 Jul 12 21:57 74b041412db16c9ff64d64a513e308ba.bak
drwxr-xr-x 2 omada omada 4096 Jul 12 21:49 e207aa3c17ca140add09c89549ed3070.bak
root@localhost:/opt/tplink/EAPController/data/device-firmware/569176d68e945ba2fc6ec3d08d5c64cc# ls -la
total 16528
drwxr-xr-x 2 omada omada 4096 Jul 16 00:01 .
drwxr-xr-x 6 omada omada 4096 Jul 16 00:01 ..
-rw-r--r-- 1 omada omada 16914744 Jul 16 00:01 569176d68e945ba2fc6ec3d08d5c64cc.bin
So it appears that the controller downloaded two extra signed binaries for this model incorrectly and that is why it wouldn't or couldn't upgrade the access points. It couldn't select the correct one.
thanks,
Jeff
- Copy Link
- Report Inappropriate Content
Hi @jeff_m
You may try manually upload the firmware file via Config>Manage Device>Browse:
If the latest 1.0.14 failed, you can try update version by version.
- Copy Link
- Report Inappropriate Content
Thank you for the reply. I do know how to do that and will try increamental releases to find which one works. Then try the offered firmware release to see if it will take.
But actually I want to know is where to upload the firmware to the actual controller i.e., the location to place the firmware file, extracted or not. So the controller gives me the option to select whichever firmware works 1st. I'm going to be doing 75 access points on this site and do not want to have to waste time upgrading each access point standalone to some minimum level before the controller AP upgrade will work. It defeats the purpose of a controller managed system now doesn't it?
thanks,
Jeff
- Copy Link
- Report Inappropriate Content
Hi @jeff_m
All firmwares are stored on our cloud servers. When you upgrade automatically via the controller, the controller will send a request to the cloud server to download the corresponding firmware version. Normally, there will be no issue with downloading, uploading, and upgrading. In other words, we don't need to manually upload firmware one by one.
Your previous feedback can be considered as an abnormality, that's why I provided the suggestion as I did before.
- Copy Link
- Report Inappropriate Content
Hello, @Vincent-TP
I was hoping that your answer would be more helpful. Oh well, I can find the correct directory to place the firmware file for the pending/suggested upgrades on my own. Just thought it wouldn't be a big deal to post the actual location as it would make it easier for others that have this anomaly as it may exist at some point for other models.
Anyway, I do have another question. When I scp the firmware to the correct location and do not remove the one that won't install, will the controller show "two" possible choices for firmware updates? This would be helpful to know as there may be a case for downgrading the firmware within the controller for certain models of access points.
thanks,
Jeff
- Copy Link
- Report Inappropriate Content
Hi @jeff_m
It is not recommended to do this because the file name saved locally is a random string and may confuse the models.
BTW, you can consider the batch config function if needed.
- Copy Link
- Report Inappropriate Content
That is helpful thanks but does not work, same failure message as before. The only way I've been able to upgrade firmware is to forget device from controller, log in locally to APs webserver and do it there. Then reset AP to set it back to default admin/admin so the controller can re-adopt it.
thanks,
Jeff
- Copy Link
- Report Inappropriate Content
How many EAP653 have you installed? Are they all v1.0.6? does all of them have the firmware update issue?
And will all of them show this error message? The upgrade file is invalid. Please select a correct file.
- Copy Link
- Report Inappropriate Content
I got it sorted out. I stopped the controller and renamed each directory in the device-firmware directory to *.bak then restarted the controller. Waited a bit then went back to the controller management page and chose upgrade. In few seconds and new directory was created with same name as before "569176d68e945ba2fc6ec3d08d5c64cc" and the upgrade proceeded properly.
Of interest is that there where 3 directories in the device-firmware directory with 3 apparently different firmwares but note that two of them had the same size bin file. Whether that is due to regulatory domains, don't know. Anyway below is before renaming of directories.
root@localhost:/opt/tplink/EAPController/data/device-firmware# ls -la
total 20
drwxr-xr-x 5 omada omada 4096 Jul 12 21:57 .
drwxrwxr-x 8 omada omada 4096 Jul 12 22:01 ..
drwxr-xr-x 2 omada omada 4096 Jul 10 20:34 569176d68e945ba2fc6ec3d08d5c64cc
drwxr-xr-x 2 omada omada 4096 Jul 12 21:57 74b041412db16c9ff64d64a513e308ba
drwxr-xr-x 2 omada omada 4096 Jul 12 21:49 e207aa3c17ca140add09c89549ed3070
root@localhost:/opt/tplink/EAPController/data/device-firmware# cd 569176d68e945ba2fc6ec3d08d5c64cc/
root@localhost:/opt/tplink/EAPController/data/device-firmware/569176d68e945ba2fc6ec3d08d5c64cc# ls -la
total 16528
drwxr-xr-x 2 omada omada 4096 Jul 10 20:34 .
drwxr-xr-x 5 omada omada 4096 Jul 12 21:57 ..
-rw-r--r-- 1 omada omada 16914744 Jul 10 20:34 569176d68e945ba2fc6ec3d08d5c64cc.bin
root@localhost:/opt/tplink/EAPController/data/device-firmware/569176d68e945ba2fc6ec3d08d5c64cc# cd ../74b041412db16c9ff64d64a513e308ba/
root@localhost:/opt/tplink/EAPController/data/device-firmware/74b041412db16c9ff64d64a513e308ba# ls -la
total 16528
drwxr-xr-x 2 omada omada 4096 Jul 12 21:57 .
drwxr-xr-x 5 omada omada 4096 Jul 12 21:57 ..
-rw-r--r-- 1 omada omada 16914713 Jul 12 21:57 74b041412db16c9ff64d64a513e308ba.bin
root@localhost:/opt/tplink/EAPController/data/device-firmware/74b041412db16c9ff64d64a513e308ba# cd ../e207aa3c17ca140add09c89549ed3070/
root@localhost:/opt/tplink/EAPController/data/device-firmware/e207aa3c17ca140add09c89549ed3070# ls -la
total 16528
drwxr-xr-x 2 omada omada 4096 Jul 12 21:49 .
drwxr-xr-x 5 omada omada 4096 Jul 12 21:57 ..
-rw-r--r-- 1 omada omada 16914713 Jul 12 21:49 e207aa3c17ca140add09c89549ed3070.bin
Below is after stopping controller and renaming the directories (firmwares) downloaded, then restarting controller and selecting upgrade.
root@localhost:/opt/tplink/EAPController/data/device-firmware# ls -la
total 24
drwxr-xr-x 6 omada omada 4096 Jul 16 00:01 .
drwxrwxr-x 8 omada omada 4096 Jul 15 23:54 ..
drwxr-xr-x 2 omada omada 4096 Jul 16 00:01 569176d68e945ba2fc6ec3d08d5c64cc
drwxr-xr-x 2 omada omada 4096 Jul 10 20:34 569176d68e945ba2fc6ec3d08d5c64cc.bak
drwxr-xr-x 2 omada omada 4096 Jul 12 21:57 74b041412db16c9ff64d64a513e308ba.bak
drwxr-xr-x 2 omada omada 4096 Jul 12 21:49 e207aa3c17ca140add09c89549ed3070.bak
root@localhost:/opt/tplink/EAPController/data/device-firmware/569176d68e945ba2fc6ec3d08d5c64cc# ls -la
total 16528
drwxr-xr-x 2 omada omada 4096 Jul 16 00:01 .
drwxr-xr-x 6 omada omada 4096 Jul 16 00:01 ..
-rw-r--r-- 1 omada omada 16914744 Jul 16 00:01 569176d68e945ba2fc6ec3d08d5c64cc.bin
So it appears that the controller downloaded two extra signed binaries for this model incorrectly and that is why it wouldn't or couldn't upgrade the access points. It couldn't select the correct one.
thanks,
Jeff
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 505
Replies: 8
Voters 0
No one has voted for it yet.