EAP 225 stuck in adopting after updating from 5.0.5 to 5.0.7

EAP 225 stuck in adopting after updating from 5.0.5 to 5.0.7

EAP 225 stuck in adopting after updating from 5.0.5 to 5.0.7
EAP 225 stuck in adopting after updating from 5.0.5 to 5.0.7
2022-02-01 13:47:55 - last edited 2022-06-13 02:55:16
Model: EAP225  
Hardware Version: V3
Firmware Version: 5.0.7

We have a Windows Omada software controller that was in 5.0.15. 

 

There were three EAP225 connected to it. Yesterday we updated them to 5.0.7 and they have been stuck on ADOPTING since then.

 

We have restarted the Windows computer, updated the software controller to 5.0.30 with no luck.

 

We have even tried resetting one of the APs (quite difficult because they are not in easily accessible places) and it appeared as PENDING but also failes to adopt with a "This device doesn't responde to adopt commands" or something like that.

 

We have updated 8 EAP245 connected to hardware controllers with no issues, but we don't know what to do about these three.

  2      
  2      
#1
Options
1 Accepted Solution
Re:EAP 225 stuck in adopting after updating from 5.0.5 to 5.0.7-Solution
2022-06-10 20:19:52 - last edited 2022-06-13 02:55:16

@shberge and you were right... cool thanks!

 

I saw that in the firmware notes but I thought that since my Omada Controller and the AP are in the same subnet without a firewall, there could be nothing blocking the connection... except that my Omada Controller is running in docker and the 29814 port was not exposed... after opening it up, the AP got successfully adopted with the new firmware.

 

So if anyone is running Omada Controller via docker, make sure the 29814 port is exposed.

Recommended Solution
  1  
  1  
#9
Options
8 Reply
Re:EAP 225 stuck in adopting after updating from 5.0.5 to 5.0.7
2022-02-02 06:37:26

@ccarpio Hello,

This error message means that communication between the EAP and the controller is blocked. Please try the following suggestions to see if they solve your problem.

1) Omada Software Controller/ Hardware Controller communicates with Omada EAP via TCP/UDP port 29810-29814. Some anti-virus programs or firewalls may block this kind of packet. You can disable the anti-virus or firewalls (on the PC that the Omada Software Controller is installed) in your network first for checking. And you need to open TCP/UDP port 29810-29814 in the anti-virus/firewalls.

2) To make sure the Omada EAP is accessible, please ping the IP address of EAP on the PC that the Omada Software Controller is installed.

3) If you have VLAN settings in your network, please make sure the EAP and Omada Software Controller/ Hardware Controller belong to the same VLAN.

2022 TP-Link Wi-Fi 7 Product Launch Event | Watch the Replay at https://www.tp-link.com/us/wifi7/event/.
  0  
  0  
#2
Options
Re:EAP 225 stuck in adopting after updating from 5.0.5 to 5.0.7
2022-02-03 08:11:37

@Hank21 Thanks a lot! 

 

Omada was set up in the Firewall rules as allowed, but it seems it wasn't working properly. I disabled the firewall and it worked.

  1  
  1  
#3
Options
Re:EAP 225 stuck in adopting after updating from 5.0.5 to 5.0.7
2022-02-04 11:53:36

@Hank21 Thanks a lot for your efforts.

But I have exactly the same problem, too.

All previous firmware upgrades of my EAP225(EU)v3.0  have been successful.

EAP is accessible.

I have opened the ports 28910-28914.

I hoped that latest firmware upgrade of the OC200 controller would solve the problem.

But unfortunately, nothing worked.

EAP 225 could not be adopted after the firmware upgrade.

I have reverted to the previous EAP225 firmware, then EAP225 (running the old firmware 5.0.5) is successfully adopted.

I suppose we should wait for the next firmware update to solve the problem ?

 

PS : Exactly the same problem occurs with EAP245(EU)v3.0 in my office. I am going to visit the forum for EAP245, too.

 

IMPORTANT : Both EAP225 and EAP245 communicate with the OC200 controller via the internet, as OC200 is in headquarters far away from here. Not a single problem has been ever occurred in firmware upgrades until this one.

  0  
  0  
#4
Options
Re:EAP 225 stuck in adopting after updating from 5.0.5 to 5.0.7
2022-05-29 11:09:29

  @dakorres Hi, I'm having the same issues with 9 x EAP225 v3 devices managed on the Omada Cloud Controller (Running 5.3.1).

 

Not getting much back from the support guys with the Controller, have attempted several times using different upgrade methods, but always end up reverting to firmware 5.0.5 in order to re-adopt the AP.

 

I see there is version 5.0.8 now available but haven't tried that yet...

 

As with your experience, firmware upgrades up to version 5.0.5 went through without issue.

 

Thanks,

 

Mike Houghton

  0  
  0  
#5
Options
Re:EAP 225 stuck in adopting after updating from 5.0.5 to 5.0.7
2022-06-10 18:05:21

Exact same issue here - cannot adopt AP with Omada controller after upgrading the AP firmware:

  • EAP225-Outdoor V1 (EU) - upgraded to 5.0.7 (but tried with 5.0.8 as well)
  • Omada Controller 5.1.7

 

Adoption keeps failing. Tried factory reset, the AP is working fine otherwise (I can access its own management console + use it serves the clients).

 

If I downgrade to 5.0.5, adoption works again... It's clearly a bug with either the new Omada version or the 5.0.7+ firmwares...

  0  
  0  
#6
Options
Re:EAP 225 stuck in adopting after updating from 5.0.5 to 5.0.7
2022-06-10 18:51:58 - last edited 2022-06-10 18:53:03

I've submitted a bug report. Maybe someone will notice it: https://community.tp-link.com/us/home/forum/topic/560226?page=1

  0  
  0  
#7
Options
Re:EAP 225 stuck in adopting after updating from 5.0.5 to 5.0.7
2022-06-10 19:25:01 - last edited 2022-06-12 09:09:47

Hello everyone...

 

Have you Reading what writing in red in the release note for the firmware?

You have to open TCP 29814 to get the new firmware to adopt.

 

 

Another new thing is firmware upgrade port is changed, this is really bad documented.

if you not have changed this port is default port.

Software controller TCP 8043

Hardware controller TCP 443

so if you have a remote site on your controller you have to open this ports in Firewalls.

 

And be aware of the risks of opening this ports, you give the world access to manage your controller. so tp-link thanks for another security hole.

my recommendation is and open only when making firmware upgrades, then close this port for the world when update is done.

 

 

 

 

 

  1  
  1  
#8
Options
Re:EAP 225 stuck in adopting after updating from 5.0.5 to 5.0.7-Solution
2022-06-10 20:19:52 - last edited 2022-06-13 02:55:16

@shberge and you were right... cool thanks!

 

I saw that in the firmware notes but I thought that since my Omada Controller and the AP are in the same subnet without a firewall, there could be nothing blocking the connection... except that my Omada Controller is running in docker and the 29814 port was not exposed... after opening it up, the AP got successfully adopted with the new firmware.

 

So if anyone is running Omada Controller via docker, make sure the 29814 port is exposed.

Recommended Solution
  1  
  1  
#9
Options

Information

Helpful: 2

Views: 1067

Replies: 8

Related Articles