Attempting to upgrade EAP660 to 1.1.1 through controller fails with no helpful details
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Attempting to upgrade EAP660 to 1.1.1 through controller fails with no helpful details
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I recreated the docker container, and restarted the AP. Still won't upgrade. The previous upgrade to 1.1.0 succeeded with this same configuration.
Controller log:
[Failed]Failed to upgrade ap-1 to firmware version 1.1.0 Build 20211027 Rel. 35153 online.
server.log:
05-10-2022 03:16:35.665 INFO [manager-upgrade-center-pool-0] [] c.t.s.o.m.d.d.m.u.t.DeviceUpgradeStaticTask(149): upgrade task upgradeId [...] of OmadacId(...) is running...
05-10-2022 03:16:35.667 INFO [manager-upgrade-center-pool-0] [] c.t.s.o.m.d.d.m.u.t.DeviceUpgradeStaticTask(330): v2 device mac[mac] of omadacId... upgradeId... finished upgrade process in FIRMWARE_DOWNLOAD_FAILED
05-10-2022 03:16:35.678 INFO [manager-upgrade-center-pool-0] [] c.t.s.o.m.d.d.m.u.c.c(396): OmadacId(...) upgradeId[...] DeviceMac(...) upgrade status change from[false] to [true]
05-10-2022 03:16:35.680 INFO [manager-upgrade-center-pool-0] [] c.t.s.o.m.d.d.m.u.t.DeviceUpgradeStaticTask(469): OmadacId(...) upgrade[id=...] finish.
05-10-2022 03:16:35.682 INFO [manager-upgrade-center-pool-0] [] c.t.s.o.m.d.d.m.u.t.DeviceUpgradeStaticTask(155): upgrade task upgradeId [...] of OmadacId(...) is finished
05-10-2022 03:16:35.683 INFO [manager-upgrade-center-pool-0] [] c.t.s.o.m.d.d.m.u.c.c(223): OmadacId(...) upgradeId[...] releaseUpgradeCatelog finished
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Not sure if related, but during the upgrade I get this error in server.log with the MAC of the AP:
WARN [manage-work-group-12] [] c.t.s.o.m.d.p.t.h.a(191): send set request to OmadacId(...) DeviceMac(...) fail, com. tplink. smb. ecsp. common. TransResult@65eaeb30[errCode=2600,msg=ERR_DEVICE_SEND_TCP_TIMEOUT,result=<null>,addressDTO=<null>]
(added spaces to com tplink smb common TransResult to get around some weird URL filter)
- Copy Link
- Report Inappropriate Content
I'm going to suggest you try to downgrade the AP back to 1.0.6 from 1.1.0, then go straight to 1.1.1 from there.
- Copy Link
- Report Inappropriate Content
@d0ugmac1 Upgrading back to 1.0.6 also fails in the same way.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Finally figured this out. I was binding the HTTP ports to a specific IP address, because 80 & 443 were in use by another site on the same server. Binding the 29810-29814 ports to a specific IP never worked because of broadcast issues, so they were bound to 0.0.0.0.
I changed the HTTP ports so they didn't conflict, and removed the IP address binding, and the upgrade succeeded.
My guess is that the EAP and/or the controller was getting confused, or the way firmware files were send/fetched changed in the latest controller or firmware, and the EAP was trying to fetch the file from a management port on an IP that it wasn't bound to. The port FAQ (which is also out of date) says that one of the 2981x ports is used for upgrades, but now apparently one of the management HTTP ports is also used.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2150
Replies: 15
Voters 0
No one has voted for it yet.