OC300 cannot adopt EAP670
I suddenly have problems adopting my 3 APs throuch the controller Web UI.
My APs are all
EAP670 1.0
Firmware: 1.1.1 Build 20250326 Rel. 61737(4555)
- I have a management network on vlan 100
- I have configured the port on the switch that wires directly to the AP with "All" profile.
- There no ACLs at all configured
- All Networks are interfaces with a specified vlan number
- I resetted all APs (web UI shows wizard)
- So currently no dedicated management vlan is set on the AP standalone config
- All devices can be reached by ping (also intermediate switches)
- My topology is
- Router
- Controller
- Switch MAIN
- Switch AP
- AP 1
- AP 2
- AP 3
- Switch AP
- Router
When I am in the user vlan (different than management) with my workstation I can ping the APs, but I cannot reach the UI of the APs. When I am in the Management network with my workstation I can ping and reach the web ui.
The APs pop up in the list of devices as PENDING, but when I try to adopt the adoption fails because "the AP dis not react to adoption commands".
If I go through the wizard and set the controller ip in the APs settings, I first get an adoption error because of the uasername/password (expected), if then enter them in the window in the controller ui, i get the same error as above.
This setup worked for > 2 years. suddenly connection to the APs where broken, I tried to forget them and re-provision and now i am in this situation.
What can I do to solve this? How can I debug?
I restarted every device in the network, all firmwares are up to date.
The APs get a ip from the management network (vlan=100, management vlan).
The ports on which the APs a wired are configured with "All" Profile.
There are only Omada components in the network and they are all configured by the controller.
There is no ACL configured for Gateway, Switch, AP.
The AP in its standalone settings has no management vlan configured, if I do that they become inaccessible, I guess because although controller and AP has both management network ips, the vlan flag is not set, but it is management network by beeing untagged.
There are 2 more APs which I currently have deactivated because they are open otherwise.
Controller gets an IP from the management network. It is on a router lan port with the following settings:
The whole experience happens equally on different client workstations. There is no Anti-Virus Software and only totally standard Windows Firewall.