Omada Controller 5.0.15 Adopting & Provisioning loop
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello everyone, After the Omada Controller Update to 5.0.15, most of our sites have the following problem: All APs in the site are in an Adopting & Provisioning loop. I don't know how to end it Restarting the controller or the entire server on which the controller is installed did not help. No clients can log in in this state. The problem affects the EAP225 and EAP245.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Dear @Marda236,
Marda236 wrote
hello everyone, in my environment the bug no longer appears in version 5.0.27. I haven't changed anything in the meantime. and the support didn't adjust my backup either.
Thank you so much for your feedback and confirmation! Glad to hear that your concern was resolved.
StefsKay wrote
Exactly the same issue here, not entirely happy having to play about with the backup file etc, is there a plan to have this fixed as a part of a proper update?
Dear @StefsKay,
To confirm, have you ever tried upgrading to Controller v5.0.27 and found that the Adopting & Provisioning loop issue still exists?
Dear @WirelessForEver,
Your case may be different from what @Marda236 reported so that Controller v5.0.27 didn't work for you.
To figure out the issue, please kindly reply to the support email for further follow-up, the support engineer will help you effectively.
Thank you for your cooperation and patience!
- Copy Link
- Report Inappropriate Content
No I actually haven't, I have however noticed that people have suggested the same issue is still happening, additionally I cannot see an update on the download page (https://www.tp-link.com/uk/support/download/omada-software-controller).
You do realise that every change costs time which in turns costs money, if the change has not been successful, a rollback is required in order to recover a stable service which in turn is seen a regrettable spend of money so I am apprehensive attempting to complete the upgrade where the original issue does not appear to have been identified and resolved.
Please confirm the situation with the original report in the 5.0.15?
- Copy Link
- Report Inappropriate Content
Dear @StefsKay,
StefsKay wrote
Please confirm the situation with the original report in the 5.0.15?
If your Controller was originally upgraded from v3, upgrading to v5.0.15 may have the Adopting & Provisioning loop issue because the backup file between the v3 and v5.0.15 is incompatible. In that situation, the issue has been fixed in Controller v5.0.27.
Omada_Controller_V5.0.27_Windows
If you still have the issue after upgrading to Controller v5.0.27 and restoring the backup file, your case may be different.
In that case, please save the Logs before you roll back the controller, and provide the saved Logs and backup file for analysis.
- Copy Link
- Report Inappropriate Content
Just a quick question. I upgraded our controller from 3.2.1 to 4.1.5. Can I upgrade without any issues to the latest version? Do I need to uninstall and reinstall like I had to do with the upgrade from 3.x to 4.x?
Thanks for any reply!
- Copy Link
- Report Inappropriate Content
Dear @TPDckx,
TPDckx wrote
Just a quick question. I upgraded our controller from 3.2.1 to 4.1.5. Can I upgrade without any issues to the latest version? Do I need to uninstall and reinstall like I had to do with the upgrade from 3.x to 4.x?
If your current controller is v4.1.5 (Windows), you can upgrade without any issues to the Omada Controller v5.0.27 above, no need to uninstall and reinstall, but it's always suggested to backup the current settings before the upgrade.
- Copy Link
- Report Inappropriate Content
Hi there,
Marda236 wrote
After the Omada Controller Update to 5.0.15, most of our sites have the following problem: All APs in the site are in an Adopting & Provisioning loop. I don't know how to end it Restarting the controller or the entire server on which the controller is installed did not help. No clients can log in in this state. The problem affects the EAP225 and EAP245.
As an update, this issue has been fixed in Controller v5.0.29.
Omada Software Controller_v5.0.29_Window has been released on December 17, 2021
Thank you for your attention!
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I guess controller is remote, Tp-link have change adoption port to 29814 TCP and remote device not adopt without this port opened in firewall
- Copy Link
- Report Inappropriate Content
No, OC300 is local in the same network. All ports are open
- Copy Link
- Report Inappropriate Content
then I have no suggestion, I fixed the problem by opening the new TCP port 29814 in the firewall.
What firmware do you use on the access points?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 8191
Replies: 39
Voters 0
No one has voted for it yet.