Failure to adopt TL-R605 after firmware upgrade
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi,
this is the second time this happens. I have a setup consisting of a few switches, a few EAPs and a TL-R605 router. When I upgrade the firmware on my core switch or the router itself, Omada controller (software based) complains about the router failing to adopt; specifically, it shows the router as "Adopt Failed" and it cannot be managed. If I press the "retry" button, it's asking about the username/password of the device, as if it was managed by some other instance of Omada SDN.
Has anyone faced this issue before? Is there some fix?
Thank you
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi all,
indeed, after rebooting the router, it got adopted again. Actually, what happened was the following:
- I upgraded one of my switches (not "between" my controller and router): no problems
- I upgraded my "core" switch (which is "between" my controller and router): this is what caused the router to show up as "adopt failed"; I assumed that I had pressed by mistake the upgrade button on the router, hence triggering this situation, but that was not the case actually, it was upgrading the core switch that caused it
- When I actually upgraded the router itself, it got readopted automatically without any problems
- Copy Link
- Report Inappropriate Content
@lexam Hello,
I had the same problem: https://community.tp-link.com/en/business/forum/topic/265924
- Copy Link
- Report Inappropriate Content
@lexam Same problem after upgrade. Frankly - each time router/switch is upgraded there is a problem with adopting it. Usually I make several factory resets on all devices (router, switch, EAPs), for TL-R605 v1.0.1 I had to reset ALL DEVICES and connect OC200 directly to router - this helped, but is seems like random problem with upgrade process.
- Copy Link
- Report Inappropriate Content
@PavelV
Same with me tonight as well.
Hoping things like this smooth out.
- Copy Link
- Report Inappropriate Content
How about reboot the device and then try to adopt the device? After upgrade the firmware version, the controller software needs some time to send the adopt command and file to the router. Maybe that is the point.
- Copy Link
- Report Inappropriate Content
Hi all,
indeed, after rebooting the router, it got adopted again. Actually, what happened was the following:
- I upgraded one of my switches (not "between" my controller and router): no problems
- I upgraded my "core" switch (which is "between" my controller and router): this is what caused the router to show up as "adopt failed"; I assumed that I had pressed by mistake the upgrade button on the router, hence triggering this situation, but that was not the case actually, it was upgrading the core switch that caused it
- When I actually upgraded the router itself, it got readopted automatically without any problems
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2354
Replies: 5
Voters 0
No one has voted for it yet.