Lost control of all devices after installing new controller version
I had an issue with my old controller which was running 5.12. It kept crashing and whenever I tried to update I kept getting errors.
I decided to take a backup and start over with a fresh install of the latest. It seemed to take the backup just fine, but it will not adopt any of my switches or access points. Some of the switches are stuck at 'Adopting' and have been for several hours. Others say 'Adopt failed' and if I click retry they go back to 'Adopting' for a while and then fail again.
I took one WAP offline and factory reset it, and it still will not adopt.
I am very concerned that this whole network is about to go down if there is a power event and all my port mappings are lost. Any suggestions on how I can get the backup config to actually do what it's advertised to do?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
The issue ended up being simpler than this. There seem to be discrepancies about which firewall ports are needed. Looking at the Omada Software Controller User Guide for V5.15.24, it says on Page 36 that ports 29810-29813 need to be open for discovering and adopting devices, and those are the ports I had open.
On Page 44 talking about the 'Integrated Gateway' which I do not have, it says that ports 29810-29814 need to be open for discovering and adopting devices. Since logically it seems to me that the endpoint devices are what determine the ports they are reaching out on, not the controller itself, then this must be a typo one way or another. So as an experiment I added port 29814 and the devices switched from 'Adopting' to 'Provisioning' within seconds. So I stressed out for hours about an issue that I thought was my network or the hardware, when it was just caused by faulty documentation.
I have since found other tidbits on various pages that also mention ports 29815 and 29816. As far as I can tell my system is working without those ports, and the user guide does not mention them at all. This page https://community.tp-link.com/en/business/kb/detail/362 however says that
| TCP 29815 |
✔ |
✔ |
Starting from v5.9, Omada Controller receives Device Info, Packet Capture Files, and DPI Application Statistic Data from the Omada devices. |
|
|
TCP 29816 |
✔ |
✔ |
Starting from v5.9, Omada Controller establishes the remote control terminal session with the Omada devices. |
So are these ports useful or not?
That page also seems to imply that port 29813 is no longer used for version 5.x
If anyone from TP-Link is reading this, please update the user manual to accurately reflect the firewall ports that are needed and why for the version of controller that particular guide is written for.
- Copy Link
- Report Inappropriate Content
Try to do another restore of the backup you took before you reset the controller, it is important that you do not reset any of the devices otherwise they will have to be adopted again.
I have done it many times and it works every time. everything should come back if you have done the restore and backup correctly.
if you get adopt fail you can try retry and enter the device username and password
- Copy Link
- Report Inappropriate Content
The issue ended up being simpler than this. There seem to be discrepancies about which firewall ports are needed. Looking at the Omada Software Controller User Guide for V5.15.24, it says on Page 36 that ports 29810-29813 need to be open for discovering and adopting devices, and those are the ports I had open.
On Page 44 talking about the 'Integrated Gateway' which I do not have, it says that ports 29810-29814 need to be open for discovering and adopting devices. Since logically it seems to me that the endpoint devices are what determine the ports they are reaching out on, not the controller itself, then this must be a typo one way or another. So as an experiment I added port 29814 and the devices switched from 'Adopting' to 'Provisioning' within seconds. So I stressed out for hours about an issue that I thought was my network or the hardware, when it was just caused by faulty documentation.
I have since found other tidbits on various pages that also mention ports 29815 and 29816. As far as I can tell my system is working without those ports, and the user guide does not mention them at all. This page https://community.tp-link.com/en/business/kb/detail/362 however says that
| TCP 29815 |
✔ |
✔ |
Starting from v5.9, Omada Controller receives Device Info, Packet Capture Files, and DPI Application Statistic Data from the Omada devices. |
|
|
TCP 29816 |
✔ |
✔ |
Starting from v5.9, Omada Controller establishes the remote control terminal session with the Omada devices. |
So are these ports useful or not?
That page also seems to imply that port 29813 is no longer used for version 5.x
If anyone from TP-Link is reading this, please update the user manual to accurately reflect the firewall ports that are needed and why for the version of controller that particular guide is written for.
- Copy Link
- Report Inappropriate Content
Hi @KocherJJ
Thanks for the sharing and the feedback about the user guide.
Here is faq introducing the ports about Omada controllers:
Which ports do Omada SDN Controller and Omada Discovery Utility use? (above Controller 5.0.15)
I will also provide feedback to update the user guide. Thanks.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 64
Replies: 3
Voters 0
No one has voted for it yet.