Omada Controller 5.3.1 not adopting EAP225 firmware 5.0.7 devices

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

Omada Controller 5.3.1 not adopting EAP225 firmware 5.0.7 devices

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Omada Controller 5.3.1 not adopting EAP225 firmware 5.0.7 devices
Omada Controller 5.3.1 not adopting EAP225 firmware 5.0.7 devices
2022-05-25 20:01:15
Model: EAP225  
Hardware Version: V3
Firmware Version: 5.0.7

My Omada Software Controller (on a Raspberry Pi) upgraded to version 5.3.1.

The 2 devices I have that are on firmware 5.0.7 are not adopting anymore.
Their status is alternating between provisioning and adopting.

How can I fix this?

  0      
  0      
#1
Options
9 Reply
Re:Omada Controller 5.3.1 not adopting EAP225 firmware 5.0.7 devices
2022-05-25 20:03:28

Here are some screenshots:

 

https://www.dropbox.com/scl/fi/qloofqkq8lnamjkryea6o/Omada.paper?dl=0&rlkey=50nlzqjyoh66fds62ba6eo4zn

  0  
  0  
#2
Options
Re:Omada Controller 5.3.1 not adopting EAP225 firmware 5.0.7 devices
2022-05-25 20:28:38 - last edited 2022-05-25 20:32:20

  @FlashWeave 

 

Do you run in a docker? you need to open TCP 29814 or if you have controller in another VLAN or port NATed in to controller from remote site

 

they have change two ports without it being documented very well.
TCP 29814 for adoption
Software controller TCP 8043 and TCP 443 OC200 / OC300 For firmware update

 

  0  
  0  
#3
Options
Re:Omada Controller 5.3.1 not adopting EAP225 firmware 5.0.7 devices
2022-05-25 21:00:50

  @shberge yes, I use https://github.com/mbentley/docker-omada-controller

 

It exposes port 29814: https://github.com/mbentley/docker-omada-controller/blob/master/Dockerfile.v5.3.x

  0  
  0  
#4
Options
Re:Omada Controller 5.3.1 not adopting EAP225 firmware 5.0.7 devices
2022-05-25 21:08:03

  @FlashWeave 

 

Ok, try to telnet from windows command prompt from network where the device is, use this command 

telnet ip to controller 29814 eg. telnet 192.168.1.2 29814

 

if there answer on this port all ok

  0  
  0  
#5
Options
Re:Omada Controller 5.3.1 not adopting EAP225 firmware 5.0.7 devices
2022-06-21 19:50:48

  @shberge thank you for trying to help me.  This is my result: the test succeeded: https://www.dropbox.com/s/35udiil8m42m7nc/rJZzIYOSXA.png?dl=0

  0  
  0  
#6
Options
Re:Omada Controller 5.3.1 not adopting EAP225 firmware 5.0.7 devices
2022-06-22 05:47:44

  @FlashWeave 

 

Ok, and you still have problem with adoption?

 

  0  
  0  
#7
Options
Re:Omada Controller 5.3.1 not adopting EAP225 firmware 5.0.7 devices
2022-06-22 06:02:01

  @shberge yes, the exact same 2 devices are still "provisioning" or "adopting" all the time. 

  0  
  0  
#8
Options
Re:Omada Controller 5.3.1 not adopting EAP225 firmware 5.0.7 devices
2022-06-22 09:35:00

  @FlashWeave 

 

Strange!! And your controller ip is 192.168.0.101?

  0  
  0  
#9
Options
Re:Omada Controller 5.3.1 not adopting EAP225 firmware 5.0.7 devices
2022-06-22 13:17:35

Yes 192.168.0.101 is the IP adress of the physical device the Omada controller is on (=a Raspberry Pi).

 

  0  
  0  
#10
Options

Information

Helpful: 0

Views: 1088

Replies: 9

Related Articles