Business Community > WiFi > Adoption of EAP245v3 fails after Upgrade Controller to 5.0.30
< WiFi

Adoption of EAP245v3 fails after Upgrade Controller to 5.0.30

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Adoption of EAP245v3 fails after Upgrade Controller to 5.0.30

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Adoption of EAP245v3 fails after Upgrade Controller to 5.0.30
Adoption of EAP245v3 fails after Upgrade Controller to 5.0.30
2022-01-23 11:18:23 - last edited 2022-01-23 16:16:45
Model: EAP245  
Hardware Version: V3
Firmware Version: 5.0.4.

Hi All,

 

just today upgraded my Controller from 5.0.29 to 5.0.30.

After that my three EAP245(EU)V3 APs are no longer adopted.

 

Even Factory resetted the APs and forgot them in the controler.

Can see them with discovery tool then direct them to the controller, where they show up in pending state.

Trying to adopt them fails with:

 

01-23-2022 12:11:29.320 WARN [async-business-timeout-pool-0] [] c.t.s.o.m.d.d.m.a.a(176): timeout wait adopt watch result of OmadacId(e2ea8f6090678de6dae26e4a9b941931) DeviceMac(B0-95-75-7C-2A-04) BusinessId(topic=smb_omada_business_223cfd44-6db7-4f03-bf8b-1c4821dd83df, id=a138e841-de78-43d7-a43a-ba081d94e7f6), response:OperationResponse(errorCode=-39002, msg=Device adoption failed because the device does not respond to adopt commands

 

My EAP115V4 (5.0.2 FW) works like a charm.

 

Any ideas ? Help would be appreciated.

Thx

   Mike

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:Adoption of EAP245v3 fails after Upgrade Controller to 5.0.30 -Solution
2022-01-23 14:27:02 - last edited 2022-01-23 16:16:45

@Mike1972 

 

a little bit of information so I have to guess a little.
it's probably your firewall that blocks port TCP 29814 and I'm guessing you upgraded EAP245 to the latest version as well,
v5.0.4 requires the new port
so if you have a remote controller or controller on another VLAN check that the TCP 29814 is open.

 

Recommended Solution
  1  
  1  
#2
Options
2 Reply
Re:Adoption of EAP245v3 fails after Upgrade Controller to 5.0.30 -Solution
2022-01-23 14:27:02 - last edited 2022-01-23 16:16:45

@Mike1972 

 

a little bit of information so I have to guess a little.
it's probably your firewall that blocks port TCP 29814 and I'm guessing you upgraded EAP245 to the latest version as well,
v5.0.4 requires the new port
so if you have a remote controller or controller on another VLAN check that the TCP 29814 is open.

 

Recommended Solution
  1  
  1  
#2
Options
Re:Adoption of EAP245v3 fails after Upgrade Controller to 5.0.30
2022-01-23 16:16:38

@shberge you are absolutely right. I read the info in the release notes about TCP 29814, but only checked my docker host which exposes the port via -net host. I forgot about my firewall. Opening the port solved the problem instantly.
Thank you for your help !

  2  
  2  
#3
Options

Information

Helpful: 0

Views: 1029

Replies: 2

Related Articles
Fast roaming between EAP245v1, EAP245v3 and other router
585 0
L3 Adoption of EAP660 HD fails
3836 0
EAP245 v3 - roaming without controller / beamforming
8508 0
Adoption loop after upgrade to 5.12.9
427 0
Eap245v1 vs eap245v3
1291 0
how to troubleshoot fail Adoption of EAP245v3
430 0
About Us
Press
Copyright © TP-LINK CORPORATION PTE. LTD. All rights reserved.