EAP245 and 225 stuck at "ADOPTING" after power cycle on SDN v5

EAP245 and 225 stuck at "ADOPTING" after power cycle on SDN v5
EAP245 and 225 stuck at "ADOPTING" after power cycle on SDN v5
2022-02-23 15:01:21 - last edited 2022-02-25 20:21:20
Model: EAP245
Hardware Version: V3
Firmware Version: 5.0.4

After upgrading my Controller to v5.0.30 everything appeared to be working normally, until a brief power failure at one of my EAP245s caused it to reboot. At this point it appeared in the Devices list as "ADOPTING", and remained like this for 5 solid days.

 

I checked the Forum here and saw the "Adopting and provisioning loop" thread. The device never says "Provisioning" and I am on x.30 so I don't think this is relevant, but I made sure AI Roaming was off anyway. This didn't help, so I rebooted my controller VM, and now oth my EAP 245s and single EAP 225 are stuck at "ADOPTING" and have been for over 24 hours. My lonely EAP235 Wall mount is the only WAP that is connected.

 

Devices can still connect to the EAPs just fine and from a user point of view there is no apparent issue, but of course none of these clients show up in the controller, and I cannot make any adjustments to my SSIDs or VLANs.

 

What further steps can I take to resolve this?

 

Omada is running on a dedicated Ubuntu 20.04 server instance, on the same subnet as the Management VLan that was set on my EAPs and Switches. Incidentally, all three of my switches are connected just fine. Three different models.

0
0
#1
Options
1 Accepted Solution
Re:EAP245 and 225 stuck at "ADOPTING" after power cycle on SDN v5-Solution
2022-02-24 02:00:28 - last edited 2022-02-25 20:21:20
Just in case, make sure port 29814 is not blocked. Omada V5 is using 29814 to adopt the devices, while old version only use 29810-29813.
Recommended Solution
0
0
#2
Options
2 Reply
Re:EAP245 and 225 stuck at "ADOPTING" after power cycle on SDN v5-Solution
2022-02-24 02:00:28 - last edited 2022-02-25 20:21:20
Just in case, make sure port 29814 is not blocked. Omada V5 is using 29814 to adopt the devices, while old version only use 29810-29813.
Recommended Solution
0
0
#2
Options
Re:EAP245 and 225 stuck at "ADOPTING" after power cycle on SDN v5
2022-02-25 20:21:35 - last edited 2022-02-25 20:22:30

  @Somnus 

 

Thanks! That was the issue. All EAP units are connected and the clients and statistics are showing up again.

0
0
#3
Options