how to troubleshoot fail Adoption of EAP245v3

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

how to troubleshoot fail Adoption of EAP245v3

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
how to troubleshoot fail Adoption of EAP245v3
how to troubleshoot fail Adoption of EAP245v3
2022-06-15 14:28:28 - last edited 2022-07-22 07:09:18
Model: EAP245  
Hardware Version: V3
Firmware Version: 5.0.5

I've had trouble getting EAP245's to adopt/provision after upgrading Omada Controller to latest version (5.3.1).

 

I've removed and reinstalled Omada Controller and I've reset the AP's and can connect to them directly. 

 

The controller fails to adopt and then prompts for credentials. If I provide the EAP245 credentials it moves to 'Provisioning' and I can see it is sucessfully pulling data from the AP. (Eg if I change the fallback ip address and try again, the Controller displays the updated information in Config -> IP Settings).

 

But after several minutes it silently fails back to Pending. 

 

Any tips on trouble shooting ?

 

Cheers

N

  0      
  0      
#1
Options
3 Reply
Re:how to troubleshoot fail Adoption of EAP245v3
2022-06-16 07:07:26 - last edited 2022-07-22 07:09:18

  @Ne. Hi I've read many related ports before.

 

Many people have this issue because the new controller version need to use port 29814 to adopt the devices.

Old version controller only use 29810-29813.

 

So you may need to check the PC firewall settings and make sure there is no limitation on these ports.

 

Some details.

 

Related posts.

  0  
  0  
#2
Options
Re:how to troubleshoot fail Adoption of EAP245v3
2022-06-16 09:16:52 - last edited 2022-07-22 07:09:18

  @Somnus 

 

Thanks @Somnus for your reply. This one seems it might be a bit different. I had already created allow rules for TCP and UDP ports 29811 - 29814.


I can see the process is running:

tasklist |findstr "java.exe"
java.exe                     13504 Console                    1    742,004 K

 

is listening on those 4 original ports:

netstat -n -o -p | findstr "13504"

  TCP    [::]:8043              [::]:0                 LISTENING       13504
  TCP    [::]:8088              [::]:0                 LISTENING       13504
  TCP    [::]:8843              [::]:0                 LISTENING       13504
  TCP    [::]:29811             [::]:0                 LISTENING       13504
  TCP    [::]:29812             [::]:0                 LISTENING       13504
  TCP    [::]:29813             [::]:0                 LISTENING       13504
  TCP    [::]:29814             [::]:0                 LISTENING       13504

 

I can also see the connection establish when it goes from Adopting to Provisioning: 

TCP    [ip.add.of.omada]:29814     [ip.add.of.wap]:52634        ESTABLISHED     13504

 

Any suggestions? :)

 

  0  
  0  
#3
Options
Re:how to troubleshoot fail Adoption of EAP245v3
2022-07-11 18:48:58 - last edited 2022-07-22 07:09:18

  @Ne. 

Please check below :

 

AP connectivity to the Controller - make it sure they are on the same LAN

If you have network filtering for traffic going to the internet - make it sure the IP address of the concern AP is allowed.

 

 

  0  
  0  
#4
Options

Information

Helpful: 0

Views: 641

Replies: 3

Related Articles