納管 EAP 是批次管理 EAP 的第一步。完成納管後，控制器上的所有設定將套用至所有納管的 EAP 當中。了解關於納管 Omada EAP

本文介紹如何透過不同方式在 Local 端或遠端納管 EAP，參考 FAQ 協助解決在納管過程中可能遇到的問題。

若要透過有線連線納管 EAP，請依照以下說明操作。

注意：以下將已基本架構範例來說，使用 EAP 與控制器位於同一子網路中。

1. Choose a Method

選擇集中管理平台類型來管理 EAP，並選擇管理設備的平台。若要了解如何根據您的需求進行選擇，請參閱Omada EAP 網路的管理方式。

管理平台

Omada 軟體控制器和 Omada 雲端控制器都可以用來管理 EAP。

圖 1 選擇管理平台

說明：

1) Omada 軟體控制器僅支援 Windows 和 Linux 系統。對於其他操作系統，建議在電腦上安裝虛擬機，這樣就可以在虛擬機上安裝運作 Omada 軟體控制器。

2) 本文以 Windows 系統為例。若是 Linux 系統，請參考檔案下載中的使用者指南。

管理裝置

管理裝置是用來登入控制器介面的裝置。控制器可以在電腦（網頁介面）和行動裝（Omada App）上使用。

圖 2 選擇管理設備

說明：

1) 若要透過電腦登入，建議使用最新版本的 Google Chrome、Firefox、IE 或 Safari。

2) 若要透過行動裝置登入，請先下載 Omada App。

2. Build the Topology

依據您使用的存取方式和方法，以下介紹 Local 端或遠端納管 EAP 的網路拓樸。

Local 納管 EAP 的網路拓樸

圖 3 和圖 4 顯示了 Local 管理 EAP 的網路拓樸。EAP 已開機，且路由器作為 DHCP 伺服器，為 EAP 指派 IP 位址。

圖 3 透過電腦 Local 管理 EAP 的拓樸

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

3. Adopt EAPs with a Wired Connection Locally

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.

4. Adopt EAPs with a Wired Connection Remotely

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.

5.(Optional)Adopt EAPs with the Mesh Function

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