How to adopt EAP in Controller Mode?
EAP adoption is the first step to manage EAPs in batches. Once adopted, all configurations on the controller will be applied to all managed EAPs. Learn more about EAP Adoption
This article introduces how to adopt EAPs locally or remotely using different methods and lists Related FAQs to help solve problems that may arise during adoption.
To adopt EAPs with a wired connection, follow the instructions below.
Note: To take a basic example, EAPs are assumed to be in the same subnet with the controller.
Choose a management platform to manage the EAPs and a management device to log in to the platform. To learn how to choose one based on your needs, refer to Methods for Managing Omada EAPs Network.
Management Platform
Both Omada Software Controller and Omada Cloud Controller can be used to manage EAPs.
Figure 1 Choose a Management Platform
Note:
1) Omada Software Controller only supports the Windows and Linux systems. For other operation systems, you are recommended to install a virtual machine on the computer so that you can run Omada Software Controller on it.
2) This article takes the Windows system as an example. For the Linux system, refer to User Guide in the Download Center.
Management Device
Management devices are the devices used to log in to the controller. Controllers are both available for computers and mobile devices.
Figure 2 Choose a Management Device
Note:
1) To log in via a computer, you are recommended to use the latest version of Google Chrome, Firefox, IE or Safari.
2) To log in via a mobile device, download the Omada app first.
Based on the access way and method you use, the following introduces network topologies for adopting EAPs locally or remotely.
Network Topology for Adopting EAPs Locally
Figure 3 and Figure 4 show the topologies for managing EAPs locally. EAPs are powered on, and a router acts as a DHCP server to assign IP addresses to them.
Figure 3 Topology for Managing EAPs Locally via a Computer
Figure 4 Topology for Managing EAPs Locally via a Mobile Device
According to the controller you use, notice that:
(For Omada Software Controller) The controller should be running on a computer in the same subnet with EAPs. The computer is called Controller Host which can also be used as a management computer.
(For Omada Cloud Controller) The controller should be powered on and in the same subnet with EAPs. Power LED will be on when the Cloud Controller is powered on
→ Next step: Adopt EAPs with a Wired Connection Locally
Network Topology for Adopting EAPs Remotely
The network topology is shown as below.
Figure 5 Topology for Managing EAPs Remotely
→ Next step: Adopt EAPs with a Wired Connection Remotely
Follow the instructions below to launch the management page and adopt EAPs locally.
Step 1 Launch the Management Page Locally
-
Via a computer
(For Omada Software Controller) Double click the software icon and wait for a while to open the web browser. Then enter the username and password and click Log in to launch the controller.
(For Omada Cloud Controller) Launch a web browser, enter the controller’s IP address in the address bar and press Enter (Windows) or Return (Mac). Then enter the username and password and click Log in to launch the controller.
Note:
1) By default, the username and password are both admin.
2) To get the IP address of Omada Cloud Controller, check the DHCP server (typically a router).
Figure 6 Log in via a Computer Locally
-
Via a mobile device
1) Connect your mobile device to the EAP’s wireless network
Find the default SSID (format: TP-Link 2.4GHz/5GHz_XXXXXX) printed on the label at the bottom of the EAP, and connect your mobile device to the EAP’s wireless network using the default SSID.
2) Log in to the controller
Open the Omada app, tap Local Access at the bottom and wait for the controller to be discovered. Then tap the controller and enter the username and password to launch the controller. By default, the username and password are both admin.
If the controller cannot be found, tap + on the upper-right corner and enter its IP address and port to add the controller manually.
Note: A DHCP server is needed as shown in Build the Topology to allocate an IP address to the EAP. Therefore, you can connect the mobile device to the EAP’s wireless network and find the controller’s IP address on the DHCP server.
Step 2 Adopt EAPs
For the first time to log in to the controller via a computer, follow the setup wizard and select EAPs to be adopted in AP Configuration. The controller will automatically adopt the selected EAPs using the default username and password (both are admin).
For other situations, follow the instructions below to adopt EAPs manually.
-
Via a computer
Go to Access Points > Pending to open the Pending list. Then click the Adopt icon in the corresponding entry.
Figure 7 Adopt EAPs via a Computer Locally
-
Via a mobile phone
Tap APs to view the EAP list. Then tap the Pending EAP and tap Adopt to adopt it.
Figure 8 Adopt EAPs via a mobile device locally
Note: If the EAP is in the Managed By Others status, it means the EAP has been managed by an existing controller. Before adopting it by the current controller, use the username and password to unbind it from the existing controller or just press the reset button to reset the EAP.
For other problems during adoption, refer to Related FAQs.
Follow the instructions below to launch the management page and adopt EAPs remotely.
Step 1 Launch the management page remotely
-
Via a computer
Follow the setup videos to launch the management page via a computer remotely.
For Omada Software Controller:
For Omada Cloud Controller:
-
Via a mobile device
Follow the instructions below to launch the management page.
For Omada Software Controller:
1) Follow the video below (00:43–01:43) to install the controller and bind your TP-Link ID to the controller.
2) Connect your mobile device to the internet. Open the Omada app, log in with the TP-Link ID which is bound to the controller. Then tap Cloud Access and tap the controller entry to launch it.
For Omada Cloud Controller:
Step 2 Adopt EAPs
-
Via computer
Go to Access Points > Pending to open the Pending list. Then click the Adopt icon in the corresponding entry.
Figure 9 Adopt EAPs via a Computer Remotely
-
Via a mobile phone
Tap APs to view the EAP list. Then tap the Pending EAP and tap Adopt to adopt it.
Figure 10 Adopt EAPs via a Mobile Device Remotely
Note: If the EAP is in the Managed By Others status, it means the EAP has been managed by an existing controller before. Use the username and password to unbind it from the existing controller and then adopt it to the current controller.
For other problems during adoption, refer to Related FAQs.
Mesh is used to expand a wired network through a wireless connection on 5GHz radio band. After mesh network establishes, the EAP devices can be configured and managed within Omada Controller in the same way as wired EAPs. Learn more about Mesh Network
Note: EAP225-Outdoor with firmware version 1.3 or above and EAP225 V3 with firmware version 2.5.0 or above are available for mesh function currently. Only the EAPs in the same site can establish a mesh network.
The topology below shows a basic mesh network with 2 EAPs managed by Omada Controller locally. The controller and EAPs are in the same subnets and get IP addresses from a router. EAP 1 is adopted by the switch with a wired connection, while EAP 2 supporting the Mesh function needs to expand a wired network through a wireless connection.
Figure 11 Basic Topology for the Mesh Network
After adopting EAP 1, power on EAP 2 and follow the steps below to adopt it via a computer or mobile device.
Via a computer
When EAP 2 is discovered by the controller, it may be in the Pending or Isolated status based on its settings.
If EAP 2 remains factory default settings, it will be in the Pending status. To adopt it, log in to the controller, go to Access Points > Pending to open the Pending list and click Adopt. The controller will connect it to an Uplink AP automatically.
Figure 12 Adopt EAPs with factory settings in the PendingStatus via computer
If EAP 2 that has been adopted by the controller before connects to the controller wirelessly, it will be in the Isolatedstatus when discovered by the controller again. To adopt it, go to Access Points > Isolated to open the Isolated list and click
Figure 13 EAPs in the IsolatedStatus
The following page will pop up. Go to Mesh and then click Link to connect the EAP to an Uplink AP.
Figure 14 Connect the EAP to an Uplink AP
Via a mobile device
Log in to the controller. Tap APs at the bottom to view the EAP list. Then tap the EAP to adopt it.
If the EAP has factory default settings, tap Adopt and then it will be connected to the Uplink AP automatically.
Figure 15 Adopt EAPs in the PendingStatus via a Mobile Device
If not, scroll down to Connection, tap Uplink (Wireless) and select an uplink AP in the list to connect the EAP to the selected AP.
Figure 16 Adopt EAPs in the IsolatedStatus via a Mobile Device
Related FAQs
What should I do when the controller fails to discover the EAP?
What should I do if Omada Software Controller/OC200 cannot adopt Omada EAP?
Is this faq useful?
Your feedback helps improve this site.
TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.