Omada Hardware Controller fails to update any device firmware on remote sites
Omada Hardware Controller fails to update any device firmware on remote sites
My OC200 used to only manage a local site, now it manages 3 sites with a total of 3 gateways and 25 APs. The controllers is located in one of the sites (behind one of the gateways) alongside 18 of the APs.
The second site resulted from migrating it from a software controller that runned on that newwork managing one gateway and 5 APs,
The third site is a new site with only one gateway and 2 APs.
ISP router is in bridge mode in all 3 sites.
Recently there have been a great number of new firmware releases. I've never had a problem updating firmwares before on any of the sites when they were stanalone, but now I can't get the firmware upload to work on any of the devices on any of the remote sites, while it works flawleslly on all devices in the local site. Phisically moving a device from remote to local site (plus forgetting and adopting) lets the device update to succeed.
Googling the problem I found one has to foward certain ports. While this needed step should obviously be done by the omada controller automatically (and only during the updating process), I went ahead and forwareded the ports. Which ports one need to forward depends on what tp-link page you land on, so I've forwarded the ports described on any and all related tp-link pages, forums, reddits and those provided by tp-link support in response to the ticked I opened. Still it doesn't work. I've forwarded ports
8443
443
29810-29820 (currently only untill 29816 is needed, but since they've been adding more ports, I went ahead and left a few extra ports)
All TCP + UPD.
The devices use the controllers dns name, however the controller is ona a fixed public IP. I can see all devices in all sites in OC200. I can otherwise manage all the devices so why can't I just update them?
Also, NONE of the FW update methods work: Single device update, rolling update, manually updating the new firmware file. Manually updating gets stuck at 99%, then fails. His is both if using the web interface locally or through https://omada.tplinkcloud.com/, or android app.
References:
https://community.tp-link.com/en/business/forum/topic/559150
https://community.tp-link.com/en/business/forum/topic/656120
https://www.tp-link.com/en/support/faq/3281/
I'm at a loss. So is TP-Link support. After some back and forth emails they've requested access to my controller, but I'm not about to let that happen just yet for security reasons.
Does anyone has any further suggestions I might try?
Edit: DMZ the controller also didn't work, so it doesn't seem to be a port forwarding issue.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I notice that OC200's firmware is not the latest one; can you please update the firmware to the latest one first?
- Copy Link
- Report Inappropriate Content
Hank21 wrote
I notice that OC200's firmware is not the latest one; can you please update the firmware to the latest one first?
Hello @Hank21
The current firmware on the controller is 1.31.3 Build 20240620 Rel.80383 which is the latest, so either it autoupgraded since my first post, or an update came along and I upgraded it. Using the "Check for Upgrade" buttons says it is running the latest version.
Thanks anyway.
- Copy Link
- Report Inappropriate Content
Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID240907796, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
@Tintronic did you find a solution to this? even with my controller in a DMZ i cannot upgrade firmware on 4 devices at a remote site. Everything else works fine, ive a VPN set up between the two sites and can access both lans no problem
- Copy Link
- Report Inappropriate Content
Ryan213 wrote
@Tintronic did you find a solution to this? even with my controller in a DMZ i cannot upgrade firmware on 4 devices at a remote site. Everything else works fine, ive a VPN set up between the two sites and can access both lans no problem
Hello @Ryan213
No, it is still not working.
TP-Link Support has contacted me and asked me for logs, which I sent. They are looking into it.
Whay is your controller model?
I have an OC300 which currently controls only one site. I'm tempted to move my OC200 controlled remote site to the OC300 to see if that works.
Regards,
Michael K.
- Copy Link
- Report Inappropriate Content
@Tintronic i have an OC200 behind an er707 local and an er605 at the remote site.
frustrating as i also have a small unifi deployment on the same sites and they can upgrade no problem.
does anybody know if there an easy way to change the set inform address on the omada equipment so i could try and upgrade through the VPN instead of the public IP? or even do it through SSH?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1018
Replies: 16
Voters 0
No one has voted for it yet.