EAP653 disconnect/provisioning loop after loss of power
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.EAP653 disconnect/provisioning loop after loss of power
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello all,
I currently want to equip the site with EAP653 APs and have already installed them everywhere.
However, if I disconnect one of the APs from the power to connect them somewhere else or because of a power failure etc. then the EAP is in the Omada controller as offline, then as provisioning and so on.
The only way to fix this is to reset the device and set it up again.
This is simply not an option with the amount of devices used.
I ask for a timely solution, otherwise we exchange all devices for devices from other manufacturers.
Router: ER605 v1.0 1.2.1 Build 20220512 Rel.76748
Controller: OC200 1.0 1.21.7 Build 20221206 Rel.58608
This is an intolerable state of affairs.
Best regards
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello @Vinsen,
Please confirm whether the EAP225 fall into adoption loop (loop in adopting-> configuring-> heartbeat missed-> disconnected) or stuck in "Disconnected" state after you do a physical reboot.
Did this issue happen when the EAPs were in the DFS Channel (120, 124, or 128)?
- Copy Link
- Report Inappropriate Content
@aurevo Hi,
I own a OC_200 with two EAP 653 Access Points. I had the problem with the loop as well when I set up my first EAP 653.
I don't know exactly what fixes the problem, but I did this:
1. Physically disconnect OC_200 (cold reboot / Power off)
2. Forget Device in Omada
3. Reboot Acess Points once (or twice) and Re-Provision in Omada
After this, the problem dissapeared, and didn't reappear on any of the two EAP access points.
OC 200 Omada HW Controller Version: 5.9.32
EAP Access Point Firmware Version 1.0.6
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2172
Replies: 12
Voters 0
No one has voted for it yet.