1. You should bind the Omada Controller with the TP-Link ID first.

2. Log in to the cloud platform (omada.tplinkcloud.com) with corresponding TP-Link ID (Or use Omada APP). Then we can access the management page of Omada Controller in the cloud, monitor and manage Controller/EAP in real time.

 

You can refer to: https://community.tp-link.com/en/business/forum/topic/150541?page=1 and https://community.tp-link.com/en/business/forum/topic/150133?page=1

 

Dear Jonas,

 

Yhank you for the answer. I think some is going wrong. In the controller i can not see the EAP. 

Now i have acces with the mobile app to my controller, bur there is the EAP 225 not to see.

How can i connect the EAP (who i have installed via the webinterface) in the controller?

 

Mark

I think the problem is that your Controller did not manage EAP, so you can't see the EAP on the cloud via Omada Controller.

 

If the EAP and Controller locate in same subnet, you can see it in the pending list of Controller, then you can adopt it directly. If the EAP and Controller locate in different subnet, you should use Discovery Utility or DHCP Option 138 to tell the IP address of Controller to EAP first, then EAP will show up in the pending list of Contorller. You can refer to this Configuration guide: https://www.tp-link.com/en/configuration-guides/configuration_guide_for_managing_eaps_via_eap_controller/?configurationId=2969

Hi Mark, you may tell us about your topology first. Where do you place your EAP and controller? Are they in the same subnet or different subnet?