Home » TP-Link Manuals » Networking » TP-Link EAP225-Wall » Manual Viewer

TP-Link EAP225-Wall Omada Controller Software 3.1.13 User Guide - Page 55

other APs is Uplink AP. A Root AP or an intermediate AP can be the Uplink AP. And the AP

View all TP-Link EAP225-Wall manuals

Add to My Manuals
Save this manual to your list of manuals

Page 55 highlights

and managed within Omada controller in the same way as wired EAPs. Meanwhile, because of the ability to self-organize and self-configure, mesh also can efficiently reduce the configuration overhead. Note •• Only EAP225-Outdoor with specific firmware (version 1.3 or above) is available for mesh function currently. •• Only the EAPs in the same site can establish a mesh network. To understand how mesh can be used, the following terms used in Omada Controller will be introduced: ■■ Root AP: The AP is managed by Omada Controller with a wired data connection that can be configured to relay data to and from mesh APs (Downlink AP). ■■ Isolated AP: When the EAP which has been managed before by Omada Controller connects to the network wirelessly and cannot reach the gateway, it goes into the Isolated state. ■■ Mesh AP: An isolated AP will be mesh AP after establishing a wireless connection to the AP with network access. ■■ Uplink AP/Downlink AP: Among mesh APs, the AP that offers the wireless connection for other APs is Uplink AP. A Root AP or an intermediate AP can be the Uplink AP. And the AP that connects to the Uplink AP is called Downlink AP. An uplink AP can offer direct wireless connection for 4 Downlink APs at most. ■■ Wireless Uplink: The action that a Downlink AP connects to the uplink AP. ■■ Hops: In a deployment that uses a root AP and more than one level of wireless uplink with intermediate APs, the uplink tiers can be referred to by root, first hop, second hop and so on. The hops cannot be more than 3. In a basic mesh network as shown below, there is a root AP that is connected by Ethernet cable, while other isolated APs have no wired data connection. Mesh allows the isolated APs to communicate with pre-configured root AP on the network. Once powered up, factory default or unadopted EAPs can sense the EAP in range and make itself available for adoption within the Omada controller. 49

