Adopt AP to Omada controller in Local host window server
Adopt AP to Omada controller in Local host window server
Hi,
when I connect my TP link AP with the same IP, I can adopt it through the controller. But when I installed the controller in local window server (IP is not the same with the TP link AP getting AP), I can't see my AP in pending state of controller. How can I adopt and inform my AP to it's controller.
1 Accepted Solution
Re:Adopt AP to Omada controller in Local host window server
The controller IP and EAP245 can ping each other. EAP can be discovered when it has the same IP with controller, but when I changed port to get 10.0.72.73 for EAP, it showed "disconnected" in controller and I can't see connected anymore. In Ubiquiti, we put set-inform cmd in ssh to find it's unifi controller. But in EAP Omada controller, we can't put set-inform cmd.