Section	Page
1 Quick Start	7
1.1 Determine the Network Topology	8
1.1.1 Management on the local Network	8
1.1.2 Management via Cloud Access	10
1.2 Install Omada Controller Software	11
1.2.1 Installation on Windows Host	11
1.2.2 Installation on Linux Host	11
1.3 Inform the EAPs of the Controller Host's Address	13
1.4 Start and Log In to the Omada Controller	14
1.4.1 Launch Omada Controller	14
1.4.2 Do the Basic Configurations	15
1.4.3 Log In to the Management Interface	18
1.5 Create Sites and Adopt EAPs	18
1.5.1 Create Sites	19
1.5.2 Adopt the EAPs	21
1.6 Monitor and Manage the EAPs	22
2 Monitor and Manage the Network	24
2.1 View the Statistics of the Network	25
2.1.1 View the Client Distribution on SSID	25
2.1.2 Have a Quick Look at EAPs and Clients	25
2.1.3 View Current Usage-Top EAPs	26
2.1.4 View Recent Activities	26
2.2 Monitor the Network with the Map	27
2.2.1 Add a Map	27
2.2.2 Monitor the EAPs on the Map	30
2.3 Monitor and Manage the EAPs	31
2.3.1 Manage the EAPs in Different Status	31
2.3.2 View the Detailed Information of EAPs	32
2.3.3 Manage the EAPs in the Action Column	32
2.4 Monitor and Manage Clients	34
2.4.1 View the Current Information of Clients	34
2.4.2 Manage Clients in the Action Column	34
2.5 View Clients Statistics During the Specified Period	35
2.5.1 Select a Specified Period	35
2.5.2 View the History Information of Clients	36
2.5.3 Manage Clients in the Action Column	36
2.6 Manage the Rogue APs List	36
2.6.1 Manage the Untrusted Rogue APs List	37
2.6.2 Manage the Trusted Rogue APs List	37
2.7 View Past Guest Authorization	38
2.8 View Logs	38
3 Configure the EAPs Globally	40
3.1 Wireless Network	41
3.1.1 Add Wireless Networks	41
3.1.2 Configure Advanced Wireless Parameters	51
3.1.3 Configure Band Steering	53
3.1.4 Configure Mesh	54
3.2 Access Control	59
3.3 Portal Authentication	60
3.3.1 No Authentication	61
3.3.2 Simple Password	65
3.3.3 Local User	69
3.3.4 Voucher	77
3.3.5 SMS	84
3.3.6 Facebook	89
3.3.7 External RADIUS Server	90
3.3.8 External Portal Server	96
3.4 Free Authentication Policy	97
3.5 MAC Filter	98
3.6 Scheduler	100
3.7 QoS	102
3.8 Site Settings	105
3.8.1 LED	105
3.8.2 Device Account	105
3.8.3 Reboot Schedule	106
3.8.4 Log Settings	106
3.8.5 Batch Upgrade	108
3.8.6 SSH	110
3.8.7 Management VLAN	111
4 Omada Cloud Service	112
4.1 Configure the Cloud Access	113
4.1.1 Enable Cloud Access	113
4.1.2 Manage the Cloud Users	113
4.2 Manage the Controller via Omada Cloud	115
4.2.1 Access the controller via Omada Cloud	116
4.2.2 Change your TP-Link ID information	118
5 Configure the EAPs Separately	119
5.1 View the Information of the EAP	120
5.1.1 Active Channel Information	120
5.1.2 Overview	121
5.1.3 LAN	121
5.1.4 Radio	122
5.2 View Clients Connecting to the EAP	122
5.2.1 User	122
5.2.2 Guest	123
5.3 View Mesh Information of the EAP	123
5.3.1 Uplinks	123
5.3.2 Downlinks	124
5.4 Configure the EAP	124
5.4.1 Basic Config	124
5.4.2 IP Setting	125
5.4.3 Radio	126
5.4.4 Load Balance	127
5.4.5 WLANs	128
5.4.6 LED	128
5.4.7 Trunk Settings (Only for EAP330)	129
5.4.8 Rogue APs Detection	129
5.4.9 Local LAN Port Settings (Only for EAP115-Wall and EAP225-Wall)	130
5.4.10 Forget this AP	130
6 Manage the Omada Controller	131
6.1 User Account	132
6.2 General Setting	133
6.2.1 Configure Controller Name	133
6.2.2 Configure Mail Server	133
6.3 History Data Retention	135
6.4 Backup&Restore	136
6.5 Auto Backup	136
6.6 Migrate	139
6.6.1 Controller Migrate	139
6.6.2 Site Migrate	143
6.7 Information About the Software	147
7 Application Example	148
7.1 Basic Configuration	149
7.2 Advanced Settings	149
7.2.1 Monitor the EAPs with Map	149
7.2.2 Configure Portal Authentication	150
7.2.3 Create a SSID for the Employees	152
7.2.4 Configure Scheduler	153
Appendix: Omada App	155
1 Install Omada App on the Mobile Device	156
2 Manage your Network in Standalone Mode	156
3 Manage your Network in Controller Mode	159
3.1 Locally manage your EAPs using the Omada App	159

Match case Limit results 1 per page

and managed within Omada controller in the same way as wired EAPs. Meanwhile, because of

the ability to self-organize and self-configure, mesh also can efficiently reduce the configuration

overhead.

²NtTs

•

Only EAP225-Outdoor with specific firmware (version 1.3 or above) is available for mesh function currently.

•

Only the EAPs in the same site can establish a mesh network.

To understand how mesh can be used, the following terms used in Omada Controller will be

introduced:

■

Root AP: The AP is managed by Omada Controller with a wired data connection that can be

configured to relay data to and from mesh APs (Downlink AP).

■

Isolated AP: When the EAP which has been managed before by Omada Controller connects to

the network wirelessly and cannot reach the gateway, it goes into the Isolated state.

■

Mesh AP: An isolated AP will be mesh AP after establishing a wireless connection to the AP with

network access.

■

Uplink AP/Downlink AP: Among mesh APs, the AP that offers the wireless connection for

other APs is Uplink AP. A Root AP or an intermediate AP can be the Uplink AP. And the AP

that connects to the Uplink AP is called Downlink AP. An uplink AP can offer direct wireless

connection for 4 Downlink APs at most.

■

Wireless Uplink: The action that a Downlink AP connects to the uplink AP.

■

Hops: In a deployment that uses a root AP and more than one level of wireless uplink with

intermediate APs, the uplink tiers can be referred to by root, first hop, second hop and so on.

The hops cannot be more than 3.

In a basic mesh network as shown below, there is a root AP that is connected by Ethernet

cable, while other isolated APs have no wired data connection. Mesh allows the isolated APs to

communicate with pre-configured root AP on the network. Once powered up, factory default or

unadopted EAPs can sense the EAP in range and make itself available for adoption within the

Omada controller.