TP-LINK Omada SDN Controller - Joystick

Omada SDN Controller - Joystick TP-LINK - Free user manual and instructions

Find the device manual for free Omada SDN Controller TP-LINK in PDF.

📄 512 pages English EN Download 💬 AI Question 10 questions ⚙️ Specs
Notice TP-LINK Omada SDN Controller - page 9
Pick your language and provide your email: we'll send you a specifically translated version.
Product Type Omada SDN Controller
Brand TP-Link
Model Omada SDN Controller (Software, Hardware, or Cloud-Based)
Dimensions (Hardware Controller) Approximately 5.0 x 3.0 x 1.0 inches
Weight (Hardware Controller) Approximately 0.5 lbs
Power Supply (Hardware Controller) PoE (802.3af) or DC adapter (5V/1A)
Supported Devices Omada Gateways, Switches, and Access Points
Management Capabilities Centralized configuration, monitoring, and management of network devices
Deployment Options Software (Windows/Linux), Hardware (OC200/OC300), Cloud-Based
Number of Managed Devices Up to 500 devices per site (varies by controller version and license)
Supported Sites Unlimited sites per controller
Wireless Features Fast Roaming, Band Steering, AI Roaming, Mesh support
Security Features ACL, URL Filtering, MAC Filtering, Attack Defense, Firewall, IDS/IPS
VPN Support IPsec, OpenVPN, PPTP, L2TP, WireGuard
Authentication Methods Portal, 802.1X, MAC-Based Authentication
Maintenance Backup, restore, firmware upgrade via controller interface
Cleaning Wipe with a dry cloth; avoid liquids
Safety Operate in a well-ventilated area; avoid exposure to moisture
Spare Parts & Repairability No user-serviceable parts; contact TP-Link support for repairs
Quiet Operation Fanless design (hardware controller) ensures silent operation

Frequently Asked Questions - Omada SDN Controller TP-LINK

What is the Omada SDN Controller?
The Omada SDN Controller is a centralized management platform for TP-Link Omada devices, including gateways, switches, and access points. It allows you to configure and monitor your entire network from a single interface.
How do I install the Omada Software Controller?
Download the installation file from the TP-Link support site. For Windows, run the installer. For Linux, install using .tar.gz or .deb files after ensuring Java 8 and MongoDB are installed.
Can I access the controller remotely?
Yes, enable Cloud Access and bind a TP-Link ID to your controller. Then use the Omada app or web browser to access it via the cloud.
What devices are compatible with the controller?
The controller supports TP-Link Omada Gateways, Switches, and Access Points. Check the Omada Cloud SDN Platform Compatibility List for specific models.
How do I adopt devices to the controller?
Ensure devices are in the same LAN as the controller (or use Layer 3 techniques like DHCP Option 138). Go to the Devices page, and click the adopt button next to discovered devices.
What wireless features are supported?
The controller supports Fast Roaming, Band Steering, AI Roaming, and Mesh for seamless wireless connectivity.
How do I configure VPN on the controller?
Go to Settings > Transmission > VPN. You can set up IPsec, OpenVPN, PPTP, L2TP, or WireGuard tunnels for secure remote access.
Can I manage multiple sites with one controller?
Yes, you can create multiple sites within the controller. Each site can have its own configuration and devices, managed globally from the Global View.
Is there a mobile app for management?
Yes, the Omada app is available for iOS and Android. It supports both local and cloud access for monitoring and configuration on the go.
How do I back up the controller configuration?
Go to Settings > Maintenance > Backup. Click Backup to save the current configuration file, which can be restored later if needed.

User questions about Omada SDN Controller TP-LINK

0 question about this device. Answer the ones you know or ask your own.

Ask a new question about this device

The email remains private: it is only used to notify you if someone responds to your question.

No questions yet. Be the first to ask one.

Download the instructions for your Joystick in PDF format for free! Find your manual Omada SDN Controller - TP-LINK and take your electronic device back in hand. On this page are published all the documents necessary for the use of your device. Omada SDN Controller by TP-LINK.

USER MANUAL Omada SDN Controller TP-LINK

This User Guide provides information for centrally managing TP-Link devices via Omada SDN Controller. Please read this guide carefully before operation.

Intended Readers

This User Guide is intended for network managers familiar with IT concepts and network terminologies.

Conventions

When using this guide, notice that:

■ Features available in Omada SDN Controller may vary due to your region, controller version, and device model. All images, steps, and descriptions in this guide are only examples and may not reflect your actual experience.
■ The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied. Users must take full responsibility for their application of any products.
This guide uses the specific formats to highlight special messages. The following table lists the notice icons that are used throughout this guide.

In this guide, the following conventions are used:

Controller Stands for the Omada SDN Controller.

Gateway/Router Stands for the Omada Gateway/Router.

Switch Stands for the Omada Switch.

AP Stands for the Omada AP.

TP-LINK Omada SDN Controller - Conventions - 1

Note

The note contains the helpful information for a better use of the controller.

TP-LINK Omada SDN Controller - Conventions - 2

Configuration Guidelines

Provide tips for you to learn about the feature and its configurations.

More Information

■ For technical support, the latest version of the User Guide and other information, please visit https://www.tp-link.com/support/?type=smb.
■ To ask questions, find answers, and communicate with TP-Link users or engineers, please visit https://community.tp-link.com/business to join TP-Link Community.

CONTENTS

About this Guide

1. Omada SDN Controller Solution Overview

1.1 Overview....2
1.2 Core Components .... 3

2.Get Started with Omada SDN Controller

2.1 Set Up Your Software Controller....7

2.1.1 Determine the Network Topology....7
2.1.2 Install the Software Controller 8
2.1.3 Start and Log In to the Software Controller.... 10

2.2 Set Up Your Hardware Controller.... 15

2.2.1 Determine the Network Topology....15
2.2.2 Deploy the Hardware Controller....15
2.2.3 Start and Log in to the Controller 16

2.3 Set Up Your Cloud-Based Controller 20

3.Manage Omada Managed Devices and Sites

3.1 Create Sites....22
3.2 Adopt Devices.... 26

3.2.1 For Software Controller / Hardware Controller 26
3.2.2 For Cloud-Based Controller 37

4. Configure the Network with the SDN Controller

4.1 Navigate the UI 42
4.2 Modify the Current Site Configuration.... 47

4.2.1 Site Configuration....47
4.2.2 Services....48
4.2.3 Advanced Features 50
4.2.4 Device Account 53

4.3 Configure Wired Networks....54

4.3.1 Set Up an Internet Connection 54
4.3.2 Configure LAN Networks....74

4.4 Configure Wireless Networks....88

4.4.1 Set Up Basic Wireless Networks 88
4.4.2 Advanced Settings 95
4.4.3 WLAN Schedule....96
4.4.4 802.11 Rate Control....97
4.4.5 MAC Filter 98
4.4.6 Multicast/Broadcast Management 99
4.4.7 WLAN Optimization....100

4.5 Network Security....103

4.5.1 ACL 103
4.5.2 URL Filtering....113
4.5.3 MAC Filtering....116
4.5.4 Attack Defense 117
4.5.5 Firewall 121
4.5.6 IP-MAC Binding....123
4.5.7 IDS/IPS 125
4.5.8 Application Control....130

4.6 Transmission....134

4.6.1 Routing....134
4.6.2 NAT 137
4.6.3 Session Limit 142
4.6.4 Bandwidth Control....143
4.6.5 Gateway QoS 145
4.6.6 Switch OSPF 149
4.6.7 Switch QoS....151
4.6.8 VRRP 153

4.7 Configure VPN....156

4.7.1 VPN 156
4.7.2 VPN User....182
4.7.3 IPsec Failover 184
4.7.4 SSL VPN....185
4.7.5 WireGuard VPN 192

4.8 Create Profiles....195

4.8.1 Time Range 195
4.8.2 Groups 197
4.8.3 Rate Limit....199
4.8.4 PPSK 201
4.8.5 Gateway QoS Service 204
4.8.6 Bonjour Service....205
4.8.7 RADIUS Profile 205

4.8.8 LDAP Profiles 208
4.8.9 APN Profile....210

4.9 Authentication....212

4.9.1 Portal 212
4.9.2 802.1X....221
4.9.3 MAC-Based Authentication 224

4.10 Services....227

4.10.1 DHCP Reservation....227
4.10.2 Dynamic DNS 228
4.10.3 mDNS 231
4.10.4 SNMP 233
4.10.5 UPnP 234
4.10.6 SSH 234
4.10.7 Reboot Schedule 235
4.10.8 Port Schedule 236
4.10.9 IPTV....238
4.10.10 Upgrade Schedule 239
4.10.11 DNS Proxy 240
4.10.12 DNS Cache 241
4.10.13 Export Data 242

4.11 SIM....244

4.11.1 Statistics 244
4.11.2 SMS Message 246
4.11.3 SMS Settings 248

4.12 CLI Configuration....251

4.12.1 Site CLI 253
4.12.2 Device CLI 254

5. Configure the SDN Controller

5.1 System Settings 258

5.1.1 Controller Status 258
5.1.2 HTTPS Certificate 258
5.1.3 System Logging 260
5.1.4 Access Config....260

5.2 Controller Settings 263

5.2.1 General Settings.... 263
5.2.2 User Interface 266
5.2.3 Services....267
5.2.4 History Data Retention 268

5.2.5 Join User Experience Improvement Programm....269

5.3 Server Settings 270

5.3.1 Mail Server 270

5.3.2 Built-in RADIUS....271

5.3.3 Radius Proxy Server 272

5.4 Account Security......273

5.5 Cloud Access....274

5.6 Maintenance....276

5.6.1 Backup 276

5.6.2 Restore 278

5.6.3 Export for Support....280

5.6.4 Export Data 280

5.7 Migration....282

5.7.1 Site Migration....282

5.7.2 Controller Migration....287

6.Configure and Monitor Controller-Managed Devices

6.1 Introduction to the Devices Page 296

6.2 Configure and Monitor the Gateway....300

6.2.1 Configure the Gateway....300

6.2.2 Monitor the Gateway....313

6.3 Configure and Monitor Switches....314

6.3.1 Configure Switches 314

6.3.2 Monitor Switches 341

6.4 Configure and Monitor APs....345

6.4.1 Configure APs....345

6.4.2 Monitor APs 358

6.5 Create and Manage Stack Groups 371

6.5.1 Introduction to Stack 371

6.5.2 Create a Stack Group 371

6.5.3 Configure and Monitor the Stack Group 372

6.6 Create and Manage Bridge Groups....373

6.6.1 Introduction to Bridge 373

6.6.2 Create a Bridge Group 373

6.6.3 Configure and Monitor the Bridge Group.... 374

7. Monitor and Manage the Clients

7.1 Manage Wired and Wireless Clients in Clients Page 376

7.1.1 Introduction to Clients Page 376

7.1.2 Using the Clients Table to Monitor and Manage the Clients 376
7.1.3 Using the Properties Window to Monitor and Manage the Clients 378

7.2 Manage Client Authentication in Hotspot Manager 383

7.2.1 Dashboard 383
7.2.2 Authorized Clients 384
7.2.3 Vouchers 384
7.2.4 Local Users 389
7.2.5 Form Auth Data 393
7.2.6 Operators 393

8. Monitor the Network

8.1 View the Status of Network with Dashboard....397

8.1.1 Page Layout of Dashboard....397
8.1.2 Explanation of Widgets 399

8.2 View the Statistics of the Network 411

8.2.1 Performance 411
8.2.2 Application Analytics 417

8.3 Monitor the Network with Map 418

8.3.1 Topology 418
8.3.2 Heat Map....420
8.3.3 Device Map 425
8.3.4 Site Map 428

8.4 Monitor the Network with Reports 431

8.5 View the Statistics During Specified Period with Insight 433

8.5.1 Known Clients 433
8.5.2 Past Connections 434
8.5.3 Past Portal Authorizations 435
8.5.4 Switch Status 436
8.5.5 Port Forwarding Status 440
8.5.6 VPN Status 441
8.5.7 Routing Table 444
8.5.8 Dynamic DNS 445
8.5.9 Rogue APs 445

8.6 View and Manage Logs 448

8.6.1 Alerts 449
8.6.2 Events 450
8.6.3 Notifications 451

8.7 Monitor the Network with Tools 457

8.7.1 Network Check 457
8.7.2 Packet Capture 458
8.7.3 Terminal 459

9.Manage Accounts of the SDN Controller

9.1 Introduction to User Accounts....462
9.2 Create and Manage Custom Account Roles 462
9.3 Manage and Create Local User Accounts 464

9.3.1 Edit the Main Administrator Account....464
9.3.2 Create and Manage Other Local Accounts 464

9.4 Manage and Create Cloud User Accounts 467

9.4.1 Set Up the Cloud Main Administrator 467
9.4.2 Create and Manage Other Cloud Accounts 467

10.Manage Customer Networks in MSP Mode

10.1 Quick Start 471

10.1.1 Enable the MSP Mode 471
10.1.2 Add and Manage Customers 472
10. 1. 3 Assign and Manage Licenses....473
10. 1. 4 Add Sites and Devices.... 474

10.2 Add and Manage Accounts 475

10.2.1 Configure Role Settings....475
10.2.2 Manage the Main Administrator Account 477
10.2.3 Add New MSP User Accounts 478

10.3 Manage System Settings....481

10.3.1 Configure MSP Settings 481
10.3.2 Export for Support 486
10.3.3 Export Data 486

11.Configure Platform Integration

11.1 Open API 489

Appendix 1: Omada APP

1 Install Omada App on the Mobile Device 492
2 Manage Your Network in Standalone Mode 492
3 Manage Your Network in Controller Mode 495

3.1 Locally Manage Your Devices Using the Omada App....495
3.2 Remotely Manage Your Devices Using the Omada App 498

1

Omada SDN Controller Solution Overview

Omada SDN Controller Solution offers centralized and efficient management for configuring enterprise networks comprised of security gateways, switches, and wireless access points.

With a reliable network management platform powered by TP-Link Omada SDN Controller, you can develop comprehensive, software-defined networking across demanding, high-traffic environments with robust wired and wireless solutions.

The chapter includes the following sections:

• 1.1 Overview
• 1.2 Core Components

TP-LINK Omada SDN Controller - Omada SDN Controller Solution Overview - 1

1.1 Overview

Omada SDN Controller Solution is designed to provide business-class networking solutions for demanding, high-traffic environments such as campuses, hotels, malls, and offices. It simplifies deploying and managing large-scale enterprise networks and offers easy maintenance, ongoing monitoring, and flexible scalability.

This figure shows a sample architecture of an Omada SDN enterprise network:

TP-LINK Omada SDN Controller - Overview - 1

flowchart
graph TD
    subgraph Site_C
        A["AP"] -->|68888| B["Switch"]
        C["AP"] -->|68888| B
        B --> D["Router"]
        D --> E["OMoão SDN Controller"]
    end

    subgraph Site_B
        F["AP"] --> G["Switch"]
        H["AP"] --> G
        G --> I["Router"]
        I --> J["Switch"]
        J --> K["AP APAP"]

    subgraph Site_A
        L["AP"] --> M["Switch"]
        N["AP"] --> M
        M --> O["Router"]
        O --> P["Switch"]
        P --> Q["AP APAP"]

    subgraph Site_D
        R["AP"] --> S["Switch"]
        T["AP"] --> S
        S --> U["Router"]
        U --> V["Switch"]
        V --> W["AP APAP"]

    end

    style Site_C fill:#f9f,stroke:#333
    style Site_B fill:#f9f,stroke:#333
    style Site_A fill:#f9f,stroke:#333
    style Site_D fill:#f9f,stroke:#333
    style Site_E fill:#f9f,stroke:#333

The interconnected elements that work together to deliver a unified enterprise network include: SDN Controller, gateways, switches, access points, and client devices. Beginning with a base of client devices, each element adds functionality and complexity as the network is developing, interconnecting with the elements above and below it to create a comprehensive, secure wired and wireless solution.

The SDN Controller is a command center and management platform at the heart of the network. With a single platform, the network administrators configure and manage enterprise networks comprised of routers, switches, and wireless access points in batches. This unleashes new levels of management to avoid complex and costly over-provisioning.

1.2 Core Components

An Omada SDN network consists of the following core components:

■ SDN Controller — A command center and management platform at the heart of network solution for the enterprise. With a single platform, the network administrators configure and manage all Omada products which have all your needs covered in terms of routing, switching and Wi-Fi.
■ Gateways — Boast excellent data processing capabilities and an array of powerful functions, including IPsec/OpenVPN/PPTP/L2TP VPN, Load Balance, and Bandwidth Control, which are ideal for the business network where a large number of users require a stable, secure connection.
■ Switches — Offer flexible and cost-effective network solution with powerful Layer 2 features and PoE options. Advanced features such as Access Control, QoS, LAG and Spanning Tree will satisfy advanced business networks.
■ Access Points — Satisfy the mainstream Wi-Fi Standard and address your high-density access needs with TP-Link's innovation to help you build the versatile and reliable wireless network for all business applications.

SDN Controller

Tailored to different needs and budgets, Omada SDN Controller offers diverse deployment solutions. Omada Software Controller, Hardware Controller, and Cloud-Based Controller each has their own set of advantages and applications.

■ Omada Software Controller

Omada Software Controller can be hosted on any computers with Windows or Linux systems on your network.

TP-LINK Omada SDN Controller - SDN Controller - 1

flowchart
graph TD
    A["Internet"] --> B["SafeStream Gateway"]
    B --> C["JetStream Switch"]
    D["Software Controller"] --> C
    C --> E["Access Points"]

■ Omada Hardware Controller

Omada Hardware Controller is the management device which is pre-installed with Omada Software Controller. You just need to purchase the device, then the built-in software controller is ready to use. About the size of a mobile phone, the device is easy to deploy and install on your network.

TP-LINK Omada SDN Controller - ■ Omada Hardware Controller - 1

flowchart
graph TD
    A["Internet"] --> B["SafeStream Gateway"]
    B --> C["JetStream Switch"]
    C --> D["Hardware Controller"]
    C --> E["Access Points"]

■ Omada Cloud-Based Controller

Omada Cloud controller is deployed on the Omada Cloud server, providing paid license service with tiered pricing. With paid licenses bound to the devices on the controller, you can configure and manage the devices via the cloud Service. And you need not purchase an additional hardware device or install the software on the host.

TP-LINK Omada SDN Controller - ■ Omada Cloud-Based Controller - 1

flowchart
graph TD
    A["Cloud Server"] --> B["Internet"]
    B --> C["SafeStream Gateway"]
    B --> D["JetStream Switch"]
    C --> E["Access Points"]
    D --> E
    E --> F["..."]
    style A fill:#333,stroke:#fff,color:#fff
    style B fill:#fff,stroke:#000
    style C fill:#fff,stroke:#000
    style D fill:#fff,stroke:#000
    style E fill:#fff,stroke:#000
    style F fill:#fff,stroke:#000

The controllers differ in forms, but they have almost the same browser-based management interface and serve the same functions of network management. In this guide, Omada Software Controller, Omada Hardware Controller, and Omada Cloud-Based Controller are referred to as the controller, unless we mention otherwise.

Gateways

TP-Link's Omada Router supports Gigabit Ethernet connections on both WAN and LAN ports which keep the data moving at top speed. Including all the routing and network segmentation functions that a business router must have, SafeStream VPN Router will be the backbone of the SDN network. Moreover, the router provides a secure and easy approach to deploy site-to-site VPN tunnels and access for remote clients.

Managing the gateway centrally through Omada SDN Controller is available on certain models only. Please check the Omada Cloud SDN Platform Compatibility List for more information.

Switches

TP-Link's JetStream Switch provides high-performance and enterprise-level security strategies and lots of advanced features, which is ideal access-edge for the SDN network.

Managing the switch centrally through Omada SDN Controller is available on certain models only. Please check the Omada Cloud SDN Platform Compatibility List for more information.

Access Points

TP-Link's Omada Access Point provides business-class Wi-Fi with superior performance and range which guarantees reliable wireless connectivity for the SDN network.

Managing the access points centrally through Omada SDN Controller is available on certain models only. Please check the Omada Cloud SDN Platform Compatibility List for more information.

2

Get Started with Omada SDN Controller

This chapter guides you on how to get started with Omada SDN Controller to configure the network. Omada Software Controller, Omada Hardware Controller, and Omada Cloud-Based Controller differ in forms, but they have almost the same browser-based management interface for network management. Therefore, they have almost the same initial setup steps, including building your network topology, deploying your controller, and logging in to the controller. The chapter includes the following sections:

• 2.1 Set Up Your Software Controller
• 2.2 Set Up Your Hardware Controller
• 2.3 Set Up Your Cloud-Based Controller

2.1 Set Up Your Software Controller

Omada SDN Controller Solution is designed for scalable networks. Deployments and configurations vary according to actual situations. Understanding your network requirements is the first step when planning to provision any project. After you have identified these requirements, follow the steps below to initially set up the Software Controller:

1) Determine the network topology.
2) Install the Software Controller.
3) Start and log in to the controller.

2.1.1 Determine the Network Topology

The network topology that you create for the SDN Controller varies depending on your business requirements. The following figure shows a typical topology for a high-availability use case.

TP-LINK Omada SDN Controller - Determine the Network Topology - 1

flowchart
graph TD
    A["Internet"] --> B["SafeStream Gateway"]
    B --> C["JetStream Switch"]
    C --> D["SDK Controller"]
    C --> E["Access PointsSoftware Controller"]
    C --> F["SDK Controller"]
    C --> G["Access PointsSoftware Controller"]
    C --> H["SDK Controller"]
    C --> I["Access PointsSoftware Controller"]

Note:

When using the Omada SDN Controller, we recommend that you deploy the full topology with Omada-supported TP-Link devices. If you use third-party devices, Omada SDN Controller cannot discover and manage them.

2.1.2 Install the Software Controller

Omada Software Controller is provided for both Windows and Linux operating systems. Determine your operating system and follow the introductions below to install the Software Controller.

Installation on Windows Host

Omada Software Controller can be hosted on any computers with Windows systems on your network. Make sure your PC's hardware and system meet the following requirements, then properly install the Software Controller.

■ Hardware Requirements

To guarantee operational stability, we recommend that you use the hardware which meets or exceeds the following specifications:

CPU: Intel Core i3-8100, i5-6500, or i7-4700 with 2 or more cores and 4 or more threads.

Memory: 16 GB RAM or more.

■ System Requirements

Operating System: Microsoft Windows 7/8/10/Server. (We recommend that you deploy the controller on a 64-bit operating system to guarantee the software stability.)

Web Browser: Mozilla Firefox 32 (or above), Google Chrome 37 (or above), Opera 24 (or above), or Microsoft Internet Explorer 11 (or above).

■ Install the Software Controller

Download the installation file of Software Controller from the https://www.tp-link.com/support/download/omada-software-controller. Then follow the instructions to install the controller. After a successful installation, a shortcut icon of the controller will be created on your desktop.

Installation on Linux Host

Two versions of installation package are provided: .tar.gz file and .deb file. Both of them can be used in multiple versions of Linux operating system, including Ubuntu, CentOS, Fedora, and Debian.

Make sure your PC's hardware and system meet the following requirements, then choose the proper installation files to install the Software Controller.

■ Hardware Requirements

To guarantee operational stability, we recommend that you use the hardware which meets or exceeds the following specifications:

CPU: Intel Core i3-8100, i5-6500, or i7-4700 with 2 or more cores and 4 or more threads.

Memory: 16 GB RAM or more.

■ System Requirements

Operating System: 64-bit Linux operating system, including Ubuntu 14.04/16.04/17.04/18.04, CentOS 6.x/7.x, Fedora 20 (or above), and Debian 9.8.

Web Browser: Mozilla Firefox 32 (or above), Google Chrome 37 (or above), Opera 24 (or above), or Microsoft Internet Explorer 11 (or above).

■ Install the Software Controller

Download the installation file of Software Controller from the https://www.tp-link.com/support/download/omada-software-controller. Check the prerequisites and follow the steps based on your file version to install the controller.

- Prerequisites for installing

To successfully install the Software Controller, ensure that you have performed the following tasks before your installation:

a. Ensure that the Java Runtime Environment (JRE) has been installed in your system. The controller requires that the system has Java 8 installed. Download the file according to your operating system from https://www.java.com/download/linux_manual.jsp and follow the instructions to install the JRE.

For Ubuntu16.04 or above, you can use the command: apt-get install openjdk-8-jre-headless to get the Java 8 installed.

b. Ensure that MongoDB has been installed in your system. The controller works when the system runs MongoDB 3.0.15–3.6.18. Download the file according to your operating system from the https://www.mongodb.com/try/download and follow the instructions to install the MongoDB.

c. Ensure that you have jsvc and curl installed in your system before installation, which is vital to the smooth running of the system. If your system does not have jsvc or curl installed, you can install it manually with the command: apt-get install or yum install. For example, you can use the command: apt-get install jsvc or yum install jsvc to get jsvc installed. And if dependencies are missing, you can use the command: apt-get -f install to fix the problem.

- Install the .tar.gz file

a. Make sure your PC is running in the root mode. You can use this command to enter root mode: sudo

b. Extract the tar.gz file using the command: tar zxvf Omada_Controller_vx.x.x_linux_x64_targz.tar.gz

c. Install the Controller using the command: sudo bash ./install.sh

- Install the .deb file

a. Make sure your PC is running in the root mode. You can use this command to enter root mode: sudo

b. Install the .deb file using the command: dpkg -i Omada_Controller_vx.x.x_linux_x64.deb

If dependencies are missing during the installation, you can use the command: apt-fix-broken install to fix the problem.

After installing the controller, use the following commands to check and change the status of the controller.

a. tpeap start — Start the controller, use the command.
b. tpeap stop — Stop running the Controller.
c. tpeap status — Show the status of Controller.

For more detailed information about the installation on Linux hosts, refer to the Installation Instructions.

① Note:

  • For installing the .tar.gz, if you want the Controller to run as a user (it runs as root by default) you should modify OMADA_USER value in bin/control.sh.
    • To uninstall the Controller, go to the installation path: /opt/tplink/EAPController, and run the command: sudo bash ./uninstall.sh.
  • During uninstallation, you can choose whether to back up the database. The backup folder is /opt/tplink/eap_db_backup.
  • During installation, you will be asked whether to restore the database if there is any backup database in the folder /opt/tplink/eap_db_backup.

2. 1.3 Start and Log In to the Software Controller

Launch the Software Controller and follow the instructions to complete basic configurations, and then you can log in to the management interface.

Launch the Software Controller

Double-click the icon and the following window will pop up. After a while, your web browser will automatically open.

tp-link tp-link | omada Started Details: Launch

TP-LINK Omada SDN Controller - Launch the Software Controller - 2

Note:

  • If your browser does not open automatically, click Launch. You can also launch a web browser and enter http://127.0.0.1:8088 in the address bar.
  • If your web browser opens but prompts a problem with the website's security certificate, click Continue.

Complete Basic Configurations

In the web browser, you can see the configuration page. Follow the setup wizard to complete the basic settings for the Controller.

  1. Click Let's Get Started.

omada Welcome to use Omada Controller Please follow the wizard to set up your controller. Let's Get Started

  1. Set up controller access settings.

Controller Access

Create an administrator name and password for local login to Omada Controller.

Controller Main Administrator

Administrator Name:

TP-LINK Omada SDN Controller - Controller Main Administrator - 1

Enter the username with letters (case-sensitive), numbers, underscores, or hyphens.

Email:

TP-LINK Omada SDN Controller - Controller Main Administrator - 2

TP-LINK Omada SDN Controller - Controller Main Administrator - 3

Password:

TP-LINK Omada SDN Controller - Controller Main Administrator - 4

Confirm Password:

TP-LINK Omada SDN Controller - Controller Main Administrator - 5

To enjoy Omada Cloud Service, you can log in and bind your TP-Link ID to your controller.

Cloud Access:

TP-LINK Omada SDN Controller - Cloud Access: - 1

TP-Link ID:

TP-LINK Omada SDN Controller - Cloud Access: - 2

Password:

TP-LINK Omada SDN Controller - Cloud Access: - 3

Log in and bind

No TP-Link ID? Register now.

Terms

☐ I accept the Terms of Use and confirm that I have fully read and understood the Privacy Policy

a. Create an Administrator username and password for login to the controller. Specify the email address for resetting your password in case that you forget the password. After logging into the Controller, set a mail server so that you can receive emails and reset your password. For how to set a mail server, refer to 8.6.3 Notifications.
b. If you want to access the controller to manage networks remotely, enable Cloud Access, and bind your TP-Link ID to your Controller. For more details about cloud access, please refer to 5.5 Cloud Access.
c. Read and agree to TP-Link's Terms of Use.
d. Click Next.

  1. Choose how would you like to set up your new controller. You can configure a new setup or restore from backup file.

TP-LINK Omada SDN Controller - Terms - 1

How would you like to set up your new controller?

Config New Setup

Restore from backup file

  1. Follow the setup wizard to set up the controller.

TP-LINK Omada SDN Controller - Terms - 2

Successful!

Please confirm the settings below. Once finished you will be directed to the management interface.

Controller Name:

Omada Controller_6C59C3

Controller Country/Region:

China mainland

Controller Timezone:

(UTC) Coordinated Universal Time

Administrator Name:

Cloud Access:

TP-Link ID:

TP-LINK Omada SDN Controller - Successful! - 1

TP-LINK Omada SDN Controller - Successful! - 2

Site Name:

SZ

Site Country/Region:

China mainland

Site Time Zone:

(UTC) Coordinated Universal Time

Device Username:

Device Password:

Application Scenario:

TP-LINK Omada SDN Controller - Successful! - 3

TP-LINK Omada SDN Controller - Successful! - 4

Network Name (SSID):

Password:

TP-LINK Omada SDN Controller - Successful! - 5

TP-LINK Omada SDN Controller - Successful! - 6

Back

Finish

Log In to the Management Interface

Once the basic configurations are finished, the browser will be redirected to the following page. Log in to the management interface using the username and password you have set in the basic configurations.

Omada SDN Controller

TP-LINK Omada SDN Controller - Omada SDN Controller - 1

Username / TP-Link ID

TP-LINK Omada SDN Controller - Omada SDN Controller - 2

Password

TP-LINK Omada SDN Controller - Omada SDN Controller - 3

TP-LINK Omada SDN Controller - Omada SDN Controller - 4

Remember Me

Log in

Forgot password?

TP-LINK Omada SDN Controller - Omada SDN Controller - 5

Note:

In addition to the Controller Host, other hosts in the same LAN can also manage EAPs via remote access to the Controller Host. For example, if the IP address of the Controller Host is 192.168.0.100 and the Controller is running normally on this host, you can enter https://192.168.0.100:8043, or http://192.168.0.100:8088 in the web browser of other hosts in the same LAN to log in to the the Controller and manage EAPs. Or you can log in to the Controller using other management devices through Cloud service.

2.2 Set Up Your Hardware Controller

Omada SDN Controller Solution is designed for scalable networks. Deployments and configurations vary according to actual situations. Understanding your network requirements is the first step when planning to provision any project. After you have identified these requirements, follow the steps below to initially set up the Hardware Controller:

1) Determine the network topology.
2) Deploy the Hardware Controller.
3) Start and log in to the controller.

2.2.1 Determine the Network Topology

The network topology that you create for the SDN Controller varies depending on your business requirements. The following figure shows a typical topology for a high-availability use case.

TP-LINK Omada SDN Controller - Determine the Network Topology - 1

flowchart
graph TD
    A["Internet"] --> B["SafeStream Gateway"]
    B --> C["JetStream Switch"]
    C --> D["Access Points Hardware Controller"]
    C --> E["Access Points Hardware Controller"]
    C --> F["Access Points Hardware Controller"]
    C --> G["Access Points Hardware Controller"]
    C --> H["Access Points Hardware Controller"]
    C --> I["Access Points Hardware Controller"]
    C --> J["Access Points Hardware Controller"]
    C --> K["Access Points Hardware Controller"]
    C --> L["Access Points Hardware Controller"]
    C --> M["Access Points Hardware Controller"]
    C --> N["Access Points Hardware Controller"]
    C --> O["Access Points Hardware Controller"]
    C --> P["Access Points Hardware Controller"]
    C --> Q["Access Points Hardware Controller"]
    C --> R["Access Points Hardware Controller"]
    C --> S["Access Points Hardware Controller"]
    C --> T["Access Points Hardware Controller"]
    C --> U["Access Points Hardware Controller"]
    C --> V["Access Points Hardware Controller"]
    C --> W["Access Points Hardware Controller"]
    C --> X["Access Points Hardware Controller"]
    C --> Y["Access Points Hardware Controller"]
    C --> Z["Access Points Hardware Controller"]
    C --> AA["Access Points Hardware Controller"]
    C --> AB["Access Points Hardware Controller"]
    C --> AC["Access Points Hardware Controller"]
    C --> AD["Access Points Hardware Controller"]
    C --> AE["Access Points Hardware Controller"]
    C --> AF["Access Points Hardware Controller"]
    C --> AG["Access Points Hardware Controller"]
    C --> AH["Access Points Hardware Controller"]
    C --> AI["Access Points Hardware Controller"]
    C --> AJ["Access Points Hardware Controller"]
    C --> AK["Access Points Hardware Controller"]
    C --> AL["Access Points Hardware Controller"]
    C --> AM["Access Points Hardware Controller"]
    C --> AN["Access Points Hardware Controller"]
    C --> AO["Access Points Hardware Controller"]
    C --> AP["Access Points Hardware Controller"]
    C --> AQ["Access Points Hardware Controller"]
    C --> AR["Access Points Hardware Controller"]
    C --> AS["Access Points Hardware Controller"]
    C --> AT["Access Points Hardware Controller"]
    C --> AU["Access Points Hardware Controller"]
    C --> AV["Access Points Hardware Controller"]
    C --> AW["Access Points Hardware Controller"]
    C --> AX["Access Points Hardware Controller"]
    C --> AY["Access Points Hardware Controller"]
    C --> AZ["Access Points Hardware Controller"]
    C --> BA["Access Points Hardware Controller"]
    C --> BB["Access Points Hardware Controller"]
    C --> BC["Access Points Hardware Controller"]
    C --> BD["Access Points Hardware Controller"]
    C --> BE["Access Points Hardware Controller"]
    C --> BF["Access Points Hardware Controller"]
    C --> BG["Access Points Hardware Controller"]
    C --> BH["Access Points Hardware Controller"]
    C --> BI["Access Points Hardware Controller"]
    C --> BJ["Access Points Hardware Controller"]
    C --> BK["Access Points Hardware Controller"]
    C --> BL["Access Points Hardware Controller"]
    C --> BM["Access Points Hardware Controller"]
    C --> BN["Access Points Hardware Controller"]

Note:

When using the Omada SDN Controller, we recommend that you deploy the full topology with Omada-supported TP-Link devices. If you use third-party devices, Omada SDN Controller cannot discover and manage them.

2.2.2 Deploy the Hardware Controller

Omada Hardware Controller comes with the pre-installed controller software, so installation is not necessary. After deploying the Hardware Controller on your network infrastructure, proceed to configure the controller.

2.2.3 Start and Log in to the Controller

Log In to the Management Interface

Follow the steps below to enter the management interface of the Hardware Controller:

  1. Make sure that your management device has the route to access the controller.
  2. Check the DHCP server (typically a router) for the IP Address of the controller. If the controller fails to get a dynamic IP address from the DHCP server, the default fallback IP address 192.168.0.253, is used.
  3. Launch a web browser and type the IP address of the controller in the address bar, then press Enter (Windows) or Return (Mac).

Complete Basic Configurations

In the web browser, you can see the configuration page. Follow the setup wizard to complete the basic settings for the Controller.

  1. Click Let's Get Started.

omada Welcome to use Omada Controller Please follow the wizard to set up your controller. Let's Get Started

  1. Set up controller access settings.

Controller Access

Create an administrator name and password for local login to Omada Controller.

Controller Main Administrator

Administrator Name:

TP-LINK Omada SDN Controller - Controller Main Administrator - 1

Enter the username with letters (case-sensitive), numbers, underscores, or hyphens.

Email:

TP-LINK Omada SDN Controller - Controller Main Administrator - 2

TP-LINK Omada SDN Controller - Controller Main Administrator - 3

Password:

TP-LINK Omada SDN Controller - Controller Main Administrator - 4

Confirm Password:

TP-LINK Omada SDN Controller - Controller Main Administrator - 5

To enjoy Omada Cloud Service, you can log in and bind your TP-Link ID to your controller.

Cloud Access:

TP-LINK Omada SDN Controller - Cloud Access: - 1

TP-Link ID:

TP-LINK Omada SDN Controller - Cloud Access: - 2

Password:

TP-LINK Omada SDN Controller - Cloud Access: - 3

Log in and bind

No TP-Link ID? Register now.

Terms

☐ I accept the Terms of Use and confirm that I have fully read and understood the Privacy Policy

a. Create an Administrator username and password for login to the controller. Specify the email address for resetting your password in case that you forget the password. After logging into the Controller, set a mail server so that you can receive emails and reset your password. For how to set a mail server, refer to 8.6.3 Notifications.
b. If you want to access the controller to manage networks remotely, enable Cloud Access, and bind your TP-Link ID to your Controller. For more details about cloud access, please refer to 5.5 Cloud Access.
c. Read and agree to TP-Link's Terms of Use.
d. Click Next.

  1. Choose how would you like to set up your new controller. You can configure a new setup or restore from backup file.

TP-LINK Omada SDN Controller - Terms - 1

How would you like to set up your new controller?

Config New Setup

Restore from backup file

  1. Follow the setup wizard to set up the controller.

TP-LINK Omada SDN Controller - Terms - 2

Successful!

Please confirm the settings below. Once finished you will be directed to the management interface.

Controller Name:

Omada Controller_6C59C3

Controller Country/Region:

China mainland

Controller Timezone:

(UTC) Coordinated Universal Time

Administrator Name:

Cloud Access:

TP-Link ID:

TP-LINK Omada SDN Controller - Successful! - 1

TP-LINK Omada SDN Controller - Successful! - 2

Site Name:

SZ

Site Country/Region:

China mainland

Site Time Zone:

(UTC) Coordinated Universal Time

Device Username:

Device Password:

Application Scenario:

TP-LINK Omada SDN Controller - Successful! - 3

TP-LINK Omada SDN Controller - Successful! - 4

Network Name (SSID):

Password:

TP-LINK Omada SDN Controller - Successful! - 5

TP-LINK Omada SDN Controller - Successful! - 6

Back

Finish

Log In to the Management Interface

Once the basic configurations are finished, the browser will be redirected to the following page. Log in to the management interface using the username and password you have set in the basic configurations.

Omada SDN Controller

TP-LINK Omada SDN Controller - Omada SDN Controller - 1

Username / TP-Link ID

TP-LINK Omada SDN Controller - Omada SDN Controller - 2

Password

TP-LINK Omada SDN Controller - Omada SDN Controller - 3

TP-LINK Omada SDN Controller - Omada SDN Controller - 4

Remember Me

Log in

Forgot password?

TP-LINK Omada SDN Controller - Omada SDN Controller - 5

Note:

In addition to the Controller Host, other hosts in the same LAN can also manage EAPs via remote access to the Controller Host. For example, if the IP address of the Controller Host is 192.168.0.100 and the Controller is running normally on this host, you can enter https://192.168.0.100:8043, or http://192.168.0.100:8088 in the web browser of other hosts in the same LAN to log in to the Controller and manage EAPs. Or you can log in to the Controller using other management devices through Cloud service.

2.3 Set Up Your Cloud-Based Controller

Omada SDN Controller Solution is designed for scalable networks. Deployments and configurations vary according to actual situations. Understanding your network requirements is the first step when planning to provision any project. After you have identified these requirements, follow the steps below to initially set up the Cloud-Based Controller:

  1. Contact the sales staff to grant the Omada Cloud-Based Controller permission.
  2. Launch a web browser and enter https://omada.tplinkcloud.com in the address bar. Enter your TP-Link ID and password to log in. If you do not have a TP-Link ID, create a TP-Link ID first.
  3. Click Add Controller and register for an Omada Cloud-Based Controller. Follow the instructions to complete the setup process.
  4. Add devices with the serial number, make sure the devices are online and in factory default.
  5. Assign appropriate licenses in order to manage and configure the devices on the cloud-based controller. Then wait until your controller is deployed

For detailed information about device-based licensing, refer to https://www.tp-link.com/omada-sdn/license/.

Note:

Only when you have available licenses can you register for the Cloud-Based Controller and manage the devices. To successfully register for a Cloud-Based Controller, purchase appropriate licenses.

3

Manage Omada Managed Devices and Sites

Start managing your network by creating sites and adopting devices so that you can configure and monitor your devices centrally while keeping things organized. The chapter includes the following sections:

• 3.1 Create Sites
• 3.2 Adopt Devices

TP-LINK Omada SDN Controller - Manage Omada Managed Devices and Sites - 1

3.1 Create Sites

Overview

Different sites are logically separated network locations, like different subsidiary companies or departments. It's best practice to create one site for each LAN (Local Area Network) and add all the devices within the network to the site, including the router, switches and APs.

TP-LINK Omada SDN Controller - Overview - 1

flowchart
graph TD
    subgraph Site_C
        A["Site C"] --> B["Router"]
        B --> C["LAN 3"]
        C --> D["AP"]
        C --> E["AP"]
    end

    subgraph Site_B
        F["Site B"] --> G["Router"]
        G --> H["LAN 2"]
        H --> I["AP APAP"]
        G --> J["Switch"]
    end

    subgraph Site_A
        K["Site A"] --> L["Router"]
        L --> M["LAN 1"]
        M --> N["AP"]
        M --> O["AP AP"]
        L --> P["Switch"]
    end

    subgraph Site_D
        Q["Site D"] --> R["Router"]
        R --> S["LAN 4"]
        S --> T["AP"]
        S --> U["AP"]
    end

    style Site_C fill:#f9f,stroke:#333
    style Site_B fill:#f9f,stroke:#333
    style Site_A fill:#f9f,stroke:#333
    style Site_D fill:#f9f,stroke:#333
    style Site_E fill:#f9f,stroke:#333

Devices at one site need unified configurations, whereas those at different sites are not relative. To make the best of a site, configure features simultaneously for multiple devices at the site, such as VLAN and PoE Schedule for switches, and SSID and WLAN Schedule for APs, rather than set them up one by one.

Configuration

To create and manage a site, follow these steps:

1) Create a site.
2) View and edit the site.
3) Go into the site.

Create a Site View and Edit the Site Go Into the Site

To create a site, choose one from the following methods according to your needs.

■ Create a site from scratch

  1. In Global view, click Add New Site in the Site List section.
  2. Enter a Site Name to identify the site, and configure other parameters according to where the site is located. Create a username and password for login to newly adopted devices. Then click Apply. The new site will be added to the Site List and the drop-down list of Organization.

Add New Site Site Configuration Name: Country/Region: China mainland Time Zone: (UTC) UTC Application Scenario: Hotel Longitude: (Optional, -180~180, with a maximum of 16 decimal places) Latitude: (Optional, -90~90, with a maximum of 16 decimal places.) Address: (Optional) Refresh Device Account Username: Password: Apply Cancel

■ Copy an existing site

You can quickly create a site based on an existing one by copying its site configuration, wired configuration, and wireless configuration among others. After that, you can flexibly modify the new site configuration to make it different from the old.

  1. In the Site List, click 📋 in the ACTION column of the site which you want to copy.

  2. Enter a Site Name to identify the new site. Click Apply. The new site will be added to the Site List and the drop-down list of Organization.

Site Copy Site Name: Note: With Site Copy, you can create a new site with the same configuration as the existing site. Apply Cancel

■ Import a site from another controller

If you want to migrate seamlessly from an old controller to a new one, import the site configuration file of the old controller into the new. Before that, you need to export the site configuration file from the old controller, which is covered in 5.7.1 Site Migration.

  1. Click ↑ Import Site in the Site List section.
  2. Enter a Site Name to identify the site, and configure other parameters according to actual site needs. Browse your file explorer and choose a site configuration file. Click Import Site. The new site will be added to the Site List and the drop-down list of Organization.

Import Site Name: Retain Device Info: Enable Import: Import from Local File Import from File Server Choose File: Please select a file. Browse i For controller v5.13.11.41 and above, only the configuration file from the controller with the same first- three-part version number (Major.Minor.Patch) can be imported. Import Cancel

Create a Site View and Edit the Site Go Into the Site

After you create the site, you can view the site status in the Site List. You can click the icons in the ACTION column to edit, copy, delete and launch the site.

Search Site Name NAME COUNTRY/REGION ALERTS UPGRADE GATEWAY SWITCHES EAPS CLIENTS ACTION Default Netherlands 0 / 1 0 / 2 / 0 ✓ 0 0 0 0 Youty United States 0 / 8 0 / 285 / 0 ✓ 0 0 0 0 Showing 1-2 of 2 records 1 > 10 / page Go To page

Create a Site View and Edit the Site Go Into the Site

To monitor and configure a site, you need first go into the site.

Click the 📋 icon of the site in the Site List to go into the site. Alternatively, select the site from the dropdown list of Organization.

tp-link | omado | Omada Controller DST Organization Global View Search Site Name Default Younty Controller Overview 2 Sites 0 Gateways 9 Switches 287 APs 0 Clients Aants 2 Sites in 2 Countries Connected 0 Connected 0 Connected 0 Connected 0 Wind Users 0 Global 0 Disconnected 0 Disconnected 9 Disconnected 287 Disabled 0 Disabled Users 0 Disabled Users 0 Site List Site Map Search Site Name Import Site Add New Site NAME COUNTRY/REGION ALERTS UPGRADE GATEWAY SWITCHES EAPS CLIENTS ACTION Default Netherlands 0 0 / 1 0 / 2 / 0 0 0 10 County United States 0 0 / 8 0 / 265 / 0 0 0 10 Showing 1-2 of 2 records < 1 > 10 / page Go To page

The Organization field indicates the site which you are currently in. Some configuration items in the menu are applied to the site which you are currently in, whereas others are applied to the whole controller.

TP-LINK Omada SDN Controller - Create a Site View and Edit the Site Go Into the Site - 2

3.2 Adopt Devices

Overview

After you create a site, add your devices to the site by making the controller adopt them. Make sure that your devices in each LAN are added to the corresponding site so that they can be managed centrally.

TP-LINK Omada SDN Controller - Overview - 1

flowchart
graph TD
    subgraph Site_C
        A["Site C"] --> B["Router"]
        B --> C["Switch"]
        C --> D["LAN 3"]
        C --> E["AP"]
        C --> F["AP"]
    end

    subgraph Site_B
        G["Site B"] --> H["Router"]
        H --> I["Switch"]
        I --> J["LAN 2"]
        I --> K["AP APAP"]
    end

    subgraph Site_A
        L["Site A"] --> M["Router"]
        M --> N["Switch"]
        N --> O["LAN 1"]
        N --> P["AP"]
        N --> Q["AP"]
    end

    subgraph Site_D
        R["Site D"] --> S["Router"]
        S --> T["Switch"]
        T --> U["LAN 4"]
        T --> V["AP"]
        T --> W["AP"]
    end

    style Site_C fill:#f9f,stroke:#333
    style Site_B fill:#bbf,stroke:#333
    style Site_A fill:#bfb,stroke:#333
    style Site_D fill:#ffb,stroke:#333
    style Site_E fill:#cfc,stroke:#333

Configuration

Choose a procedure according to the type of your controller:

■ 3.2.1 For Software Controller / Hardware Controller
■ 3.2.2 For Cloud-Based Controller

3.2.1 For Software Controller / Hardware Controller

To adopt the devices on the controller, follow these steps:

1) Prepare for communication between the controller and devices.
2) Prepare for device discovery.
3) Adopt the devices.

Prepare for Communication Prepare for Device Discovery Adopt the Devices

TP-LINK Omada SDN Controller - For Software Controller / Hardware Controller - 1

Note:

If the controller and devices are in the same LAN, subnet and VLAN, skip this step.

Make sure that the controller can communicate with the devices. Otherwise, the controller cannot discover or adopt the devices by any means. If the controller and devices are in different LANs, subnets or VLANs, use the following techniques to build up the connection according to your scenario.

1. Set up the Network

■ Scenario 1: Across VLANs or Subnets

As shown in the following figures, the controller and devices are in different VLANs or subnets. You need to set up a layer 3 interface for each VLAN or subnet, and make sure the interfaces can communicate with each other.

TP-LINK Omada SDN Controller - ■ Scenario 1: Across VLANs or Subnets - 1

flowchart
graph TD
    A["Internet"] --> B["Gateway"]
    B --> C["Interface 1 Interface 2"]
    B --> D["Omada SDN Controller Site"]
    C --> E["Switch"]
    E --> F["AP AP"]
    E --> G["VLAN 1 VLAN 2"]
    D --> H["Unified Management from One Interface"]
    D --> I["Gateway Switch APs"]
    J["Internet"] --> K["Gateway"]
    K --> L["Interface 1 Interface 2"]
    K --> M["SDN Controller Site"]
    L --> N["Switch"]
    N --> O["AP AP"]
    N --> P["Subnet 1: 192.168.0.0/24 Subnet 2: 192.168.1.0/24"]

■ Scenario 2: Across LANs

As shown in the following figure, the controller and devices are in different LANs. You need to establish communication across the internet and the gateways.

By default, devices in LAN 1 cannot communicate with the controller in LAN 2, because Gateway B is in front of the controller and block access to it. To make the controller accessible to the devices, you can use Port Forwarding or VPN.

- Use Port Forwarding

Configure Port Forwarding on Gateway B and open port 29810-29813 for the controller, which are essential for discovering and adopting devices. If you are using firewalls in the networks, make sure that the firewalls don't block those ports.

TP-LINK Omada SDN Controller - - Use Port Forwarding - 1

flowchart
graph TD
    A["Internet"] --> B["Gateway A"]
    A --> C["Switch"]
    B --> D["AP AP"]
    B --> E["AP AP"]
    C --> F["AP AP"]
    C --> G["AP AP"]
    H["Port Forwarding Gateway B"] --> I["SDN Controller Site"]
    I --> J["Unified Management from One Interface"]
    I --> K["Gateway Switch APs"]

To configure Port Forwarding on Gateway B, you need first adopt Gateway B on the controller. For how to adopt Gateway B, refer to Adopt the Devices. Go to Settings > Transmission > NAT > Port Forwarding. Click + Create New Rule to load the following page. Specify a name to identify the Port Forwarding rule, check Enable for Status, select Any as Source IP, select the desired WAN port

as Interface, disable DMZ, specify 29810-29813 as Source Port and Destination Port, specify the controller's IP address as Destination IP, and select All as Protocol. Then click Create.

Create New Rule

Name:

open-port-for-controller

Status:

TP-LINK Omada SDN Controller - Create New Rule - 1

Enable

Source IP:

TP-LINK Omada SDN Controller - Create New Rule - 2

Any

TP-LINK Omada SDN Controller - Create New Rule - 3

Limited IP Address

Interface:

WAN ×

DMZ:

TP-LINK Omada SDN Controller - Create New Rule - 4

Enable

Source Port:

29810-29813

(1-65535. e.g. 80 or 80-100)

Destination IP:

192

168

0

26

Destination Port:

29810-29813

(1-65535. e.g. 80 or 80-100)

Protocol:

TP-LINK Omada SDN Controller - Create New Rule - 5

All

TP-LINK Omada SDN Controller - Create New Rule - 6

TCP

TP-LINK Omada SDN Controller - Create New Rule - 7

UDP

Create

Cancel

- Use VPN

Set up a VPN connection between Gateway A and Gateway B in Standalone Mode. For details about VPN configuration, refer to the User Guide of the gateways.

TP-LINK Omada SDN Controller - - Use VPN - 1

flowchart
graph TD
    A["Internet"] -->|VPN Connection| B["Gateway A"]
    A -->|VPN Connection| C["Gateway B"]
    B --> D["Switch"]
    D --> E["AP AP"]
    D --> F["AP AP"]
    C --> G["SDN Controller Site"]
    G --> H["Unified Management from One Interface"]
    G --> I["Gateway Switch APs"]

2. (Optional) Test the network

If you are not sure whether the controller and devices can establish communication, it's recommended to do the ping test from the devices to the controller.

Let's take a switch for example. Log into the web page of the switch in Standalone Mode. Then Go to MAINTENANCE > Network Diagnostics > Ping to load the following page, and specify Destination IP as the IP address of the controller (if you have configured Port Forwarding on the controller side, use the public WAN IP address of the gateway instead). Then click Ping.

TP-LINK Omada SDN Controller - (Optional) Test the network - 1

Note:

To ping the router, please turn off Block WAN Ping on the Settings > Network Security > Attack Defense page.

Ping Config Destination IP: 192.168.0.26 (Format: 192.168.0.1 or 2001::1) Ping Times: 4 (1-10) Data Size: 64 bytes (1-1500) Interval: 1000 milliseconds (100-1000) Ping Ping Result Pinging 192.168.0.26 with 64 bytes of data: Reply from 192.168.0.26 : bytes=64 time=19ms TTL=64 Reply from 192.168.0.26 : bytes=64 time=3ms TTL=64 Reply from 192.168.0.26 : bytes=64 time=3ms TTL=64 Reply from 192.168.0.26 : bytes=64 time=3ms TTL=64 Ping statistics for 192.168.0.26 : Packets: Sent=4, Received=4, Loss=0 (0%Loss) Approximate round trip times in milliseconds: Maximum=19ms, Minimum=3ms, Average=7ms

If the ping result shows the packets are received, it implies that the controller can communicate with the devices. Otherwise, the controller cannot communicate with the devices, then you need to check your network.

Prepare for Communication

Prepare for Device Discovery

Adopt the Devices

Note:

If the controller and devices are in the same LAN, subnet and VLAN, skip this step. In this scenario, the controller can discover the devices directly, and no additional settings are required.

Make sure that the controller can discover the devices.

When the controller and devices are in different LANs, subnets or VLANs, the controller cannot discover the devices directly. You need to choose Controller Inform URL, Discovery Utility, or DHCP Option 138 as the method to help the controller discover the devices.

■ Controller Inform URL

Controller Inform URL informs the devices of the controller's URL or IP address. Then the devices make contact with the controller so that the controller can discover the devices.

You can configure Controller Inform URL for devices in Standalone Mode. Let's take a switch for example. Log into the management page of the switch in Standalone Mode and go to SYSTEM > Controller Settings to load the following page. In Controller Inform URL, specify Inform URL/

IP Address as the controller's URL or IP address (if you have configured Port Forwarding on the controller side, use the public WAN IP address of the gateway instead). Then click Apply.

Cloud-Based Controller Management Connection Status: Disabled Cloud-Based Controller Management: Enable Notes: To enjoy centralized management on Omada Cloud-Based Controller, enable Cloud-Based Controller Management and add the device to the controller via its serial number. You can disable this feature if you do not need to manage the device with the Omada Cloud-Based Controller. Controller Inform URL Inform URL/IP Address: 102.168.0.26 Notes: Enter the inform URL or IP address of your controller to tell the device where to discover the controller. This feature is commonly used for the device to be managed by the controller in Layer 3 deployments. Apply

■ Discovery Utility

Discovery Utility can discover the devices in the same LAN, subnet and VLAN, and inform the devices of the controller's IP address. Then the devices make contact with the controller so that the controller can discover the devices.

  1. Download Discovery Utility from the https://www.tp-link.com/hk/support/download/omada-software-controller/#Omada_Discovery_Utility and then install it on your PC which should be located in the same LAN, subnet and VLAN as your devices.

  2. Open Discovery Utility and you can see a list of devices. Select the devices to be adopted and click Batch Setting.

Omada Discovery Utility Discovering EAPs... MAC, IP, Status Select MAC Address IP Address Model Version Status Action D8-0D-17-DA-46-89 192.168.0.3 EAP115-Wall 1.2.0 Build 2018060... Pending Manage EA-23-51-06-22-52 192.168.0.5 EAP225-Outdoor 1.5.0 Build 2018112... Pending Manage EA-33-51-A8-22-A0 192.168.0.4 EAP225-Outdoor 1.3.0 Build 2018061... Pending Manage Displayed EAP : 3 Select All Batch Setting

  1. Specify Controller Hostname/IP as the IP address of the controller (if you have configured Port Forwarding on the controller side, use the public WAN IP address of the gateway instead), and

enter the username and password of the devices. By default, the username and password are both admin. Then click Apply. Wait until the setting succeeds.

Omada Discovery Utility Discovering EAPs... MAC, IP, Status Select MAC Address ✓ D8-0D-17-DA-46-8 ✓ EA-23-51-06-22-52 ✓ EA-33-51-A8-22-A Batch Setting Controller Hostname/IP: 192.168.0.26 Username: admin Password: •••••• Apply Cancel Status Action Loading Manage Loading Manage Loading Manage Displayed EAP : 3 Select All Batch Setting

■ DHCP Option 138

DHCP Option 138 informs a DHCP client, such as a switch or an EAP, of the controller's IP address when the DHCP client sends DHCP requests to the DHCP server, which is typically a gateway.

  1. To use DHCP Option 138, you need to adopt the gateway on the controller first, which may require other techniques like Controller Inform URL or Discovery Utility if necessary.
  2. After the gateway is adopted, go to Settings > Wired Networks > LAN > Networks, and click in the ACTION column of the LAN where the DHCP clients are located. Enable DHCP Server and configure common DHCP parameters. Then click Advanced DHCP Options and specify Option

138 as the controller's IP address (if you have configured Port Forwarding on the controller side, use the public WAN IP address of the gateway instead). Click Save.

Edit Network Name: LAN Purpose: Interface VLAN LAN Interfaces: WAN/LAN2 WAN/LAN3 LAN1 VLAN: 1 (1-4090) i Gateway/Subnet: 192 . 168 . 1 . 1 / 24 i Update DHCP Range Gateway IP 192.168.1.1 Network Broadcast IP 192.168.1.255 Network IP Count 254 Network IP Range 192.168.1.1 - 192.168.1.254 Network Subnet Mack 255.255.255.0 Domain Name: (Optional) IGMP Snooping: Enable i DHCP Server: Enable DHCP Range: 192 . 168 . 1 . 1 - 192 . 168 . 1 . 254 DNS Server: Auto Manual Lease Time: 120 minutes (2-2880) Default Gateway: Auto Manual DHCP Omada Controller: (Optional) i Legal DHCP Servers: Enable i Advanced DHCP Options Option 60: (Optional) i Option 66: (Optional) i Option 138: 192 . 168 . 0 . 26 (Optional) i Save Cancel

  1. To make DHCP Option 138 take effect, you need to renew DHCP parameters for the DHCP clients. One possible way is to disconnect the DHCP clients and then reconnect them.

Prepare for Communication Prepare for Device Discovery Adopt the Devices

  1. Decide which site you want to add the devices to. On the controller configuration page, select the site from the drop-down list of Organization.

tp-link omado Omada Controller GOZT Organization Global View Search Site Name Default Youthly Controller Overview 2 Sites 0 Gateways 9 Switches 287 APs 0 Clients Alets 2 Sites in 2 Countries Connected 0 Connected 0 Connected 0 Wired Users 0 Global 0 Disconnected 5 Disconnected 287 Wireless Users 0 Disabled 0 Disabled Guests 0 Site List Site Map Search Site Name Import Site Add New Site NAME COUNTRY/REGION ALERTS UPGRADE GATEWAY SWITCHES EAPS CLIENTS ACTION Default Netherlands 0 0 / 1 0 / 2 / 0 0 0 0 Youthly United States 0 0 / 8 0 / 285 / 0 0 0 0 Showing 1-2 of 2 records < 1 > 10 / page Go To page: Up

  1. Go to Devices, and devices which have been discovered by the controller are displayed.

Search Name: IP, Status, Model or Tag All Gateway/Switches APs Start Rolling Upgrade Batch Action DEVICE NAME IP ADDRESS STATUS Y MODEL SomATION UPTIME ACTION 1C-61-B4-CS-48-83 192.168.0.1 CONNECTED ER805 v2.0 2.1.0 4day(s) 20h 22m... 00-FF-00-05-40-5D 192.168.0.18 CONNECTED TL-SG2428P v1.0 1.1.7 22day(s) 19h 49... 00-00-FF-FC-30-92 -- MANAGED BY OTHERS EEP770 v1.0 - 00-00-FF-FF-00-28 -- PENDING EEP225 v5.0 - 00-00-FF-FF-0F-BB -- PENDING EEP225 v5.0 - Showing 1-5 of 7 records < 1 2 > 5 /page Go To page: GO

  1. Click ✅ in the ACTION column of the devices which you want to add to the site. Wait until the STATUS turns into Connected. Then the devices are adopted by the controller and added to the current site. Once the devices are adopted, they are subject to central management in the site.

3.2.2 For Cloud-Based Controller

To adopt the devices on the controller, follow these steps:

1) Connect to the internet.
2) Prepare for controller management.
3) Adopt the devices.

Connect to the Internet Prepare for Controller Management Adopt the Devices

1. Set up the network.

Make sure that your devices are connected to the internet.

TP-LINK Omada SDN Controller - Set up the network. - 1

flowchart
graph TD
    A["SDN Controller"] --> B["Site"]
    B --> C["Internet"]
    C --> D["Gateway A"]
    C --> E["Switch"]
    D --> F["AP AP"]
    E --> G["AP AP"]
    style A fill:#333,stroke:#fff,color:#fff
    style B fill:#999,stroke:#000,color:#fff
    style C fill:#ccc,stroke:#000,color:#fff
    style D fill:#eee,stroke:#000,color:#fff
    style E fill:#eee,stroke:#000,color:#fff
    style F fill:#eee,stroke:#000,color:#fff
    style G fill:#eee,stroke:#000,color:#fff

If you are using firewalls in your network, make sure that the firewall doesn't block traffic from the controller. To configure your firewall policy, you may want to know the URL of the controller. After you open the web page of the controller, you can get the URL from the address bar of the browser.

2. (Optional) Test the network.

If you are not sure whether the devices are connected to the internet, it's recommended to do the ping test from the devices to a public IP address, such as 8.8.8.8.

Let's take a switch for example. Log into the web page of the switch in Standalone Mode. Go to MAINTENANCE > Network Diagnostics > Ping to load the following page. Specify Destination IP as a public IP address, such as 8.8.8.8. Then click Ping.

Ping Config Destination IP: 8.8.8.8 (Format: 192.168.0.1 or 2001:1) Ping Times: 4 (1-10) Data Size: 64 bytes (1-1500) Interval: 1000 milliseconds (100-1000) Ping Ping Result Pinging 8.8.8.8 with 64 bytes of data: Reply from 8.8.8.8 : bytes=64 time=3ms TTL=64 Reply from 8.8.8.8 : bytes=64 time=3ms TTL=64 Reply from 8.8.8.8 : bytes=64 time=3ms TTL=64 Reply from 8.8.8.8 : bytes=64 time=3ms TTL=64 Ping statistics for 8.8.8.8 : Packets: Sent=4, Received=4, Loss=0 (0%Loss) Approximate round trip times in milliseconds: Maximum=3ms , Minimum=3ms, Average=3ms

If the ping result shows the packets are received, it implies that the devices are connected to the internet. Otherwise, the devices are not connected to the internet, then you need to check your network.

TP-LINK Omada SDN Controller - (Optional) Test the network. - 2

flowchart
graph LR
    A["Connect to the Internet"] --> B["Prepare for Controller Management"]
    B --> C["Adopt the Devices"]

① Note:

If your devices are on the factory default setting, skip this step.

The Cloud-Based Controller Management feature allows the devices to be adopted by the Cloud-Based Controller. Make sure Cloud-Based Controller Management is enabled on the devices. For details, refer to the User Guide of your devices, which can be downloaded from https://www.tp-link.com/support/download/.

Let's take a switch for example. Log into the web page of the switch in Standalone Mode. Go to SYSTEM > Controller Settings to load the following page. In Cloud-Based Controller Management, enable Cloud-Based Controller Management and click Apply.

Cloud-Based Controller Management

Connection Status: Off-line

Cloud-Based Controller Management: ☑ Enable

Notes:

To enjoy centralized management on Omada Cloud-Based Controller, enable Cloud-Based Controller Management and add the device to the controller via its serial number.

You can disable this feature if you do not need to manage the device with the Omada Cloud-Based Controller.

Controller Inform URL

Inform URL/IP Address:

Notes:

Enter the inform URL or IP address of your controller to tell the device where to discover the controller. This feature is commonly used for the device to be managed by the controller in Layer 3 deployments.

Apply

Connect to the Internet Prepare for Controller Management Adopt the Devices

On the controller configuration page, go into the site where you want to add the devices. Go to Devices and click Add Devices. Then add your devices to the controller. Once the devices are adopted, they are subject to central management in the site.

4

Configure the Network with the SDN Controller

This chapter guides you on how to configure the network with the SDN Controller. As the command center and management platform at the heart of the SDN network, the Controller provides a unified approach to configuring enterprise networks comprised of routers, switches, and wireless access points. The chapter includes the following sections:

• 4.1 Navigate the UI
• 4.2 Modify the Current Site Configuration
• 4.3 Configure Wired Networks
• 4.4 Configure Wireless Networks
• 4.5 Network Security
• 4.6 Transmission
• 4.7 Configure VPN
• 4.8 Create Profiles
• 4.9 Authentication
• 4.10 Services
• 4.11 SIM
• 4.12 CLI Configuration

TP-LINK Omada SDN Controller - Configure the Network with the SDN Controller - 1

4.1 Navigate the UI

As you start using the management interface of the controller (Controller UI) to configure and monitor your network, it is helpful to familiarize yourself with the Controller UI.

■ Global Overview

Know the status of your sites at a glance, and manage sites in the platform.

  • Site Monitoring—Keep you informed of accurate, real-time status of every site.
  • Site Management—Manage all sites to deploy the whole network.
  • Account Settings—Manage all administrative accounts.

tp-link Organization: Global View Search Site name Device List Logs 20 Site 23 Gateways 23 Switches 23 EAPs Global default Manage Cloud Access > 20 Sites in 5 Country Connected Disconnected 2121 0 Connected Disconnected 20 Connected Disconnected Isolated 20 wind wireless Quests Site Switch Back to Global View Global Search My Account More Settings Address Search for address name or site code... New York 47 W 13th St, New York, NY 10011, USA + Driving new site Jersey City New York Account Settings Controller Settings SiteManagement through Map&List

■ Site Overview

Know the status of your network at a glance, gain insights, and manage network devices all in the platform.

• Statistics & Monitoring—Keep you informed of accurate, real-time status of every network

device and client.

- Settings—Configure all your network devices centrally.

TP-LINK Omada SDN Controller - ■ Site Overview - 1

bar | Category | Value | | :--- | :--- | | Normal Internet | 2.4 GHz | | N/A Getway | 5 GHz | | Switch | 36 | | 5/10 EAP | 40 | | 90 Clients | 52 | | Controller Stats CPU | 50% | | Controller Stats Memory | 30% | | Controller Stats Storage | 70% | | Most Active EAPs Office | 32.07 GB | | Most Active EAPs Lab | 125 GB | | Most Active EAPs Lobby | 125 GB | | Most Active EAPs Meeting | 125 GB | | Most Active EAPs Office1 | 1 GB (≤1.2) | | Clients with onboarding times < 10s Time (seconds) | 75% (≥10s Threshold) | | Settings | - |

■ Site Overview

Site, which means logically separated network location, is the largest unit for managing networks with the SDN Controller. You can simultaneously configure features for multiple devices at a site.

- Add New Site — Click Add New Site to add a new site, which is the logically separated network

location. The site is the largest unit for managing the network.

  • Import Site — Click Import Site to import the site from another controller.
  • Site Bookmark – Click Bookmark to place frequently-used sites on the top of the list.

tp-link Organization: Global View Cloud Based Controller Overall Connected Cloud Access 20 Site 23 Gateways 23 Switches 23 EAPs Manage Cloud Access > 30 Sites in % Country Connected 2121 Connected 26 Connected 30 Connected 20 Wireless 20 Alert 5 Connected 0 Disconnected 0 Disconnected Isolated 0 Guests 20 Site Switch Site Bookmark Site List Site Map Search site name Add New Site Import Site NAME COUNTRY/REGION ALERTS WAN LAN CONNECTED DISCONNECTED WLAN CONNECTED DISCONNECTED ISOLATED USERS ACTION Default United States 0 2 4 1 7 2 2 8 Office 1 13 0 13 5 11 8 13 1 5 Office 2 54 0 54 22 9 54 54 2 6 Office 3 2 0 2 3 23 7 2 4 2 Office 4 1 0 1 6 12 8 1 1 2 Hospital 44 0 44 23 5 33 44 1 2 1234 6 0 0 0 0 0 0 0 Others 6 0 0 0 0 0 0 0 Showing 1-10 of BS records < 1 2 3 4 5 ... 9 > 10 Items/page Go to 12

■ Network Monitoring

Visual data keeps the network administrator informed about accurate status of every network device and client on the wired and wireless network.

The Controller UI is grouped into task-oriented menus. These menus are located in the top right-hand corner and the left-hand navigation bar of the page. Note that the settings and features that appear in the UI depend on your user account permissions. The following image depicts the main elements of the Controller UI.

The elements in the top right corner of the screen give quick access to:

Organization: default

Organization Management

Global View — Know the status of your Site at a glance, and manage sites in the platform.

Site View — Know the status of your network at a glance, gain insights, and manage network devices all in the platform.

Hotspot Manager — Centrally monitor and manage the clients authorized by portal authentication.

Global Search Feature

Click 🔒 and enter the keywords to quickly look up the functions or devices that you want to configure. And you can search for the devices by their MAC addresses and device names.

My Account

Click the account icon 🔔 to display account information, Account Settings and Log Out. You can change your password on Account Settings.

More Settings

Click : to display Preferences, About, Tutorial and Feedback.

Preferences: Click to jump to Maintenance and customize the Controller UI depending on your needs. For details, refer to 5.6 Maintenance

About: Click to display the controller version.

Tutorial: Click to view the quick Getting Started guide which demonstrates the navigation and tools available for the controller.

Feedback: Click to send your feedback to us.

The left-hand navigation bar provides access to:

Dashboard
StatisticsDashboard displays a summarized view of the network status through different visualizations. The customizable and widget-driven dashboard is a powerful tool that arms you with real-time data for monitoring the network. With the drag and drop feature, you can modify your dashboard and re-arrange it to let you track all the important metrics.
MapStatistics provides a visual representation of the clients and network managed by the controller. The run charts show changes in device performances over time, including the status of switches and speed test results.
DevicesMap generates the system topology automatically and you can look over the provisioning status of devices. By clicking on each node, you can view the detailed information of each device. You can also upload images of your location for a visual representation of your network.
Clients
InsightsDevice displays all TP-Link devices discovered on the site and their general information. This list view can change depending on your monitoring need through customizing the columns. You can click any device on the list to reveal the Properties window for more detailed information of each device and provisioning individual configurations to the device.
Logs
ToolsClients displays a list view of wired and wireless clients that are connected to the network. This list view can change depending on your monitoring need through customizing the columns. You can click any clients on the list to reveal the Properties window for more detailed information of each client and provisioning individual configurations to the client.
ReportsInsights displays a list of statistics of your network device, clients and services during a specified period. You can change the range of date in one-day increments.
Log shows log lines about varied activities of users, devices, and systems events, such as administrative actions and abnormal device behaviors. Comprehensive logs make historical information more accurate, readily accessible, and usable, which allows for proactive troubleshooting. And you can determine alert-level events and enable pushing notifications.
Tools provides various network tools for you to test the device connectivity, capture packets for troubleshooting, and open Terminal to execute CLI or Shell commands.
Reports provides intuitive charts and detailed statistics concerning your network situation, managed devices, and connected clients.
Settings allows you to provision and configure all your network devices on the same site in minutes and maintain the controller system for best performance.

4.2 Modify the Current Site Configuration

You can view and modify the configurations of the current site in Site, including the basic site information, centrally-managed device features, and the device account. The features and device account configured here are applied to all devices on the site, so you can easily manage the devices centrally.

4.2.1 Site Configuration

Overview

In Site Configuration, you can view and modify the site name, location, time zone, and application scenario of the current site.

Configuration

Select a site from the drop-down list of Organization in the top-right corner, go to Settings > Site, and configure the following information of the site in Site Configuration. Click Save.

Site Configuration
Site Name: default Country/Region: China mainland Time Zone: (UTC) UTC Daylight Saving Time Enable

TP-LINK Omada SDN Controller - Configuration - 2

- DST is applicable only when the device supports the feature. To make DST work properly, it is recommended to upgrade your devices to the latest firmware version. - The DST configuration here only takes effect on the site. To configure the DST for the controller, go to the Controller Configuration. - With DST configured, the valid duration of Local User will be influenced accordingly

Time Offset: 60 minutes Starts On: Week Day Month Time 1st Sunday January 00:00 Ends On: Week Day Month Time 1st Sunday January 00:00

Application Scenario: Hotel Longitude: (Optional, -180~180, with a maximum of 16 decimal places.) Latitude: (Optional, -90~90, with a maximum of 16 decimal places.) Address: (Optional) Refresh

Site Name Specify the name of the current site. It should be no more than 64 characters.

Country/Region Select the location of the site.

Time Zone Select the time zone of the site.

Daylight Saving TimeEnable the feature if your country/region implements DST. When it is enabled, the iconDSTwill appear on the upper right, showing the DST settings and status.
Time Offset Select the time added in minutes when Daylight Saving Time starts.
Starts OnSpecify the time when the DST starts. The clock will be set forward by the time offset you specify.
Ends On Specify the time when the DST ends.The clock will be set back by the time offset you specify.
Application ScenarioSpecify the application scenario of the site. To customize your scenario, clickCreate New Scenarioin the drop-down list.
Longitude / Latitude / AddressConfigure the parameters according to where the site is located. These fields are optional.

4.2.2 Services

Overview

In Services, you can view and modify the features applied to devices on the current site. Most features are applied to all devices, such as LED and Alert Emails, while some are applied to APs only, such as Channel Limit and Mesh.

Configuration

Select a site from the drop-down list of Sites in the top-right corner, go to Settings > Site, and configure the following features for the current site in Services. Click Save.

Services

LED:

TP-LINK Omada SDN Controller - Services - 1

Enable

Channel Limit:

TP-LINK Omada SDN Controller - Services - 2

Enable

TP-LINK Omada SDN Controller - Services - 3

Mesh

TP-LINK Omada SDN Controller - Services - 4

Enable

TP-LINK Omada SDN Controller - Services - 5

Auto Failover:

TP-LINK Omada SDN Controller - Services - 6

Enable

TP-LINK Omada SDN Controller - Services - 7

Connectivity Detection

Auto (Recommended)

Full-Sector DFS:

TP-LINK Omada SDN Controller - Services - 8

Enable

TP-LINK Omada SDN Controller - Services - 9

LLDP

TP-LINK Omada SDN Controller - Services - 10

Enable

TP-LINK Omada SDN Controller - Services - 11

Remote Logging:

TP-LINK Omada SDN Controller - Services - 12

Enable

TP-LINK Omada SDN Controller - Services - 13

Syslog Server IP/Hostname

TP-LINK Omada SDN Controller - Services - 14

-

TP-LINK Omada SDN Controller - Services - 15

Syslog Server Port

TP-LINK Omada SDN Controller - Services - 16

4

TP-LINK Omada SDN Controller - Services - 17

Client Detail Logs

TP-LINK Omada SDN Controller - Services - 18

Enable

TP-LINK Omada SDN Controller - Services - 19

Advanced Features

TP-LINK Omada SDN Controller - Services - 20

Enable

TP-LINK Omada SDN Controller - Services - 21

The advanced features needs to be configured by network administrators with the knowledge of WLAN parameters. If you are not sure about your network conditions and the potential impact of any settings, we recommend you keep the default configurations

LED Enable or disable LEDs of all devices in the site.

By default, the device follows the LED setting of the site it belongs to. To change the LED setting for certain devices, refer to Chapter 6. Configure and Monitor Controller-Managed Devices.

Channel Limit

(For Outdoor APs) When enabled, outdoor APs do not use the channel with the frequency ranging from 5150 MHz to 5350 MHz to meet the local laws and regulations limit in EU countries.

Mesh When enabled, APs supporting Mesh can establish the mesh network at the site.

Auto Failover

(For APs in the mesh network) Auto Failover is used to automatically maintain the mesh network. When enabled, the controller will automatically select a new wireless uplink for the AP if the original uplink fails.

To enable this feature, enable Mesh first.

Connectivity Detection(For APs in the mesh network) Specify the method of Connection Detection when mesh is enabled.In a mesh network, the APs can send ARP request packets to a fixed IP address to test the connectivity. If the link fails, the status of these APs will change to Isolated.Auto (Recommended): Select this method and the mesh APs will send ARP request packets to the default gateway for the detection.Custom IP Address: Select this method and specify a desired IP address. The mesh APs will send ARP request packets to the custom IP address to test the connectivity. If the IP address of the AP is in different network segments from the custom IP address, the AP will use the default gateway IP address for the detection.
Full-Sector DFS(For APs in the mesh network) With this feature enabled, when radar signals are detected on current channel by one AP, the other APs in the mesh network will be also informed. Then all APs in the mesh network will switch to an alternate channel.To enable this feature, enable Mesh first.
LLDP Click the checkbox to enable LLDP (Link Layer Discovery Protocol) for device discovery and auto-configuration of VoIP devices.
Remote LoggingWith this feature configured, the controller will send generated site logs to the log server.When enabled, the following items are required:Syslog Server IP/Hostname: Enter the IP address or hostname of the log server.Syslog Server Port: Enter the port of the server.Client Detail Logs: With this feature enabled, the logs of clients will be sent to the syslog server.
Advanced Features(For APs) When enabled, you can configure more features for APs in Advanced Features.When disabled, these features keep the default settings.For detailed configuration, refer to 4.2.3 Advanced Features.

4.2.3 Advanced Features

Overview

Advanced features include Fast Roaming, Band Steering, and Beacon Control. They are applicable to APs and wireless gateways/routers. With these advanced features configured properly, you can improve the network's stability, reliability and communication efficiency.

Advanced features are recommended to be configured by network administrators with the WLAN knowledge. If you are not sure about your network conditions and the potential impact of all settings, keep Advanced Features disabled in Services to use their default configurations.

Configuration

Select a site from the drop-down list of Organization in the top-right corner, go to Settings > Site, and enable Advanced Features in Services first. Then configure the following features in Advanced Features. Click Save.

Advanced Features: Enable The advanced features needs to be configured by network administrators with the knowledge of WLAN parameters. If you are not sure about your network conditions and the potential impact of any settings, we recommend you keep the default configurations. Fast Roaming: Enable i AI Roaming: Enable i Dual Band 11k Report: Enable i Force-Disassociation: Enable i Band Steering: Prefer 5 GHz / 6 GHz i Beacon Control 2.4 GHz 5 GHz 6 GHz Beacon Interval: Custom 100 ms (40-500) DTIM Period: 1 (1-255) RTS Threshold: 2347 (1-2347) Fragmentation Threshold: 2346 (256-2346, works only on 802.11b/g mode.) Airtime Fairness: Enable i

Fast RoamingWith this feature enabled, wireless clients that support 802.11k/v can improve fast roaming experience when moving among different APs and wireless gateways/routers.By default, it is disabled. This feature is available for some certain devices.
AI RoamingWith Fast Roaming enabled, you can enable AI Roaming to facilitate Fast Roaming, which improves roaming experience of the wireless clients that support 802.11k/v. This feature is available for certain models.
Dual Band 11k ReportWhen disabled, the controller provides neighbor list that contains only neighbor APs and wireless gateways/routers in the same band with which the client is associated.When enabled, the controller provides neighbor list that contains neighbor APs and wireless gateways/routers in both 2.4 GHz and 5 GHz bands.This feature is available only when Fast Roaming is enabled. By default, it is disabled.
Force-DisassociationWith this feature disabled, the AP and wireless gateway/router only issues an 802.11v roaming suggestion when a client's link quality drops below the predefined threshold and there is a better option of AP or wireless gateway/router, but whether to roam or not is determined by the client.With this feature enabled, the AP and wireless gateway/router will force disassociate the client if it does not re-associate to another AP or wireless gateway/router.This feature is available only when Fast Roaming is enabled. By default, it is disabled.
Band SteeringBand steering can adjust the number of clients in 2.4 GHz, 5 GHz and 6 GHz bands to provide better wireless experience.When enabled, multi-band clients will be steered to the 5 GHz and 6 GHz band according to the configured parameters. This function can improve the network performance because the 5 GHz and 6 GHz band supports a larger number of non-overlapping channels and is less noisy.
Beacon ControlBeacons are transmitted periodically by the AP and wireless gateway/router to announce the presence of a wireless network for the clients. Click +, select the band, and configure the following parameters of Beacon Control.Beacon Interval: Specify how often the APs and wireless gateways/routers send a beacon to clients. By default, it is 100.DTIM Period: Specify how often the clients check for buffered data that are still on the AP or wireless gateway/router awaiting pickup. By default, the clients check for them at every beacon.DTIM (Delivery Traffic Indication Message) is contained in some Beacon frames indicating whether the AP or wireless gateway/router has buffered data for client devices. An excessive DTIM interval may reduce the performance of multicast applications, so we recommend that you keep the default interval, 1.RTS Threshold: RTS (Request to Send) can ensure efficient data transmission by avoiding the conflict of packets. If a client wants to send a packet larger than the threshold, the RTS mechanism will be activated to delay packets of other clients in the same wireless network.We recommend that you keep the default threshold, which is 2347. If you specify a low threshold value, the RTS mechanism may be activated more frequently to recover the network from possible interference or collisions. However, it also consumes more bandwidth and reduces the throughput of the packet.Fragmentation Threshold: Fragmentation can limit the size of packets transmitted over the network. If a packet to be sent exceeds the Fragmentation threshold, the Fragmentation function will be activated, and the packet will be fragmented into several packets. By default, the threshold is 2346.Fragmentation helps improve network performance if properly configured. However, too low fragmentation threshold may result in poor wireless performance because of the increased message traffic and the extra work of dividing up and reassembling frames.Airtime Fairness: With this option enabled, each client connecting to the AP or wireless gateway/router can get the same amount of time to transmit data so that low-data-rate clients do not occupy too much network bandwidth and network performance improves as a whole. We recommend you enable this function under multi-rate wireless networks.

4.2.4 Device Account

You can specify a device account for all adopted devices on the site in batches. Once the devices are adopted by the controller, their username and password become the same as settings in Device Account to protect the communication between the controller and devices. By default, the username is admin and the password is generated randomly.

Select a site from the drop-down list of Organization. Go to Settings > Site and modify the username and password in Device Account. Click Save and the new username and password are applied to all devices on the site.

Device Account

Username:

admin

Password:

●●●●●●●

TP-LINK Omada SDN Controller - Device Account - 1

4.3 Configure Wired Networks

Wired networks enable your wired devices and clients including the gateway, switches, APs and PCs to connect to each other and to the internet.

As shown in the following figure, wired networks consist of two parts: Internet and LAN.

Wired Networks
TP-LINK Omada SDN Controller - Configure Wired Networks - 1

flowchart
graph TD
    A["Internet"] --> B["WAN Port"]
    B --> C["Gateway"]
    C --> D["Switch C"]
    D --> E["Omada Controller"]
    D --> F["Switch A"]
    D --> G["Switch B"]
    D --> H["FTP Server"]
    style A fill:#99CCFF
    style B fill:#99CCFF
    style C fill:#99CCFF
    style D fill:#99CCFF
    style E fill:#99CCFF
    style F fill:#99CCFF
    style G fill:#99CCFF
    style H fill:#99CCFF

For Internet, you determine the number of WAN ports on the gateway and how they connect to the internet. You can set up an IPv4 connection and IPv6 connection to your internet service provider (ISP) according to your needs. The parameters of the internet connection for the gateway depend on which connection types you use. For an IPv4 connection, the following internet connection types are available: Dynamic IP, Static IP, PPPoE, L2TP, and PPTP. For an IPv6 connection, the following internet connection types are available: Dynamic IP (SLAAC/ DHCPv6), Static IP, PPPoE, 6to4 Tunnel, and Pass-Through (Bridge). And, when more than one WAN port is configured, you can configure Load Balancing to optimize the resource utilization if needed.

For LAN, you configure the wired internal network and how your devices logically separate from or connect to each other by means of VLANs and interfaces. Advanced LAN features include IGMP Snooping, DHCP Server and DHCP Options, PoE, Voice Network, 802.1X Control, Port Isolation, Spanning Tree, LLDP-MED, and Bandwidth Control.

4.3.1 Set Up an Internet Connection

Configuration

To set up an internet connection, follow these steps:

1) Configure the number of WAN ports on the gateway based on needs.
2) Configure WAN Connections. You can set up the IPv4 connection, IPv6 connection, or both.
3) (Optional) Configure Load Balancing if more than one WAN port is configured.

Select WAN Mode Configure WAN Connections (Optional) Configure Load Balancing

Select a site from the drop-down list of Organization. Go to Settings > Wired Networks > Internet to load the following page. In WAN Mode, configure the number of WAN ports deployed by the gateway and other parameters. Then click Apply.

WAN Mode

TP-LINK Omada SDN Controller - WAN Mode - 1

WAN Settings Overrides:

TP-LINK Omada SDN Controller - WAN Mode - 2

TP-LINK Omada SDN Controller - WAN Mode - 3

  • With WAN Settings Overrides disabled, the WAN settings of the newly adopted Omada gateway in standalone mode will take effect on the controller.
  • When WAN Settings Overrides is turned on, the gateway will use the configurations on the Controller after adoption. Please make sure the configurations are correct. Otherwise the gateway may be unable to access the internet after adoption.
  • If the number of preconfigured WAN ports does not match the number of WAN ports enabled in the adopted Omada gateway, the gateway will automatically reboot after adoption.
  • If the adopted device does not support some pre-configurations, the relevant configurations will be deleted after adoption.

Gateway Model.

Online Detection Interval:

Custom Time:

TP-LINK Omada SDN Controller - WAN Mode - 4

Custom

10

Seconds

(1-3600)

TP-LINK Omada SDN Controller - WAN Mode - 5

Online Detection results will influence whether Load Balancing and Link Backup features take effect. The smaller the online detection interval, the faster Load Balancing and Link Backup features will respond, and meanwhile more detection packets will be sent

WAN Settings Overrides

With this option disabled, the WAN settings of the newly adopted Omada gateway in standalone mode will take effect on the controller.

When this option is turned on, the gateway will use the configurations on the Controller after adoption. Please make sure the configurations are correct. Otherwise the gateway may be unable to access the internet after adoption. If the adopted device does not support some pre-configurations, the relevant configurations will be deleted after adoption.

Gateway Model Specify the gateway model and version. If you change the gateway, follow the web instructions to select WAN ports and copy WAN port settings.

If the number of preconfigured WAN ports does not match the number of WAN ports enabled in the adopted Omada gateway, the gateway will automatically reboot after adoption.

Online Detection Interval

Select how often the WAN ports detect WAN connection status. If you don't want to enable online detection, select Disable.

Online Detection results will influence whether Load Balancing and Link Backup features take effect. The smaller the online detection interval, the faster Load Balancing and Link Backup features will respond, and meanwhile more detection packets will be sent.

Select WAN Mode

Configure WAN Connections

(Optional) Configure Load Balancing

TP-LINK Omada SDN Controller - (Optional) Configure Load Balancing - 1

Note:

The number of configurable WAN ports is decided by WAN Mode.

- Set Up USB Modem Connection

Select a site from the drop-down list of Organization. Go to Settings > Wired Networks > Internet. In the WAN Ports Config section, click the edit icon of USB Modem and configure the parameters.

USB Modem Description: (Optional) USB Modem: No USB modem Connected. Config Type: Auto Location: Argentina Mobile ISP: Claro SIM/UIM PIN: (Optional) Connection Mode: Connect Automatically Connect Manually Authentication Type: Auto MTU Size: 1480 bytes Use the following DNS Servers: Enable

Description Enter a description for identification.

USB Modem Display whether a USB modem is connected to the device and the name of the connected USB modem.

Config Type Select a configuration type for the USB modem.
Auto: Use the Location and Mobile ISP information below for configuration.Manually: Enter the Dial Number, APN, Username, and password provided by your Mobile ISP.
Location Select your location.
Mobile ISP Select your mobile ISP.
Message Display the current status of the SIM card.
SIM/UIM PIN (Optional) Enter the PIN of your SIM card.The field is required when the following information appears in the Message: PIN protection is enabled and the PIN is invalid.
Connection Mode Select the connection mode.
Connect Automatically: The router will use the USB modem to connect to the internet automatically.
Connect Manually: You need to turn on/off the internet manually for the gateway on the device page.
Authentication ModeSelect the Authentication mode for the USB modem. The default value is Auto, and it is recommended to keep the default value.
MTU Size Specify the MTU (Maximum Transmission Unit) of the USB WAN port. The default value is 1480, and it is recommended to keep the default value.MTU is the maximum data unit transmitted in the physical network.
Use the following DNS ServersEnable the feature if you want to specify the Primary and Secondary DNS servers manually.

- Set Up IPv4 Connection

Select a site from the drop-down list of Organization. Go to Settings > Wired Networks > Internet. In the WAN Ports Config section, click the edit icon of a WAN port and configure the Connection Type according to the service provided by your ISP.

Connection Type

Dynamic IP: If your ISP automatically assigns the IP address and the corresponding parameters, choose Dynamic IP.

Static IP: If your ISP provides you with a fixed IP address and the corresponding parameters, choose Static IP.

PPPoE: If your ISP provides you with a PPPoE account, choose PPPoE.

L2TP: If your ISP provides you with an L2TP account, choose L2TP.

PPTP: If your ISP provides you with a PPTP account, choose PPTP.

■ Dynamic IP

Choose Connection Type as Dynamic IP and configure the parameters.

IPv4 Connection Type: Dynamic IP Advanced Settings Unicast DHCP: Enable Primary DNS Server: . . . (Optional) Secondary DNS Server: . . . (Optional) Host Name: (Optional) MTU: 1500 (575-1500, default:1500) Internet VLAN: Enable WAN IP Alias

Unicast DHCP With this option enabled, the gateway will require the DHCP server to assign the IP address by sending unicast DHCP packets. Usually you need not to enable the option.
Primary DNS Server / Secondary DNS ServerEnter the IP address of the DNS server provided by your ISP if there is any.
Host Name Enter a name for the gateway.
MTU Specify the MTU (Maximum Transmission Unit) of the WAN port.MTU is the maximum data unit transmitted in the physical network. When the connection type is Dynamic IP, MTU can be set in the range of 576-1500 bytes. The default value is 1500.
Internet VLAN Add the WAN port to a VLAN and you need to specify the VLAN ID. Generally, you don't need to manually configure it unless required by your ISP.
Internet VLAN PriorityPriority is only available when Internet VLAN is enabled. The Internet VLAN Priority function helps to prioritize the internet traffic based on your needs. You can determine the priority level for the traffic by specifying the tag. The tag ranges from 0 to 7. None means the packet will be forwarded without any operation.
WAN IP Alias WAN IP Alias supports configuring multiple IP addresses on one WAN port, and these IP addresses can be used to configure virtual server and other functions.

■ Static IP

Choose Connection Type as Static IP and configure the parameters.

IPv4 Connection Type: Static IP IP Address: . . . . Subnet Mask: . . . . Default Gateway: . . . (Optional) Advanced Settings Primary DNS Server: . . . . (Optional) Secondary DNS Server: . . . . (Optional) MTU: 1500 (576-1500, default:1500) Internet VLAN: Enable WAN IP Alias

IP Address Enter the IP address provided by your ISP.
Subnet Mask Enter the subnet mask provided by your ISP.
Default Gateway Enter the default gateway provided by your ISP.
Primary DNS Server / Secondary DNS ServerEnter the IP address of the DNS server provided by your ISP if there is any.
MTU Specify the MTU (Maximum Transmission Unit) of the WAN port.MTU is the maximum data unit transmitted in the physical network. When the connection type is Static IP, MTU can be set in the range of 576-1500 bytes. The default value is 1500.
Internet VLAN Add the WAN port to a VLAN and you need to specify the VLAN ID. Generally, you don't need to manually configure it unless required by your ISP.
Internet VLAN PriorityPriority is only available when Internet VLAN is enabled. The Internet VLAN Priority function helps to prioritize the internet traffic based on your needs. You can determine the priority level for the traffic by specifying the tag. The tag ranges from 0 to 7. None means the packet will be forwarded without any operation.
WAN IP Alias WAN IP Alias supports configuring multiple IP addresses on one WAN port, and these IP addresses can be used to configure virtual server and other functions.

■ PPPoE

Choose Connection Type as PPPoE and configure the parameters.

IPv4 Connection Type: PPPoE Username: Password: Advanced Settings Get IP Address from ISP: Enable Primary DNS Server: . . . (Optional) Secondary DNS Server: . . . (Optional) Connection Mode: Connect Automatically Connect Manually Time-based Redial Interval: 10 Seconds (1-99999) Service Name: (Optional) i MTU: 1492 (576-1492, default:1492) MRU: 1492 (576-1492, default:1492) MSS Clamping: Disable Auto Custom (532-1452) Internet VLAN: Enable Secondary Connection: None Static IP Dynamic IP

Username Enter the PPPoE username provided by your ISP.

Password Enter the PPPoE password provided by your ISP.

Get IP address from ISPWith this option enabled, the gateway gets IP address from ISP when setting up the WAN connection.With this option disabled, you need to specify theIP Addressprovided by your ISP.
Primary DNS Server / Secondary DNS ServerEnter the IP address of the DNS server provided by your ISP if there is any.
Connection Mode Connect Automatically: The gateway activates the connection automatically when the connection is down. You need to specify theRedial Interval, which decides how often the gateway tries to redial after the connection is down.Connect Manually: You can manually activate or terminate the connection.Time-Based: During the specified period, the gateway will automatically activate the connection. You need to specify theTime Rangewhen the connection is up.
Service Name Keep it blank unless your ISP requires you to configure it.
MTU Specify the MTU (Maximum Transmission Unit) of the WAN port.MTU is the maximum data unit transmitted in the physical network. When the connection type is PPPoE, MTU can be set in the range of 576-1492 bytes. The default value is 1492.
MRU Specify the MRU (Maximum Receive Unit) of the WAN port. MRU is the maximum data unit transmitted in the Data link layer.
MSS Clamping Specify the upper limit of the value of the MSS (Maximum Segment Size) field negotiated by the sending and receiving parties when establishing TCP connection to avoid IP fragmentation. If the value of the MSS field negotiated by the communication parties exceeds the specified value, the gateway will change the negotiated MSS field to the specified valueDisabled: Disable the MSS Clamping function, and the gateway will not intervene in the MSS value negotiated by the communication parties.Auto: Automatically calculate MSS value based on path MTU.Custom: Select this option to specify the MSS value. It should not exceed the MTU value.
Internet VLAN Add the WAN port to a VLAN and you need to specify the VLAN ID. Generally, you don't need to manually configure it unless required by your ISP.
Internet VLAN PriorityPriority is only available when Internet VLAN is enabled. The Internet VLAN Priority function helps to prioritize the internet traffic based on your needs. You can determine the priority level for the traffic by specifying the tag. The tag ranges from 0 to 7. None means the packet will be forwarded without any operation.

Secondary Connection Secondary connection is required by some ISPs. Select the connection type required by your ISP.

None: Select this if the secondary connection is not required by your ISP.

Static IP: Select this if your ISP provides you with a fixed IP address and subnet mask for the secondary connection. You need to specify the IP Address and Subnet Mask provided by your ISP.

Dynamic IP: Select this if your ISP automatically assigns the IP address and subnet mask for the secondary connection.

L2TP

Choose Connection Type as L2TP and configure the parameters.

IPv4 Connection Type: L2TP Username: Password: VPN Server/Domain Name: Get IP Address from ISP: ✓ Enable Primary DNS Server: . . . . (Optional) Secondary DNS Server: . . . . (Optional) Connection Mode: ● Connect Automatically ○ Connect Manually ○ Time-based Redial Interval: 10 Seconds (1-99999) MTU: 1460 (576-1460, default:1460) MSS Clamping: ○ Disable ● Auto ○ Custom (532-1452) Internet VLAN: □ Enable Secondary Connection: ○ Static IP ● Dynamic IP

Username Enter the L2TP username provided by your ISP.

Password Enter the L2TP password provided by your ISP.

VPN Server / Domain Name Enter the VPN Server/Domain Name provided by your ISP.

Get IP address from ISP With this option enabled, the gateway gets IP address from ISP when setting up the WAN connection.

With this option disabled, you need to specify the IP address provided by your ISP.

Primary DNS Server / Secondary DNS ServerEnter the IP address of the DNS server provided by your ISP if there is any.
Connection Mode Connect Automatically: The gateway activates the connection automatically when the connection is down. You need to specify the Redial Interval, which decides how often the gateway tries to redial after the connection is down.
Connect Manually: You can manually activate or terminate the connection.
Time-Based: During the specified period, the gateway will automatically activate the connection. You need to specify the Time Range when the connection is up.
MTU Specify the MTU (Maximum Transmission Unit) of the WAN port.
MTU is the maximum data unit transmitted in the physical network. When the connection type is L2TP, MTU can be set in the range of 576-1460 bytes. The default value is 1460.
MSS Clamping Specify the upper limit of the value of the MSS (Maximum Segment Size) field negotiated by the sending and receiving parties when establishing TCP connection to avoid IP fragmentation. If the value of the MSS field negotiated by the communication parties exceeds the specified value, the gateway will change the negotiated MSS field to the specified value
Disabled: Disable the MSS Clamping function, and the gateway will not intervene in the MSS value negotiated by the communication parties.
Auto: Automatically calculate MSS value based on path MTU.
Custom: Select this option to specify the MSS value. It should not exceed the MTU value.
Internet VLAN Add the WAN port to a VLAN and you need to specify the VLAN ID. Generally, you don't need to manually configure it unless required by your ISP.
Internet VLAN PriorityPriority is only available when Internet VLAN is enabled. The Internet VLAN Priority function helps to prioritize the internet traffic based on your needs. You can determine the priority level for the traffic by specifying the tag. The tag ranges from 0 to 7. None means the packet will be forwarded without any operation.
Secondary Connection Select the connection type required by your ISP.
Static IP: Select this if your ISP provides you with a fixed IP address and subnet mask for the secondary connection. You need to specify the IP Address, Subnet Mask, Default Gateway (Optional), Primary DNS Server (Optional), and Secondary DNS Server (Optional) provided by your ISP.
Dynamic IP: Select this if your ISP automatically assigns the IP address and subnet mask for the secondary connection.

■ PPTP

Choose Connection Type as PPTP and configure the parameters.

IPv4 Connection Type: PPTP Username: Password: VPN Server/Domain Name: Get IP Address from ISP: Enable Primary DNS Server: . . . (Optional) Secondary DNS Server: . . . (Optional) Connection Mode: Connect Automatically Connect Manually Time-based Redial Interval: 10 Seconds (1-99999) MTU: 1420 (576-1420, default:1420) MSS Clamping: Disable Auto Custom (532-1452) Internet VLAN: Enable Secondary Connection: Static IP Dynamic IP

Username Enter the PPTP username provided by your ISP.
Password Enter the PPTP password provided by your ISP.
VPN Server / Domain Name Enter the VPN Server/Domain Name provided by your ISP.
Get IP address from ISPWith this option enabled, the gateway gets IP address from ISP when setting up the WAN connection.With this option disabled, you need to specify theIP addressprovided by your ISP.
Primary DNS Server / Secondary DNS ServerEnter the IP address of the DNS server provided by your ISP if there is any.
Connection Mode Connect Automatically: The gateway activates the connection automatically when the connection is down. You need to specify the Redial Interval, which decides how often the gateway tries to redial after the connection is down.
Connect Manually: You can manually activate or terminate the connection.
Time-Based: During the specified period, the gateway will automatically activate the connection. You need to specify the Time Range when the connection is up.
MTU Specify the MTU (Maximum Transmission Unit) of the WAN port.
MTU is the maximum data unit transmitted in the physical network. When the connection type is PPTP, MTU can be set in the range of 576-1420 bytes. The default value is 1420.
MSS Clamping Specify the upper limit of the value of the MSS (Maximum Segment Size) field negotiated by the sending and receiving parties when establishing TCP connection to avoid IP fragmentation. If the value of the MSS field negotiated by the communication parties exceeds the specified value, the gateway will change the negotiated MSS field to the specified value
Disabled: Disable the MSS Clamping function, and the gateway will not intervene in the MSS value negotiated by the communication parties.
Auto: Automatically calculate MSS value based on path MTU.
Custom: Select this option to specify the MSS value. It should not exceed the MTU value.
Internet VLAN Add the WAN port to a VLAN and you need to specify the VLAN ID. Generally, you don't need to manually configure it unless required by your ISP.
Internet VLAN PriorityPriority is only available when Internet VLAN is enabled. The Internet VLAN Priority function helps to prioritize the internet traffic based on your needs. You can determine the priority level for the traffic by specifying the tag. The tag ranges from 0 to 7. None means the packet will be forwarded without any operation.

Secondary Connection Select the connection type required by your ISP.

Static IP: Select this if your ISP provides you with a fixed IP address and subnet mask for the secondary connection. You need to specify the IP Address, Subnet Mask, Default Gateway (Optional), Primary DNS Server (Optional), and Secondary DNS Server (Optional) provided by your ISP.

Dynamic IP: Select this if your ISP automatically assigns the IP address and subnet mask for the secondary connection.

- Set Up IPv6 Connection

For IPv6 connections, check the box to enable the IPv6 connection, select the internet connection type according to the requirements of your ISP.

Connection Type

Dynamic IP (SLAAC/DHCPv6): If your ISP uses Dynamic IPv6 address assignment, either DHCPv6 or SLAAC+Stateless DHCP, select Dynamic IP (SLAAC/DHCPv6).

Static IP: If your ISP provides you with a fixed IPv6 address, select Static IP.

PPPoE: If your ISP uses PPPoEv6, and provides a username and password, select PPPoE.

6to4 Tunnel: If your ISP uses 6to4 deployment for assigning IPv6 address, select 6to4 Tunnel. 6to4 is an internet transition mechanism for migrating from IPv4 to IPv6, a system that allows IPv6 packets to be transmitted over an IPv4 network. The IPv6 packet will be encapsulated in the IPv4 packet and transmitted to the IPv6 destination through IPv4 network.

Pass-Through (Bridge): In Pass-Through (Bridge) mode, the gateway works as a transparent bridge. The IPv6 packets received from the WAN port will be transparently forwarded to the LAN port and vice versa. No extra parameter is required.

■ Dynamic IP (SLAAC/DHCPv6)

Choose Connection Type as Dynamic IP (SLAAC/DHCPv6) and configure the parameters.

Connection Type: Dynamic IP (SLAAC/DHCPv6) Get IPv6 Address: Automatically Vía SLAAC Vía DHCPv6 Non-Address Prefix Delegation: Enable i Prefix Delegation Size: (48-64) i DNS Address: Get from ISP Dynamically Use the Following DNS Addresses

Get IPv6 Address Select the proper method whereby your ISP assigns IPv6 address to your gateway.
Automatically: With this option selected, the gateway will automatically select SLAAC or DHCPv6 to get IPv6 addresses.
Via SLAAC: With SLAAC (Stateless Address Auto-Configuration) selected, your ISP assigns the IPv6 address prefix to the gateway and the gateway automatically generates its own IPv6 address. Also, your ISP assigns other parameters including the DNS server address to the gateway.
Via DHCPv6: With DHCPv6 selected, your ISP assigns an IPv6 address and other parameters including the DNS server address to the gateway using DHCPv6.
Non-Address: With this option selected, the gateway will not get an IPv6 address.
Prefix Delegation Select Enable to get an address prefix by DHCPv6 server from your ISP, or Disable to designate an address prefix for your LAN port manually. Clients in LAN will get an IPv6 address with this prefix.
Prefix Delegation SizeWith Prefix Delegation enabled, enter the Prefix Delegation Size to determine the length of the address prefix. If you are not sure about the value, you can ask your ISP.
DNS Address Select whether to get the DNS address dynamically from your ISP or designate the DNS address manually.
Get from ISP Dynamically: The DNS address will be automatically assigned by the ISP.
Use the Following DNS Addresses: Enter the DNS address provided by the ISP.

■ Static IP

Choose Connection Type as Static IP and configure the parameters.

Connection Type:Static IP
IPv6 Address:(Format: 2001::)
Prefix Length:(1-128) i
Default Gateway:(Format: 2001::)
Primary DNS Server:(Format: 2001::)
Secondary DNS Server:(Optional. Format: 2001::)

IPv6 Address Enter the static IPv6 address information received from your ISP.

Prefix Length Enter the prefix length of the IPv6 address received from your ISP.

Default Gateway Enter the default gateway provided by your ISP.

Primary DNS Server Enter the IP address of the primary DNS server provided by your ISP.

Secondary DNS Server (Optional) Enter the IP address of the secondary DNS server, which provides redundancy in case the primary DNS server goes down.

■ PPPoE

Choose Connection Type as PPPoE and configure the following parameters. Then click Apply.

Connection Type: PPPoE Share the same PPPoE session with IPv4 Username: Password: Get IPv6 Address: Automatically Via SLAAC Via DHCPv6 Non-Address Specified by ISP Prefix Delegation: Enable i Prefix Delegation Size: (48-64) i DNS Address: Get from ISP Dynamically Use the Following DNS Addresses

Share the same PPPoE session with IPv4If your ISP provides only one PPPoE account for both IPv4 and IPv6 connections, and you have already established an IPv4 connection on this WAN port, you can check the box, then the WAN port will use the PPP session of IPv4 PPPoE connection to get the IPv6 address. In this case, you do not need to enter the username and password of the PPPoE account. If your ISP provides two separate PPPoE accounts for the IPv4 and IPv6 connections, or the IPv4 connection of this WAN port is not based on PPPoE, do not check the box and manually enter the username and password for the IPv6 connection.
Username Enter the username of your PPPoE account provided by your ISP.
Password Enter the password of your PPPoE account provided by your ISP.
Get IPv6 Address Select the proper method whereby your ISP assigns IPv6 address to your gateway.
Automatically: With this option selected, the gateway will automatically select the method to get IPv6 addresses between SLAAC and DHCPv6.
Via SLAAC: With SLAAC (Stateless Address Auto-Configuration) selected, your ISP assigns the IPv6 address prefix to the gateway and the gateway automatically generates its own IPv6 address. Also, your ISP assigns other parameters including the DNS server address to the gateway.
Via DHCPv6: With DHCPv6 selected, your ISP assigns an IPv6 address and other parameters including the DNS server address to the gateway using DHCPv6.
Non-Address: With this option selected, the gateway will not get an IPv6 address.
Specified by ISP: With this option selected, enter the IPv6 address you get from your ISP.
Prefix DelegationSelect Enable to get an address prefix by DHCPv6 server from your ISP, or Disable to designate an address prefix for your LAN port manually. Clients in LAN will get an IPv6 address with this prefix.
Prefix Delegation SizeWith Prefix Delegation enabled, enter the Prefix Delegation Size to determine the length of the address prefix. If you are not sure about the value, you can ask your ISP.
DNS Address Select whether to get the DNS address dynamically from your ISP or designate the DNS address manually.
Get from ISP Dynamically: The DNS address will be automatically assigned by the ISP.
Use the Following DNS Addresses: Enter the DNS address provided by the ISP.

■ 6to4 Tunnel

Choose Connection Type as 6to4 Tunnel and configure the parameters.

Connection Type:

6to4 Tunnel

TP-LINK Omada SDN Controller - ■ 6to4 Tunnel - 1

If you want to configure the IPv6 address on the LAN side, it is recommended to use the SLAAC+Stateless DHCP or SLAAC+RDNSS dialing method on the LAN side. If you want to use the DHCPv6 configuration, ensure that the first 48 bits are the same as the 6to4 IPv6 address on the WAN side; otherwise IPv6 WAN-LAN connection may not work.

DNS Address:

TP-LINK Omada SDN Controller - ■ 6to4 Tunnel - 2

Get from ISP Dynamically

TP-LINK Omada SDN Controller - ■ 6to4 Tunnel - 3

Use the Following DNS Addresses

DNS Address Select whether to get the DNS address dynamically from your ISP or designate the DNS address manually.

Get from ISP Dynamically: The DNS address will be automatically assigned by the ISP.

Use the Following DNS Addresses: Enter the DNS address provided by the ISP.

■ Pass-Through (Bridge)

Choose Connection Type as Pass-Through (Bridge) and no configuration is required for this type of connection.

Connection Type:

Pass-Through(Bridge)

- Set Up MAC Address

Select a site from the drop-down list of Organization. Go to Settings > Wired Networks > Internet. In the WAN Ports Config section, click the edit icon of a WAN port and configure the MAC address according to actual needs.

MAC Address Use Default MAC Address: The WAN port uses the default MAC address to set up the internet connection. It's recommended to use the default MAC address unless required otherwise.

Customize MAC Address: The WAN port uses a customized MAC address to set up the internet connection and you need to specify the MAC address. Typically, this is required when your ISP bound the MAC address with your account or IP address. If you are not sure, contact the ISP.

Select WAN Mode Configure WAN Connections (Optional) Configure Load Balancing

TP-LINK Omada SDN Controller - - Set Up MAC Address - 1

Note:

Loading Balancing is only available when you configure more than one WAN port.

Select a site from the drop-down list of Organization. Go to Settings > Wired Networks > Internet to load the following page. In Load Balancing, configure the following parameters and click Apply.

Load Balancing

Load Balancing Weight:1:1Pre-Populate
Application Optimized Routing:Enable i
Link Backup:Enable
Backup WAN:Please Select...
Primary WAN:Please Select...
Backup Mode:Link Backup i
Always Link Primary i
Mode:Enable backup link when any primary WAN fails
Enable backup link when all primary WANs fail

Load Balancing Weight Specify the ratio of network traffic that each WAN port carries.

Alternatively, you can clickPre-Populateto test the speed of WAN ports and automatically fill in the appropriate ratio according to test result.
Application Optimized RoutingWith Application Optimized Routing enabled, the router will consider the source IP address and destination IP address (or destination port) of the packets as a whole and record the WAN port they pass through. Then the packets with the same source IP address and destination IP address ( or destination port) will be forwarded to the recorded WAN port.This feature ensures that multi-connected applications work properly.
Link Backup With Link Backup enabled, the router will switch all the new sessions from dropped lines automatically to another to keep an always on-line network.
Backup WAN / Primary WANThe backup WAN port backs up the traffic for the primary WAN ports under the specified condition.
Backup Mode Link Backup: The system will switch all the new sessions from dropped line automatically to another to keep an always on-link network.Always Link Primary: Traffic is always forwarded through the primary WAN port unless it fails. The system will try to forward the traffic via the backup WAN port when it fails, and switch back when it recovers.
Mode Select whether to enable backup link when any primary WAN fails or all primary WANs fail.

4.3.2 Configure LAN Networks

Overview

The LAN function allows you to configure wired internal network. Based on 802.1Q VLAN, the Controller provides a convenient and flexible way to separate and deploy the network. The network can be logically segmented by departments, application, or types of users, without regard to geographic locations.

Configuration

To create a LAN, follow the guidelines:

1) Create a Network with specific purpose. For Layer 2 isolation, create a network as VLAN. To realize inter-VLAN routing, create a network as Interface, which is configured with a VLAN interface.
2) Create a port profile for the network. The profile defines how the packets in both ingress and egress directions are handled.
3) Assign the port profile to the desired ports of the switch to activate the LAN.

Create a Network Create a Port Profile Assign the Port Profile to the Ports

① Note:

A default Network (default VLAN) named LAN is preconfigured as Interface and is associated with all LAN ports of the Gateway and all switch ports. The VLAN ID of the default Network is 1. The default Network can be edited, but not deleted.

  1. Select a site from the drop-down list of Organization. Go to Settings > Wired Networks > LAN > Networks to load the following page.

Batch Delete VLAN NAME PURPOSE SUBNET PORTAL PORTAL NAME ACCESS CONTROL RULE RATE LIMIT VLAN ACTION Default Interface 192.168.0.1 / 24 1 Showing 1-1 of 1 records < 1 > 10 /page Go to page: GO + Create New LAN

  1. Click + Create New LAN to load the following page, enter a name to identify the network, and select the purpose for the network.

Create New LAN Name: Purpose: Interface VLAN

Purpose

Interface: Create the network with a Layer 3 interface, which is required for inter-VLAN routing.

VLAN: Create the network as a Layer 2 VLAN.

  1. Configure the parameters according to the purpose for the network.

■ Interface

Create New LAN

Name:

Purpose:

Interface

○ VLAN

LAN Interfaces:

WAN/LAN3

LAN

VLAN:

TP-LINK Omada SDN Controller - Create New LAN - 1

(1-4090) i

Gateway/Subnet:

TP-LINK Omada SDN Controller - Create New LAN - 2

TP-LINK Omada SDN Controller - Create New LAN - 3

Domain Name:

TP-LINK Omada SDN Controller - Create New LAN - 4

(Optional)

IGMP Snooping:

Enable i

MLD Snooping:

Enable i

DHCP Server:

Enable

DHCP Range:

TP-LINK Omada SDN Controller - Create New LAN - 5

TP-LINK Omada SDN Controller - Create New LAN - 6

DNS Server:

Auto

○ Manual

Lease Time:

120 minutes (2-10080)

Default Gateway:

Auto

○ Manual

Legal DHCP Servers:

Enable i

Legal DHCPv6 Servers:

Enable i

DHCP L2 Relay:

Enable i

TP-LINK Omada SDN Controller - Create New LAN - 7

Advanced DHCP Options

TP-LINK Omada SDN Controller - Create New LAN - 8

Configure IPv6

LAN Interface

Select the physical interfaces of the Gateway that this network will be associated with.

VLAN Enter a VLAN ID with the values between 1 and 4090. Each VLAN can be uniquely identified by VLAN ID, which is transmitted and received as IEEE 802.1Q tag in an Ethernet frame.

Gateway/Subnet Enter the IP address and subnet mask in the CIDR format. The CIDR Notation here includes the IP address and subnet mask of the default gateway. The summary of the information that you entered will show up below in real time.
Domain Name Enter the domain name.
IGMP SnoopingClick the checkbox to monitor IGMP (Internet Group Management Protocol) traffic and thereby manage multicast traffic.
MLD SnoopingClick the checkbox to monitor MLD (Multicast Listener Discovery) traffic and thereby manage IPv6 multicast traffic.
DHCP ServerClick the checkbox to allow the Gateway to serve as the DHCP server for this network. A DHCP server assigns IP addresses, DNS server, default gateway, and other parameters to all devices in the network. Deselect the box if there is already a DHCP server in the network.
DHCP Range Enter the starting and ending IP addresses of the DHCP address pool in the fields provided. For quick operation, click the Update DHCP Range beside the Gateway/Subnet entry to get the IP address range populated automatically, and edit the range according to your needs.
DNS Server Select a method to configure the DNS server for the network.
Auto: The DHCP server automatically assigns DNS server for devices in the network. It uses the IP address specified in the Gateway/Subnet entry as the DNS server address.
Manual: Specify DNS servers manually. Enter the IP address of a server in each DNS server field.
Lease TIme Specify how long a client can use the IP address assigned from this address pool.
Default Gateway Enter the IP address of the default gateway.
Auto: The DHCP server automatically assigns default gateway for devices in the network. It uses the IP address specified in the Gateway/Subnet entry as the default gateway address.
Manual: Specify default gateway manually. Enter the IP address of the default gateway in the field.
Legal DHCP ServersClick the checkbox to specify legal DHCP servers for the network. With legal DHCP servers configured, Gateways and Switches ensure that clients get IP addresses only from the DHCP servers specified here.
Legal DHCPv6 ServersClick the checkbox to specify legal DHCPv6 servers for the network. With legal DHCPv6 servers configured, Gateways and Switches ensure that clients get IPv6 addresses only from the DHCPv6 servers specified here.
DHCP L2 Relay Click the checkbox to enable DHCP L2 Relay for the network.

You can expand and configure Advanced DHCP Options if needed.

Advanced DHCP Options Option 60: (Optional) i Option 66: (Optional) i Option 138: . . . (Optional) i

Option 60Enter the value for DHCP Option 60. DHCP clients use this field to optionally identify the vendor type and configuration of a DHCP client. Mostly it is used in the scenario where the APs apply for different IP addresses from different servers according to the needs.
Option 66Enter the value for DHCP Option 66. It specifies the TFTP server information and supports a single TFTP server IP address.
Option 138Enter the value for DHCP Option 138. It is used in discovering the devices by the controller.

You can expand and configure IPv6 connections for the LAN clients if needed. First, determine the method whereby the gateway assigns IPv6 addresses to the clients in the local network. Some

clients may support only a few of these connection types, so you should choose it according to the compatibility of clients in the local network.

Configure IPv6 IPv6 Interface Type: DHCPv6 Gateway/Subnet: / DHCP Range: Lease Time: 1440 minutes (1-11520) DHCPv6 DNS: Auto Manual

IPv6 Interface TypeConfigure the type of assigning IPv6 address to the clients in the local network.
None: IPv6 connection is not enabled for the clients in the local network.
DHCPv6: The gateway assigns an IPv6 address and other parameters including the DNS server address to each client using DHCPv6.
SLAAC+Stateless DHCP: The gateway assigns the IPv6 address prefix to each client and the client automatically generates its own IPv6 address. Also, the gateway assigns other parameters including the DNS server address to each client using DHCPv6.
SLAAC+RDNSS: The gateway assigns the IPv6 address prefix to each client and the client automatically generates its own IPv6 address. Also, the gateway assigns other parameters including the DNS server address to each client using the RDNSS option in RA (Router Advertisement).
Pass-Through: Select this type if the WAN ports of the gateway use the Pass-Through for IPv6 connections.
With DHCPv6 selected, configure the following parameters.
Gateway/Subnet Enter the IP address and subnet mask in the CIDR format. The CIDR notation here includes the IP address and subnet mask of the default gateway. The summary of the information that you entered will show up below in real time.
DHCP Range Enter the starting and ending IP addresses of the DHCP address pool in the fields provided. For quick operation, click the Update DHCP Range beside the Gateway/Subnet entry to get the IP address range populated automatically, and edit the range according to your needs.
Lease Time This entry determines how long the assigned IPv6 address remains valid. Either keep the default 1440 minutes or change it if required by your ISP.
DHCPv6 DNSSelect a method to configure the DNS server for the network. With Auto selected, the DHCP server automatically assigns DNS server for devices in the network. With Manual selected, enter the IP address of a server in each DNS server field.
With SLAAC+Stateless DHCP selected, configure the following parameters.
Prefix Configure the IPv6 address prefix for each client in the local network.
Manual Prefix: With Manual Prefix selected, enter the prefix in the Address Prefix field.
Get from Prefix Delegation: With Get from Prefix Delegation selected, select the WAN port with Prefix Delegation configured, and the clients will get the address prefix from the Prefix Delegation.
IPv6 Prefix IDWith Get from Prefix Delegation selected, enter the Prefix ID, which will be added to the prefix to obtain a /64 subnet.The range of IPv6 Prefix ID is determined by the larger value of Prefix Delegation Size and Prefix Delegation Length (obtained from the ISP). Note that if the Prefix Delegation Length is larger than 64, the IPv6 Prefix ID cannot be obtained from Prefix Delegation, please select another method. In site view, go to Settings > Wired Network > Internet to configure Prefix Delegation Size.
DNS Server Select a method to configure the DNS server for the network.
Auto: With Auto selected, the DHCP server automatically assigns DNS server for devices in the network.Manual: With Manual selected, enter the IP address of a server in each DNS server field.
With SLAAC+RDNSS selected, configure the following parameters.
Prefix Configure the IPv6 address prefix for each client in the local network.
Manual Prefix: With Manual Prefix selected, enter the prefix in the Address Prefix field.Get from Prefix Delegation: With Get from Prefix Delegation selected, select the WAN port with Prefix Delegation configured, and the clients will get the address prefix from the Prefix Delegation.
IPv6 Prefix IDWith Get from Prefix Delegation selected, enter the Prefix ID, which will be added to the prefix to obtain a /64 subnet.
DNS Server Select a method to configure the DNS server for the network.
Auto: With Auto selected, the DHCP server automatically assigns DNS server for devices in the network.Manual: With Manual selected, enter the IP address of a server in each DNS server field.
With Pass-Through selected, configure the following parameters.

IPv6 Prefix Delegation Interface

Select the WAN port using Pass-Through (Bridge) for the IPv6 connection.

Create New LAN

Name:

Purpose:

TP-LINK Omada SDN Controller - Create New LAN - 1

Interface

VLAN

VLAN:

Application:

TP-LINK Omada SDN Controller - Create New LAN - 2

(1-4090, for example: 2-100,200) i

Gateways and Switches

○ Switches Only

IGMP Snooping:

Enable i

MLD Snooping:

Enable i

Legal DHCP Servers:

Enable i

Legal DHCPv6 Servers.

Enable ①

DHCP L2 Relay:

Enable i

VLAN Enter a VLAN ID with the values between 1 and 4090. Each VLAN can be uniquely identified by VLAN ID, which is transmitted and received as IEEE 802.1Q tag in an Ethernet frame.

Application Choose the device type that this entry applies to.

IGMP SnoopingClick the checkbox to monitor IGMP (Internet Group Management Protocol) traffic and thereby manage multicast traffic.
MLD SnoopingClick the checkbox to monitor MLD (Multicast Listener Discovery) traffic and thereby manage IPv6 multicast traffic.
Legal DHCP ServersClick the checkbox to specify legal DHCP servers for the network. With legal DHCP servers configured, Gateways and Switches ensure that clients get IP addresses only from the DHCP servers specified here.
Legal DHCPv6 ServersClick the checkbox to specify legal DHCPv6 servers for the network. With legal DHCPv6 servers configured, Gateways and Switches ensure that clients get IPv6 addresses only from the DHCPv6 servers specified here.

DHCP L2 Relay Click the checkbox to enable DHCP L2 Relay for the network.

  1. Click Save. The new LAN will be added to the LAN list. In the ACTION column, you can click ☐ to edit the LAN and click 🔒 to delete the LAN. You can click Batch Delete VLANs to delete VLANs.

Batch Delete VLAN NAME PURPOSE SUBNET PORTAL PORTAL NAME ACCESS CONTROL RULE RATE LIMIT VLAN ACTION Default Interface 192.168.0.1/24 1 tp-link VLAN 2 Showing 1-2 of 2 records ( ) 10/page Go to page: 50 + Create New LAN

Create a Network

Create a Port Profile

Assign the Port Profile to the Ports

Note:

- Three default port profiles are preconfigured on the controller. They can be viewed, but not edited or deleted.

All: In the All profile, all networks except the default network (LAN) are configured as Tagged Network, and the native network is the default network (LAN). This profile is assigned to all switch ports by default.

Disable: In the Disable profile, no networks are configured as the native network, Tagged Networks and Untagged Networks. With this profile assigned to a port, the port does not belong to any VLAN.

LAN: In the LAN profile, the native network is the default network (LAN), and no networks are configured as Tagged Networks and Untagged Networks.

- When a network is created, the system will automatically create a profile with the same name and configure the network as the native network for the profile. In this profile, the network itself is configured as the Untagged Networks, while no networks are configured as Tagged Networks. The profile can be viewed and deleted, but not edited.

1. Go to Settings > Wired Networks > LAN > Profile to load the following page.

NAME PoE NATIVE NETWORK ISOLATION STORM CONTROL ACTION All Keep the Device's Settings LAN Off # Disable Keep the Device's Settings None Off # LAN Keep the Device's Settings LAN Off # Shewing 1-3 of 3 records ( 1 ) 10 /page Go Te page: GO + Create New Port Profile

2. Click + Create New Port Profile to load the following page, and configure the following parameters.

Create New Port Profile NAME: PoE: Keep the Device's Settings Enable Disable Networks/VLANs Native Network: Default(1) i Tagged Networks: Please Select... i Untagged Networks: Default(1) x i Voice Network: None i + Advanced Options

Name Enter a name to identify the port profile.

PoE Select the PoE mode for the ports.
Keep the Device's Settings: PoE keep enabled or disabled according to the switches' settings. By default, the switches enable PoE on all PoE ports.
Enable: Enable PoE on PoE ports.
Disable: Disable PoE on PoE ports.
Native NetworkSelect the native network from all networks. The native network determines the Port VLAN Identifier (PVID) for switch ports. When a port receives an untagged frame, the switch inserts a VLAN tag to the frame based on the PVID, and forwards the frame in the native network. Each physical switch port can have multiple networks attached, but only one of them can be native.
Tagged Networks Select the Tagged Networks. Frames sent out of a Tagged Network are kept with VLAN tags. Usually networks that connect the switch to network devices like routers and other switches, or VoIP devices like IP phones should be configured as Tagged Networks.
Untagged NetworksSelect the Untagged Networks. Frames that sent out of an Untagged Network are stripped of VLAN tags. Usually networks that connect the switch to endpoint devices like computers should be configured as Untagged Networks. Note that the native network is untagged.
Voice NetworkSelect the network that connects VoIP devices like IP phones as the Voice Network. Switches will prioritize the voice traffic by changing its 802.1p priority. To configure a network as Voice Network, configure it as Tagged Network first, and then enable LLDP-MED. Only tagged networks can be configured as Voice Network, and Voice Network will take effect with LLDP-MED enabled.

3. Expand and configure Advanced Options if needed.

Advanced Options 802.1X Control: ○ Force Unauthorized i ○ Force Authorized ● Auto Port Isolation: □ Enable i Flow Control: □ Enable EEE: □ Enable i Loopback Control: i ● Off ○ Loopback Detection Port Based ○ Loopback Detection VLAN Based i ○ Spanning Tree LLDP-MED: ✓ Enable i Bandwidth Control: ● Off i ○ Rate Limit ○ Storming Control DHCP L2 Relay: □ Enable

802.1X ControlSelect 802.1X Control mode for the ports. To configure the 802.1X authentication globally, enter the site view and go to Settings > Authentication > 802.1X.
Auto: The port is unauthorized until the client is authenticated by the authentication server successfully.
Force Authorized: The port remains in the authorized state, sends and receives normal traffic without 802.1X authentication of the client.
Force Unauthorized: The port remains in the unauthorized state, ignoring all attempts by the client to authenticate. The switch cannot provide authentication services to the client through the port.
Port IsolationClick the checkbox to enable Port Isolation. An isolated port cannot communicate directly with any other isolated ports, while the isolated port can send and receive traffic to non-isolated ports.
Flow ControlWith this option enabled, when a device gets overloaded it will send a PAUSE frame to notify the peer device to stop sending data for a specified period of time, thus avoiding the packet loss caused by congestion.

EEE Click the checkbox to enable EEE (Energy Efficient Ethernet) to allow power reduction.

Loopback ControlLoopback refers to the routing of data streams back to their source in the network. You can disable loopback control for the network or choose a method to prevent loopback happening in your network.Off: Disable loopback control on the port.Loopback Detection Port Based: Loopback Detection Port Based helps detect loops that occur on a specific port. When a loop is detected on a port, the port will be blocked.Loopback Detection VLAN Based: Loopback Detection VLAN Based helps detect loops that occur on a specific VLAN. When a loop is detected on a VLAN, the current port will be removed from the VLAN.Spanning Tree: Select STP (Spanning Tree Protocol) to prevent loops in the network. STP helps block specific ports of the switches to build a loop-free topology and detect topology changes and automatically generate a new loop-free topology.If you want to enable Spanning Tree for the switch, you also need to select the Spanning Tree protocol in the Device Config page. For details, refer to 6.3 Configure and Monitor Switches.
LLDP-MED Click the checkbox to enable LLDP-MED (Link Layer Discovery Protocol-Media Endpoint Discovery) for device discovery and auto-configuration of VoIP devices.
Bandwidth ControlSelect the type of Bandwidth Control functions to control the traffic rate and traffic threshold on each port to ensure network performance.Off: Disable Bandwidth Control for the port.Rate Limit: Select Rate limit to limit the ingress/egress traffic rate on each port. With this function, the network bandwidth can be reasonably distributed and utilized.Storm Control: Select Storm Control to allow the switch to monitor broadcast frames, multicast frames and UL-frames (Unknown unicast frames) in the network. If the transmission rate of the frames exceeds the set rate, the frames will be automatically discarded to avoid network broadcast storm.
Ingress Rate LimitWhen Rate Limit selected, click the checkbox and specify the upper rate limit for receiving packets on the port.
Egress Rate LimitWhen Rate Limit selected, click the checkbox and specify the upper rate limit for sending packets on the port.
Broadcast ThresholdWhen Storm Control selected, click the checkbox and specify the upper rate limit for receiving broadcast frames. The broadcast traffic exceeding the limit will be processed according to the Action configurations.
Multicast ThresholdWhen Storm Control selected, click the checkbox and specify the upper rate limit for receiving multicast frames. The multicast traffic exceeding the limit will be processed according to the Action configurations.
UL-Frame ThresholdWhen Storm Control selected, click the checkbox and specify the upper rate limit for receiving unknown unicast frames. The traffic exceeding the limit will be processed according to the Action configurations..

Action

When Storm Control selected, select the action that the switch will take when the traffic exceeds its corresponding limit. With Drop selected, the port will drop the subsequent frames when the traffic exceeds the limit. With Shutdown selected, the port will be shutdown when the traffic exceeds the limit.

DHCP L2 Relay Click the checkbox to enable DHCP L2 Relay for the network.

Format Select the format of option 82 sub-option value field.

Normal: The format of sub-option value field is TLV (type-length-value).

Private: The format of sub-option value field is just value.

  1. Click Save. The new port profile is added to the profile list. You can click ☑ in the ACTION column to edit the port profile. You can click 🔒 in the ACTION column to delete the port profile.

NAME PoE NATIVE NETWORK ISOLATION STORM CONTROL ACTION All Keep the Device's Settings LAN Off Disable Keep the Device's Settings None Off LAN Keep the Device's Settings LAN Off Ip-link Keep the Device's Settings LAN Off Showing 1-4 of 4 records ( 1 ) 10 page ✓ Go To page: GO + Create New Port Profile

Create a Network Create a Port Profile Assign the Port Profile to the Ports

① Note:

By default, there is a port profile named All, which is assigned to all switch ports by default. In the All profile, all networks except the default network (LAN) are configured as Tagged Network, and the native network is the default network (LAN).

  1. Go to Devices, and click the switch in the devices list to reveal the Properties window. Go to Ports, you can either click ☑ in the Action column to assign the port profile to a single port, or select

the desired ports and click Edit Selected on the top to assign the port profile to multiple ports in batch.

Port LAG Edit Selected Name Status Profile ACTION 1 Port1 All ✓ 2 Port2 FAE ✓ 3 Port3 All ✓ 4 Port4 All ✓ 5 Port5 All ✓

  1. Select the profile from the drop-down list to assign the port profile to the desired ports of the switch. You can enable profile overrides to customize the settings for the ports, and all the configuration here overrides the port profile. For details, refer to Chapter 6. Configure and Monitor Controller-Managed Devices.

Edit Port1 Name: Port1 Profile: All Manage Profiles Profile Overrides Apply Cancel

TP-LINK Omada SDN Controller - ① Note: - 3

4.4 Configure Wireless Networks

Wireless networks enable your wireless clients to access the internet. Once you set up a wireless network, your APs typically broadcast the network name (SSID) in the air, through which your wireless clients connect to the wireless network and access the internet.

A WLAN group is a combination of wireless networks. Configure each group so that you can flexibly apply these groups of wireless networks to different APs according to your needs.

After setting up basic wireless networks, you can further configure WLAN Schedule, 802.11 Rate Control, MAC Filter, and other advanced settings.

4.4.1 Set Up Basic Wireless Networks

Configuration

To create, configure and apply wireless networks, follow these steps:

1) Create a WLAN group.
2) Create Wireless Networks
3) Apply the WLAN group to your APs

Create a WLAN Group Create Wireless Networks Apply the WLAN Group

TP-LINK Omada SDN Controller - Configuration - 1

Note:

The controller provides a default WLAN group. If you simply want to configure wireless networks for the default WLAN group and apply it to all your APs, skip this step.

  1. Select a site from the drop-down list of Organization. Go to Settings > Wireless Networks to load the following page.

WLAN Group: Default SSID NAME SECURITY BAND GUEST NETWORK Portal ACCESS CONTROL RULE RATE LIMIT VLAN ACTION No wireless networks yet + Create New Wireless Network

  1. Select + Create New Group from the drop-down list of WLAN Group to load the following page. Enter a name to identify the WLAN group.

Add New WLAN Group Name: Copy WLANs: Copy All SSIDs from the WLAN Group Default Save Cancel

  1. (Optional) If you want to create a new WLAN group based on an existing one, check Copy All SSIDs from the WLAN Group and select the desired WLAN group. Then you can further configure wireless networks based on current settings.

Add New WLAN Group Name: test Copy WLANs: ✓ Copy All SSIDs from the WLAN Group Default Default Default tp-link Save Cancel

  1. Click Save. The new WLAN Group is added to the WLAN Group list. You can select a WLAN Group from the list to further create and configure its wireless networks. You can click ☑ to edit the name of the WLAN Group. You can click 🔒 to delete the WLAN Group.

WLAN Group: test SSID NAME Default toist No what to link + Create New Group BAND GUEST NETWORK Portal ACCESS CONTROL RULE RATE LIMIT VLAN ACTION

Create a WLAN Group Create Wireless Networks Apply the WLAN Group

  1. Select the WLAN group for which you want to configure wireless networks from the drop-down list of WLAN Group.

WLAN Group: Default SSID NAME SECURITY BAND GUEST NETWORK Portal ACCESS CONTROL RULE RATE LIMIT VLAN ACTION No wireless networks yet. + Create New Wireless Network

  1. Click + Create New Wireless Network to load the following page. Configure the basic parameters for the network.

① Note:

The 6 GHz band is only available for certain devices.

Create New Wireless Network Network Name (SSID): Device Type: EAP Gateway Band: 2.4 GHz 5 GHz 6 GHz Guest Network: Enable Security: WPA-Personal Security Key: Password + Advanced Settings + WLAN Schedule + 802.11 Rate Control + MAC Filter + Multicast/Broadcast Management + DHCP Option 82 Apply Cancel

Network Name (SSID)Enter the network name (SSID) to identify the wireless network. The users of wireless clients choose to connect to the wireless network according to the SSID, which appears on the WLAN settings page of wireless clients.
Device Type Select the type of devices that the wireless network can apply to.
Band Enable the radio band(s) for the wireless network. When 6GHz is turned on, Security cannot be PPSK with/without RADIUS since 6GHz does not support them.
Guest NetworkWith Guest Network enabled, all the clients connecting to the SSID are blocked from reaching any private IP subnet.
Security Select the encryption method for the wireless network based on needs.
  1. Select the security strategy for the wireless network.

■ None

With None selected, the hosts can access the wireless network without authentication, which is applicable to lower security requirements.

Security: None OWE: Enable i

OWE Opportunistic Wireless Encryption, also known as Enhanced Open, is a certification

provided by the Wi-Fi Alliance as part of the WPA3 wireless security standard. OWE will enable two wireless VAPs per radio, one for access of OWE-supported stations, and one for access of other stations. An SSID with OWE enabled will be counted as two SSID entries.

■ WPA-Personal

With WPA-Personal selected, traffic is encrypted with a Security Key you set,

Security:

WPA-Personal

Security Key:

TP-LINK Omada SDN Controller - ■ WPA-Personal - 1

Security Key Specify a security key to encrypt the traffic.

■ WPA-Enterprise

WPA-Enterprise requires an authentication server to authenticate wireless clients, and probably an accounting server to record the traffic statistics.

Security:

WPA-Enterprise

RADIUS Profile:

TP-LINK Omada SDN Controller - ■ WPA-Enterprise - 1

Default (TP-Link: MAC Address)

NAS ID:

TP-LINK Omada SDN Controller - ■ WPA-Enterprise - 2

Follow Device Name

TP-LINK Omada SDN Controller - ■ WPA-Enterprise - 3

TP-LINK Omada SDN Controller - ■ WPA-Enterprise - 4

Custom

RADIUS Profile

Select a RADIUS Profile, which records the settings of the authentication server and accounting server. You can create a RADIUS Profile by clicking Create New Radius Profile from the drop-down list of RADIUS Profile. For details, refer to 4.9 Authentication.

NAS ID Configure a Network Access Server Identifier (NAS ID) for the authentication.

Authentication request packets from the controller to the RADIUS server carry the NAS ID. The RADIUS server can classify users into different groups based on the NAS ID, and then choose different policies for different groups.

The NAS ID can be a default one (TP-Link: MAC Address), follow the device name, or a customized one.

■ PPSK without RADIUS

PPSK (private pre-shared key) can provide a unique PSK for each wireless user. Compared with the traditional SSID solution with one password for all users, it is more secure.

Security: PPSK without RADIUS PPSK Profile: Please Select... Manage PPSK Profile PPSK Profile Select a PPSK Profile, which records the PPSK settings. You can create a PPSK by clicking Create New PPSK Profile from the drop-down list of PPSK Profile. For details, refer to 4.8.4 PPSK.

■ PPSK with RADIUS

PPSK (private pre-shared key) can provide a unique PSK for each wireless use. PPSK with RADIUS requires an authentication server to authenticate wireless clients and probably an accounting server to record the traffic statistics. The SSID will not be applied to the device firmware not supporting PPSK.

Security: PPSK with RADIUS RADIUS Profile: Authentication type: Generic Radius with bound MAC NAS ID: (Optional) MAC Address Format: aa:bb:cc:dd:ee:ff

RADIUS ProfileSelect a RADIUS Profile, which records the settings of the authentication server and accounting server. You can create a RADIUS Profile by clicking + Create New Radius Profile from the drop-down list of RADIUS Profile. For details, refer to 4.9 Authentication.
Authentication type Choose the authentication type.
Generic Radius with bound MAC: This type needs to specify device MAC addresses.
NAS ID Configure a Network Access Server Identifier (NAS ID) for the authentication. Authentication request packets from the controller to the RADIUS server carry the NAS ID. The RADIUS server can classify users into different groups based on the NAS ID, and then choose different policies for different groups.
MAC Address FormatSelect clients' MAC address format which the controller uses for authentication. Then configure the MAC addresses in the specified format as usernames for the clients on the RADIUS server.
  1. (Optional) You can also configure Advanced Settings, WLAN Schedule, 802.11 Rate Control, and MAC Filter, and more according to your needs. Related topics are covered later in this chapter.
  2. Click Apply. The new wireless network is added to the wireless network list under the WLAN group. You can click in the ACTION column to edit the wireless network. You can click in the ACTION column to delete the wireless network.

WLAN Group: tp-link SSID NAME SECURITY BAND GUEST NETWORK Portal ACCESS CONTROL RULE RATE LIMIT VLAN ACTION wireless network 1 WPA-Personal 2.4GHz, 5GHz wireless network 2 WPA-Personal 2.4GHz, 5GHz Showing 1-2 of 2 records < 1 > Go Te page GO + Create New Wireless Network

Create a WLAN Group Create Wireless Networks Apply the WLAN Group

① Note:

The controller provides a default WLAN group. If you simply want to configure wireless networks for the default WLAN group and apply it to all your APs, skip this step.

■ Apply to a Single AP

Go to Devices, select the AP. In the Properties window, go to Config > WLANs, select the WLAN group to apply.

EAP225 CONNECTED 6 b/g/n mixed 2.4G (41% Utilized) High 44 a/n/ac mixed 5G (17% Utilized) Good Rx Frames Tx Frames Interference Free Details Clients Mesh Config Statistics General IP Settings Radios WLANs WLAN Group: Default Services Advanced Manage Device

■ Apply to APs in batch

  1. Go to Devices, select the APs tab, click Batch Action, and then select Batch Config, check the boxes of APs which you want to apply the WLAN group to, and click Done.

Search or select tag All Gateway/Switches APs Overview Mesh Performance Config Edit Selected DEVICE NAME IP ADDRESS STATUS MODEL VERSION UPTIME CLIENTS DOWN UP CHANNEL ACTION EA-23-51-06-22-52 10.0.1.70 CONNECTED EAP225- Outdoor(EU) v1.0 2.0.0 1 days 07:54:08 0 2.11 GB 369.62 MB 11(2.4G), 36(5G) EA-33-51-A8-22-A0 10.0.0.196 CONNECTED EAP225- Outdoor(EU) v1.0 2.0.0 0 days 06:15:18 1 13.61 MB 3.00 MB 11(2.4G), 36(5G)

  1. In the Properties window, go to Config > WLANs, select the WLAN group which you want to apply to the AP.

WLANs WLAN Group: Default

4.4.2 Advanced Settings

Select a site from the drop-down list of Organization. Go to Settings > Wireless Networks, click in the ACTION column of the wireless network which you want to configure, and click + Advanced Settings to load the following page. Configure the parameters and click Apply.

Advanced Settings SSID Broadcast: ✓ Enable VLAN: ● Default ○ Custom WPA Mode: MLO: □ Enable i PMF: ○ Mandatory ○ Capable ● Disable Group Key Update Period: □ Enable GIK rekeying every 0 Seconds √ (30-86400) 802.11r: □ Enable i Client Rate Limit Profile: Default √ i SSID Rate Limit Profile: Default √ i

SSID BroadcastWith SSID Broadcast enabled, APs broadcast the SSID (network name) in the air so that wireless clients can connect to the wireless network, which is identified by the SSID. With SSID Broadcast disabled, users of wireless clients must enter the SSID manually to connect to the wireless network.
VLAN Configure the uplink port VLAN corresponding to the SSID.
Default: Using untagged transmission.
Custom: Modifying the VLAN ID by binding a network or manually entering a VLAN ID. Traffic in different wireless networks will be marked with different VLAN tags accordingly. Then the APs work together with the switches which also support 802.1Q VLAN, to distribute the traffic to different VLANs according to the VLAN tags. As a result, wireless clients in different VLANs cannot directly communicate with each other.
WPA Mode If you select WPA-Personal or WPA-Enterprise as the security strategy, you can select the WPA Mode including the version of WPA, and the encryption type.Select the version of WPA according to your needs.Select the encryption type. Some encryption type is only available under certain circumstances.AES: AES stands for Advanced Encryption Standard.Auto: APs automatically decide the encryption type in the authentication process.
MLO MLO (Multi-Link Operation) enables Wi-Fi 7 devices to simultaneously send and receive data across different frequency bands and channels. This ensures fast and reliable connections even in dense network environments.
PMF Protected Management Frames (PMF) provide protection for unicast and multicast management action frames. When Mandatory is selected, non-PMF-capable clients may fail to connect to the network.Disable: Disables PMF for a network. It is not recommended to use this setting, only in case non-PMF-capable clients experience connection issues with the “Capable” option.Capable: Both types of clients, capable of PMF or not, can connect to the network. Clients capable of PMF will negotiate it with the AP.Mandatory: Only PMF-capable clients can connect to the network.
Group Key Update PeriodIf you select WPA-Personal or WPA-Enterprise as the security strategy, you can specify whether and how often the security key changes. If you want the security key to change periodically, enable GIK rekeying and specify the time period.
802.11r Enable this feature to allow faster roaming when both the AP and client have 802.11r capabilities. Currently 802.11r does not support WPA3 encryption.
Client Rate Limit ProfileSpecify the profile to limit the download and upload rates of each client to balance bandwidth usage.You can use the default profile or custom a profile.
SSID Rate Limit ProfileSpecify the profile to limit the download and upload rates of each wireless band. Bandwidth is shared among all clients connected to the same wireless band of the same AP.You can use the default profile or custom a profile.⚠ Note: This feature requires new firmware updates for Omada APs, and the rate limit settings will only take effect on those APs running firmware that supports the feature.

4.4.3 WLAN Schedule

Overview

WLAN Schedule can turn on or off your wireless network in the specific time period as you desire.

Configuration

Select a site from the drop-down list of Organization. Go to Settings > Wireless Networks, click ☑ in the ACTION column of the wireless network which you want to configure, and click + WLAN Schedule to load the following page. Enable WLAN schedule and configure the parameters .Then click Apply.

WLAN Schedule WLAN Schedule: Enable Action: Radio on i Radio off i Time Range: Please select a Time Range entry. Manage Time Range Entries

Action Radio On: Turn on your wireless network within the time range you set, and turn it off beyond the time range.

Radio Off: Turn off your wireless network within the time range you set, and turn it on beyond the time range.

Time Range

Select the Time Range for the action to take effect. You can create a Time Range entry by clicking + Create New Time Range Entry from the drop-down list of Time Range. For details, refer to 4.8 Create Profiles.

4.4.4 802.11 Rate Control

Overview

Note:

802.11 Rate Control is only available for certain devices.

802.11 Rate Control can improve performance for higher-density networks by disabling lower bit rates and only allowing the higher. However, 802.11 Rate Control might make some legacy devices incompatible with your networks, and limit the range of your wireless networks.

Configuration

Select a site from the drop-down list of Organization. Go to Settings > Wireless Networks, click in the ACTION column of the wireless network which you want to configure, and click + 802.11 Rate Control to load the following page. Select one or multiple bands to enable minimum data rate control

according to your needs, move the slider to determine what bit rates your wireless network allows, and configure the parameters. Then click Apply.

TP-LINK Omada SDN Controller - Configuration - 1

Note:

The 6 GHz band is only available for certain devices.

802.11 Rate Control 2.4 GHz Data Rate Control: Enable Minimum Data Rate Control i 6 Mbps 54 Mbps Lower Density Higher Density Limited range and no connectivity for 802.11b devices. Disable CCK Rates (1/2/5.5/11 Mbps) Require Clients to Use Rates at or Above the Specified Value Send Beacons at 1 Mbps 5 GHz Data Rate Control: Enable Minimum Data Rate Control i 6 Mbps 54 Mbps Lower Density Higher Density Full device compatibility and range. Require Clients to Use Rates at or Above the Specified Value Send Beacons at 6 Mbps

Disable CCK Rates (1/2/5.5/11 Mbps)Select whether to disable CCK (Complementary Code Keying), the modulation scheme which works with 802.11b devices. Disable CCK Rates (1/2/5.5/11 Mbps) is only available for 2.4 GHz band.
Require Clients to Use Rates at or Above the Specified ValueSelect whether or not to require clients to use rates at or above the value specified on the minimum data rate controller slider.
Send Beacons at 1 Mbps/6 MbpsSelect whether or not to send Beacons at the minimum rate of 1Mbps for 2.4 GHz band or 6Mbps for 5 GHz band.

4.4.5 MAC Filter

Overview

MAC Filter allows or blocks connections from wireless clients of specific MAC addresses.

Configuration

Select a site from the drop-down list of Organization. Go to Settings > Wireless Networks, click ☑ in the ACTION column of the wireless network which you want to configure, and click + MAC Filter to load the following page. Enable MAC Filter and configure the parameters .Then click Apply.

MAC Filter MAC Filter: Enable Policy: Allow List i Deny List i MAC Addresses List: Please select a MAC Group. Manage MAC Groups Apply Cancel

PolicyAllow List: Allow the connection of the clients whose MAC addresses are in the specified MAC Address List, while blocking others.
Deny List: Block the connection of the clients whose MAC address are in the specified MAC Addresses List, while allowing others.
MAC Address ListSelect the MAC Group which you want to allow or block according to the policy. You can create new MAC group by clicking + Create New MAC Group from the drop-down list of MAC Address List. For details, refer to 4.8 Create Profiles.

4.4.6 Multicast/Broadcast Management

Overview

Multicast/Broadcast Management allows packet conversion and multicast filtering.

Configuration

Select a site from the drop-down list of Organization. Go to Settings > Wireless Networks, click in the ACTION column of the wireless network which you want to configure, and click + Multicast/Broadcast Management to load the following page. Configure the parameters .Then click Apply.

Multicast/Broadcast Management Multicast-to-Unicast Conversion: ✓ Enable Converse multicast to unicast when the channel utilization is below 100 % ARP-to-Unicast Conversion: ✓ Enable IPv6-Multicast-to-Unicast Conversion: ✓ Enable Multicast Filtering: ✓ Enable ⓘ

Multicast-to-Unicast ConversionWhen enabled, the controller will convert multicast packets into unicast packets when the channel utilization is below the specified threshold.
ARP-to-Unicast ConversionWhen enabled, the controller will convert ARP packets into unicast packets.
IPv6-Multicast-to-Unicast ConversionEnable this option if you have high requirements for IPv6 multicast streaming transmission, such as high-definition video on demand. When enabled, the AP maintains IPv6 multicast-to-unicast entries by listening to MLD report packets and MLD leave packets reported by clients. When the AP sends an IPv6 multicast packet to a client, it converts the packet into an IPv6 unicast packet according to the multicast-to-unicast entry, thereby improving the IPv6 transmission efficiency for better wireless experience.
Multicast FilteringWhen enabled, the controller will block IPv4 multicast packets of the specified protocols. Improper settings may cause network issues.

4.4.7 WLAN Optimization

Overview

WLAN Optimization helps improve the wireless network performance. With the WLAN Optimization feature, the controller will detect WiFi interference and monitor the wireless environment. Based on the environmental factors including network topology, deployment size, traffic, and client factors, the controller can determine the optimum wireless configurations (such as channel, power, etc.) for the access points (APs), and thus ensures that wireless clients of each AP can enjoy better WiFi experience.

In WLAN Optimization, the results of the last 10 scans are displayed. You can also enable automatic optimization to allow the controller to conduct RF optimization automatically and set optimization schedules. In Optimization Log, the past optimization records are displayed, and you can also restore the previous optimization results as needed.

Configuration

① Note:

  1. WiFi experience may be influenced during optimization. Please select the spare time to scan and optimize to reduce its impact on user experience.
  2. Because the APs should stay connected during optimization, please set a different time for WLAN Optimization and Reboot Schedule. It is recommended to stagger at least 10 minutes to avoid dissatisfactory results.

  3. Select a site from the drop-down list of Organization. Go to Settings > Wireless Networks > WLAN Optimization.

  4. Click Deploy Now to begin the optimization. The controller will scan the wireless environment to conclude the optimum WLAN network configurations. You can view the optimization results in Optimization Log.

WLAN Optimization

Optimization Config

With the WLAN optimization service, the controller will determine the optimum operation channels and power concluded from the scanning, considering the traffic, deployment size, and client factors. The connection to internet will be lost for several minutes during the scanning and optimization. Please select a spare time of network to start scanning.

Deploy Now

  1. (Optional) Click Optimization Config if you want to custom configurations.

Optimization Config Mode: Default Custom Automatic Channel Optimization: Automatic Power Optimization: Advanced Settings Custom Channel Width: 2.4 GHz Auto 5 GHz Auto 6 GHz Auto Power Range: Auto Custom Power Threshold: Auto Custom Excluded 5 GHz Channels: Enable Save Cancel

Mode Specify the optimization mode.

Default: The controller will conduct the optimization with the default configurations.

Custom: The controller will conduct the optimization with the configurations you set.

Automatic Channel OptimizationEnable this function, and the controller will scan the wireless environment to conclude the optimum operation channels for the APs and wireless routers.
Automatic Power OptimizationEnable this function, and the controller will scan the wireless environment to conclude the optimum transmission power for the APs and wireless routers.
Custom Channel WidthSelect the channel width for each band, and the optimization will maintain the selected channel width.
Power RangeSelect Custom if you want to optimize the power within the specified range. You can limit the transmit power range of each AP/wireless routers after the power deployment is completed. For high-density deployment, you can try to set a smaller power range. An over-low value may lead to limited coverage, while an over-high value may lead to strong interference. (Note: The deployment may fail if the minimum power you select exceeds the maximum power of the AP to be deployed.)
Power ThresholdSelect Custom if you want to optimize the power within the specified threshold. You can adjust the power deployment override threshold according to the actual deployment height and spacing of APs/wireless routers, achieving optimal wireless coverage after RF optimization. The larger the threshold, the larger the adjusted overall power value.
Excluded 5 GHz ChannelsWhen enabled, you can specify the channels so they will not execute the automatic optimization.
  1. (Optional) In the Excluded APs List, click Add to add the APs that will be excluded from WLAN Optimization. The following APs will be added to the list automatically: APs in the mesh network and APs with unsupported firmware.
Excluded APs List
ADD
DEVICE NAMEIP ADDRESSSTATUSMODELACTION
No entry in the table.

4.5 Network Security

Network Security is a portfolio of features designed to improve the usability and ensure the safety of your network and data. It implements policies and controls on multiple layers of defenses in the network.

4.5.1 ACL

Overview

ACL (Access Control List) allows a network administrator to create rules to restrict access to network resources. ACL rules filter traffic based on specified criteria such as source IP addresses, destination IP addresses, and port numbers, and determine whether to forward the matched packets. These rules can be applied to specific clients or groups whose traffic passes through the gateway, switches and APs.

The system filters traffic against the rules in the list sequentially. The first match determines whether the packet is accepted or dropped, and other rules are not checked after the first match. Therefore, the order of the rules is critical. By default, the rules are prioritized by their created time. The rule created earlier is checked for a match with higher priority. To reorder the rules, select a rule and drag it to a new position. If no rules match, the device forwards the packet because of an implicit Permit All clause.

The system provides three types of ACL:

■ Gateway ACL

After Gateway ACLs are configured on the controller, they can be applied to the gateway to control traffic which is sourced from LAN ports and forwarded to the WAN ports.

You can set the Network, IP address, port number of a packet as packet-filtering criteria in the rule.

■ Switch ACL

After Switch ACLs are configured on the controller, they can be applied to the switch to control inbound and outbound traffic through switch ports.

You can set the Network, IP address, port number and MAC address of a packet as packet-filtering criteria in the rule.

■ AP ACL

After AP ACLs are configured on the controller, they can be applied to the APs to control traffic in wireless networks.

You can set the Network, IP address, port number and SSID of a packet as packet-filtering criteria in the rule.

Configuration

To complete the ACL configuration, follow these steps:

1) Create an ACL with the specified type.
2) Define packet-filtering criteria of the rule, including protocols, source, and destination, and determine whether to forward the matched packets.

■ Configuring Gateway ACL

  1. Select a site from the drop-down list of Organization. Go to Settings > Network Security > ACL. On Gateway ACL tab, click + Create New Rule to load the following page.

Create New Rule Description: Status: Enable Only Omada gateways with certain firmware versions can set the status of an ACL rule as disabled. Please ensure that your gateway supports the feature before adoption. The status configuration will be lost if the adopted gateway is not compatible. Direction: Please Select... Policy: Deny Permit Protocols: Please Select... Log: Enable Rule: Source Type: Please Select... Deny Destination Type: Please Select... Please Select the type Please Select the type Advanced Settings Create Cancel

  1. Define packet-filtering criteria of the rule, including protocols, source, and destination, and determine whether to forward the matched packets. Refer to the following table to configure the required parameters and click Apply.

Name Enter a name to identify the ACL.

Status Click the checkbox to enable the ACL.

Direction Select the direction of ACL application traffic.

LAN->LAN: Control packet forwarding between LAN side devices.

LAN->WAN: Control packet forwarding in the LAN-WAN direction.

Policy Select the action to be taken when a packet matches the rule.

Permit: Forward the matched packet.

Deny: Discard the matched packet.

Protocols Select one or more protocol types to which the rule applies from the drop-down list. The default is All, indicating that packets of all protocols will be matched. When you select one of TCP and UDP or both of them, you can set the IP address and port number of a packet as packet-filtering criteria in the rule.

Log When enabled, the system can collect ACL entry effective log. To use this function, please configure the remote logging function first.

From the Source drop-down list, choose one of these options to specify the source of the packets to which this ACL applies:

NetworkSelect the network you have created. If no networks have been created, you can select the default network (LAN), or go to Settings > Wired Networks > LAN to create one. The gateway will examine whether the packets are sourced from the selected network.
SSIDSelect the SSID you have created. If no SSIDs have been created, go to Settings > Wireless Networks to create one. The system will examine whether the SSID of the packet is the SSID selected here.
IP GroupSelect the IP Group you have created. If no IP Groups have been created, click +Create on this page or go to Settings > Profiles > Groups to create one. The gateway will examine whether the source IP address of the packet is in the IP Group.
IP-Port GroupSelect the IP-Port Group you have created. If no IP-Port Groups have been created, click +Create on this page or go to Settings > Profiles > Groups to create one. The gateway will examine whether the source IP address and port number of the packet are in the IP-Port Group.
IPv6 Group IPv6 Group:Select the IPv6 Group you have created. If no IPv6 Groups have been created, click + Create on this page or go to Settings > Profiles > Groups to create one. The system will examine whether the source IPv6 address of the packet is in the IPv6 Group.
IPv6-Port GroupIPv6-Port Group:Select the IPv6-Port Group you have created. If no IPv6-Port Groups have been created, click + Create on this page or go to Settings > Profiles > Groups to create one. The system will examine whether the source IPv6 address and port number of the packet are in the IPv6-Port Group.
Location Select one or multiple locations from the list as the source address, and the system will judge whether the source IP of the data packet belongs to the selected locations.

Location Group Select a location group you have created, and the system will judge whether the source IP of the data packet belongs to this location group. If no location group has been created, click the create button to create one, or go to Settings > Profiles > Groups to create one.

From the Destination drop-down list, choose one of these options to specify the destination of the packets to which this ACL applies:

IP GroupSelect the IP Group you have created. If no IP Groups have been created, click +Create on this page or go to Settings >Profiles >Groups to create one. The gateway will examine whether the destination IP address of the packet is in the IP Group.
IP-Port GroupSelect the IP-Port Group you have created. If no IP-Port Groups have been created, click +Create on this page or go to Settings >Profiles >Groups to create one. The gateway will examine whether the destination IP address and port number of the packet are in the IP-Port Group.
IPv6 GroupSelect the IPv6 Group you have created. If no IPv6 Groups have been created, click +Create on this page or go to Settings >Profiles >Groups to create one. The system will examine whether the destination IPv6 address of the packet is in the IPv6 Group.
IPv6-Port Group Select the IPv6-Port Group you have created. If no IPv6-Port Groups have been created, click +Create on this page or go to Settings >Profiles >Groups to create one. The system will examine whether the destination IPv6 address and port number of the packet are in the IPv6-Port Group.
Location Select one or multiple locations from the list as the destination address, and the system will judge whether the destination IP of the data packet belongs to the selected locations.
Location Group Select a location group you have created, and the system will judge whether the destination IP of the data packet belongs to this location group. If no location group has been created, click the create button to create one, or go to Settings >Profiles >Groups to create one.
Gateway Management PageThis option will allow/block LAN network devices to access the gateway management page.

Set the advanced settings according to your needs:

Time Range Select the checkbox to enable time-based ACL. You can create a time range or select an existing time range for the ACL rule to take effect.
Bi-DirectionalWhen Direction is LAN->LAN, you can enable this option to configure bi-directional traffic rule.

States Type Determine the type of stateful ACL rule. It is recommended to use the default Auto type.

Auto (Match Sate New/Established/Related): Match the new, established, and related connection states.

Manual: If selected, you can manually specify the connection states to match.

Match State New: Match the connections of the initial state. For example, a SYN packet arrives in a TCP connection, or the router only receives traffic in one direction.

Match State Established: Match the connections that have been established. In other words, the firewall has seen the bidirectional communication of this connection.

Match State Related: Match the associated sub-connections of a main connection, such as a connection to a FTP data channel.

■ Configuring Switch ACL

  1. Select a site from the drop-down list of Organization. Go to Settings > Network Security > ACL. Under the Switch ACL tab, click + Create New Rule to load the following page.

Create New Rule Name: Status: Enable Policy: Deny Permit Protocols: Please Select... Time Range: Enable i Ethertype: Enable Bi-Directional: Enable Rule: i Source Type: Please Select... Deny Destination Type: Please Select... Please Select the type Please Select the type ACL Binding Binding Type: Ports VLAN Ports: All Ports Custom Ports Create Cancel

  1. Define packet-filtering criteria of the rule, including protocols, source, and destination, and determine whether to forward the matched packets. Refer to the following table to configure the required parameters.
Name Enter a name to identify the ACL.
Status Click the checkbox to enable the ACL.
Policy Select the action to be taken when a packet matches the rule.
Permit: Forward the matched packet.
Deny: Discard the matched packet.
Protocols Select one or more protocol types to which the rule applies from the drop-down list. The default is All, indicating that packets of all protocols will be matched. When you select one of TCP and UDP or both of them, you can set the IP address and port number of a packet as packet-filtering criteria in the rule.
Time Range Select the checkbox to enable time-based ACL. You can create a time range or select an existing time range for the ACL rule to take effect.
Ethertype Click the checkbox if you want the switch to check the ethertype of the packets, and configure the Ethertype based on needs.
Bi-DirectionalClick the checkbox to enable the switch to create another symmetric ACL with the name “xxx_reverse”, where “xxx” is the name of the current ACL. The two ACLs target at packets with the opposite direction of each other.

From the Source drop-down list, choose one of these options to specify the source of the packets to which this ACL applies:

NetworkSelect the network you have created. If no networks have been created, you can select the default network (LAN), or go to Settings > Wired Networks > LAN to create one. The switch will examine whether the packets are sourced from the selected network.
IP GroupSelect the IP Group you have created. If no IP Groups have been created, click +Create on this page or go to Settings > Profiles > Groups to create one. The switch will examine whether the source IP address of the packet is in the IP Group.
IP-Port GroupSelect the IP-Port Group you have created. If no IP-Port Groups have been created, click +Create on this page or go to Settings > Profiles > Groups to create one. The switch will examine whether the source IP address and port number of the packet are in the IP-Port Group.
MAC Group Select the MAC Group you have created. If no MAC Groups have been created, click +Create on this page or go to Settings > Profiles > Groups to create one. The switch will examine whether the source MAC address of the packet is in the MAC Group.
IPv6 Group Select the IPv6 Group you have created. If no IPv6 Groups have been created, click +Create on this page or go to Settings > Profiles > Groups to create one. The switch will examine whether the source IP address of the packet is in the IPv6 Group.

IPv6-Port Group Select the IPv6-Port Group you have created. If no IPv6-Port Groups have been created, click +Create on this page or go to Settings >Profiles >Groups to create one. The switch will examine whether the source IP address and port number of the packet are in the IPv6-Port Group.

From the Destination drop-down list, choose one of these options to specify the destination of the packets to which this ACL applies:

NetworkSelect the network you have created. If no networks have been created, you can select the default network (LAN), or go to Settings > Wired Networks > LAN to create one. The switch will examine whether the packets are forwarded to the selected network.
IP GroupSelect the IP Group you have created. If no IP Groups have been created, click +Create on this page or go to Settings > Profiles > Groups to create one. The switch will examine whether the destination IP address of the packet is in the IP Group.
IP-Port GroupSelect the IP-Port Group you have created. If no IP-Port Groups have been created, click +Create on this page or go to Settings > Profiles > Groups to create one. The switch will examine whether the destination IP address and port number of the packet are in the IP-Port Group.
MAC Group Select the MAC Group you have created. If no MAC Groups have been created, click +Create on this page or go to Settings > Profiles > Groups to create one. The switch will examine whether the destination MAC address of the packet is in the MAC Group.
IPv6 Group Select the IPv6 Group you have created. If no IPv6 Groups have been created, click +Create on this page or go to Settings > Profiles > Groups to create one. The switch will examine whether the destination IP address of the packet is in the IPv6 Group.
IPv6-Port Group Select the IPv6-Port Group you have created. If no IPv6-Port Groups have been created, click +Create on this page or go to Settings > Profiles > Groups to create one. The switch will examine whether the destination IP address and port number of the packet are in the IPv6-Port Group.
  1. Bind the switch ACL to a switch port or a VLAN and click Apply. Note that a switch ACL takes effect only after it is bound to a port or VLAN.

Binding Type Specify whether to bind the ACL to ports or a VLAN.

Ports: Select All Ports or Custom Ports as the interfaces to be bound with the ACL. With All ports selected, the rule is applied to all ports of the switch. With Custom ports selected, the rule is applied to the selected ports of the switch. Click the ports from the Device List to select the binding ports.

Device List ✓ Device Name Ports/Lags Status Model Firmware Version ✓ switch Port 1 2 3 4 5 6 7 8 9 10 CONNECTED TL-SG2210MP 1.0.0 Build 20200608 Rel7560

VLAN: Select a VLAN and specify the switches as the interface to be bound with the ACL. If no VLANs have been created, you can select the default VLAN 1 (LAN), or go to Settings > Wired Networks > LAN to create one.

■ Configuring AP ACL

  1. Select a site from the drop-down list of Organization. Go to Settings > Network Security > ACL. Under the AP ACL tab, click + Create New Rule to load the following page.

Create New Rule Name: Status: Enable Policy: Deny Permit Protocols: All Rule: Source Type: IP Group IPGroup_Any 0/1 Items + Create Destination Type: IP Group Deny IPGroup_Any 0/1 Items + Create Apply Cancel

  1. Define packet-filtering criteria of the rule, including protocols, source, and destination, and determine whether to forward the matched packets. Refer to the following table to configure the required parameters and click Apply.

Name Enter a name to identify the ACL.

Status Click the checkbox to enable the ACL.

Policy Select the action to be taken when a packet matches the rule.

Permit: Forward the matched packet.

Deny: Discard the matched packet.

Protocols Select one or more protocol types to which the rule applies from the drop-down list. The default is All, indicating that packets of all protocols will be matched. When you select one of TCP and UDP or both of them, you can set the IP address and port number of a packet as packet-filtering criteria in the rule.

From the Source drop-down list, choose one of these options to specify the source of the packets to which this ACL applies:

NetworkSelect the network you have created. If no networks have been created, you can select the default network (LAN), or go to Settings > Wired Networks > LAN to create one. The AP will examine whether the packets are sourced from the selected network.
IP GroupSelect the IP Group you have created. If no IP Groups have been created, click +Create on this page or go to Settings > Profiles > Groups to create one. The AP will examine whether the source IP address of the packet is in the IP Group.
IP-Port GroupSelect the IP-Port Group you have created. If no IP-Port Groups have been created, click +Create on this page or go to Settings > Profiles > Groups to create one. The AP will examine whether the source IP address and port number of the packet are in the IP-Port Group.
SSID Select the SSID you have created. If no SSIDs have been created, go to Settings > Wireless Networks to create one. The AP will examine whether the SSID of the packet is the SSID selected here.
IPv6 Group Select the IPv6 Group you have created. If no IPv6 Groups have been created, click +Create on this page or go to Settings > Profiles > Groups to create one. The AP will examine whether the source IP address of the packet is in the IPv6 Group.
IPv6-Port Group Select the IPv6-Port Group you have created. If no IPv6-Port Groups have been created, click +Create on this page or go to Settings > Profiles > Groups to create one. The AP will examine whether the source IP address and port number of the packet are in the IPv6-Port Group.

From the Destination drop-down list, choose one of these options to specify the destination of the packets to which this ACL applies:

NetworkSelect the network you have created. If no networks have been created, you can select the default network (LAN), or go to Settings > Wired Networks > LAN to create one. The AP will examine whether the packets are forwarded to the selected network.
IP GroupSelect the IP Group you have created. If no IP Groups have been created, click +Create on this page or go to Settings > Profiles > Groups to create one. The AP will examine whether the destination IP address of the packet is in the IP Group.
IP-Port GroupSelect the IP-Port Group you have created. If no IP-Port Groups have been created, click +Create on this page or go to Settings >Profiles >Groups to create one. The AP will examine whether the destination IP address and port number of the packet are in the IP-Port Group.
IPv6 Group Select the IPv6 Group you have created. If no IPv6 Groups have been created, click +Create on this page or go to Settings >Profiles >Groups to create one. The AP will examine whether the destination IP address of the packet is in the IPv6 Group.
IPv6-Port Group Select the IPv6-Port Group you have created. If no IPv6-Port Groups have been created, click +Create on this page or go to Settings >Profiles >Groups to create one. The AP will examine whether the destination IP address and port number of the packet are in the IPv6-Port Group.

4.5.2 URL Filtering

Overview

URL Filtering allows a network administrator to create rules to block or allow certain websites, which protects it from web-based threats, and deny access to malicious websites.

In URL filtering, the system compares the URLs in HTTP, HTTPS and DNS requests against the lists of URLs that are defined in URL Filtering rules, and intercepts the requests that are directed at a blocked URLs. These rules can be applied to specific clients or groups whose traffic passes through the gateway and APs.

The system filters traffic against the rules in the list sequentially. The first match determines whether the packet is accepted or dropped, and other rules are not checked after the first match. Therefore, the order of the rules is critical. By default, the rules are prioritized based on the sequence they are created. The rule created earlier is checked for a match with a higher priority. To reorder the rules, select a rule and drag it to a new position. If no rules match, the device forwards the packet because of an implicit Permit All clause.

Note that URL Filtering rules take effects with a higher priority over ACL rules. That is, the system will process the URL Filtering rule first when the URL Filtering rule and ACL rules are configured at the same time.

Configuration

To complete the URL Filtering configuration, follow these steps:

1) Create a new URL Filtering rule with the specified type.
2) Define filtering criteria of the rule, including source, and URLs, and determine whether to forward the matched packets.

■ Configuring Gateway Rules

  1. Select a site from the drop-down list of Organization. Go to Settings > Network Security > URL Filtering. Under the Gateway Rules tab, click + Create New Rule to load the following page.

Create New Rule Name: Status: Enable Policy: Deny Permit Source Type: Network Network: Please Select... URLs: http(s):// Apply Cancel Add URL

  1. Define filtering criteria of the rule, including source and URLs, and determine whether to forward the matched packets. Refer to the following table to configure the required parameters and click Apply.

Name Enter a name to identify the URL Filtering rule.

Status Click the checkbox to enable the URL Filtering rule.

Policy Select the action to be taken when a packet matches the rule.

Deny: Discard the matched packet and the clients cannot access the URLs.

Permit: Forward the matched packet and clients can access the URLs.

Source Type Select the source of the packets to which this rule applies.

Network: With Network selected, select the network you have created from the Network drop-down list. If no networks have been created, you can select the default network (LAN), or go to Settings > Wired Networks > LAN to create one. The gateway will filter the packets sourced from the selected network.

IP Group: With IP Group selected, select the IP Group you have created from the IP Group drop-down list. If no IP Groups have been created, click +Create New IP Group on this page or go to Settings > Profiles > Groups to create one. The gateway will examine whether the source IP address of the packet is in the IP Group.

URLs Enter the URL address using up to 128 characters.

URL address should be given in a valid format. The URL which contains a wildcard(*) is supported. One URL with a wildcard(*) can match multiple subdomains. For example, with *.tp-link.com specified, community.tp-link.com will be matched.

■ Configuring AP Rules

  1. Select a site from the drop-down list of Organization. Go to Settings > Network Security > URL Filtering. On AP Rules tab, click + Create New Rule to load the following page.

Create New Rule Name: Status: Enable Policy: Deny Permit Source Type: SSID SSID: Please Select... URLs: http(s):// Add URL Apply Cancel

  1. Define filtering criteria of the rule, including source and URLs, and determine whether to forward the matched packets. Refer to the following table to configure the required parameters and click Apply.

Name Enter a name to identify the URL Filtering rule.

Status Click the checkbox to enable the URL Filtering rule.

Policy Select the action to be taken when a packet matches the rule.

Deny: Discard the matched packet and the clients cannot access the URLs.

Permit: Forward the matched packet and clients can access the URLs.

Source Type Select the SSID of the packets to which this rule applies.

URLs Enter the URL address using up to 128 characters.

URL address should be given in a valid format. The URL which contains a wildcard(*) is supported. One URL with a wildcard(*) can match multiple subdomains. For example, with *.tp-link.com specified, community.tp-link.com will be matched.

4.5.3 MAC Filtering

Overview

MAC Filtering can drop or allow packets from certain devices passing through the router based on the MAC address of the devices. After the MAC filtering policy and MAC filtering list are configured, the router will apply the filter policy to the packets matching the MAC address, and thus limit network traffic and manage network access behaviors.

Configuration

  1. Select a site from the drop-down list of Organization. Go to Settings > Network Security > MAC Filtering.
  2. Enable MAC Filtering and configure the parameters.

General MAC Filtering: Type: Allow packets with the MAC addresses listed below and deny the rest Deny packets with the MAC addresses listed below and allow the rest Direction: ALL Apply Cancel

Type Select the mode of MAC Filtering.

Allow packets with the MAC addresses listed below and deny the rest: Select to allow packets with the listed MAC address to pass through the router, and packets with other MAC addresses will be dropped.
Deny packets with the MAC addresses listed below and allow the rest: Select to drop packets with the listed MAC address, and packets with other MAC addresses will be allowed to pass through the router.
DirectionSelect All when you want to apply the policy to traffic both from LAN to LAN and from LAN to WAN. Select LAN -> WAN when you want to apply the policy only to traffic from LAN to WAN.

3. Click Add MAC Filtering to add MAC addresses or groups to the list.

Add MAC Filtering Name: Policy: MAC Group MAC Address MAC Group: Please Select... Create Cancel

Name Specify the name for the entry.

Policy

Choose MAC Group and specify the MAC groups of devices, then the MAC filtering policy will be applied to traffic with the MAC groups.

Choose MAC Address and specify the MAC addresses of devices, then the MAC filtering policy will be applied to traffic with the MAC addresses.

4.5.4 Attack Defense

Overview

Attacks initiated by utilizing inherent bugs of communication protocols or improper network deployment have negative impacts on networks. In particular, attacks on a network device can cause the device or network paralysis.

With the Attack Defense feature, the gateway can identify and discard various attack packets in the network, and limit the packet receiving rate. In this way, the gateway can protect itself and the connected network against malicious attacks.

The gateway provides two types of Attack Defense:

■ Flood Defense

If an attacker sends a large number of fake packets to a target device, the target device is busy with these fake packets and cannot process normal services. Flood Defense detects flood packets in real time and limits the receiving rate of the packets to protect the device.

Flood attacks include TCP SYN flood attacks, UDP flood attacks, and ICMP flood attacks.

■ Packet Anomaly Defense

Anomalous packets are packets that do not conform to standards or contain errors that make them unsuitable for processing. Packet Anomaly Defense discards the illegal packets directly.

Configuration

■ Configuring Flood Defense

Select a site from the drop-down list of Organization. Go to Settings > Network Security > Attack Defense. In the Flood Defense, click the checkbox and set the corresponding limit of the rate at which specific packets are received.

Flood Defense

Multi-Connections TCP SYN Flood10000Pkt/s(100-99999)
Multi-Connections UDP Flood20000Pkt/s(100-99999)
Multi-Connections ICMP Flood1500Pkt/s(100-99999)
Stationary Source TCP SYN Flood4000Pkt/s(100-99999)
Stationary Source UDP Flood6000Pkt/s(100-99999)
Stationary Source ICMP Flood600Pkt/s(100-99999)
Multi-Connections TCP SYN FloodA TCP SYN flood attack occurs when the attacker sends the target system with a succession of SYN (synchronize) requests. When the system responds, the attacker does not complete the connections, thus leaving the connection half-open and flooding the system with SYN messages. No legitimate connections can then be made.With this feature enabled, the gateway limits the rate of receiving TCP SYN packets from all the clients to the specified rate.
Multi-Connections UDP FloodA UDP flood attack occurs when the attacker sends a large number of UDP packets to a target host in a short time, the target host is busy with these UDP packets and cannot process normal services.With this feature enabled, the gateway limits the rate of receiving UDP packets from all the clients to the specified rate.
Multi-Connections ICMP FloodIf an attacker sends many ICMP Echo messages to the target device, the target device is busy with these Echo messages and cannot process other data packets. Therefore, normal services are affected.With this feature enabled, the system limits the rate of receiving ICMP packets from all the clients to the specified rate.
Stationary Source TCP SYN FloodA TCP SYN flood attack occurs when the attacker sends the target system with a succession of SYN (synchronize) requests. When the system responds, the attacker does not complete the connections, thus leaving the connection half-open and flooding the system with SYN messages. No legitimate connections can then be made.With this feature enabled, the gateway limits the rate of receiving TCP SYN packets from a single client to the specified rate.
Stationary Source UDP FloodA UDP flood attack occurs when the attacker sends a large number of UDP packets to a target host in a short time, the target host is busy with these UDP packets and cannot process normal services.With this feature enabled, the gateway limits the rate of receiving UDP packets from a single client to the specified rate.
Stationary Source ICMP FloodIf an attacker sends many ICMP Echo messages to the target device, the target device is busy with these Echo messages and cannot process other data packets. Therefore, normal services are affected.With this feature enabled, the system limits the rate of receiving ICMP packets from a single clients to the specified rate.

■ Configuring Packet Anomaly Defense

Select a site from the drop-down list of Organization. Go to Settings > Network Security > Attack Defense. In the Packet Anomaly Defense, click the checkbox and set the corresponding limit of the rate at which specific packets are received.

Packet Anomaly Defense ⓘ

√ Block Fragment Traffic
√ Block TCP Scan (Stealth FIN/Xmas/Null)
□ Block TCP Scan with RST
√ Block Ping of Death
√ Block Large Ping
√ Block Ping from WAN
√ Block WinNuke Attack
√ Block TCP Packets with SYN and FIN Bits Set
√ Block TCP Packets with FIN Bit but No ACK Bit Set
√ Block Packets with Specified Options

√ Security Option
√ Loose Source Route Option
√ Strict Source Route Option
Record Route Option
Stream Option
√ Timestamp Option
No Operation Option

Block Fragment Traffic

With this option enabled, the fragmented packets without the first part of the packet will be discarded.

Block TCP Scan (Stealth FIN/Xmas/Null)With this option enabled, the gateway will block the anomalous packets in the following attack scenarios:Stealth FIN Scan: The attacker sends the packet with its SYN field and the FIN field set to 1. The SYN field is used to request initial connection whereas the FIN field is used to request disconnection. Therefore, the packet of this type is illegal.Xmas Scan: The attacker sends the illegal packet with its TCP index, FIN, URG and PSH field set to 1.Null Scan: The attacker sends the illegal packet with its TCP index and all the control fields set to 0. During the TCP connection and data transmission, the packets with all control fields set to 0 are considered illegal.
Block TCP Scan with RSTWith this option enabled, the gateway will respond to RST messages. It is disabled by default.
Block Ping of DeathWith this option enabled, the gateway will block Ping of Death attack. Ping of Death attack means that the attacker sends abnormal ping packets which are smaller than 64 bytes or larger than 65535 bytes to cause system crash on the target computer.
Block Large PingWith this option enabled, the router will block the ping packets which are larger than 1024 packets to protect the system from Large Ping attack.
Block Ping from WAN With this option enabled, the router will block the ICMP request from WAN.
Block WinNuke AttackWith this option enabled, the router will block WinNuke attacks. WinNuke attack refers to a remote DoS (denial-of-service) attack that affects some Windows operating systems, such as the Windows 95. The attacker sends a string of OOB (Out of Band) data to the target computer on TCP port 137, 138 or 139, causing system crash or Blue Screen of Death.
Block TCP Packets with SYN and FIN Bits SetWith this option enabled, the router will filter the TCP packets with both SYN Bit and FIN Bit set.
Block TCP Packets with FIN Bit but No ACK Bit SetWith this option enabled, the router will filter the TCP packets with FIN Bit set but without ACK Bit set.
Block Packets with Specified OptionsWith this option enabled, the router will filter the packets with specified IP options including Security Option, Loose Source Route Option, Strict Source Route Option, Record Route Option, Stream Option, Timestamp Option, and No Operation Option.You can choose the options according to your needs.

4.5.5 Firewall

Overview

Firewall is used to enhance the network security. In State Timeouts, you can specify a number of timeouts for sessions including TCP, UDP, and ICMP connection. The packets will be forwarded within the specified timeout. When there is no response after the specified time, the session or status will be closed. State timeout will help close inactive sessions and thus avoid network malfunction. In

Firewall Options, you can further configure the gateway to prevent attacks like SYN flood attacks and broadcast ping.

Configuration

■ Configuring State Timeouts

Select a site from the drop-down list of Organization. Go to Settings > Network Security > Firewall. In the Sate Timeouts, set the time limit for the different sessions.

State Timeouts

ICMP:60Seconds(1-21474836)i
Other:600Seconds(1-21474836)i
TCP Close:10Seconds(1-21474836)i
TCP Close Wait:60Seconds(1-21474836)i
TCP Established:7440Seconds(1-21474836)i
TCP FIN Wait:120Seconds(1-21474836)i
TCP Last ACK:30Seconds(1-21474836)i
TCP SYN Recv:60Seconds(1-21474836)i
TCP SYN Sent:120Seconds(1-21474836)i
TCP Time Wait:120Seconds(1-21474836)i
UDP Other:60Seconds(1-21474836)i
UDP Stream:180Seconds(1-21474836)i

ICMP The ICMP session will be closed if there is no response after the set time.

Other The sessions for protocols excluding TCP, UDP, and ICMP will be closed if there is no response after the set time.

TCP Close The TCP Close status will be closed if there is no response after the set time.

TCP Close Wait The TCP Close Wait status will be closed if there is no response after the set time.

TCP Established The TCP Established status will be closed if there is no response after the set time.

TCP FIN Wait The TCP FIN Wait status will be closed if there is no response after the set time.

TCP Last ACK The TCP Last ACK status will be closed if there is no response after the set time.
TCP SYN RecvThe TCP SYN (Synchronize) Recv status will be closed if there is no response after the set time.
TCP SYN SentThe TCP SYN (Synchronize) Sent status will be closed if there is no response after the set time.
TCP Time WaitThe TCP Time Wait status will be closed if there is no response after the set time.
UDP OtherThe UDP connections with traffic in only one direction will be stopped if there is no response after the set time.
UDP StreamThe UDP connections with bidirectional traffic will be stopped if there is no response after the set time.

■ Configuring Firewall Options

Select a site from the drop-down list of Organization. Go to Settings > Network Security > Firewall. In the Sate Timeouts, set the time limit for the different sessions.

Firewall Options Broadcast Ping: Receive Redirects: Send Redirects: SYN Cookies:

Broadcast Ping With it enabled, the gateway will reply to broadcast pings.
Receive Redirects With it enabled, the gateway will accept ICMP redirects.
Send Redirects With it enabled, the gateway will send ICMP redirects.
SYN CookiesWith it enabled, the SYN cookies will be used to resist SYN flood attacks that want to open ports on the gateway.

4.5.6 IP-MAC Binding

Overview

ARP (Address Resolution Protocol) is used to map IP addresses to the corresponding MAC addresses so that packets can be delivered to their destinations. However, if attackers send ARP spoofing packets with false IP address-to-MAC address mapping entries, the device will update the ARP table

based on the false ARP packets and record wrong mapping entries, which results in a breakdown of normal communication.

Anti ARP Spoofing can protect the network from ARP spoofing attacks. It works based on the IP-MAC Binding. These entries record the correct one-to-one relationships between IP addresses and MAC addresses. When receiving an ARP packet, the router checks whether it matches any of the IP-MAC Binding entries. If not, the router will ignore the ARP packets. In this way, the router maintains the correct ARP table.

Configuration

  1. Select a site from the drop-down list of Organization. Go to Settings > Network Security > IP-MAC Binding.
  2. Enable ARP Spoofing Defense and configure general settings. Click Apply.

General

ARP Spoofing Defense:

Enable

Interface:

TP-LINK Omada SDN Controller - General - 1

√ Permit the packets matching the IP-MAC Binding entries only

√ Send GARP packets when ARP attack is detected

Interval:

TP-LINK Omada SDN Controller - General - 2

Apply

Cancel

ARP Spoofing Defense Check the box to globally enable ARP Spoofing Defense.

Interface Select the interface on which the entries will take effect.

Permit the packets matching the IP-MAC Binding entries only

With this option enabled, when receiving a packet, the router will check whether the IP address, MAC address and receiving interface match any of the IP-MAC Binding entries. Only the matched packets will be forwarded. This feature can be enabled only when ARP Spoofing Defense is enabled.

Send GARP packets when ARP attack is detected

With this option enabled, the router will send GARP packets to the hosts if it detects ARP spoofing packets on the network. The GARP packets will inform the hosts of the correct ARP information, which is used to replace the wrong ARP information in the hosts. This feature can be enabled only when ARP Spoofing Defense is enabled.

Interval Specify the time interval for sending GARP packets. The valid values are from 1 to 10000.

  1. Click Create New IP-MAC Binding Entry and add an IP-MAC binding entry. Click Apply.

Create New IP-MAC Binding Entry IP Address: .... MAC Address: .... Interface: Please Select... Description: [Optional] Status: Enable Apply Cancel

IP Address Specify the IP address to be bound.

MAC Address Specify the MAC address to be bound.

Interface Select the interface on which the entries will take effect.

Description Enter a description for identification.

Status Enable the entry. Only when the status is enabled will the entry take effect.

4.5.7 IDS/IPS

Overview

IDS/IPS is a security mechanism that detects intrusions based on attack characteristics. It can detect malware, Trojan horses, worms, ActiveX and other attacks to protect the network security of users.

! Note:

Using Intrusion Detection/Prevention may reduce maximum throughput speeds.

Configure IDS/IPS

  1. Select a site from the drop-down list of Organization. Go to Settings > Network Security > IDS/IPS.

2. Enable Intrusion Detection/Prevention and configure the parameters.

IDS/IPS Intrusion Detection/Prevention: Type: Detect Only (IDS) Detect and Prevent (IPS) Using Intrusion Detection/Prevention may reduce maximum throughput speeds. GEO Enforcer: Enable Security Level: High 12 of 12 Threat Categories Enabled. Effective Time: Enable Apply Cancel

Type Specify the working mode.

In IDS mode, the system will only report the threat log.

In IPS mode, the system will block the corresponding connection for 300s after a threat is detected.

GEO Enforcer Enable geographic location identification of threat logs.

Security Level Choose the protection level. A higher protection level means more threat types are detected, while a lower protection level only detects some important threats. You can also customize the protection level.

Effective Time Specify the effective time period of the IDS/IPS module.

3. Apply the settings.

When the system discovers a threat, the corresponding threat log will be displayed on the Insights > Threat Management page.

Manage Threats in a Site

  1. Select a site from the drop-down list of Organization. Go to Insights > Threat Management.

  2. Click a threat that the system discovered, then you can choose a specified response strategy for the corresponding attack IP: Block, Isolate Device, Signature Suppression, or Allow.

Session Unit Xpert Clients Post Connecticut Post Portal Authorizations Switch Status Post Forwarding Status vPH Status Reading Table Dynamic DNS Windows CS:RTs Throat Management One Data Date TIME SOURCE LOCATION THREAT DESCRIPTION SEVERITY CATEGORY New 21, 2023 14:30:00 ET DNS Query to a " No. Major DNS New 13, 2023 18:22:40 ET DNS Query to a " No. Major DNS New 10, 2023 16:11:55 ET DNS Non DNS of No. Low DNS Serving 1-2 of 3 records 10 / page Go in page. Throat Management Detail Overview Unarchived Date Time Nov 21, 2023 14:30:00 Source IP Location Destination IP Location United States Source IP Destination IP: 192.168.192.15 0.9.8.9 Threat Description Severity ET DNS Query to a " top contain - Likely Hostire • Major" Category Classification DNS? bad-unknown Activity Protocol 70 B UDP Block Isolate Device Signature Suppression Allow

Block Drop traffic to/from the external IP address and the specific internal IP address.

If you block an entry, it will be added to the Block List at Settings > Network Security > IDS/IPS.

Isolate Device Drop traffic to/from the external IP address and any internal IP address.

Signature Suppression Mute the alerting on certain signatures. This will also disable blocking on traffic matching the designated suppression rule.

If you suppress the signature of an entry, it will be added to the Signature Suppression list at Settings > Network Security > IDS/IPS.

Allow Trust the IP address so that the traffic, depending on the direction selected, will not get blocked to or from the identified IP address.

If you allow an entry, it will be added to the Allow List at Settings > Network Security > IDS/IPS.

  1. You can further check and edit processed entries at Settings > Network Security > IDS/IPS.

■ Block List

The Block List page displays all block entries added through the Threat Management page. You can choose to block all traffic of the source IP in the threat log, or block all traffic between the source IP and the destination IP in the threat log.

■ Allow List

On the Allow List page, you can add, view, and edit the exemption entries of IDS/IPS detection, so that the specified objects will no longer trigger threat logs.

Click Create New Allow List and configure the parameters.

Create New Allow List Direction: Source Track By: IP Address IP Address: . Submit Cancel

DirectionSpecify the location of the object (target) exempt from triggering the threat: source, destination, or both directions.
Track By Specify the type of object (target) exempt from triggering the threat: IP address, Network, or Subnet.
IP Address/Network/SubnetSpecify the value of the object.

■ Signature Suppression

The Signature Suppression page displays all the signature suppression entries added through the Threat Management page, and the objects with signature suppressed will no longer trigger specific threat logs.

Manage Threats Globally

In Global view, go to Security.

■ Threat Management List

In the Threat Management List, you can check top threats by severity, locations of top threats, and unarchived and archived threats.

TP-LINK Omada SDN Controller - ■ Threat Management List - 1

pie Total Threats By Severity | Location | Attempts | Source | Count | | :--- | :--- | :--- | :--- | | - | 982 | Multiple | 982 | | China | 1 | 171.06-41.72 | 1 | | Canada | 1 | 164.75-221.167 | 1 | Source-DESTINATION LOCATION DATE TIME THREAT DESCRIPTION SEVERITY SITE CATEGORY CLASSIFICATION CLASSIFICATION DESCRIF - - - Feb 04, 2024 01:58:29 pm ET DNS Query to a tk d... Low UES_ER707-M2v1 DNS ① bad-unknown Potentially Bad Traffic - - - Feb 04, 2024 01:58:28 pm ET DNS Query to a tk d... Low UES_ER707-M2v1 DNS ① bad-unknown Potentially Bad Traffic - - - China Feb 04, 2024 01:58:26 pm ET DNS Query to a tk d... Low UES_ER707-M2v1 DNS ① bad-unknown Potentially Bad Traffic - - - China Feb 04, 2024 01:58:26 pm ET DNS Query for to T... Moderate UES_ER707-M2v1 DNS ① bad-unknown Potentially Bad Traffic - - - - Feb 04, 2024 01:58:24 pm ET DNS Query for Is T... Moderate UES_ER707-M2v1 DNS ① bad-unknown Potentially Bad Traffic

In the unarchived threat list, click an entry, then you can choose a specified response strategy for the corresponding attack IP: Block, Isolate Device, Signature Suppression, or Allow.

TP-LINK Omada SDN Controller - ■ Threat Management List - 2

pie Total Threats By Severity | Location | Attempts | | :--- | :--- | | - | 582 | | China | 1 | | Canada | 1 | | Source IP Location | Destination IP Location | | --- | --- | | 192 168 187 9 | 223.5 5.5 | | Threat Description | Severity | | :--- | :--- | | ET DNS Query to a 3c domain - Likely Hostile | Low | | Category: DNS (1) | Classification: bad-unknown | | :--- | :--- | | Activity: 83 B | Protocol: UDP | | SOURCE-DESTINATION LOCATION | DATE TIME | THREAT DESCRIPTION | SEVERITY | SITE | CATEGORY | | :--- | :--- | FTDS Query to a 3rd... | Low | UES_ER074Mv1 | DNS (1) | | :--- | :--- | FTDS Query to a 3rd... | Low | UES_ER074Mv1 | DNS (1) | | :--- | China | FTDS Query to a 3rd... | Low | UES_ER074Mv1 | DNS (1) | | :--- | China | FTDS Query for to T... | Moderate | UES_ER074Mv1 | DNS (1) | | :--- | China | FTDS Query for to T... | Moderate | UES_ER074Mv1 | DNS (1) | | Source IP Location: - | Destination IP Location: China mainland | | :--- | :--- | | Source IP: 192 168 187 9 | Destination IP: 223.5 5.5 | | Threat Description: ET DNS Query to a 3c domain - Likely Hostile: | Severity | | :--- | :--- | | Category: DNS (1) | Classification: bad-unknown | | Activity: 83 B | Protocol: UDP | | Source IP Location: - | Destination IP Location: China mainland | | :--- | :--- | | Source IP: 192 168 187 9 | Destination IP: 223.5 5.5 | | Threat Description: ET DNS Query to a 3c domain - Likely Hostile: | Severity | | :--- | :--- | | Category: DNS (1) | Classification: bad-unknown | | Activity, Protocol, UDP: | Protocol, UDP | | Source IP Location: - | Destination IP Location: China mainland | | :--- | :--- | | Source IP: 192 168 187 9 | Destination IP: 223.5 5.5 | | Source IP Location: - | Destination IP Location: China mainland | | :--- | :--- | | Source IP: 192 168 187 9 | Destination IP: 223.5 5.5 | | Threat Description: ET DNS Query to a 3c domain - Likely Hostile: | Severity | | :--- | :--- | | Category: DNS (1) | Classification: bad-unknown | | Activity; Protocol; UDP: | Protocol; UDP | | Source IP Location: - | Destination IP Location: China mainland | | :--- | :--- | | Source IP Location: 192 168 187 9 | Destination IP Location: 223.5 5.5 | | Source IP Location: - | Destination IP Location: China mainland | | :--- | :--- | | Source IP Location: 192 168 187 9 | Destination IP Location: 223.5 5.5 | | Source IP Location: - | Destination IP Location: China mainland | | :--- | :--- | | Source IP Location: 192 168 187 9 | DestinationIP Location: 223.5 5.5 | | Source IP Location: - | Destination IP Location: China mainland | | :--- | :--- | | Source IP Location: 192 168 187 9 | Destination IP Location: 223.5 5.5 | | Source IP Location: - | Destination IP Location: China mainland | | :--- | :--- | | Source IP Location: 192.168.187.9 | Destination IP Location: 223.5.5.5 | | Source IP Location: - | Destination IP Location: China mainland | | :--- | :--- | | Source IP Location: 192.168.187.9 | Destination IP Location: 223.5.5.5 | | Source IP Location: - | Destination IP Location: China mainland | | :--- | :--- | | Source IP Location: 192.168.187.39 | Destination IP Location: 223.5.5.5 | | Source IP Location: - | Destination IP Location: China mainland | | :--- | :--- | | Source IP Location: 192.168.187.39 | Destination IP Location: 223.5.5.5 | | Source IP Location: - | Destination IP Location: China mainland | | :--- | :--- | | Source IP Location/Source IP Location / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target); Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) or Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) , Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) / Target (Target) .

Block Drop traffic to/from the external IP address and the specific internal IP address.

If you block an entry, it will be added to the Block List at Settings > Network Security > IDS/IPS.

Isolate Device Drop traffic to/from the external IP address and any internal IP address.

Signature SuppressionMute the alerting on certain signatures. This will also disable blocking on traffic matching the designated suppression rule.If you suppress the signature of an entry, it will be added to the Signature Suppression list at Settings > Network Security > IDS/IPS.
Allow Trust the IP address so that the traffic, depending on the direction selected, will not get blocked to or from the identified IP address.If you allow an entry, it will be added to the Allow List at Settings > Network Security > IDS/IPS.

■ Threat Management Map

In the Threat Management Map, you can view the threat sources and numbers of attacks that the system has discovered. You can click a number in the map to view attack details.

You can right-click a location to block its attack events and manage the Block Locations list.

If excessive attacks have been detected, you can choose specific severity levels to display.

Threat Management Map Threat Management List Feb 03, 2024 Feb 04, 2024 All Low Minor Moderate Major Critical Back Location Locations Attacked by Canada DESTINATION LOCATIONS TIME THREAT DESCRIPTION SITE CATEGORY CLASSIFICATION CLASSIFICATION DESCRIPTION DATA USAGE — Feb 03, 2024 08:12:51 ppt ET TOR Known Tor Relay/Router (Not Exit) Node Traffic group 241 UEB_ER797.MDv1 Tor mac-attack Mac Attack 74 B

4.5.8 Application Control

Overview

DPI (Deep Packet Inspection) helps you identify, analyze, and control the traffic at the application layer in the network. DPI engine includes the latest application identification signatures to track which applications are using the most bandwidth. You can better manage and distribute network traffic usage through DPI.

Configuration

  1. Select a site from the drop-down list of Organization. Go to Settings > Network Security > Application Control.

  2. On the Deep Packet Inspection page, enable Deep Packet Inspection and Logging Traffic, then apply the settings.

Deep Packet Inspection Deep Packet Inspection: Logging Traffic: Apply Cancel

Deep Packet InspectionWhen enabled, the device will send the forwarded traffic to a professional local DPI engine for analysis, so as to judge and identify the type of traffic.
Logging TrafficWhen enabled, the device will collect and save the results of traffic analysis. You can check the results on the Statistics > Application Analytics page.
  1. Apply the settings.

  2. On the Rules Management page, click Create New Rule. You can predefine one or more rules, and APP control strategy that can be referenced, and realize block or QoS actions for specified Apps within a specified time period.

Create New Rule Rays Name: Schedule: Manage Time Range Entry QoS: Enable Select Apps Search Name NAME CATEGORY DESCRIPTION ACTION 1-clickshare-com Shareholding:The application 1-clickshare-com was used to classify traffic from the hoster with the same name. It was deprecated because the website is no longer reachable. 1-upload-com Shareholding:The application 1-upload-com was used to classify traffic from the hoster with the same name. It was deprecated because the website is no longer reachable. 1-upload-to Shareholding:The application 1-upload-to was used to classify traffic from the hoster with the same name. It was deprecated because the website is no longer reachable. 10upload-com Shareholding:The application 10upload-com was used to classify traffic from the hoster with the same name. It was deprecated because the website is no longer reachable. 123VPN Tunnel 123VPN is a free VPN application provided by Ampusnet SRL. 123upload Shareholding:The application 123upload was used for traffic from the hoster with the same name. It was deprecated because the website is no longer reachable. 123upload-pt Shareholding:The application 123upload-pt was used to classify traffic from the hoster with the same name. It was deprecated because the website is no longer reachable. 138span-com Shareholding:The application 138span-com was used to classify traffic from the hoster with the same name. It was deprecated because the website is no longer reachable. 160pan-com Shareholding:The application 160pan-com was used to classify traffic from the hoster with the same name. It was deprecated because the website is no longer reachable. 14clockshare-net Shareholding:The application 14clockshare-net was used to classify traffic from the hoster with the same name. It was deprecated because the website is no longer reachable. Select 0 of 2005 items: Select AI Showing 1-10 of 2005 records < 1 2 3 4 5 ... 209 > 10 / page On To page Apply Cancel

Rule NameSpecify the name of the rule.
ScheduleSpecify the time period when the rule takes effect. You can create new time range according to your needs.
QoSEnable this option and select QoS Class to configure the QoS strategy if needed.
When enabled, the traffic will be limited according to the configuration. When disabled, the App will be blocked.
Select AppsSelect the Apps for the rule.
  1. On the Application Filter page, click Create New Application Filter. You can apply the defined rules and divide multiple rules into one filter set for easy management.

Create New Application Filter Name: Description: Select Rules + Add RULES NAME APP NUMBER QOS STATUS SCHEDULE ACTION AD 144 Disabled everyday Select 0 of 1 items Select All Showing 1-1 of 1 records < 1 > 10 / page Go To page: Go Create Cancel

NameSpecify the name of the filter.
DescriptionEnter a description for identification.
Select RulesSelect the rules for the filter.
  1. On the DPI Packet Inspection page, click Create New Assign Restriction. Select a network to apply a pre-defined filter.

Create New Assign Restriction Network: Filter: Please Select. Confirm Cancel

NetworkSelect a network to apply the filter.
FilterSelect a pre-defined filter.
  1. Save the settings. You can view the results of traffic analysis on the Statistics > Application Analytics page.

TP-LINK Omada SDN Controller - Configuration - 5

pie | Category | Messaging (GB) | Enterprise Services (GB) | Streaming (GB) | Social (GB) | | :--- | :--- | :--- | :--- | :--- | | Messaging | 118.75 | 86.76 | 47.00 | 35.82 | | Enterprise Services | 86.92 | 36.96 | 34.22 | 31.56 | | Streaming | 47.00 | 25.96 | 5.83 | 3.22 | | Social | 35.82 | 10.37 | 7.92 | 9.11 | | Development Tools and Services | 28.76 | 21.90 | 17.27 | 8.69 | The chart displays a pie chart with percentage shares for each category. The data is presented in a grid layout with categories labeled by name and value. Key metrics include transaction volume (GB), market share (%), and revenue (MB).

If you want to clear DPI data of a time period, go to the Deep Packet Inspection page, click the Clear Data button and specify the period.

TP-LINK Omada SDN Controller - Configuration - 6

4.6 Transmission

Transmission helps you control network traffic in multiple ways. You can add policies and rules to control transmission routes and limit the session and bandwidth.

4.6.1 Routing

Overview

■ Static Route

Network traffic is oriented to a specific destination, and Static Route designates the next hop or interface where to forward the traffic.

■ Policy Routing

Policy Routing designates which WAN port the router uses to forward the traffic based on the source, the destination, and the protocol of the traffic.

Configuration

■ Static Route

  1. Go to Setting > Transmission > Routing > Static Route. Click + Create New Route to load the following page and configure the parameters.

Create New Route

Name:

TP-LINK Omada SDN Controller - Create New Route - 1

Status:

TP-LINK Omada SDN Controller - Create New Route - 2

Enable

Destination IP/Subnet:

TP-LINK Omada SDN Controller - Create New Route - 3

TP-LINK Omada SDN Controller - Create New Route - 4

Add Subnet

Route Type:

TP-LINK Omada SDN Controller - Create New Route - 5

Next Hop

TP-LINK Omada SDN Controller - Create New Route - 6

Interface

Next Hop:

TP-LINK Omada SDN Controller - Create New Route - 7

Metric:

TP-LINK Omada SDN Controller - Create New Route - 8

Create

Cancel

Name Enter the name to identify the Static Route entry.

Status Enable or disable the Static Route entry.

Destination IP/SubnetDestination IP/Subnet identifies the network traffic which the Static Route entry controls. Specify the destination of the network traffic in the format of 192.168.0.1/24. You can click + Add Subnet to specify multiple Destination IP/Subnets and click 📄 to delete them.
Route Type Next Hop: With Next Hop selected, your devices forward the corresponding network traffic to a specific IP address. You need to specify the IP address as Next Hop.
Metric Define the priority of the Static Route entry. A smaller value means a higher priority. If multiple entries match the Destination IP/Subnet of the traffic, the entry of higher priority takes precedence. In general, you can simply keep the default value.
  1. Click Create. The new Static Route entry is added to the table. You can click ☑ to edit the entry. You can click 🔒 to delete the entry.

Search Static Route Entry NAME ENABLED DESTINATION IP TYPE INTERFACE NEXT HOP METRIC ACTION tp-link ● 192.168.2.3/24 Next Hop 192.168.3.1 0 Showing 1-1 of 1 records < 1 > 10 /page Go To page: GO + CreateNewRoute

■ Policy Routing

  1. Go to Setting > Transmission > Routing > Policy Routing. Click + Create New Routing to load the following page and configure the parameters.

Create New Routing Name: Status: Enable Protocols: All WAN: Please Select... Use the other WAN port if the current one is down: Enable i Routing Legend Source Type: Network LAN MGMT VLAN 0/2 Items Destination Type: IP Group Please Select... IPGroup_Any 0/1 Items + Create Create Cancel

Name Enter the name to identify the Policy Routing entry.

Status Enable or disable the Policy Routing entry.

Protocols Select the protocols of the traffic which the Policy Routing entry controls. The Policy Routing entry takes effect only when the traffic matches the criteria of the entry including the protocols.

WAN Select the WAN port to forward the traffic through. If you want to forward the traffic through the other WAN port when the current WAN is down, enable Use the other WAN port if the current WAN is down.

Routing Legend The Policy Routing entry takes effect only when the traffic using specified protocols matches the source and destination which are specified in the Routing Legend.
Select the type of the traffic source and destination.
Network: Select the LAN Interfaces for the traffic source or destination.
IP Group: Select the IP Group for the traffic source or destination. You can click + Create to create a new IP Group.
IP-Port Group: Select the IP-Port Group for the traffic source or destination. You can click + Create to create a new IP-Port Group.
  1. Click Create. The new Policy Routing entry is added to the table. You can click ☑ to edit the entry. You can click 🔒 to delete the entry.
NAMEENABLEPROTOCOLSOURCEDESTINATIONWANACTION
tp-LinkAllLANIPGroup_AmyWAN

4.6.2 NAT

Overview

■ Port Forwarding

You can configure Port Forwarding to allow internet users to access local hosts or use network services which are deployed in the LAN.

Port Forwarding helps establish network connections between a host on the internet and the other in the LAN by letting the traffic pass through the specific port of the gateway. Without Port Forwarding, hosts in the LAN are typically inaccessible from the internet for the sake of security.

ALG

ALG ensures that certain application-level protocols function appropriately through your gateway.

■ One-to-One NAT

One-to-One NAT will establish a correspondence between a private IP and a public IP, allowing access to the device with the private IP through the corresponding public IP.

Configuration

■ Port Forwarding

  1. Go to Setting > Transmission > NAT > Port Forwarding. Click + Create New Rule to load the following page and configure the parameters.

Create New Rule Name: Status: Enable Source IP: Any Limited IP Address Interface: WAN × DMZ: Enable Source Port: (1-65535. e.g. 80 or 80-100) Destination IP: . . . . Destination Port: (1-65535. e.g. 80 or 80-100) Protocol: All TCP UDP Create Cancel

Name Enter the name to identify the Port Forwarding rule.

Status Enable or disable the Port Forwarding rule.

Source IP

Any: The rule applies to traffic from any source IP address.

Limited IP Address: The rule only applies to traffic from specific IP addresses. With this option selected, specify the IP addresses and subnets according to your needs.

Interface Select the interface which the rule applies to. Traffic which is received through the interface is forwarded according to the rule.

DMZWith DMZ enabled, all the traffic is forwarded to the Destination IP in the LAN, port to port. You need to specify the Destination IP.With DMZ disabled, only the traffic which matches the Source Port and the Protocol is forwarded. The traffic is forwarded to the Destination Port of the Destination IP in the LAN. You need to specify the Source Port, Destination IP, Destination Port, and Protocol.
Source PortThe gateway uses the Source Port to receive the traffic from the internet. Only the traffic which matches the Source Port and the Protocol is forwarded.
Destination IPThe traffic is forwarded to the host of the Destination IP in the LAN.
Destination PortThe traffic is forwarded to the Destination Port of the host in the LAN.
Protocol Network traffic is transmitted using either TCP or UDP protocol. Only the traffic which matches the Source Port and the Protocol is forwarded.If you want both TCP traffic and UDP traffic to be forwarded, select All.
  1. Click Create. The new Port Forwarding entry is added to the table. You can click ☑ to edit the entry. You can click 🔒 to delete the entry.
NAMEENABLEPROTOCOLSOURCEDESTINATIONWANACTION
tp-tekAllIPGroup_AmyWAN

ALG

Go to Setting > Transmission > NAT > ALG. Enable or disable certain types of ALG according to your needs and click Apply.

ALG FTP ALG: ✓ Enable H.323 ALG: ✓ Enable PPTP ALG: ✓ Enable SIP ALG: ✓ Enable IPsec ALG: ✓ Enable Apply Cancel

FTP ALG FTP ALG allows the FTP server and client to transfer data using the FTP protocol in one of the following scenarios:

  • The FTP server is in the LAN, while the FTP client is on the internet.
  • The FTP server is on the internet, while the FTP client is in the LAN.
  • The FTP server and FTP client are in different LANs.

H.323 ALG H.323 ALG allows the IP phones and multimedia devices to set up connections using the H.323 protocol in one of the following scenarios:

  • One of the endpoints is in the LAN, while the other is on the internet.
  • The endpoints are in different LANs.

PPTP ALG PPTP ALG allows the PPTP server and client to set up a PPTP VPN in one of the following scenarios:

  • The PPTP server is in the LAN, while the PPTP client is on the internet.
  • The PPTP server is on the internet, while the PPTP client is in the LAN.
  • The PPTP server and PPTP client are in different LANs.

SIP ALG SIP ALG allows the IP phones and multimedia devices to set up connections using the SIP protocol in one of the following scenarios:

• One of the endpoints is in the LAN, while the other is on the internet.
- The endpoints are in different LANs.

IPsec ALG IPsec ALG allows the IPsec endpoints to set up an IPsec VPN in one of the following scenarios:

• One of the endpoints is in the LAN, while the other is on the internet.
- The endpoints are in different LANs.

■ One-to-One NAT

  1. Go to Setting > Transmission > NAT > One-to-One NAT. Click + Create New Rule to load the following page and configure the parameters.

Create New Rule Name: Status: Enable Interface: Please Select... Original IP: . . . . Translated IP: . . . . DMZ Forwarding: Enable Description: (Optional) Create Cancel

Name Enter the name to identify the one-to-one NAT rule.
Status Enable or disable the one-to-one NAT rule.
Interface Specify the effective interface for the rule only when the connection type is Static IP.
Original IP Specify the original IP address for the rule, which means the device's private IP. The original IP address cannot be the broadcast address, network segment or interface IP. With One-to-One NAT enabled, the original IP will map to the translated IP.
Translated IPSpecify the translated IP address for the rule, which means the public IP of device. The translated IP address cannot be the broadcast address, network segment or interface IP. With One-to-One NAT enabled, the original IP will map to the translated IP.
DMZ Forwarding Choose to enable DMZ Forwarding. The packets transmitted to the translated IP address will be forwarded to the host with the original IP address if DMZ Forwarding is enabled.
Description (Optional) Enter a description for identification.
  1. Click Create to add the one-to-one NAT rule.

4.6.3 Session Limit

Overview

Session Limit optimizes network performance by limiting the maximum sessions of specific sources.

Configuration

  1. Go to Setting > Transmission > Session Limit. In Session Limit, enable Session Limit globally and click Apply.

Session Limit Session Limit: Apply

  1. In Session Limit Rule List, click + Create New Rule to load the following page and configure the parameters.

Create New Rule Name: Status: Enable Source Type: Network IP Group Network: Please Select... Maximum Sessions: (1-999999) Create Cancel

Name Enter the name to identify the Session Limit rule.

Status Enable or disable the Session Limit rule.

Source Type Network: Limit the maximum sessions of specific LAN networks. With this option selected, select the networks, which you can customize in Wired Networks > LAN Networks. For detailed configuration of networks, refer to 4.3.2 Configure LAN Networks.

IP Group: Limit the maximum sessions of specific IP Groups. With this option selected, select the IP Groups, which you can customize in Profiles >Groups. For detailed configuration of IP groups, refer to 4.8 Create Profiles.

Maximum Sessions Enter the maximum sessions of the specific sources.

  1. Click Create. The new Session Limit rule is added to the list. You can click ☑ to edit the rule. You can click 🔒 to delete the rule.

Session Limit Rule List NAME ENABLED SOURCE MAXIMUM SESSIONS ACTION tp-link ● Network: LAN 60000 + CreateNewRule

4.6.4 Bandwidth Control

Overview

Bandwidth Control optimizes network performance by limiting the bandwidth of specific sources.

Configuration

  1. Go to Setting > Transmission > Bandwidth Control. In Bandwidth Control, enable Bandwidth Control globally and configure the parameters. Then click Apply.

Bandwidth Control Bandwidth Control: Threshold Control: Enable Bandwidth Control when bandwidth usage reaches 80 % WAN Upstream Bandwidth: Kbps (100-999999) Test Speed Downstream Bandwidth: Kbps (100-999999) Apply Cancel

Threshold Control

With Threshold Control enabled, Bandwidth Control takes effect only when total bandwidth usage reaches the specified percentage. You need to specify the total Upstream Bandwidth and Downstream Bandwidth of the WAN ports. It's recommended to use the Test Speed tool to decide the actual Upstream Bandwidth and Downstream Bandwidth.

2. In Bandwidth Control Rule List, click + Create New Rule to load the following page and configure the parameters.

Create New Rule

Name:

Status:

Source Type:

Network:

WAN:

Upstream Bandwidth:

Downstream Bandwidth:

Mode:

TP-LINK Omada SDN Controller - Create New Rule - 1

TP-LINK Omada SDN Controller - Create New Rule - 2

TP-LINK Omada SDN Controller - Create New Rule - 3

TP-LINK Omada SDN Controller - Create New Rule - 4

Please Select...

Please Select...

TP-LINK Omada SDN Controller - Create New Rule - 5

TP-LINK Omada SDN Controller - Create New Rule - 6

TP-LINK Omada SDN Controller - Create New Rule - 7

TP-LINK Omada SDN Controller - Create New Rule - 8

TP-LINK Omada SDN Controller - Create New Rule - 9

TP-LINK Omada SDN Controller - Create New Rule - 10

(100-999999)

Kbps

Kbps

(100-999999)

Create

Cancel

Name Enter the name to identify the Bandwidth Control rule.

Status Enable or disable the Bandwidth Control rule.

Source Type

Network: Limit the maximum bandwidth of specific LAN networks. With this option selected, select the networks, which you can customize in Wired Networks > LAN Networks. For detailed configuration of networks, refer to 4.3.2 Configure LAN Networks.

IP Group: Limit the maximum bandwidth of specific IP Groups. With this option selected, select the IP Groups, which you can customize in Profiles >Groups. For detailed configuration of IP groups, refer to 4.8 Create Profiles.

WAN Select the WAN port which the rule applies to.

Upstream BandwidthSpecify the limit of Upstream Bandwidth, which the specific local hosts use to transmit traffic to the internet through the gateway.
Downstream BandwidthSpecify the limit of Downstream Bandwidth, which the specific local hosts use to receive traffic from the internet through the gateway.
Mode Specify the bandwidth control mode for the specific local hosts.
Shared: The total bandwidth for all the local hosts is equal to the specified values.
Individual: The bandwidth for each local host is equal to the specified values.
  1. Click Create. The new Bandwidth Control rule is added to the list. You can click ☑ to edit the rule. You can click 🔒 to delete the rule.
Bandwidth Control Rule List
NAMEENABLEDSOURCEWANUPSTREAM BANDWIDTHDOWNSTREAM BANDWIDTHMODEACTION
tp-linkNetwork: LANWAN/LAN150000Kbps50000KbpsShared
+ CreateNewRule

4.6.5 Gateway QoS

■ Bandwidth Control

This page allows you to configure rules to limit various data flows. In this way, you can optimize the network performance by reasonably utilizing the bandwidth.

  1. Select a site from the drop-down list of Organization. Go to Setting > Transmission > Gateway QoS.

2. Click Create New Rule.

Create New Rule

WAN Interface:

Please Select...

TP-LINK Omada SDN Controller - Create New Rule - 1

Status:

TP-LINK Omada SDN Controller - Create New Rule - 2

Enable

UDP Bandwidth Control:

TP-LINK Omada SDN Controller - Create New Rule - 3

Enable

Limited Bandwidth Ratio:

TP-LINK Omada SDN Controller - Create New Rule - 4

TP-LINK Omada SDN Controller - Create New Rule - 5

Outbound TCP ACK Prioritize:

TP-LINK Omada SDN Controller - Create New Rule - 6

Enable

Direction:

Both

TP-LINK Omada SDN Controller - Create New Rule - 7

Inbound Bandwidth:

1000000

Kbps

Outbound Bandwidth :

1000000

Kbps

TP-LINK Omada SDN Controller - Create New Rule - 8

natural_image Abstract circular logo with three colored segments (yellow, blue, cyan) forming a ring (no text or symbols)

Class 1:

25

TP-LINK Omada SDN Controller - Create New Rule - 9

Class 2:

25

TP-LINK Omada SDN Controller - Create New Rule - 10

Class 3:

25

TP-LINK Omada SDN Controller - Create New Rule - 11

Others:

TP-LINK Omada SDN Controller - Create New Rule - 12

TP-LINK Omada SDN Controller - Create New Rule - 13

Create

Cancel

3. Configure the parameters and click Apply.

WAN Interface Select the WAN port. You can configure the QoS rule for a WAN port only when the port is enabled.

Status Enable or disable QoS for the current entry.

UDP Bandwidth Control Check the box to enable UDP bandwidth control.

Limited Bandwidth RatioWhen UDP Bandwidth Control is enabled, specify the bandwidth ratio of UDP at each level of class1/2/3/other.
Outbound TCP ACK PrioritizeCheck the box to prioritize outbound TCP ACK packets. This function ensures that traffic is not slowed down by remote hosts waiting for ACK packets before sending further traffic.
DirectionSpecify the direction of the controlled traffic. “out” means control sending packets. “in” means receiving packets. “both” means both are controlled.
Inbound/Outbound BandwidthEnter the maximum threshold of the inbound/outbound bandwidth.
Class1/Class2/Class3/OthersSpecify the proportion of the maximum bandwidth that Class1, Class2, Class3 and Others can occupy to limit the bandwidth usage of specific classification traffic.

■ Class Rule

This page allows you to add or delete class rules. Rules will be matched from top to bottom according to the rule sequence number. When the traffic matches a rule, it will be assigned to the corresponding class and will not continue to match down.

  1. Select a site from the drop-down list of Organization. Go to Setting > Transmission > Gateway QoS > Class Rule.
  2. Click Create New Class Rule.

Create New Class Rule

Status:

TP-LINK Omada SDN Controller - Create New Class Rule - 1

Enable

IP Version :

TP-LINK Omada SDN Controller - Create New Class Rule - 2

IPv4

TP-LINK Omada SDN Controller - Create New Class Rule - 3

IPv6

Local Address :

Please Select...

TP-LINK Omada SDN Controller - Create New Class Rule - 4

Remote Address :

Please Select...

TP-LINK Omada SDN Controller - Create New Class Rule - 5

DSCP:

Please Select...

TP-LINK Omada SDN Controller - Create New Class Rule - 6

Service Name:

Please Select...

TP-LINK Omada SDN Controller - Create New Class Rule - 7

Qos Class:

Please Select...

TP-LINK Omada SDN Controller - Create New Class Rule - 8

Create

Cancel

3. Configure the parameters and click Apply.

Status Check the box to enable the rule.
IP Version Specify the protocol version: IPv4 or IPv6.
Local AddressMatch the source IP address of the traffic. For IPv4 protocol, you can use the IP Group object configured in the Profiles >Groups module. For the IPv6 protocol, you can use the IPv6 Group object configured in the Profiles >Groups module.
Remote AddressMatch the destination IP address of the traffic. For IPv4 protocol, you can use the IP Group object configured in the Profiles >Groups module. For the IPv6 protocol, you can use the IPv6 Group object configured in the Profiles >Groups module.
DSCP Match the DSCP value of the traffic: Any, IP procedure, AF, or EF.
Service NameMatch the port number of the traffic. Select the service type object defined in the Preference >Service Type module.
QoS Class Select the category of traffic that meets the rule.

■ VoIP Prioritization

This page allows you to configure VoIP prioritization.

  1. Select a site from the drop-down list of Organization. Go to Setting > Transmission > Gateway QoS > VoIP Prioritization.
  2. Enable the first priority for VoIP SIP/RTP and enter the SIP UDP port. Then apply the settings.

VoIP Prioritization Enable the First Priority for VoIP SIP/RTP: SIP UDP Port: Apply Cancel

Enable the First Priority for VoIP SIP/RTP Check the box to enable prioritize VoIP traffic.

SIP UDP Port Enter the UDP port ID of the VoIP traffic.

■ Tag Outbound Traffic

This page allows you to add a DSCP or Precedence value for traffic in different classes.

  1. Select a site from the drop-down list of Organization. Go to Setting > Transmission > Gateway QoS > Tag Outbound Traffic.

  2. Check the box for your desired class and select the DSCP or Precedence value.

Tag Outbound Traffic Class 1: Add DSCP or Precedence value Please Select... Class 2: Add DSCP or Precedence value Please Select... Class 3: Add DSCP or Precedence value Please Select... Others: Add DSCP or Precedence value Please Select... Apply Cancel

Class 1/2/3/Others

Check the box and select the DSCP (Any, IP procedure, AF, or EF) or Precedence value for traffic.

4.6.6 Switch OSPF

Overview

The OSPF protocol (Open Shortest Path First) is a link-state-based dynamic routing protocol that uses Dijkstra's SPF (shortest path first) algorithm to calculate routes within a single AS (autonomous system). OSPF establishes a link state database by advertising the state of network interfaces between routers, and generates shortest path trees. Other OSPF routers in the area use these shortest paths to construct routes.

■ OSPF Process

On this page, you can configure the process of the dynamic routing protocol to divide the local router into multiple virtual networks. The configurations only work for the local router.

  1. Go to Setting > Transmission > Switch OSPF.
  2. In OSPF Process, click Create New OSPF Process.

3. Configure the parameters and apply the settings.

Create New OSPF Process Device Name: Process ID: Router ID: Auto Route Redistribution Static: Enable Connected: Enable Area Search Area Id AREA ID AREA TYPE NETWORK ACTION No entry in the table. + Create New Area Create Cancel

Device Name Specify the name of the OSPF process.

Process ID Enter a number between 1 and 65535 to identify the OSPF process locally on the router.
Router IDSpecify the identity of the router. The selection priority order is manually configured interface, loopback interface, then physical interface.
StaticCheck the box to enable static route. With this option selected, configure the following parameters:Metric: Specify the path cost when importing external routes.Metric Type: Specify the cost calculation type. Type 1 calculates internal cost and external cost. Type 2 calculates external cost only. The default value is type 2.
Connected Check the box to enable direct route.
Area Configure the OSPF areas.

■ OSPF Interface

On this page, you can divide the router into areas and set their OSPF parameters.

  1. Go to Setting > Transmission > Switch OSPF.
  2. In OSPF Interface, click Create New OSPF Interface.

3. Configure the parameters and apply the settings.

Create New OSPF Interface Device Name: Please Select... VLAN ID: Please Select... Cost: 1 (1-65535) Network Type: Broadcast Hello Interval: 10 (1-65535) Authentication Type: None Simple MD5 Create Cancel

Device Name Specify the name of the OSPF interface.

VLAN ID Specify the ID of the VLAN.

Cost Specify the interface overhead.

Network Type Specify the network type of the OSPF interface.

Hello Interval Specify the interval between Hello packets sent on the interface.

Authentication Type Specify the interface area verification method.

None: No authentication.

Simple: Simple authentication mode. The key is transmitted with clear texts. With this option selected, specify the Simple Key for authentication.

MD5: MD5 authentication mode. The key and key ID are transmitted through MD5 encryption. With this option selected, specify the MD5 Key ID and MD5 Key for authentication.

4.6.7 Switch QoS

Overview

■ CoS Basic Settings

QoS (Quality of Service) function is used to optimize network performance. Typically, networks treat all traffic equally on FIFO (First In First Out) delivery basis. When congestion occurs, the switch will drop the later packets no matter what kind of traffic they are. With QoS configured, the switch

forwards traffic according to the priority of the packets. Critical traffic like VoIP and video conference can be preferentially treated.

■ Queue Mapping & Scheduler Profile

Queue Mapping function is used to classify the packets based on the value of 802.1p priority, then map them to different queues. IEEE 802.1p standard defines three bits in 802.1Q tag as PRI filed. The PRI values are called 802.1p priority and used to represent the priority of the layer 2 packets. This function requires packets with VLAN tags.

Scheduler Config function is used to set the scheduler rule for corresponding queue.

Configuration

  1. Go to Setting > Transmission > Switch QoS.
  2. In Queue Mapping & Scheduler Profile, the system provides a default profile. You can also click Create New Profile to create a profile according to site needs.

Search Profile Name Profile NAME SCHEDULER TYPE ACTION Default SP (Strict) Showing 1-1 of 1 records < 1 > 10 / page Go to page: Go + Create New Profile

  1. In CoS Basic Settings, click Create New CoS Rule. Select a switch, configure the parameters and apply the settings.

Create New CoS Rule Device: 90-04-EC-77-10-01 Port LAG Unit 1 PORT BID.1P PRIORITY TRUST MODE LAG 1 0 Untrusted - 2 0 Untrusted - 3 0 Untrusted - 4 0 Untrusted - 5 0 Untrusted - 6 0 Untrusted - 7 0 Untrusted - 8 0 Untrusted - 9 0 Untrusted - 10 0 Untrusted - Shaving 1-10 of 28 records 2 3 > 10/page Go to page Profile Setting Query Mapping & Scheduler Profile: Create Cancel

Port Select one or more ports to configure.
802.1p PrioritySpecify the port-to-802.1p priority mapping for the desired port. The ingress packets are first mapped to 802.1p priority, then to TC queues according to the 802.1p-to-queue mappings.
Trust ModeSelect the Trust mode for the desired port. The switch will process the ingress packets according to the trusted priority mode.
Untrusted: In this mode, the packets will be processed according to the port priority configuration.
Trust 802.1p: In this mode, the packets will be processed according to the 802.1p priority configuration.
Trust DSCP: In this mode, the packets will be processed according to the DSCP priority configuration.
LAG Displays the LAG that the port belongs to.
Queue Mapping & Scheduler ProfileSelect the Queue Mapping & Scheduler Profile to be bound.

4.6.8 VRRP

Overview

VRRP or Virtual Routing Redundancy Protocol is a function on the switch that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. The VRRP router that controls the IP address associated with a virtual router is called the Master and will forward packets sent to this IP address. This will allow any Virtual Router IP address on the LAN to be used as the default first hop router by end hosts.

Configuration

  1. Go to Setting > Transmission > VRRP.

2. Click Create VRRP Rule. Set the VRRP Name and VRID.

VRRP Rules Config VRRP Name: route1 VRID: 3 Device List NAME MAC PRIORITY INTERFACE NETWORK TRACKED INTERFACE REDUCED PRIORITY ACTION 00-0A-EC-77-1C-01 00-0A-EC-77-1C-01 2 1 IPv4 DHCP Mode Showing 1-1 of 1 records < 1 > Virtual IP : IPv4 . . . + + Optional Settings Apply Cancel

VRRP Name Enter a name to identify the rule.

VRID Enter the VRID to create a new VRRP. The VRID ranges from 1 to 255.

Device ListClick Add to select a switch and configure device VRRP. The switch you add will display in the Device List.Device Name: Name of the device.MAC: MAC address of the device.Priority: Priority associated with the VRRP. It ranges from 1 to 254.Interface: Interface ID associated with the VRRP.Network: Intersection of device network (IP/mask).Tracked Interface: Interface to be tracked.Reduced Priority: Priority to reduce if the associated interface is down.
Virtual IPAdd virtual IP addresses associated with the VRRP. Up to 16 virtual IP addresses can be added for every VRRP.

3. Expand and configure Optional Settings if needed.

Optional Settings Advertise Timer: 1 (1-255) Preempt Mode: Enable Delay Time: 0 (0-255) Authentication Type: None Simple MD5

Advertise Timer Enter the advertise timer associated with the VRRP. It ranges from 1 to 255.
Preempt Mode Select Enable or disable the preempt Mode from the pull-down list. If you selectEnable, a backup router will preempt the master router if it has a priority greater than the master virtual router's priority. The Preempt Mode is enabled by default.
Delay Time Enter the delay time associated with the VRRP. It ranges from 0 to 255.
AuthenticationSelect the type of Authentication for the Virtual Router from the pull-down list. The default is None.None: No authentication will be performed.Simple: Authentication will be performed using a text password. If you select this mode, enter the Key.MD5: Authentication of MD5 will be performed using a text password. If you select this mode, enter the Key.

4. Apply the settings.

4.7 Configure VPN

VPN (Virtual Private Network) provides a means for secure communication between remote computers across a public wide area network (WAN), such as the internet. The gateways supports various types of VPN.

4.7.1 VPN

Overview

VPN (Virtual Private Network) gives remote LANs or users secure access to LAN resources over a public network such as the internet. Virtual indicates the VPN connection is based on the logical end-to-end connection instead of the physical end-to-end connection. Private indicates users can establish the VPN connection according to their requirements and only specific users are allowed to use the VPN connection.

The core of VPN connection is to realize tunnel communication, which fulfills the task of data encapsulation, data transmission and data decompression via the tunneling protocol. The gateway supports common tunneling protocols that a VPN uses to keep the data secure:

IPsec

IPsec (IP Security) can provide security services such as data confidentiality, data integrity and data authentication at the IP layer. IPsec uses IKE (Internet Key Exchange) to handle negotiation of protocols and algorithms based on the user-specified policy, and to generate the encryption and authentication keys to be used by IPsec. IPsec can be used to protect one or more paths between a pair of hosts, between a pair of security gateways, or between a security gateway and a host.

■ PPTP

PPTP (Point-to-Point Tunneling Protocol) is a network protocol that enables the secure transfer of data from a remote client to a private enterprise server by creating a VPN across TCP/IP-based data networks. PPTP uses the username and password to validate users.

L2TP

L2TP (Layer 2 Tunneling Protocol) provides a way for a dialup user to make a virtual Point-to-Point Protocol (PPP) connection to an L2TP network server (LNS), which can be a security gateway. L2TP sends PPP frames through a tunnel between an L2TP access concentrator (LAC) and the LNS. Because of the lack of confidentiality inherent in the L2TP protocol, it is often implemented along with IPsec. L2TP uses the username and password to validate users.

■ OpenVPN

OpenVPN uses OpenSSL for encryption of UDP and TCP for traffic transmission. OpenVPN uses a client-server connection to provide secure communications between a server and a remote client over the internet. One of the most important steps in setting up OpenVPN is obtaining a certificate which is used for authentication. The SDN controller supports generating the certificate which can be downloaded as a file on your computer. With the certificate imported, the remote clients are checked out by the certificate and granted access to the LAN resources.

There are many variations of virtual private networks, with the majority based on two main models:

■ Site-to-Site VPN

A Site-to-Site VPN creates a connection between two networks at different geographic locations. Typically, headquarters set up Site-to-Site VPN with the subsidiary to provide the branch office with access to the headquarters' network.

TP-LINK Omada SDN Controller - ■ Site-to-Site VPN - 1

flowchart
graph LR
    A["Site-to-Site VPN"] --> B["Internet"]
    B --> C["Building 1"]
    B --> D["Building 2"]

Branch Office Headquarters

The gateway supports two types of Site-to-Site VPNs:

- Auto IPsec

The controller automatically creates an IPsec VPN tunnel between two sites on the same controller. The VPN connection is bidirectional. That is, creating an Auto IPsec VPN from site A to site B also provides connectivity from site B to site A, and nothing is needed to be configured on site B.

- Manual IPsec

You create an IPsec VPN tunnel between two peer routers over internet manually, from a local router to a remote router that supports IPsec. The gateway on this site is the local peer router.

■ Client-to-Site VPN

A Client-to-Site VPN creates a connection to the LAN from a remote host. It is useful for teleworkers and business travelers to access their central LAN from a remote location without compromising privacy and security.

The first step to build a Client-to-Site VPN connection is to determine the role of the gateways and which VPN tunneling protocol to use:

- VPN Server

The gateway on the central LAN works as a VPN server to provide a remote host with access to the local network. The gateway which functions as a VPN server can use L2TP, PPTP, IPsec, or OpenVPN as the tunneling protocol.

- VPN Client

Either the remote user's gateway or the remote user's laptop or PC works as the VPN client.

When the remote user's gateway works as the VPN client, the gateway helps create VPN tunnels between its connected hosts and the VPN server. The gateway which functions as a VPN client can use L2TP, PPTP, or OpenVPN as the tunneling protocol.

TP-LINK Omada SDN Controller - ■ Client-to-Site VPN - 1

flowchart
graph LR
    A["Remote User"] --> B["Gateway (Client) Gateway (Server)"]
    B --> C["Internet"]
    C --> D["Headquarters"]

When the remote user's laptop or PC works as the VPN client, the laptop or PC uses a VPN client software program to create VPN tunnels between itself and the VPN server. The VPN client software program can use L2TP, PPTP, IPsec, or OpenVPN as the tunneling protocol.

TP-LINK Omada SDN Controller - ■ Client-to-Site VPN - 2

flowchart
graph LR
    A["Remote User (Client)"] --> B["Gateway Gateway (Server)"]
    B --> C["Internet"]
    C --> D["Headquarters"]

TP-LINK Omada SDN Controller - ■ Client-to-Site VPN - 3

Note:

In scenario 1, you need to configure VPN client and VPN server separately on the gateways, while remote hosts can access the local networks without running VPN client software.

In scenario 2, you need to configure VPN server on the gateway, and then configure the VPN client software program on the remote user's laptop or PC, while the remote user's gateway doesn't need any VPN configuration.

Here is the infographic to provide a quick overview of VPN solutions.

TP-LINK Omada SDN Controller - Note: - 1

Create a VPN Policy

TP-LINK Omada SDN Controller - Create a VPN Policy - 1

Select the purpose of the VPN

Site-to-Site VPN

TP-LINK Omada SDN Controller - Site-to-Site VPN - 1

Internet

TP-LINK Omada SDN Controller - Site-to-Site VPN - 2

Branch Office Headquarters

Auto IPsec VPN

The controller automatically creates an IPsec VPN tunnel between two sites on the same controller.

Manual IPsec VPN

You manually create an IPsec VPN tunnel between two peer routers over internet, from a local router to a remote router that supports IPsec.

Client-to-Site VPN

TP-LINK Omada SDN Controller - Client-to-Site VPN - 1

TP-LINK Omada SDN Controller - Client-to-Site VPN - 2

Internet

TP-LINK Omada SDN Controller - Client-to-Site VPN - 3

TP-LINK Omada SDN Controller - Client-to-Site VPN - 4

Remote User

Headquarters

TP-LINK Omada SDN Controller - Client-to-Site VPN - 5

TP-LINK Omada SDN Controller - Client-to-Site VPN - 6

TP-LINK Omada SDN Controller - Client-to-Site VPN - 7

TP-LINK Omada SDN Controller - Client-to-Site VPN - 8

TP-LINK Omada SDN Controller - Client-to-Site VPN - 9

Remote User (Client)

Gateway (Server)

Headquarters

TP-LINK Omada SDN Controller - Client-to-Site VPN - 10

Select the role of the gateway and VPN tunneling protocol

VPN Server

L2TP

VPN Client

L2TP

PPTP

PPTP

IPsec

IPsec (Only for VPN client software)

OpenVPN

OpenVPN

Configuration

To complete the VPN configuration, follow these steps:

1) Create a new VPN policy and select the purpose of the VPN according to your needs. Select Site-to-Site if you want the network connected to another. Select Client-to-Site if you want some hosts connected to the network.
2) Select the VPN tunneling protocol and configure the VPN policy based on the protocol.

■ Configuring Site-to-Site VPN

The gateway supports two types of Site-to-Site VPNs: Auto IPsec and Manual IPsec.

- Configuring Auto IPsec VPN

  1. Select a site from the drop-down list of Organization. Go to Settings > VPN. Click to load the following page.

Create New VPN Policy Name: Status: Enable Purpose: Site-to-Site VPN Client-to-Site VPN VPN Type: Auto IPsec Manual IPsec Remote Site: Please Select... Create Cancel

  1. Enter a name to identify the VPN policy and select the purpose as Site-to-Site VPN. Refer to the following table to configure the required parameters and click Create.

Name Enter a name to identify the VPN policy.

Status Click the checkbox to enable the VPN policy.

Purpose Select the purpose for the VPN as Site-to-Site VPN.

VPN TypeSelect the VPN type as Auto IPsec. With Auto IPsec, the controller automatically creates an IPsec VPN tunnel between two sites on the same controller. The VPN connection is bidirectional. That is, creating an Auto IPsec VPN from site A to site B also provides connectivity from site B to site A, and nothing is needed to be configured on site B.

Remote Site Select the site on the other end of the Auto IPsec VPN tunnel. Make sure that the selected remote site has an online gateway within the same controller.

- Configuring Manual IPsec VPN

  1. Select a site from the drop-down list of Organization. Go to Settings >VPN. Click to load the following page.

Create New VPN Policy

Name:

TP-LINK Omada SDN Controller - Create New VPN Policy - 1

Status:

TP-LINK Omada SDN Controller - Create New VPN Policy - 2

Enable

Purpose:

TP-LINK Omada SDN Controller - Create New VPN Policy - 3

Site-to-Site VPN

TP-LINK Omada SDN Controller - Create New VPN Policy - 4

Client-to-Site VPN

VPN Type:

TP-LINK Omada SDN Controller - Create New VPN Policy - 5

Auto IPsec

TP-LINK Omada SDN Controller - Create New VPN Policy - 6

Manual IPsec

Remote Gateway:

TP-LINK Omada SDN Controller - Create New VPN Policy - 7

Remote Subnets:

TP-LINK Omada SDN Controller - Create New VPN Policy - 8

TP-LINK Omada SDN Controller - Create New VPN Policy - 9

Add Subnet

Local Network Type:

TP-LINK Omada SDN Controller - Add Subnet - 1

Network

TP-LINK Omada SDN Controller - Add Subnet - 2

Custom IP

Local Networks:

All

TP-LINK Omada SDN Controller - Add Subnet - 3

TP-LINK Omada SDN Controller - Add Subnet - 4

Pre-Shared Key:

Please Select...

WAN:

TP-LINK Omada SDN Controller - Add Subnet - 5

TP-LINK Omada SDN Controller - Add Subnet - 6

Advanced Settings

Create

Cancel

  1. Enter a name to identify the VPN policy and select the purpose as Site-to-Site VPN. Refer to the following table to configure the basic parameters and click Create.

Name Enter a name to identify the VPN policy.

Status Click the checkbox to enable the VPN policy.

Purpose Select the purpose for the VPN as Site-to-Site VPN.
VPN Type Select the VPN type as Manual IPsec.
Remote Gateway Enter an IP address or a domain name as the gateway on the remote peer of the VPN tunnel.
Remote Subnets Enter the IP address range of LAN on the remote peer of the VPN tunnel. Remote subnets should not be in the same network segment as the local LAN.
Local Network TypeSpecify whether to apply the VPN policy to specific local networks or IP addresses.
Network: Specify the local networks of the VPN tunnel. The VPN policy will be only applied to the selected local networks.
Custom IP: Specify the IP addresses of the VPN tunnel. The VPN policy will be only applied to the specified IP addresses.
Pre-Shared KeyEnter the pre-shared key(PSK). Both peer gateways must use the same pre-shared secret key for authentication.
A pre-shared key is a string of characters that is used as an authentication key. Both peer gateways create a hash value based on the same pre-shared key and other information. The hash values are then exchanged and verified to authenticate the other party.
The pre-shared keys should be long and random for security. Short or predictable pre-shared keys can be easily broken in brute-force attacks. To maintain a high level of security, administrators are recommended to update the pre-shared key periodically.

WAN Select the WAN port on which the IPsec VPN tunnel is established.

3. Click Advanced Settings to load the following page.

Advanced Settings Phase-1 Settings Key Exchange Version: IKEv1 i IKEv2 Proposal: SHA1 - AES256 - DH2 Exchange Mode: Main Mode Aggressive Mode Negotiation Mode: Initiator Mode Responder Mode Local ID Type: IP Address Name Remote ID Type: IP Address Name SA Lifetime: 28800 seconds (60-604800) DPD: Enable DPD Interval: 10 seconds (1-300) Phase-2 Settings Encapsulation Mode: Tunnel Mode Transport Mode Proposal: ESP - SHA1 - AES256 PFS: None SA Lifetime: 28800 seconds (120-604800) Create Cancel

Advanced settings include Phase-1 settings and Phase-2 settings. Phase-1 is used to set up a secure encrypted channel which the two peers can negotiate Phase-2, and then establish the IKE Security Associations (IKE SA). Phase-2 is used to negotiate about a set of parameters that

define what traffic can go through the VPN, and how to encrypt and authenticate the traffic, then establish the IPsec Security Associations (IPsec SA).

Refer to the following table to complete the configurations according to your actual needs and click Create.

For Phase-1 Settings:

Phase-1 SettingsThe IKE version you select determines the available Phase-1 settings and defines the negotiation process. Both VPN gateways must be configured to use the same IKE version and Phase-1 settings.
Internet Key Exchange VersionSelect the version of Internet Key Exchange (IKE) protocol which is used to set up security associations for IPsec. Both IKEv1 and IKEv2 are supported with gateways, but IKEv1 is available only when the VPN policy is applied to a single Remote Subnet and a single Local Network.Note that both peer gateways must be configured to use the same IKE version.
Proposal Specify the proposal for IKE negotiation phase-1. An IKE proposal lists the encryption algorithm, authentication algorithm and Diffie-Hellman (DH) groups to be negotiated with the remote IPsec peer.Authentication algorithms verify the data integrity and authenticity of a message.Encryption algorithms protect the data from being read by a third-party.Diffie-Hellman (DH) groups determine the strength of the key used in the key exchange process.Note that both peer gateways must be configured to use the same Proposal.
Exchange Mode Specify the IKE Exchange Mode when IKEv1 is selected.Main Mode: This mode provides identity protection and exchanges more information, which applies to scenarios with higher requirements for identity protection.Aggressive Mode: This mode establishes a faster connection but with lower security, which applies to scenarios with lower requirements for identity protection.
Negotiation Mode Specify the IKE Negotiation Mode as Initiator Mode or Responder Mode.Initiator Mode: This mode means that the local device initiates a connection to the peer.Responder Mode: This mode means that the local device waits for the connection request initiated by the peer.
Local ID TypeSpecify the type of Local ID which indicates the authentication identifier sent to the peer for IKE negotiation.
IP Address: Select IP Address to use the IP address for authentication.
Name: Select Name, and then enter the name in the Local ID field to use the name as the ID for authentication.
Note that the type and value of Local ID should be the same as Remote ID given for the remote peer of the VPN tunnel.
Local ID When the Local ID Type is configured as Name, enter a name for the local device as the ID in IKE negotiation. The name should be in the format of FQDN (Fully Qualified Domain Name).
Remote ID Type Specify the type of Remote ID which indicates the authentication identifier received from the peer for IKE negotiation.
Remote ID When the Remote ID Type is configured as Name, enter a name of the remote peer as the ID in IKE negotiation. The name should be in the format of FQDN (Fully Qualified Domain Name).
SA Lifetime Specify ISAKMP SA (Security Association) Lifetime in IKE negotiation. If the SA lifetime expired, the related ISAKMP SA will be deleted.
DPD Check the box to enable DPD (Dead Peer Detect) function. If enabled, the IKE endpoint can send a DPD request to the peer to inspect whether the IKE peer is alive.
DPD Interval Specify the interval between sending DPD requests with DPD enabled. If the IKE endpoint receives a response from the peer during this interval, it considers the peer alive. If the IKE endpoint does not receive a response during the interval, it considers the peer dead and deletes the SA.
For Phase-2 Settings:
Phase-2 SettingsThe purpose of Phase 2 negotiations is to establish the Phase-2 SA (also called the IPsec SA). The IPsec SA is a set of traffic specifications that tell the device what traffic to send over the VPN, and how to encrypt and authenticate that traffic.
Encapsulation Mode Specify the Encapsulation Mode as Tunnel Mode or Transport Mode. When both ends of the tunnel are hosts, either mode can be chosen. When at least one of the endpoints of a tunnel is a security gateway, such as a router or firewall, Tunnel Mode is recommended to ensure safety.

Proposal Specify the proposal for IKE negotiation phase-2. An IPsec proposal lists the encryption algorithm, authentication algorithm and protocol to be negotiated with the remote IPsec peer.

Note that both peer gateways must be configured to use the same Proposal.

PFS Select the DH group to enable PFS (Perfect Forward Security) for IKE mode, then the key generated in phase-2 will be irrelevant with the key in phase-1, which enhance the network security. With None selected, it means PFS is disabled and the key in phase-2 will be generated based on the key in phase-1.

SA Lifetime Specify IPsec SA (Security Association) Lifetime in IKE negotiation. If the SA lifetime expired, the related IPsec SA will be deleted.

■ Configuring Client-to-Site VPN

The gateway supports seven types of client-to-Site VPNs depending on the role of your gateway and the protocol that you used:

Configuring the gateway as a VPN server using L2TP Configuring the gateway as a VPN server using PPTP Configuring the gateway as a VPN server using IPsec Configuring the gateway as a VPN server using OpenVPN Configuring the gateway as a VPN client using L2TP Configuring the gateway as a VPN client using PPTP Configuring the gateway as a VPN client using OpenVPN

- Configuring the gateway as a VPN server using L2TP

  1. Select a site from the drop-down list of Organization. Go to Settings > VPN. Click

TP-LINK Omada SDN Controller - ■ Configuring Client-to-Site VPN - 1

Create New VPN Policy

to load the following page.

Create New VPN Policy Name: Status: Enable Purpose: Site-to-Site VPN Client-to-Site VPN VPN Type: VPN Server - L2TP IPsec Encryption: Encrypted Unencrypted Auto Authentication Mode: Local LDAP Local Network Type: Network Custom IP Local Networks: All Pre-Shared Key: WAN: Please Select... IP Pool Type: IP Address/Mask IP Address Range IP Pool: / Primary DNS Server: . . . Secondary DNS Server: . . . (Optional) Create Cancel

  1. Enter a name to identify the VPN policy and select the purpose as Client-to-Site VPN. Refer to the following table to configure the required parameters and click Create.

Name Enter a name to identify the VPN policy.

Status Click the checkbox to enable the VPN policy.

Purpose Select the purpose for the VPN as Client-to-Site VPN.

VPN Type Select the VPN type as VPN Server - L2TP.

IPsec Encryption Specify whether to enable the encryption for the tunnel.

Encrypted: Select Encrypted to encrypt the L2TP tunnel by IPsec (L2TP over IPsec). With Encrypted selected, enter the Pre-shared Key for IKE authentication. VPN server and VPN client must use the same pre-shared secret key for authentication.

Unencrypted: With Unencrypted selected, the L2TP tunnel will not be encrypted by IPsec.

Auto: With Auto selected, the L2TP server will determine whether to encrypt the tunnel according to the client's encryption settings. And enter the Pre-shared Key for IKE authentication. VPN server and VPN client must use the same pre-shared secret key for authentication.

Authentication Mode Select the authentication mode: Local or LDAP.

Local Network Type

Specify whether to apply the VPN policy to specific local networks or IP addresses.

Network: Specify the local networks of the VPN tunnel. The VPN policy will be only applied to the selected local networks.

Custom IP: Specify the IP addresses of the VPN tunnel. The VPN policy will be only applied to the specified IP addresses.

Pre-shared Key Enter the pre-shared secret key when IPsec Encryption is selected as Encrypted and Auto. Both peer routers must use the same pre-shared secret key for authentication.

WAN Select the WAN port on which the L2TP VPN tunnel is established. Each WAN port supports only one L2TP VPN tunnel when the gateway works as a L2TP server.

IP Pool Type Specify the format of the IP pool.

IP Pool If you selected IP Address/Mask type, enter the IP address and subnet mask to decide the range of the VPN IP pool. If you select IP Address Range type, enter the start and end IP addresses of the VPN IP pool.

Primary DNS Server Enter the IP address of the primary DNS server provided by your ISP.

Secondary DNS Server (Optional) Enter the IP address of the secondary DNS server, which provides redundancy in case the primary DNS server goes down.

  1. Add the VPN users account to validate remote hosts. To create VPN users, refer to 4.7.2 VPN User.

- Configuring the gateway as a VPN server using PPTP

  1. Select a site from the drop-down list of Organization. Go to Settings > VPN. Click

TP-LINK Omada SDN Controller - ■ Configuring Client-to-Site VPN - 3

Create New VPN Policy

to load the following page.

Create New VPN Policy Name: Status: Enable Purpose: Site-to-Site VPN Client-to-Site VPN VPN Type: VPN Server - PPTP MPPE Encryption: Encrypted Unencrypted Auto Authentication Mode: Local LDAP Local Network Type: Network Custom IP Local Networks: All WAN: Please Select... IP Pool Type: IP Address/Mask IP Address Range IP Pool: . . . / Primary DNS Server: . . . Secondary DNS Server: . . . (Optional) Create Cancel

  1. Enter a name to identify the VPN policy and select the purpose as Client-to-Site VPN. Refer to the following table to configure the required parameters and click Create.

Name Enter a name to identify the VPN policy.

Status Click the checkbox to enable the VPN policy.

Purpose Select the purpose for the VPN as Client-to-Site VPN.

VPN Type Select the VPN type as VPN Server - PPTP.

MPPE Encryption Specify whether to enable MPPE (Microsoft Point-to-Point Encryption) for the tunnel.

Encrypted: With Encrypted selected, the PPTP tunnel will be encrypted by MPPE.

Unencrypted: With Unencrypted selected, the PPTP tunnel will be not encrypted by MPPE.

Authentication Mode Select the authentication mode: Local or LDAP.

Local Network TypeSpecify whether to apply the VPN policy to specific local networks or IP addresses.
Network: Specify the local networks of the VPN tunnel. The VPN policy will be only applied to the selected local networks.
Custom IP: Specify the IP addresses of the VPN tunnel. The VPN policy will be only applied to the specified IP addresses.
WAN Select the WAN port on which the PPTP VPN tunnel is established. Each WAN port supports only one PPTP VPN tunnel when the gateway works as a PPTP server.
IP Pool Type Specify the format of the IP pool.
IP Pool If you selected IP Address/Mask type, enter the IP address and subnet mask to decide the range of the VPN IP pool. If you select IP Address Range type, enter the start and end IP addresses of the VPN IP pool.
Primary DNS Server Enter the IP address of the primary DNS server provided by your ISP.
Secondary DNS Server(Optional) Enter the IP address of the secondary DNS server, which provides redundancy in case the primary DNS server goes down.
  1. Add the VPN users account to validate remote hosts. To create VPN users, refer to 4.7.2 VPN User.

- Configuring the gateway as a VPN server using IPsec

  1. Select a site from the drop-down list of Organization. Go to Settings >VPN. Click + Create New VPN Policy to load the following page.

Create New VPN Policy Name: Status: Enable Purpose: Site-to-Site VPN Client-to-Site VPN VPN Type: VPN Server - IPsec Remote Host: Local Network Type: Network Custom IP Local Networks: All Pre-Shared Key: WAN: Please Select... IP Pool: . . . / Primary DNS Server: . . . Secondary DNS Server: . . . (Optional) + Advanced Settings Create Cancel

  1. Enter a name to identify the VPN policy and select the purpose as Client-to-Site VPN. Refer to the following table to configure the basic parameters and click Create.
Name Enter a name to identify the VPN policy.
Status Click the checkbox to enable the VPN policy.
Purpose Select the purpose for the VPN as Client-to-Site VPN.
VPN Type Select the VPN type as VPN Server - IPsec.
Remote Host Enter an IP address or a domain name of the host on the remote peer of the VPN tunnel. 0.0.0.0 represents any IP address.
Local Network TypeSpecify whether to apply the VPN policy to specific local networks or IP addresses.
Network: Specify the local networks of the VPN tunnel. The VPN policy will be only applied to the selected local networks.
Custom IP: Specify the IP addresses of the VPN tunnel. The VPN policy will be only applied to the specified IP addresses.
Pre-Shared KeyEnter the pre-shared key(PSK). Both peer gateways must use the same pre-shared secret key for authentication.
A pre-shared key is a string of characters that is used as an authentication key. Both VPN peers create a hash value based on the same pre-shared key and other information. The hash values are then exchanged and verified to authenticate the other party.
The pre-shared keys should be long and random for security. Short or predictable pre-shared keys can be easily broken in brute-force attacks. To maintain a high level of security, administrators are recommended to update the pre-shared key periodically.
WAN Select the WAN port on which the IPsec VPN tunnel is established.
IP Pool Enter the IP address and subnet mask to decide the range of the VPN IP pool. The VPN server will assign IP address to the remote host when the tunnel is established. You can specify any reasonable IP address that will not cause overlap with the IP address of the LAN on the local peer router.
Primary DNS Server Enter the IP address of the primary DNS server provided by your ISP.
Secondary DNS Server(Optional) Enter the IP address of the secondary DNS server, which provides redundancy in case the primary DNS server goes down.

3. Click Advanced Settings to load the following page.

Advanced Settings Phase-1 Settings Key Exchange Version: IKEv1 i IKEv2 Proposal: SHA1 - AES256 - DH2 Exchange Mode: Main Mode Aggressive Mode Negotiation Mode: Initiator Mode Responder Mode Local ID Type: IP Address Name Remote ID Type: IP Address Name SA Lifetime: 28800 seconds (60-604800) DPD: Enable DPD Interval: 10 seconds (1-300) Phase-2 Settings Encapsulation Mode: Tunnel Mode Transport Mode Proposal: ESP - SHA1 - AES256 PFS: None SA Lifetime: 28800 seconds (120-604800) Create Cancel

Advanced settings include Phase-1 settings and Phase-2 settings. Phase-1 is used to set up a secure encrypted channel which the two peers can negotiate Phase-2, and then establish the IKE Security Associations (IKE SA). Phase-2 is used to negotiate about a set of parameters that

define what traffic can go through the VPN, and how to encrypt and authenticate the traffic, then establish the IPsec Security Associations (IPsec SA).

Refer to the following table to complete the configurations according to your actual needs and click Create.

For Phase-1 Settings:

Phase-1 SettingsThe IKE version you select determines the available Phase-1 settings and defines the negotiation process. Both VPN gateways must be configured to use the same IKE version and Phase-1 settings.
Internet Key Exchange VersionSelect the version of Internet Key Exchange (IKE) protocol which is used to set up security associations for IPsec. Both IKEv1 and IKEv2 are supported with gateways, but IKEv1 is available only when the VPN policy is applied to a single Remote Subnet and a single Local Network.Note that both VPN peers must be configured to use the same IKE version.
Proposal Specify the proposal for IKE negotiation phase-1. An IKE proposal lists the encryption algorithm, authentication algorithm and Diffie-Hellman (DH) groups to be negotiated with the remote IPsec peer.Authentication algorithms verify the data integrity and authenticity of a message.Encryption algorithms protect the data from being read by a third-party.Diffie-Hellman (DH) groups determine the strength of the key used in the key exchange process.Note that both VPN peers must be configured to use the same Proposal.
Exchange Mode Specify the IKE Exchange Mode when IKEv1 is selected.Main Mode: This mode provides identity protection and exchanges more information, which applies to scenarios with higher requirements for identity protection.Aggressive Mode: This mode establishes a faster connection but with lower security, which applies to scenarios with lower requirements for identity protection.
Negotiation Mode Specify the IKE Negotiation Mode as Initiator Mode or Responder Mode.Initiator Mode: This mode means that the local device initiates a connection to the peer.Responder Mode: This mode means that the local device waits for the connection request initiated by the peer.
Local ID TypeSpecify the type of Local ID which indicates the authentication identifier sent to the peer for IKE negotiation.
IP Address: Select IP Address to use the IP address for authentication.
Name: Select Name, and then enter the name in the Local ID field to use the name as the ID for authentication.
Note that the type and value of Local ID should be the same as Remote ID given for the remote peer of the VPN tunnel.
Local ID When the Local ID Type is configured as Name, enter a name for the local device as the ID in IKE negotiation. The name should be in the format of FQDN (Fully Qualified Domain Name).
Remote ID Type Specify the type of Remote ID which indicates the authentication identifier received from the peer for IKE negotiation.
Remote ID When the Remote ID Type is configured as Name, enter a name of the remote peer as the ID in IKE negotiation. The name should be in the format of FQDN (Fully Qualified Domain Name).
SA Lifetime Specify ISAKMP SA (Security Association) Lifetime in IKE negotiation. If the SA lifetime expired, the related ISAKMP SA will be deleted.
DPD Check the box to enable DPD (Dead Peer Detect) function. If enabled, the IKE endpoint can send a DPD request to the peer to inspect whether the IKE peer is alive.
DPD Interval Specify the interval between sending DPD requests with DPD enabled. If the IKE endpoint receives a response from the peer during this interval, it considers the peer alive. If the IKE endpoint does not receive a response during the interval, it considers the peer dead and deletes the SA.
For Phase-2 Settings:
Phase-2 SettingsThe purpose of Phase 2 negotiations is to establish the Phase-2 SA (also called the IPsec SA). The IPsec SA is a set of traffic specifications that tell the device what traffic to send over the VPN, and how to encrypt and authenticate that traffic.
Encapsulation Mode Specify the Encapsulation Mode as Tunnel Mode or Transport Mode. When both ends of the tunnel are hosts, either mode can be chosen. When at least one of the endpoints of a tunnel is a security gateway, such as a router or firewall, Tunnel Mode is recommended to ensure safety.

Proposal Specify the proposal for IKE negotiation phase-2. An IPsec proposal lists the encryption algorithm, authentication algorithm and protocol to be negotiated with the remote IPsec peer.

Note that both peer gateways must be configured to use the same Proposal.

PFS Select the DH group to enable PFS (Perfect Forward Security) for IKE mode, then the key generated in phase-2 will be irrelevant with the key in phase-1, which enhance the network security. With None selected, it means PFS is disabled and the key in phase-2 will be generated based on the key in phase-1.

SA Lifetime Specify IPsec SA (Security Association) Lifetime in IKE negotiation. If the SA lifetime expired, the related IPsec SA will be deleted.

- Configuring the gateway as a VPN server using OpenVPN

  1. Select a site from the drop-down list of Organization. Go to Settings >VPN. Click + Create New VPN Policy to load the following page.

Create New VPN Policy Name: Status: Enable Purpose: Site-to-Site VPN Client-to-Site VPN VPN Type: VPN Server - OpenVPN Account Password: Enable Tunnel Mode: Split Full Protocol: TCP UDP Service Port: 1194 (1-05535) Authentication Mode: Local LDAP Local Network Type: Network Custom IP Local Networks: All WAN: Please Select... IP Pool: . . . / Primary DNS Server: . . . Secondary DNS Server: . . . (Optional) Create Cancel

  1. Enter a name to identify the VPN policy and select the purpose as Client-to-Site VPN. Refer to the following table to configure the required parameters and click Create.

Name Enter a name to identify the VPN policy.

Status Click the checkbox to enable the VPN policy.

Purpose Select the purpose for the VPN as Client-to-Site VPN.
VPN Type Select the VPN type as VPN Server - OpenVPN.
Account Password Specify whether VPN clients need to enter a user account to access the VPN tunnel. When enabled, you need to create accounts on the VPN User page.
Tunnel Mode Select the tunnel mode: Split or Full.Full tunneling uses the VPN for all your traffic, whereas split tunneling sends part of your traffic through a VPN and part of it through the open network. Full tunneling is more secure than split tunneling.
Protocol Select the communication protocol for the gateway which works as an OpenVPN Server. Two communication protocols are available: TCP and UDP.
Service Port Enter a VPN service port to which a VPN device connects.
Authentication ModeSelect the authentication mode: Local or LDAP. LDAP is used for SSO (single sign-on), which enables users to use the same password in multiple services.
Local Network TypeSpecify whether to apply the VPN policy to specific local networks or IP addresses.Network: Specify the local networks of the VPN tunnel. The VPN policy will be only applied to the selected local networks.Custom IP: Specify the IP addresses of the VPN tunnel. The VPN policy will be only applied to the specified IP addresses.
WAN Select the WAN port on which the VPN tunnel is established. Each WAN port supports only one OpenVPN tunnel when the gateway works as a OpenVPN server.
IP Pool Enter the IP address and subnet mask to decide the range of the VPN IP pool.The VPN server will assign IP address to the remote host when the tunnel is established. You can specify any reasonable IP address that will not cause overlap with the IP address of the LAN on the local peer router.
Primary DNS Server Enter the IP address of the primary DNS server provided by your ISP.
Secondary DNS Server(Optional) Enter the IP address of the secondary DNS server, which provides redundancy in case the primary DNS server goes down.
  1. After clicking Create to save the VPN policy, go to VPN Policy List and click in the Action column to export the OpenVPN file that ends in .ovpn which is to be used by the remote client. The exported OpenVPN file contains the certificate and configuration information.

NAME ENABLED PURPOSE VPN TYPE INTERFACE WAN ACTION OpenVPN ● Client-to-Site VPN OpenVPN(Server) LAN WAN ✓ ✓ ✓ Shewing 1-2 of 2 records < 1 > 10 /page Go To page: GO + Create New VPN Policy

- Configuring the gateway as a VPN client using L2TP

  1. Select a site from the drop-down list of Organization. Go to Settings > VPN. Click

+ Create New VPN Policy to load the following page.

Create New VPN Policy Name: Status: Enable Purpose: Site-to-Site VPN Client-to-Site VPN VPN Type: VPN Client - L2TP Working Mode: NAT Routing Username: Password: IPsec Encryption: Encrypted Unencrypted Auto Remote Server: Remote Subnets: . . . / Add Subnet Local Network Type: Network Custom IP Local Networks: All i Pre-Shared Key: WAN: Please Select... Create Cancel

  1. Enter a name to identify the VPN policy and select the purpose as Client-to-Site VPN. Refer to the following table to configure the required parameters and click Create.
Name Enter a name to identify the VPN policy.
Status Click the checkbox to enable the VPN policy.
Purpose Select the purpose for the VPN as Client-to-Site VPN.
VPN Type Select the VPN type as VPN Client - L2TP.
Working Mode Specify the Working Mode as NAT or Routing.
NAT: With NAT (Network Address Translation) mode selected, the L2TP client uses the assigned IP address as its source addresses of original IP header when forwarding L2TP packets.
Routing: With Routing selected, the L2TP client uses its own IP address as its source addresses of original IP header when forwarding L2TP packets.
Username Enter the username used for the VPN tunnel. This username should be the same as that of the L2TP server.
Password Enter the password of user. This password should be the same as that of the L2TP server.
IPsec Encryption Specify whether to enable the encryption for the tunnel.
Encrypted: Select Encrypted to encrypt the L2TP tunnel by IPsec (L2TP over IPsec). With Encrypted selected, enter the Pre-shared Key for IKE authentication. VPN server and VPN client must use the same pre-shared secret key for authentication.
Unencrypted: With Unencrypted selected, the L2TP tunnel will be not encrypted by IPsec.
Remote Server Enter the IP address or domain name of the L2TP server.
Remote SubnetsEnter the IP address and subnet mask to specify the remote network. It's always the IP address range of LAN on the remote peer of the VPN tunnel.
Local Network TypeSpecify whether to apply the VPN policy to specific local networks or IP addresses.
Network: Specify the local networks of the VPN tunnel. The VPN policy will be only applied to the selected local networks.
Custom IP: Specify the IP addresses of the VPN tunnel. The VPN policy will be only applied to the specified IP addresses.
Pre-shared KeyEnter the pre-shared secret key when the L2TP tunnel is encrypted by IPsec. Both peer gateways must use the same pre-shared secret key for authentication.
WAN Select the WAN port on which the VPN tunnel is established.

- Configuring the gateway as a VPN client using PPTP

  1. Select a site from the drop-down list of Organization. Go to Settings > VPN. Click

+ Create New VPN Policy

to load the following page.

Create New VPN Policy Name: Status: Enable Purpose: Site-to-Site VPN Client-to-Site VPN VPN Type: VPN Client - PPTP Working Mode: NAT Routing Username: Password: MPPE Encryption: Encrypted Unencrypted Auto Remote Server: Remote Subnets: . . . / Add Subnet Local Network Type: Network Custom IP Local Networks: All WAN: Please Select... Create Cancel

  1. Enter a name to identify the VPN policy and select the purpose as Client-to-Site VPN. Refer to the following table to configure the required parameters and click Create.

Name Enter a name to identify the VPN policy.

Status Click the checkbox to enable the VPN policy.

Purpose Select the purpose for the VPN as Client-to-Site VPN.

VPN Type Select the VPN type as VPN Client - PPTP.

Working Mode Specify the Working Mode as NAT or Routing.
NAT: With NAT (Network Address Translation) mode selected, the PPTP client uses the assigned IP address as its source addresses of original IP header when forwarding PPTP packets.
Routing: With Routing selected, the PPTP client uses its own IP address as its source addresses of original IP header when forwarding PPTP packets.
Username Enter the username used for the VPN tunnel. This username should be the same as that of the PPTP server.
Password Enter the password of user. This password should be the same as that of the PPTP server.
MPPE Encryption Specify whether to enable the encryption for the tunnel.
Encrypted: Select Encrypted to encrypt the PPTP tunnel by MPPE.
Unencrypted: With Unencrypted selected, the PPTP tunnel will be not encrypted by MPPE.
Remote Server Enter the IP address or domain name of the PPTP server.
Remote SubnetsEnter the IP address and subnet mask to specify the remote network. It's always the IP address range of LAN on the remote peer of the VPN tunnel.
Local Network TypeSpecify whether to apply the VPN policy to specific local networks or IP addresses.
Network: Specify the local networks of the VPN tunnel. The VPN policy will be only applied to the selected local networks.
Custom IP: Specify the IP addresses of the VPN tunnel. The VPN policy will be only applied to the specified IP addresses.
WAN Select the WAN port on which the VPN tunnel is established.

- Configuring the gateway as a VPN client using OpenVPN

  1. Select a site from the drop-down list of Organization. Go to Settings > VPN. Click + Create New VPN Policy to load the following page.

Create New VPN Policy Name: Status: Enable Purpose: Site-to-Site VPN Client-to-Site VPN VPN Type: VPN Client - OpenVPN Mode: Certificate Certificate+Account Remote Server: (1-65535) Local Network Type: Network Custom IP Local Networks: All WAN: Please Select... Configuration: Import Create Cancel

  1. Enter a name to identify the VPN policy and select the purpose as Client-to-Site VPN. Refer to the following table to configure the required parameters and click Create.

Name Enter a name to identify the VPN policy.

Status Click the checkbox to enable the VPN policy.

Purpose Select the purpose for the VPN as Client-to-Site VPN.

VPN Type Select the VPN type as VPN Client - OpenVPN.

Mode Select the access mode according to VPN requirements.

Certificate: Select this option if the VPN tunnel only requires the certificate.

Certificate+Account: Select this option if the VPN tunnel requires the certificate and VPN user account. If selected, configure the following parameters:

Username: Enter the username for the VPN tunnel.

Password: Enter the password for the VPN tunnel.

Remote Server Enter the IP address or domain name of the OpenVPN server.
Local Network TypeSpecify whether to apply the VPN policy to specific local networks or IP addresses.
Network: Specify the local networks of the VPN tunnel. The VPN policy will be only applied to the selected local networks.
Custom IP: Specify the IP addresses of the VPN tunnel. The VPN policy will be only applied to the specified IP addresses.
WAN Select the WAN port on which the VPN tunnel is established.
ConfigurationClickImportto import the OpenVPN file that ends in .ovpn generated by the OpenVPN server. Only one file can be imported.
If the certificate file and configuration file are generated singly by the OpenVPN server, combine two files and import the whole file.

4.7.2 VPN User

Overview

VPN User is used to configure and record your custom settings for VPN configurations, and it allows you to configure VPN users that can be used for multiple VPN servers. It saves you from setting the VPN users with the same configurations repeatedly when you want to apply the user in different VPN servers.

Configuration

To configure the VPN users, follow these steps:

  1. Select a site from the drop-down list of Organization. Go to Settings >VPN >VPN User. Click +Create New VPN User to add a new entry of VPN User.

VPN VPN User Search Name or VPN Service NAME VPN SERVER MODE ACTION ① No entry in the table. + Create New VPN User

2. Specify the parameters and click Create.

Create New VPN User

Username:

Password:

Protocol:

VPN Server:

Local IP Address:

Mode:

TP-LINK Omada SDN Controller - Create New VPN User - 1

L2TP/PPTP

Please Select...

TP-LINK Omada SDN Controller - Create New VPN User - 2

Client i

○ Network Extension Mode

TP-LINK Omada SDN Controller - Create New VPN User - 3

Maximum Connections:

3 (1-100)

Create

Cancel

Username Enter the username used for the VPN tunnel. The client use the username for the validation before accessing the network.

Password Enter the password of user. The client uses the password for the validation before accessing the network.

Protocol Select the protocol type for the VPN tunnel.

If you selected the L2TP/PPTP protocol, specify the following parameters:

VPN Server Select the VPN server that the VPN user is applied to.

Local IP Address (Optional) Specify the local IP address of the VPN tunnel.

Mode Specify the connection mode for the VPN users.

Client: This mode allows the client to request for an IP address and the server supplies the IP addresses from the VPN IP Pool. With this mode selected, set maximum number of concurrent VPN connections with the same account in Maximum Connections.

Network Extension Mode: This mode allows only clients from the configured subnet to connect to the server and obtain VPN services. With this mode selected, specify the subnets in Remote Subnets.

If you selected the OpenVPN protocol, specify the following parameter:

VPN Server Select the VPN server that the VPN user is applied to.

To edit or delete the VPN users, click the icon in the Action column. You can further filter the entries based on the VPN Server.

VPN VPN User Search Name or VPN Service NAME VPN SERVER MODE ACTION user L2TP Server: VPN Server 1 Client Showing 1-1 of 1 records < 1 > 10 /page Go To page: GO + Create New VPN User Filter the entries. View and edit the account information of users. Delete the VPN user.

4.7.3 IPsec Failover

Overview

IPsec Failover is used to configure the backup group of the IPsec connection. When the primary connection in the group is interrupted, it will try to use the secondary connection to dial up to maintain the stability of the VPN network.

Configuration

  1. Select a site from the drop-down list of Organization. Go to Settings >VPN >IPsec Failover. Click Create New IPsec Failover to add a new entry.

Create New IPsec Failover Group Name: Primary Tunnel: Please Select... Secondary Tunnel: Please Select... Automatic Failback: Gateway Failover Timeout: seconds (10-3600) Create Cancel

Group Name Enter a name to identify the IPsec Failover group.

Primary Tunnel Specify the IPsec primary connection.
Secondary Tunnel Specify the IPsec secondary connection.
Automatic FailbackSelect this function to automatically switch back to the primary connection when it is reachable.When selected, specify the Gateway Failover Timeout time, then the system will query whether the primary connection is reachable within the time, and if yes, it will switch back to the primary connection.

4.7.4 SSL VPN

Overview

SSL VPN uses Secure Socket Layer (SSL) to ensure information safety and provides abundant services such as user management, resource management, user lockout, authentication and accounting.

SSL VPN uses username and password for authentication and login. A network administrator can assign different resources to different types of users, and meanwhile associate the users with multiple resources, making it easy to manage and limit the services the users can access through the VPN.

Configuration

■ SSL VPN Server

In SSL VPN Server, you can enable the feature and configure the SSL VPN settings.

  1. Select a site from the drop-down list of Organization. Go to Settings > VPN > SSL VPN > SSL VPN Server. Enable SSL VPN Server.

SSL VPN Server Resource Management User Group User List Locked Out User SSL VPN Server SSL VPN Server: WAN: Please Select... Virtual IP Pool: . . . . . . . . . . Primary DNS: . . . . Secondary DNS: . . . . (Optional) Listen on Port: 1194 (1-65535) Authentication Type: Local Authentication RADIUS Authentication Username Lockout: IP Lockout: Idle Timeout: Full Mode: Apply Cancel Export Certificate

  1. Configure the parameters according to your needs. Click Apply.
WAN Select the port for the SSL VPN server to listen on, and the VPN tunnel will take effect on the port.
Virtual IP PoolSet a virtual IP Pool, and the SSL VPN server will assign an IP address to a connected client within the pool.
Primary/Secondary DNSSpecify the IP address of the DNS server. The clients will be informed of the DNS server, and it can help the clients resolve the domain name.
Listen on Port Specify the port for the SSL VPN server to listen on. By default, it is 1194.
Authentication TypeSelect the authentication for the clients: Local Authentication or RADIUS Authentication.
If you selected RADIUS Authentication, configure the following parameters:
RADIUS Server: Select a RADIUS server profile.
Authentication Type: Select the authentication protocol for the RADIUS server.
Max Requests: Specify the maximum number of requests sent when no response is received.
Request Timeout: Specify the maximum interval for request timeout. After timeout, the request will be sent again.
NAS IP: Specify the IP address for the router to communicate with the RADIUS server.
Username Lockout When enabled, you can lock out a username in case of excessive login attempts.
IP Lockout When enabled, you can lock out an IP address in case of excessive login attempts.
Idle TimeoutWhen enabled, the VPN tunnel will close automatically if there is no traffic for the specified amount of time.
Full Mode When enable, all traffic will go through the SSL VPN tunnel. When disabled, only the resource-related traffic will go through the tunnel.
  1. Click Export Certificate, enter the WAN IP/Domain Name to access the VPN, then click Export. The VPN configuration file will be exported for clients to access the VPN.

Export Certificate i The SSL VPN certificate will use this WAN IP. Make sure the WAN IP/domain name is filled correctly. WAN: WAN WAN IP/Domain Name: Export Cancel

■ Resource Management

In Tunnel Resources, you can configure the resources the clients can access through the VPN tunnel, including IP range and domain name.

In Resource Group, you can add the multiple tunnel resources to a group for better management. By default, two resource groups are provided: Group_ALL (indicates all resources) and Group_LAN (indicates all LAN resources).

  1. Select a site from the drop-down list of Organization. Go to Settings > VPN > SSL VPN > Resource Management.

  2. Click Create New Tunnel Resource to load the following page. Configure the parameters and click Confirm.

Create New Tunnel Resource Name: (1-20 characters, using a combination of letters, digits and underscores) Resource Type: IP Address IP/Mask: . . . / Protocol: All Confirm Cancel

Name Specify a name for the entry.

Resource Type

Select the type for the resources: IP Address or Domain Name.

If you selected IP Address, configure the following parameters:

IP/Mask: Specify IP range the clients can access.

Protocol: Select the protocol type that the client can access in the IP range, and the router will filter illegal packets through firewall rules. By default, the value is ALL, and it means there is no restriction on the client.

If you selected Domain Name, specify domain name the clients can access.

  1. Click Create New Resource Group to load the following page. Configure the parameters and click Confirm.

Create New Resource Group Resource Group: (1-20 characters, using a combination of letters, digits and underscores) Resources: Please Select... Confirm Cancel

Resource Group Specify a name for the resource group.

Resources Select the resources for the group.

■ User Group

In User Group, you can add multiple users to a group for better management.

  1. Select a site from the drop-down list of Organization. Go to Settings > VPN > SSL VPN > User Group.
  2. Click Create New User Group to load the following page. Configure the parameters and click Confirm.

Create New User Group Group Name: (1-20 characters, using a combination of letters, digits, and underscores) Resource Group List: Please Select... Confirm Cancel

Group Name Specify a name for the user group.

Resource Group List Select the resource group for the user group.

■ User List

In User List, you can view and configure all user settings of the SSL VPN.

  1. Select a site from the drop-down list of Organization. Go to Settings > VPN > SSL VPN > User List.

  2. Click Create New User to load the following page. Configure the parameters and click Confirm.

Create New User Username: (1-20 characters, using a combination of letters, digits, and underscores) Password: (1-64 characters, using a combination of letters, digits, and symbols) Max Concurrent Users: (1-100) Expiration Date: Please Select... User Group: Please Select... Status: Confirm Cancel

Username Specify the username a client used for login.
Password Specify the password a client used for login.
Max Concurrent UsersSpecify the maximum number of clients using the username for login concurrently. If the number reaches this amount, new login attempts will be rejected.
Expiration Date Specify when the user account will expire.
User Group Select which group the user belongs to. A user can only be added to one user group.
Status Click the checkbox to enable this entry.

■ Locked Out User

In Locked Out User, you can view the currently locked out users, and add, delete or edit an entry.

  1. Select a site from the drop-down list of Organization. Go to Settings > VPN > SSL VPN > Locked Out User.

  2. Click Add Locked Out User to load the following page. Configure the parameters and click Confirm.

Add Locked Out User Type: Username Username: (1-20 characters, using a combination of letters, digits and underscores) Locked Out Duration: 0h 01m Confirm Cancel

Type Specify the locked out type.

If you selected Username, specify the username of a locked out user.

If you selected IP Address, specify the IP address of a locked out user.

Lockout Duration Specify how long the entry will be locked out.

4.7.5 WireGuard VPN

Overview

WireGuard VPN is a secure, fast and modern VPN protocol. It is based on the UDP protocol and uses modern encryption algorithms to improve work efficiency.

■ WireGuard

  1. Select a site from the drop-down list of Organization. Go to Settings > VPN > WireGuard.

2. Click Create New WireGuard. Configure the parameters and click Apply.

Edit Wireguard Name: test Status: Enable MTU: 1420 (576-1440) Listen Port: 51820 (1-85535) Local IP Address: 192.168.0.2 Private Key: z+OGT9Gdtl6jcphWHUz6Bawx1W Apply Cancel

Name Specify the name that identifies the WireGuard interface.
Status Specify whether to enable the WireGuard interface.
MTU Specify the MTU value of the WireGuard interface. The default value 1420 is recommended.
Listen Port Specify the port number that the WireGuard interface listens to.
Local IP Address Specify the IP address of the WireGuard interface.
Private KeySpecify the private key of the WireGuard interface. The value will be automatically generated on the device, and you can also modify it manually.

■ Peers

  1. Select a site from the drop-down list of Organization. Go to Settings > VPN > WireGuard > Peers.

2. Click Create New Peer. Configure the parameters and click Apply.

Edit Peer Name: peer Status: Enable Interface: test Endpoint: (Optional) Endpoint Port: (Optional) Allow Address 10 . 0 . 0 . 1 24 Add Subnet Persistent Keepalive: 25 (0-65535 second) Comment: (0-128 characters) Public Key: 1hDuVvpmV2TdWNKvQw+PqUoB Preshared Key: (Optional) Apply Cancel

Name Specify the name that identifies the peer.
Status Specify whether to enable the peer.
Interface Specify the WireGuard interface to which the peer belongs.
Endpoint Specify the IP address of the peer. This parameters is required when the Router actively connects to other WireGurad Server.
Endpoint Port Specify the port number of the peer. This parameters is required when the Router actively connects to other WireGurad Server.
Allowed AddressSpecify the address segment that allows traffic to pass through. Generally, it is the same as the WireGuard VPN interface IP configured on the remote device.
Persistent Keepalive Specify the tunnel keepalive packet interval.
Comment Enter the description of the peer.
Public Key Fill in the public key information exported from the remote device.
Preshared Key Specify an optional shared key.

4.8 Create Profiles

Profiles section is used to configure and record your custom settings for site configurations. It includes Time Range and Groups profiles. In Time Range section, you can configure time templates for wireless schedule, PoE schedule, etc. In Groups section, you can configure groups based on IP, IP-Port and MAC addresses for ACL, Routing, NAT, etc. After creating the profiles, you can apply them to multiply configurations for different sites, saving you from repeatedly setting up the same information.

4.8.1 Time Range

Overview

Time Range section allows you to customize time-related configurations. You can set different time range templates which can be shared and applied to wireless schedule, PoE schedule, etc. in site configuration.

Configuration

To configure the time range profiles, follow these steps:

  1. Select a site from the drop-down list of Organization. Go to Settings > Profiles > Time Range. Click + Create New Time Range to add a new time range entry. By default, there is no entry in the list.
NAMEDAY MODETIME RANGEACTION
i No time range profiles yet.
+ Create New Time Range
  1. Enter a Name for the new entry, select the Day Mode, and specify the time range. Click +Add to add a new time period, click Apply to save the entry. After saving the newly added entry, you can apply them to site configuration.

Create New Time Range Name: Day Mode: Every Day 08:00 am 08:00 am Add Every Day 06:00 pm 06:00 pm Customized Apply Cancel

Name Enter a name for the new entry, and it is a string with 1 to 64 ASCII symbols.

Day ModeSelect Every Day, Weekday, Weekend, or Customized first before specifying the time range for each day.Every Day: You only need to set the time range once, and it will repeat every day.Weekday: You only need to set the time range once, and it will repeat every weekday from Monday to Friday.Weekend: You only need to set the time range once, and it will repeat every Saturday and Sunday.Customized: You are able to set different time range for the chosen day(s) based on your needs. When a day is not chosen, the WiFi is open all day by default.

You can view the name, day mode and time range in the list.

NAME DAY MODE TIME RANGE ACTION Time Range 1 Every Day 08:00 am-06:00 pm Showing 1-1 of 1 records < 1 > 10 /page Go To page: GO + Create New Time Range

To edit or delete the time range entry, click the icon in the Action column.

TP-LINK Omada SDN Controller - Configuration - 3

Edit the parameters in the entry.

TP-LINK Omada SDN Controller - Configuration - 4

Delete the entry.

4.8.2 Groups

Overview

Groups section allows you to customize client groups based on IP, IP-Port, or MAC Address. You can set different rules for the groups profiles which can be shared and applied to ACL, Routing, NAT, etc. in site configuration.

Configuration

To configure the group profiles, follow these steps:

  1. Select a site from the drop-down list of Organization. Go to Settings > Profiles > Groups. Click +Create New Group to add a new group profile.

NAME IPGroup_Any IP Group 1 IPv6Group_Any IPv6 Group 1 Showing 1-2 of 2 records < 1 > 10 / page Go To page: Go + Create New Group

  1. Enter a name for the new group profile entry, and select the type for the new entry.

Create New Group Name: Type: IP Group IPv6 Group IP-Port Group IPv6-Port Group MAC Group Location Group IP Subnets: . . . / Add Subnet Apply Cancel

■ To create an IP group profile:

Choose the IP Group type and specify IP subnets.

■ To create an IPv6 group profile:

Choose the IPv6 Group type and specify IPv6 addresses.

■ To Create an IP-Port group profile:

Choose the IP-Port Group type and specify the IP-Port type and ports, while it is optional to specify IP subnets. If you only specify ports without entering any IP subnets, it means the group contains the specified ports for all IP addresses.

■ To create an IPv6-Port group profile:

Choose the IPv6-Port Group type and specify the IP-Port type and ports, while it is optional to specify IPv6 addresses. If you only specify ports without entering any IPv6 addresses, it means the group contains the specified ports for all IPv6 addresses.

■ To configure a MAC group profile:

Choose the MAC Group type and add MAC addresses in the MAC Addresses List.

TP-LINK Omada SDN Controller - Configuration - 3

Add

Add MAC address individually.

TP-LINK Omada SDN Controller - Configuration - 4

Batch Add

Add MAC addresses in batches. You can enter the MAC addresses and names in the input box or import them with files in the format of Excel, txt, and text.

If you want to use the newly added MAC address(es) and names when they conflict with the existing ones, check the box to override the current MAC addresses in the list.

Note:

  1. Each MAC address and name should be entered on a new line. The MAC address and name should be separated by a space.
  2. Octets in a MAC address should be separated by a hyphen. For example, AA-BB-CC-DD-EE-FF.

TP-LINK Omada SDN Controller - Note: - 1

Add from Client List

Add MAC addresses from the clients that are connected to the devices controlled by the SDN Controller.

■ To configure a location group profile:

Choose the Location Group type and select locations. You can enter a description for identification.

3. Click Apply to save the entry.

You can view and edit the group list, and export the MAC group if needed. You can apply the customized profiles during site configuration.

NAMETYPECOUNTACTION
IP Group_1IP Group2
IPv6Group_AnyIPv6 Group1
IP-Port Group_1IP-Port Group1
IPGroup_AnyIP Group1
IPv6 Group_1IPv6 Group1
IPv6-Port Group_1IPv6-Port Group3
Location Group_1Location Group1
MAC Group_1MAC Group1

4.8.3 Rate Limit

Overview

Rate Limit allows you to customize rate-related configurations. You can set different rate limit templates. They can be bound with wireless network to limit the upload/download rate of clients connected the SSID, and applied to specific types of Portal, such as Local User and Voucher. After creating the profiles, you can apply them to multiple configurations, saving you from repeatedly setting up the same information.

Configuration

To configure the rate limit profiles, follow these steps:

  1. Select a site from the drop-down list of Organization. Go to Settings > Profiles > Rate Limit. By default, there is an entry with no limits, and it can not be deleted. Click +Create New Rate Limit Profile to add a new group entry.

NAME Download Limit Upload Limit ACTION Default Unlimited Unlimited Showing 1-1 of 1 records < 1 > 10 /page Go To page: GO + Create New Rate Limit Profile

  1. Enter a name and specify the download/upload rate limit for the new entry. After saving the newly added entry, you can apply them to other configurations such as Portal and Wireless Settings.

Create New Rate Limit Profile The rate limit profile can be applied to settings of SSID, Client, and Portal (Hotspot > Local User and Hotspot > Voucher). When a client matches multiple rate limit rules, the rule with the minimum value will take effect. Name: Download Limit: Enable Upload Limit: Enable Apply Cancel

Name Enter a name to identify the created rate limit profile.
Download LimitEnable the download limit, and specify the rate limit correspondingly in Kbps or Mbps.
Upload LimitEnable the upload limit, and specify the rate limit correspondingly in Kbps or Mbps.
  1. Click Apply to save the entry. After saving the newly added entry, you can apply them to site configuration. To apply the customized rate limit profiles in the related configurations, refer to 4.9.1 Portal, and 4.4.1 Set Up Basic Wireless Networks.

You can view the name, download limit, and upload limit in the list.

NAME Download Limit Upload Limit ACTION Default Unlimited Unlimited Limit-Day 20000 Kbps 20000 Kbps Limit-Night 50000 Kbps 50000 Kbps Showing 1-3 of 3 records < 1 > 10 /page Go To page: GO + Create New Rate Limit Profile

To view, edit or delete the rate limit profile, click the icon in the Action column.

TP-LINK Omada SDN Controller - Configuration - 4

View and edit the parameters in the entry. You cannot change the type when editing the entry.

TP-LINK Omada SDN Controller - Configuration - 5

Delete the entry.

4.8.4 PPSK

Overview

PPSK is a security solution in which individual client devices can be managed without much complexity. With PPSK, each user is assigned with a unique passphrase for authentication. Also, it allows the binding of a passphrase and the device MAC address(es), and thus only the specified device can be authenticated using the passphrase. In PPSK, you can create the PPSK list and apply them to multiple wireless networks, saving you from repeatedly setting up the same information.

Configuration

To configure the PPSK profiles, follow these steps:

  1. Select a site from the drop-down list of Organization. Go to Settings > Profiles > PPSK. Click +Create New PPSK Profile to add a new PPSK profile.

NAME $SID ACTION No entry in the table. + Create New PPSK Profile

2. Enter a name for the new profile.

Create New PPSK Profile Name: PPSK List NAME PASSPHRASE MAC ADDRESS VLAN ASSIGNMENT ACTION ① No PPSK have been configured EAPs with an earlier firmware version only support up to 50 PPSK entries Apply Cancel

3. Add new entries to the PPSK profile.

• Method 1: Add entries manually

Click Add and select Manually for PPSK Generation. Configure the parameters.

Add New PPSK PPSK Generation: Manually Auto PPSK 1 Name: Passphrase: Password MAC Address: - - - - - (Optional) VLAN Assignment: (Optional, 1-4094) Add New PPSK Apply Cancel

Name Enter a name to identify the created PPSK.

Passphrase Enter a passphrase, and the client will use the passphrase for authentication.

MAC Address (Optional) Enter the MAC address of the device that can use the passphrase for authentication.

VLAN Assignment (Optional) Enter the VLAN ID, and the client who uses the passphrase for authentication will be assigned to the specified VLAN.

Apply the settings. The new PPSK entry will be created.

• Method 2: Add entries automatically

Click Add and select Auto for PPSK Generation. Configure the parameters and apply the settings.

Add New PPSK PPSK Generation: Manually Auto Number of PPSK: (1-128) PPSK Name Prefix: (1-60 characters) Passphrase Length: (8-63) VLAN Assignment: (Optional, 1-4094) Apply Cancel

Number of PPSK Enter the number of PPSK entries to create.

PPSK Name Prefix Enter the prefix of the names for the created PPSK entries.

Passphrase Length Enter the passphrase length.

VLAN Assignment

(Optional) Enter the VLAN ID, and the client who uses the passphrase for authentication will be assigned to the specified VLAN.

Apply the settings. New PPSK entries will be created automatically.

• Method 3: Export and Import entries in batch

After creating PPSK entries, you can click Export to save them to a file locally, then access another site and click Import to import them in batches from the file.

Import PPSK Download the template and fill in your PPSK information. Then import the file. Choose File: Please select a file. Browse Import Cancel

  1. After saving the newly added profile, you can apply them to wireless networks, refer to 4.4.1 Set Up Basic Wireless Networks.

4.8.5 Gateway QoS Service

Overview

In Gateway QoS Service, you can define service type entries that will appear as matching conditions for you to choose when configuring the rules of related modules like QoS. The default entries cannot be edited or deleted. You can add other entries if your service type is not in the list.

Configuration

To configure the Gateway QoS Service profiles, follow these steps:

  1. Select a site from the drop-down list of Organization. Go to Settings > Profiles > Gateway QoS Service. Click + Create New Gateway QoS Service to add a new profile.

Create New Gateway QoS Service Service Name: Protocol: TCP Source Port Range: - (0-65535) Destination Port Range: - (0-65535) Description: (Optional) Apply Cancel

  1. Configure the parameters.
Service Name Enter a name to identify the profile.
ProtocolSpecify the protocol for the service. The system predefined protocols include TCP, UDP, TCP/UDP and ICMP. For other protocols, select the option Other.
Source Port RangeSpecify the source port range for the service. Packets whose source port and destination port are both in the range are considered as the target packets.
Destination Port RangeSpecify the destination port range for the service. Packets whose source port and destination port are both in the range are considered as the target packets.
Type Specify the type of the ICMP packets. 255 means all types are included. ICMP packets with both the type and code fields matched are considered as the target packets.
Code Specify the code of the ICMP packets. 255 means all codes are included. ICMP packets with both the type and code fields matched are considered as the target packets.
Protocol NumberSpecify the protocol number of the packets. Packets matched with the protocol number are considered as the target packets.
Description Enter a description for identification.
  1. Click Apply to save the profile. Now you can select the predefined entry of service type when configuring rules of related modules like QoS.

mDNS (Multicast DNS) Repeater can help forward mDNS request/reply packets between different VLANs. With this function, you can create a forwarding rule to allow the devices in the specified Client VLAN to discover the mDNS service in the specified Service VLAN. You can also specify the services to be forwarded.

Configuration

To configure the Bonjour Service profiles, follow these steps:

  1. Select a site from the drop-down list of Organization. Go to Settings > Profiles > Bonjour Service. Click + Create New Bonjour Service to add a new profile.

Add Service Service Name: Service ID: Add Confirm Cancel

  1. Configure the parameters.
Service Name Enter a name to identify the profile.
Service IDSpecify the domain name corresponding to the mDNS service. It is used to identify and filter mDNS packets.
  1. Click Apply to save the profile.

4.8.7 RADIUS Profile

Overview

RADIUS (Remote Authentication Dial In User Service) is a client/server protocol that provides for the AAA (Authentication, Authorization, and Accounting) needs in modern IT environments.

In authentication services including 802.1X, Portal and MAC-Based Authentication, network devices operate as clients of RADIUS to pass user information to designated RADIUS servers. A RADIUS server maintains a database which stores the identity information of legal users. It authenticates

users against the database when the users are requesting to access the network, and provides authorization and accounting services for them.

A RADIUS profile records your custom settings of a RADIUS server. After creating a RADIUS profile, you can apply it to multiple authentication policies like Portal and 802.1X, saving you from repeatedly entering the same information.

Configuration

■ Configure the Built-in RADIUS Profile (for Software/Hardware Controller only)

a. Select a site from the drop-down list of Organization. Go to Settings > Profiles > RADIUS Profile.
b. The Software/Hardware Controller provides a Built-in RADIUS Profile. Click the edit icon of the profile, then click Add New RADIUS User.
c. Configure the parameters and save the settings.

Create New RADIUS User Authentication Type: User Authentication MAC Authentication Name: Password: Password VLAN ID: (Optional, 1-4094) Session-Timeout: Seconds (Optional) Rate Limit: Traffic Limit: Apply Cancel

Authentication Type Select the Authentication Type.

User Authentication: Select this option and enter the user Name and Password for authentication.

MAC Authentication: Select this option and enter the MAC Address for authentication.

VLAN ID Enter a VLAN ID to assign VLANs to users.

Session-Timeout Configure the authentication expiration time for users.

Rate LimitWhen enabled, you can set limits for Uplink Rate and Downlink Rate of each client to balance bandwidth usage.This function applies to the portal service only.
Traffic LimitWhen enabled, you can set limits for Uplink Traffic and Downlink Traffic of each client.This function applies to the portal service only.

■ Create New RADIUS Profile

a. Select a site from the drop-down list of Organization. Go to Settings > Profiles > RADIUS Profile.
b. Click Create New RADIUS Profile. Configure the parameters and save the settings.

Create New RADIUS Profile Name: VLAN Assignment: Enable VLAN Assignment for Wireless Network Authentication Server 1 Authentication Server IP: . . . Authentication Port: 1812 (1-65535) Authentication Password: Password Add New Authentication Server RADIUS Accounting: Enable

Name Enter a name to identify the RADIUS profile.
VLAN AssignmentThis feature allows the RADIUS server to place a wireless user into a specific VLAN based on the credentials supplied by the user. To use the feature, you should create the specific VLAN first. And the user-to-VLAN mappings must be already stored in the RADIUS server database.Note:1. VLAN Assignment is not currently supported when a client is authenticated by Portal with External RADIUS Server or RADIUS Hotspot.2. VLAN Assignment is applicable only when the device supports the feature. To make this feature work properly, it is recommended to upgrade your devices to the latest firmware version.
Authentication Server IPEnter the IP address of the authentication server.
Authentication PortEnter the UDP destination port on the authentication server for authentication requests.
Authentication PasswordEnter the password that will be used to validate the communication between network devices and the RADIUS authentication server.
RADIUS AccountingClick the checkbox to enable RADIUS Accounting to meet billing needs. This feature is only available for APs with Portal to account for wireless clients.
Interim Update Click the checkbox to enable Interim Update. By default, the RADIUS accounting process needs only start and stop messages to the RADIUS accounting server. With Interim Update enabled, network devices will periodically send an Interim Update (a RADIUS Accounting Request packet containing an “interim-update” value) to the RADIUS server. An Interim Update updates the user's session duration and current data usage.
Interim Update IntervalEnter an appropriate interval between the updates of users' session duration and current data usage.
Accounting Server IP Enter the IP address of the RADIUS accounting server.
Accounting Port Enter the UDP destination port on the RADIUS server for accounting requests.
Accounting PasswordEnter the password that will be used to validate the communication between network devices and the RADIUS accounting server.

4.8.8 LDAP Profiles

Overview

The Lightweight Directory Access Protocol (LDAP) is an industry standard protocol for maintaining and accessing directory information over a network. LDAP Authentication allows you to bind the device to an LDAP server and use that server to authenticate LAN clients.

Configuration

To configure the LDAP profiles, follow these steps:

  1. Select a site from the drop-down list of Organization. Go to Settings > Profiles > LDAP Profile. Click +Create New LDAP Profile to add a new profile.

Create New LDAP Profile Status: Enable Name: Bind Type: Simple Mode Server Address: Idap:// Destination Port: 389 Use SSL: Enable Common Name Identifier: Base Distinguished Name: Apply Cancel

  1. Configure the parameters.
Status Check the box to enable LDAP Authentication.
Name Specify the profile name.
Bind Type Select the LDAP Authentication mode: Anonymous Mode, Simple Mode, or Regular Mode.
Server Address Enter the IP address of the LDAP server.
Destination PortEnter the port ID of the LDAP server. By default, the port ID is 389 when SSL is disabled and 636 when SSL is enabled.
Use SSL Determine whether to use SSL for LDAP communication.
Regular DNSpecify the distinguished name (DN) of the administrator account. This parameter is required in Regular mode.
Regular PasswordSpecify the password of the administrator account. This parameter is required in Regular mode.
Common Name Identifier Specify the common name for user authentication. It is usually "cn".
Base Distinguished NameSpecify the user identifier for user authentication. You can click the icon next to it to search and select from the LDAP directory tree.
Additional FilterSpecify the filter for user authentication. It is not supported in Simple Mode and is optional in other modes.
Group Distinguished NameSpecify the group identifier for user authentication. It is not supported in Simple Mode and is optional in other modes.
  1. Click Apply to save the profile. Now you can select the predefined entry of LDAP profile when configuring rules of related modules like LDAP Server.

4.8.9 APN Profile

Overview

APN is a network access technology required when using the SIM card to access the internet. It determines which access method the SIM card uses to access the internet.

Configuration

To configure the APN profiles, follow these steps:

  1. Select a site from the drop-down list of Organization. Go to Settings > Profiles > APN Profile. Click +Create New APN Profile to add a new profile.

Create New APN Profile Profile Name: PDP Type: IPv4 APN Type: Static APN: Username: (Optional) Password: Password (∅) (Optional) Authentication Type: None Apply Cancel

  1. Configure the parameters.

Profile Name Specify the name of the profile.

PDP Type Select the PDP (Packet Data Protocol) type: IPv4, IPv6, or IPv4 & IPv6.

APN Type Select the APN type: Static or Dynamic.

APN When APN Type is Static, specify the APN (access point name) provided by your ISP.

Username Enter the username provided by your ISP. This field is case-sensitive.

Password Enter the password provided by your ISP. This field is case-sensitive.

Authentication Type

Some ISPs need a specific authentication type, please confirm it with your ISP or keep the default value.

None: No authentication is required.

PAP: Password Authentication Protocol. The protocol allows a device to establish authentication with a peer using a two-way handshake. Select this option if your ISP requires this authentication type.

CHAP: Challenge Handshake Authentication Protocol. The protocol allows a device to establish authentication with a peer using a three-way handshake and periodically checking the peer's identity. Select this option if your ISP requires this authentication type.

  1. Click Apply to save the profile. Now you can select the predefined entry of APN profile when configuring rules of related modules.

4.9 Authentication

Authentication is a portfolio of features designed to authorize network access to clients, which enhances the network security. Authentication services include 4.9.1 Portal, 4.9.2 802.1X and 4.9.3 MAC-Based Authentication, covering all the needs to authenticate both wired and wireless clients.

4.9.1 Portal

Overview

Portal authentication provides convenient authentication services to the clients that only need temporary access to the network, such as the customers in a restaurant or in a supermarket. To access the network, these clients need to enter the authentication login page and use the correct login information to pass the authentication. In addition, you can customize the authentication login page and specify a URL which the authenticated clients will be redirected to.

Portal authentication takes effect on SSIDs and LAN networks. APs authenticate wireless clients which connect to the SSID with Portal configured, and the gateway authenticates wired clients which connect to the network with Portal configured. To make Portal authentication available for wired and wireless clients, ensure that both the gateway and APs are connected and working properly.

The controller provides several types of Portal authentication:

■ No Authentication

With this authentication type configured, clients can pass the authentication and access the network without providing any login information. Clients just need to accept the terms (if configured) and click the Login button.

■ Simple Password

With this authentication type configured, clients are required to enter the correct password to pass the authentication. All clients use the same password which is configured in the controller.

■ Hotspot

With this authentication type configured, clients can access the network after passing any type of the authentication:

- Voucher

Clients can use the unique voucher codes generated by the controller within a predefined time usage. Voucher codes can be printed out from the controller, so you can print the codes and distribute them to your costumers to tie the network access to consumption.

- Local User

Clients are required to enter the correct username and password of the login account to pass the authentication.

- SMS

Clients can get verification codes using their mobile phones and enter the received codes to pass the authentication.

- RADIUS

Clients are required to enter the correct username and password which are stored in the RADIUS server to pass the authentication.

- Form Auth

Clients are required to fill in a survey created by the network administrator to pass the authentication. It can be used for collecting feedback from your clients.

■ RADIUS Server

Clients are required to enter the correct username and password created on the RADIUS server to pass the authentication.

■ External Portal Server

The option of External Portal Server is designed for the developers. They can customize their own authentication type like Google account authentication according to the interface provided by the Controller.

Portal authentication can work with Access Control Policy, which grant specific network access to the users with valid identities. You can determine that the clients which didn't pass Portal authentication can only access the network resources allowed by Access Control Policy.

■ Pre-Authentication Access

Pre-Authentication Access allows unauthenticated clients to access the specific network resources.

■ Authentication-Free Client

Authentication-Free Clients allows the specific clients to access the specific network resources without authentication.

Create New Portal

  1. Select a site from the drop-down list of Organization. Go to Settings > Authentication > Portal.

  2. On Portal tab, click Create New Portal. Specify the portal name and enable Portal.

Create New Portal Portal Name: Portal: Controller Online Required. SSID & Network: Please Select... Authentication Type: No Authentication Authentication Timeout: 8 Hours Daily Limit: Enable i HTTPS Redirection: Enable i Landing Page: The Original URL The Promotional URL

  1. Select the SSIDs and LAN networks for the portal to take effect. The clients connected to the selected SSIDs or LAN networks will have to log into a web page to establish verification before accessing the network.
  2. Select the Authentication Type and configure authentication settings.

■ No Authentication

Authentication TimeoutSelect the login duration. Clients will be off-line after the authentication timeout.
Daily LimitClick the checkbox to enable Daily Limit. With this feature enabled, after authentication times out, clients cannot get authenticated again until the next day. With this feature disabled, after authentication times out, clients can get authenticated again without limit.

■ Simple Password

Password Specify the password for the portal.
Authentication TimeoutSelect the login duration. Clients will be off-line after the authentication timeout.

■ Hotspot

Type Select one or more authentication types according to your needs. Clients can access the network after passing any type of the authentication.

With different types of Hotspot selected, configure the related parameters.

- Voucher Portal

Voucher

Select Voucher and click to manage the voucher codes.

Refer to 7.2.3 Vouchers for detailed information about how to create vouchers.

- Local User Portal

Local User

Select Local User and click to manage the information of the login accounts.

Refer to 7.2.4 Local Users for detailed information about how to create Local Users.

- SMS Portal

Select SMS and configure the required parameters in the SMS section.

SMS Clients can get verification codes using their mobile phones and enter the received codes to pass the authentication.

Twilio SID Enter the Account SID for Twilio API Credentials.

Auth Token Enter the Authentication Token for Twilio API Credentials.

Operating Phone Number Enter the phone number that is used to send verification messages to the clients.

Maximum User Numbers Click the checkbox and enter the maximum number of users allowed to be authenticated using the same phone number at the same time.

Authentication Timeout Select the login duration. The client needs to log in again on the web authentication page to access the network.

Preset Country Code Enter the default country code that will be filled automatically on the authentication page.

- RADIUS Portal

Select RADIUS and configure the required parameters in the RADIUS section.

Authentication Timeout

Clients are required to enter the correct username and password which are stored in the RADIUS server to pass the authentication.

RADIUS Profile Select the RADIUS profile you have created. If no RADIUS profiles have

been created, click + Create New RADIUS Profile from the drop-down list or Manage RADIUS Profile to create one. The RADIUS profile records the information of the RADIUS server which provides a method for storing the authentication information centrally.

Authentication Mode

Select the authentication protocol for the RADIUS server. Two authentication protocols are available: PAP and CHAP.

NAS ID Configure a Network Access Server Identifier (NAS ID) on the portal. Authentication request packets from the controller to the RADIUS server carry the NAS ID. The RADIUS server can classify users into different groups based on the NAS ID, and then choose different policies for different groups.
Disconnected RequestsWith the feature enabled, the controller will listen on the receiver port for disconnect requests from the RADIUS server. When the controller receives the disconnect requests in correct format, the controller will terminate the RADIUS authentication session of the clients. Note that the feature is available only when the controller is accessible to the RADIUS server.
Receiver Port Specify the port on which the controller listens when there are disconnect requests from the RADIUS server. Make sure that the specified port is not in use.
Status The entry displays the status of the receiver port, including Running, Disabled, and Error. Running means that the port is available, Disabled means that the port is closed, and Error means that the port is already in use.

- Configuring Form Authentication

Select Form Auth and click + Create New Survey in the Form Authentication section. Then follow the on-screen instructions to create a survey by adding the type and number of questions you need. You can click Preview to view how the survey looks like on website and phone.

Click Publish and then the created survey can be used for form authentication. A survey cannot be edited after it is published.

Survey Name Specify a name for the survey for identification.

Duration Specify how long clients can use the network after they pass the form authentication.

Created surveys will be displayed for you to choose for the form authentication.

■ RADIUS Server

Authentication TimeoutSelect the login duration. Clients will be off-line after the authentication timeout.
RADIUS ProfileSelect the RADIUS profile you have created. If no RADIUS profiles have been created, click Create New RADIUS Profile from the drop-down list or click Manage RADIUS Profile to create one. The RADIUS profile records information of the RADIUS server including the IP address, port and so on.
NAS ID Configure a Network Access Server Identifier (NAS ID) on the portal. Authentication request packets from the controller to the RADIUS server carry the NAS ID. The RADIUS server can classify users into different groups based on the NAS ID, and then choose different policies for different groups.
Disconnected RequestsWith the feature enabled, the controller will listen on the receiver port for disconnect requests from the RADIUS server. When the controller receives the disconnect requests in correct format, the controller will terminate the RAIDUS authentication session of the clients. Note that the feature is available only when the controller is accessible to the RADIUS server.
Receiver PortSpecify the port on which the controller listens when there are disconnect requests from the RADIUS server. Make sure that the specified port is not in use.
Status The entry displays the status of the receiver port, including Running, Disabled, and Error. Running means that the port is available, Disabled means that the port is closed, and Error means that the port is already in use.
Authentication Mode Select the authentication protocol for the RADIUS server.
Portal CustomizationSelect Local Web Portal or External Web Portal. The authentication login page of Local Web Portal is provided by the built-in portal server of the controller. The External Web Portal is provided by external portal server. Enter the authentication login page's URL provided by the external portal server in the External Web Portal URL field.

■ External LDAP Server

Authentication TimeoutSelect the login duration. Clients will be off-line after the authentication timeout.
LDAP Profile Select the LDAP profile you have created. If no LDAP profiles have been created, click Create New LDAP Profile from the drop-down list or click Manage LDAP Profile to create one. The LDAP profile records information of the LDAP server including the server address, port and so on.
Portal CustomizationSelect Local Web Portal or External Web Portal. The authentication login page of Local Web Portal is provided by the built-in portal server of the controller. The External Web Portal is provided by external portal server. Enter the authentication login page’s URL provided by the external portal server in the External Web Portal URL field.

■ External Portal Server

Custom Portal Server Specify the IP address or URL that redirect to an external portal server.

5. Configure redirection and landing settings.

HTTPS RedirectionClick the checkbox to enable HTTPS Redirection. With this feature enabled, the unauthorized clients will be redirected to the Portal page when they are trying to browse HTTPS websites. With this feature disabled, the unauthorized clients cannot browse HTTPS websites and are not redirected to the Portal page.
Landing PageSelect which page the client will be redirected to after a successful authentication.The Original URL: Clients are directed to the URL they request for after they pass Portal authentication.The Promotional URL: Clients are directed to the specified URL after they pass Portal authentication.

(Optional) Portal Customization

When creating or editing a portal entry, you can customize the Portal page in the Portal Customization section.

TP-LINK Omada SDN Controller - (Optional) Portal Customization - 1

Note:

Portal Customization is not available when you configure external authentication types.

Portal Customization

Type:

TP-LINK Omada SDN Controller - Portal Customization - 1

Edit Current Page

TP-LINK Omada SDN Controller - Portal Customization - 2

Import Customized Page

Default Language:

English

TP-LINK Omada SDN Controller - Portal Customization - 3

TP-LINK Omada SDN Controller - Portal Customization - 4

Background:

TP-LINK Omada SDN Controller - Portal Customization - 5

Solid Color

TP-LINK Omada SDN Controller - Portal Customization - 6

Picture

Background Picture:

TP-LINK Omada SDN Controller - Portal Customization - 7

Choose

Logo:

TP-LINK Omada SDN Controller - Portal Customization - 8

Enable

Logo Picture:

TP-LINK Omada SDN Controller - Portal Customization - 9

Choose

Logo Size:

Small Medium Large Upper Middle Lower

Logo Position:

TP-LINK Omada SDN Controller - Portal Customization - 11

Button Color:

TP-LINK Omada SDN Controller - Portal Customization - 12

Button Text color:

TP-LINK Omada SDN Controller - Portal Customization - 13

Button Position :

TP-LINK Omada SDN Controller - Portal Customization - 14

Button Text:

Log In

Welcome Information:

Enable

Terms of Service :

Enable

Copyright:

Enable

Show Redirection Countdown

Enable

After Authorized :

Type Select the type of the Portal page.
Edit Current Page: Edit the related parameters to customize the Portal page based on the provided page.
Import Customized Page: Click import to import your unique Portal page for branding it as per your business.
Default LanguageSelect the default language displayed on the Portal page. The controller automatically adjusts the language displayed on the Portal page according to the system language of the clients. If the language is not supported, the controller will use the default language specified here.
Background Select the background type.
Solid Color: Configure your desired background color by entering the hexadecimal HTML color code manually or through the color picker.
Picture: Click Choose and select a picture from your PC as the background.
Logo Click to show the logo on the portal page.
Logo PictureClick Choose and select a picture from your PC as the logo.
Logo Size/Adjust the logo size and position on the Portal Page.
Logo Position
Input Box Color/(For certain authentication types) Configure your desired background and text color for the input box by entering the hexadecimal HTML color code manually or through the color picker.
Input Text Color
Button Color/Configure your desired background and text color for the button by entering the hexadecimal HTML color code manually or through the color picker.
Button Text Color
Button Position Select the button position on the Portal Page.
Button Text Enter the text for the button.
Welcome Information Click the checkbox and enter text as the welcome information.
You can specify the desired text font size and configure the text color by entering the hexadecimal HTML color code manually or through the color picker.
Terms of ServiceClick the checkbox and enter text as the terms of service in the following box. Click Add Terms to enter the name and context of the terms which will appear after a client clicks the link in Terms of Service.
Copyright Click the checkbox and enter text as the copyright in the following box.
You can specify the desired text font size and configure the text color by entering the hexadecimal HTML color code manually or through the color picker.

Show Redirection Countdown After Authorized

When enabled, the system will show the portal's redirection countdown.

Click Advertisement Options and customize advertisement pictures on the authentication page if needed.

TP-LINK Omada SDN Controller - Portal Customization - 15

Advertisement:

TP-LINK Omada SDN Controller - Advertisement Options - 1

Enable

Picture Resource:

Choose

(1-5 Pictures)

TP-LINK Omada SDN Controller - Advertisement Options - 2

Advertisement Duration Time:

seconds

(1-30)

Picture Carousel Interval:

seconds

(1-10)

Allow Users To Skip Advertisement:

TP-LINK Omada SDN Controller - Advertisement Options - 3

Enable

AdvertisementClick the checkbox to enable the Advertisement feature. With this feature enabled, you can add advertisement pictures on the authentication page. These advertisement pictures will be displayed before the login page appears.
Picture ResourceClick Choose and select pictures from your PC as the advertisement pictures. When several pictures are added, they will be played in a loop.
Advertisement Duration TimeEnter the duration time for the advertisement pictures. For this duration, the pictures will be played in a loop. If the duration time is not enough for all the pictures, the rest will not be displayed.
Picture Carousel IntervalEnter the picture carousel interval. For example, if this value is set as 5 seconds, the first picture will be displayed for 5 seconds, followed by the second picture for 5 seconds, and so on.
Allow Users To Skip AdvertisementClick the checkbox to allow users to skip the advertisement.

(Optional) Access Control

On Access Control tab, you can configure access control rules if needed.

Access Control Pre-Authentication Access: ✓ Enable ⓘ Pre-Authentication Access List: TYPE INFORMATION ACTION ⓘ No Pre-Authentication Access entries have been configured. Authentication-Free Client: ✓ Enable ⓘ Authentication-Free Client List TYPE INFORMATION ACTION ⓘ No Authentication-Free Client have been configured. Apply Cancel Pre-Authentication Access Click the checkbox to enable Pre-Authentication Access. With this feature enabled, unauthenticated clients are allowed to access the subnets and web resources specified in the Pre-Authentication Access List below. Pre-Authentication Access List Click + Add to configure the IP range or URL which unauthenticated clients are allowed to access. Authentication-Free Policy Click the checkbox to enable Authentication-Free Policy. With this feature enabled, you can allow certain clients to access the internet without Portal authentication. Authentication-Free Client List Click + Add and enter the IP address or MAC address of Authentication-Free clients.

4.9.2 802.1X

Overview

802.1X provides port-based authentication service to restrict unauthorized clients from accessing to the network through publicly accessible switch ports. An 802.1X-enabled port allows only authentication messages and forbids normal traffic until the client passes the authentication.

802.1X authentication uses client-server model which contains three device roles: client/supplicant, authenticator and authentication server. This is described in the figure below:

TP-LINK Omada SDN Controller - Overview - 1

flowchart
graph LR
    A["Clients"] --> B["Switch Authenticator"]
    B --> C["Authentication Server"]

■ Client

A client, usually a computer, is connected to the authenticator via a physical port. We recommend that you install TP-Link 802.1X authentication client software on the client hosts, enabling them to request 802.1X authentication to access the LAN.

- Authenticator

An authenticator is usually a network device that supports 802.1X protocol. As the above figure shows, the switch is an authenticator.

The authenticator acts as an intermediate proxy between the client and the authentication server. The authenticator requests user information from the client and sends it to the authentication server; also, the authenticator obtains responses from the authentication server and sends them to the client. The authenticator allows authenticated clients to access the LAN through the connected ports but denies the unauthenticated clients.

■ Authentication Server

The authentication server is usually the host running the RADIUS server program. It stores information of clients, confirms whether a client is legal and informs the authenticator whether a client is authenticated.

Based on authenticated identity, 802.1X can also deliver customized services. For example, 802.1X and VLAN Assignment together make it possible to assign different authenticated users to different VLANs automatically.

Configuration

To complete the 802.1X configuration, follow these steps:

1) Click ▶ to enable 802.1X.
2) Select the RADIUS profile you have created and configure other parameters.
3) Select the ports on which 802.1X Authentication will take effect.

Enable 802.1X Configure RADIUS Profile and Parameters Select the Ports

Select a site from the drop-down list of Organization. Go to Settings > Authentication > 802.1X. Click to enable 802.1X.

802.1X

802.1X:

TP-LINK Omada SDN Controller - Enable 802.1X Configure RADIUS Profile and Parameters Select the Ports - 1

TP-LINK Omada SDN Controller - Enable 802.1X Configure RADIUS Profile and Parameters Select the Ports - 2

Switch Required.

Enable 802.1X Configure RADIUS Profile and Parameters Select the Ports

Select the RADIUS profile you have created. If no RADIUS profiles have been created, click

+ Create New RADIUS Profile from the drop-down list or to create one. The RADIUS

profile records the information of the RADIUS server which acts as the authentication server during 802.1X authentication.

Basic Info

RADIUS Profile:

Please Select...

TP-LINK Omada SDN Controller - Basic Info - 1

Manage RADIUS Profile

Authentication Protocol:

○ PAP

EAP

Authentication Type:

○ Port Based

MAC Based

MAB:

Enable

Authentication Protocol

Select the authentication protocol for exchanging messages between the switch and RADIUS server. As a bridge between the client and RADIUS server, the switch forwards messages for them. It uses AP packets to exchange messages with the client, and processes the messages according to the specified authentication protocol before forwarding them to the RADIUS server.

PAP: The AP packets are converted to other protocol (such as RADIUS) packets, and transmitted to the RADIUS server.

AP: The AP packets are encapsulated in other protocol (such as RADIUS) packets, and transmitted to the authentication server. To use this authentication mechanism, the RADIUS server should support AP attributes.

Authentication Type Select the 802.1X authentication type.

Port Based: After a client connected to the port gets authenticated successfully, other clients can access the network via the port without authentication.

MAC Based: Clients connected to the port need to be authenticated individually. The RADIUS server distinguishes clients by their MAC addresses.

VLAN Assignment

This feature allows the RADIUS server to send the VLAN configurations to the port dynamically. After the port is authenticated, the RADIUS server assigns the VLAN based on the username of the client connecting to the port. The username-to-VLAN mappings must be already stored in the RADIUS server database. This feature is available only when the 802.1X authentication type is Port Based.

MAB MAB (MAC Authentication Bypass) allows clients to be authenticated without any client software installed. MAB is useful for authenticating devices without 802.1X capability like IP phones. When MAB is enabled on a port, the switch will learn the MAC address of the client automatically and send the authentication server a RADIUS access request frame with the client's MAC address as the username and password. MAB takes effect only when 802.1X authentication is enabled on the port.

Enable 802.1X Configure RADIUS Profile and Parameters Select the Ports

Select the ports to enable 802.1X authentication or MAB for them. To enable 802.1X authentication, click the unselected ports. 802.1X-enabled ports will be marked with √. To enable MAB, click the ports marked with √. You can enable MAB only on 802.1X-enabled ports. MAB-enabled ports will be marked with √.

DEVICE NAME PORTS STATUS MODEL FIRMWARE VERSION Port CONNECTED 2.0.4

Note:

• You are not recommended to enable 802.1X authentication on the switch ports which connects to network devices without 802.1X capability like the router and APs.
- The switch authenticates wired clients which connect to the port with 802.1X enabled. And the gateway authenticates wired clients which connect to the network with Portal configured. Wired clients should pass Portal and 802.1X authentication to access the internet when both are configured.

4.9.3 MAC-Based Authentication

Overview

MAC-Based Authentication allows or disallows clients access to wireless networks based on the MAC addresses of the clients. In this authentication method, the controller takes wireless clients' MAC addresses as their usernames and passwords for authentication. The RADIUS server authenticates the MAC addresses against its database which stores the allowed MAC addresses. Clients can

access the wireless networks configured with MAC-based authentication after passing authentication successfully.

TP-LINK Omada SDN Controller - Overview - 1

Note:

Both MAC-Based Authentication and Portal authentication can authenticate wireless clients. If both are configured on a wireless network, a wireless client needs to pass MAC-Based Authentication first and then Portal authentication for internet access. You can enable MAC-Based Authentication Fallback to allow clients bypass MAC-Based Authentication, which means the client needs to pass either of the two authentication. The client tries MAC-Based Authentication first, and is allowed to try portal authentication if it failed the MAC-Based Authentication.

Configuration

  1. Select a site from the drop-down list of Organization. Go to Settings > Authentication > MAC-Based Authentication. Click ▶ to enable MAC-Based Authentication.

MAC-Based Authentication

MAC-Based Authentication:

TP-LINK Omada SDN Controller - MAC-Based Authentication - 1

  1. In the Basic Info, select the SSIDs, RADIUS Profile and other required parameters. Refer to the following table to configure the required parameters and click Save.

Basic Info SSID: Please Select... RADIUS Profile: Please Select... NAS ID: (Optional) MAC-Based Authentication Fallback: Enable i MAC Address Format: Please Select... Empty Password: Enable i Save Cancel Manage RADIUS Profile

SSID Select one or more SSIDs for MAC-based authentication to take effect.

RADIUS ProfileSelect the RADIUS profile you have created. If no RADIUS profiles have been created, click + Create New RADIUS Profile from the drop-down list or Manage RADIUS Profile to create one. The RADIUS profile records the information of the RADIUS server which acts as the authentication server during MAC-Based Authentication.
NAS ID Configure a Network Access Server Identifier (NAS ID) for the authentication. Authentication request packets from the controller to the RADIUS server carry the NAS ID. The RADIUS server can classify users into different groups based on the NAS ID, and then choose different policies for different groups.
MAC-Based Authentication FallbackFor the wireless network configured with both MAC-Based Authentication and Portal, if you enable this feature, a wireless client needs to pass only one authentication. The client tries MAC-Based Authentication first, and is allowed to try Portal authentication if it failed the MAC-Based Authentication. If you disable this feature as default, a wireless client needs to pass both the MAC-Based Authentication and portal authentication for internet access, and will be denied if it fails either of the authentication.
MAC Address FormatSelect clients' MAC address format which the controller uses for authentication. Then configure the MAC addresses in the specified format as usernames for the clients on the RADIUS server.
Empty Password Click to allow a blank password for MAC-Based Authentication. With this option disabled, the password will be the same as the username.

4.10 Services

Services provide convenient network services and facilitate network management. You can set fixed IP address for certain device in DHCP Reservation, configure servers or terminals in DDNS, SNMP, UPnP, and SSH, schedule the devices in Reboot Schedule, PoE Schedule and Upgrade Schedule, and export the information in Export Data, and more.

4. 10. 1 DHCP Reservation

Overview

It is convenient for networks to use Dynamic IP addresses assigned by Dynamic Host Configuration Protocol (DHCP), however, for devices that need to be reliably accessed, it is ideal to set fixed IP addresses for them. DHCP Reservation allows you to reserve specific IP addresses for devices in your network, and centrally manage the IP addresses.

Configuration

■ To manually add DHCP Reservation entries:

  1. Select a site from the drop-down list of Organization. Go to Settings > Services > DHCP Reservation.
  2. Click +Create New DHCP Reservation Entry and configure the parameters. Then click Apply.

Create New DHCP Reservation Entry Network: Please Select... MAC Address: - - - - - IP ADDRESS: . . . . Description: (Optional) Status: Enable Apply Cancel

Network Select the network the DHCP reservation entry is used for.

MAC Address Specify the MAC address of the device for which you want to reserve an IP address.

IP Address Specify the fixed IP address for the device.

Description Enter description for the entry for identification.

Status Enable or disable the entry.

■ To import DHCP Reservation entries in batch:

  1. Select a site from the drop-down list of Organization. Go to Settings > Services > DHCP Reservation.
  2. Click Export to export the template in csv format. Based on this template, you can add custom address reservation entries that need to be imported.
  3. Click Import and import the customized template. You can download the template, then edit and upload it for batch import.

Import DHCP Reservation List Download the template and fill in your DHCP Reservation information. Then import the file. Choose File: Please select a file. Browse Import Cancel

4. 10.2 Dynamic DNS

Overview

WAN IP Address of your gateway can change periodically because your ISP typically employs DHCP among other techniques. This is where Dynamic DNS comes in. Dynamic DNS assigns a fixed domain name to the WAN port of your gateway, which facilitates remote users to access your local network through WAN Port.

Let's illustrate how Dynamic DNS works with the following figures.

Before:

  • WAN IP Address can change periodically, if it's dynamically assigned by the ISP using DHCP among other techniques.
  • Remote User doesn't know what WAN IP Address is exactly at the moment, and cannot access Local Network.

Not sure about WAN IP Address. Can't access Local Network.

TP-LINK Omada SDN Controller - Before: - 1
Remote User

TP-LINK Omada SDN Controller - Before: - 2

WAN IP Address changes: 2020/05/27: 172.217.174.196
2020/05/28: 172.217.174.208

二、重要事项

WAN Port

TP-LINK Omada SDN Controller - Before: - 3
Gateway

TP-LINK Omada SDN Controller - Before: - 4

Local Network

After:

- Remote User can simply use Domain Name to access Local Network through WAN Port. In this example, Domain Name is mysite.ddns.net.

TP-LINK Omada SDN Controller - After: - 1

flowchart
graph LR
    A["Service Provider"] --> B["Internet"]
    B --> C["WAN Port LAN Port"]
    C --> D["Local Network"]
    E["User Interface"] --> A
    F["User Interface"] --> A
    style A fill:#4CAF50,stroke:#388E3C
    style B fill:#2196F3,stroke:#333
    style C fill:#2196F3,stroke:#333
    style D fill:#2196F3,stroke:#333
    note1["Use Domain Name (mysite.ddns.net) to access Local Network."] --> A
    note2["Domain Name is constant: 2020/05/27; mysite.ddns.net 2020/05/28; mysite.ddns.net ..."] --> B

Remote User

Prerequisite:

  • Choose one Service Provider from the four that the controller supports, i.e. DynDNS, No-IP, Peanuthull, Comexe.
  • Register at your Service Provider, then you get your Username and Password.
    • Get your Domain Name from your Service Provider.

How Dynamic DNS works:

① Gateway informs Service Provider of WAN IP Address.
② Service Provider binds WAN IP Address with Domain Name and keeps it updated as WAN IP Address changes.
③ Remote User requests for WAN IP Address by sending Domain Name to Service Provider.
④ Service Provider replies with WAN IP Address, which Remote User actually uses to access Local Network through WAN Port.
1 Gateway informs Service Provider of WAN IP Address. 2 Service Provider binds WAN IP Address with Domain Name and keeps it updated as WAN IP Address changes. 3 Remote User requests for WAN IP Address by sending Domain Name to Service Provider. 4 Service Provider replies with WAN IP Address, which Remote User actually uses to access Local Network through WAN Port.

TP-LINK Omada SDN Controller - How Dynamic DNS works: - 1

flowchart
graph TD
    A["Remote User"] -->|4| B["Service Provider"]
    B -->|3| C["Internet"]
    C -->|1| D["WAN Port LAN Port"]
    D --> E["Gateway"]
    F["Local Network"] -->|2| G["Dynamic DNS Binding: 2020/05/27: 172.217.174.196 --> mysite.ddns.net\n2020/05/28: 172.217.174.208 --> mysite.ddns.net ..."]
    H["WAN IP Address changes: 2020/05/27: 172.217.174.196\n2020/05/28: 172.217.174.208 ..."]

Configuration

Select a site from the drop-down list of Organization. Go to Settings > Services > Dynamic DNS. Click + Create New Dynamic DNS Entry, to load the following page. Configure the parameters and click Create.

Create New Dynamic DNS Entry

Service Provider:

DynDNS

TP-LINK Omada SDN Controller - Create New Dynamic DNS Entry - 1

Status:

Enable

Interface:

SFP WAN

○ WAN

Username:

Go To Register

TP-LINK Omada SDN Controller - Create New Dynamic DNS Entry - 2

Password:

TP-LINK Omada SDN Controller - Create New Dynamic DNS Entry - 3

Domain Name:

Interval Mode:

TP-LINK Omada SDN Controller - Create New Dynamic DNS Entry - 4

Fixed

Custom

Update Interval:

Please Select.

TP-LINK Omada SDN Controller - Create New Dynamic DNS Entry - 5

Service Provider Select your service provider which Dynamic DNS works with.

Status Enable or disable the Dynamic DNS entry.

Interface Select the WAN Port which the Dynamic DNS entry applies to.

Username

Enter your username for the service provider. If you haven't registered at the service provider, click Go To Register.

Password Enter your password for the service provider.

Domain Name

Enter the Domain Name which is provided by your service provider. Remote users can use the Domain Name to access your local network through WAN port.

Interval Mode Choose to use fixed or custom interval.

Update Interval

Specify the update interval to report the changes of the WAN IP address for the DDNS service.

4. 10.3 mDNS

Overview

mDNS (Multicast DNS) Repeater can help forward mDNS request/reply packets between different VLANs. With this function, you can create a forwarding rule to allow the devices in the specified Client

VLAN to discover the mDNS service in the specified Service VLAN. You can also specify the services to be forwarded.

Configuration

  1. Select a site from the drop-down list of Organization. Go to Settings > Services > mDNS.
  2. Click Create New Rule. Configure the parameters.

Create New Rule Name: Status: Enable Device Type: AP Gateway Bonjour Service: Please Select... Manage Bonjour Service Services Network VLAN: (Range: 1-4094. Enter only one VLAN ) Client Network VLAN: (Range: 1-4094. Enter one or multiple VLANs. For example: 1,2-100) Apply Cancel

Name Specify the rule name for identification.

Status Enable or disable this rule.

Device Type Specify the device type for which the rule takes effect.

Bonjour Service Specify the services to be forwarded.

Services Network - VLAN When Device Type is AP, specify the VLANs where the mDNS services are located. You can enter VLAN ranges or VLAN IDs separated by comma.

Client Network - VLAN When Device Type is AP, specify the VLANs where the Client devices are located. You can enter VLAN ranges or VLAN IDs separated by comma.

Services Network - When Device Type is Gateway, specify the networks where the mDNS services are located.

Client Network - Network When Device Type is Gateway, specify the networks where the Client devices are located.

  1. Apply the settings.

4.10.4 SNMP

Overview

SNMP (Simple Network Management Protocol) provides a convenient and flexible method for you to configure and monitor network devices. Once you set up SNMP for the devices, you can centrally manage them with an NMS (Network Management Station).

The controller supports multiple SNMP versions including SNMPv1, SNMPv2c and SNMPv3.

TP-LINK Omada SDN Controller - Overview - 1

Note:

If you use an NMS to manage devices which are managed by the controller, you can only read but not write SNMP objects.

Configuration

Select a site from the drop-down list of Organization. Go to Settings > Services > SNMP and configure the parameters. Then click Apply.

SNMPv1 & SNMPv2c

SNMPv1 & SNMPv2c:

Community String:

TP-LINK Omada SDN Controller - SNMPv1 &amp; SNMPv2c - 1

TP-LINK Omada SDN Controller - SNMPv1 &amp; SNMPv2c - 2

SNMPv3

SNMPv3:

Username:

Password:

TP-LINK Omada SDN Controller - SNMPv3 - 1

TP-LINK Omada SDN Controller - SNMPv3 - 2

TP-LINK Omada SDN Controller - SNMPv3 - 3

SNMPv1 & SNMPv2c Enable or disable SNMPv1 and SNMPv2c globally.

Community String

With SNMPv1 & SNMPv2c enabled, specify the Community String, which is used as a password for your NMS to access the SNMP agent. You need to configure the Community String correspondingly on your NMS.

SNMPv3 Enable or disable SNMPv3 globally.

Username With SNMPv3 enabled, specify the username for your NMS to access the SNMP agent. You need to configure the username correspondingly on your NMS.

Password With SNMPv3 enabled, specify the password for your NMS to access the SNMP agent. You need to configure the password correspondingly on your NMS.

4.10.5 UPnP

Overview

UPnP (Universal Plug and Play) is essential for applications including multiplayer gaming, peer-to-peer connections, real-time communication (such as VoIP or telephone conference) and remote assistance, etc. With the help of UPnP, the traffic between the endpoints of these applications can freely pass the gateway, thus realizing seamless connections.

Configuration

Select a site from the drop-down list of Organization. Go to Settings > Services > UPnP. Enable UPnP globally and configure the parameters. Then click Apply.

UPnP UPnP: Interface: SFP WAN WAN Networks: All Apply Reset

Interface Select the WAN port where UPnP takes effect.

Networks Select the LAN interface where UPnP takes effect.

4. 10. 6 SSH

Overview

SSH (Secure Shell) provides a method for you to securely configure and monitor network devices via a command-line user interface on your SSH terminal.

TP-LINK Omada SDN Controller - Overview - 1

Note:

If you use an SSH terminal to manage devices which are managed by the controller, you can only get the User privilege.

Configuration

Select a site from the drop-down list of Organization. Go to Settings > Services > SSH. Enable SSH Login globally and configure the parameters. Then click Apply.

SSH SSH Login: SSH Server Port: 22 (22 or 1025-65535) Layer 3 Accessibility: Enable i Apply Reset

SSH Server PortSpecify the SSH Sever Port which your network devices use for SSH connections. You need to configure the SSH Server Port correspondingly on your SSH terminal.
Layer 3 AccessibilityWith this feature enabled, the SSH terminal from a different subnet can access your devices via SSH. With this feature disabled, only the SSH terminal in the same subnet can access your devices via SSH.

4. 10.7 Reboot Schedule

Overview

Reboot Schedule can make your devices reboot periodically according to your needs. You can configure Reboot Schedule flexibly by creating multiple Reboot Schedule entries.

Configuration

  1. Select a site from the drop-down list of Organization. Go to Settings > Services > Reboot Schedule. Click + Create New Reboot Schedule to load the following page and configure the parameters.

Create New Reboot Schedule Name: Status: Enable Occurrence: Every Month on 1 at 12:00 in America/Bogota Devices List DEVICE NAME STATUS MODEL FIRMWARE VERSION 86-66-77-98-44-20 CONNECTED TL-ER7206 1.0.0 Build 20200331 Rel 53759 00-00-FF-FF-0E-80 CONNECTED EAP660 HD 1.0.0 Build 20200319 Rel 78769 00-0A-EB-45-F7-A5 CONNECTED TL-SO2210MP 1.0.0 Build 20200408 Rel 75394(a) Showing 1-3 of 3 records ( 1 ) 5 /page Go To page GO Create Cancel

Name Enter the name to identify the Reboot Schedule entry.

Status Enable or disable the Reboot Schedule entry.

Occurrence Specify the date and time for the devices to reboot.

Devices List Select the devices which the Reboot Schedule applies to.

  1. Click Create. The new Reboot Schedule entry will be added to the table.

4. 10.8 Port Schedule

Overview

In Port Schedule, you can set schedules to control the PoE feature of the PoE switch or control the on/off behavior of the switch port. When the PoE feature is disabled, the PoE switches will not supply power to the connected PoE devices during the specified time period, but the switches can still transmit data; when the Port feature is disabled, please check your topology and related configurations to avoid network problems. You can configure PoE or Port Schedule flexibly by creating multiple entries.

Configuration

  1. Select a site from the drop-down list of Organization. Go to Settings > Services > Port Schedule. Click + Create New Port Schedule to load the following page and configure the parameters.

Create New Port Schedule Name: Status: Enable Type: PoE Schedule Port Schedule This function only affects PoE power supply. Time Range: Please select a Time Range Manage Time Range Entries Device List: DEVICE NAME PORTS STATUS MODEL PIRMWARE VERSION 01-04-E8-45-F7-A5 CONNECTED -- Showing 1-1 of 1 records < 1 > 5 page Go To page GO Create Cancel

Name Enter the name to identify the schedule entry.

Status Enable or disable the schedule entry.

Type Type: Specify the schedule type:

PoE Schedule: This function only affects PoE power supply.
Port Schedule: This function affects LAN connections of ports but does not affect PoE power supply. To avoid network problems, please check your topology and related configurations before turning off ports.
Time RangeWhen the Type is PoE Schedule, select the time range when the PoE switches will supply power to the powered devices.
when the Type is Port Schedule, select the time range when the switches will turn on the designated ports.
You can create a Time Range entry by clicking Create New Time Range Entry from the drop down list.
Devices ListWhen Type is PoE Schedule, select the PoE switch and PoE port to apply the schedule.
When Type is Port Schedule, select the switch and port to apply the schedule.
  1. Click Create. The new schedule entry will be added to the table.

4.10.9 IPTV

Overview

IPTV includes two sections: IGMP and IPTV. In IGMP settings, you can enable IGMP proxy to detect multicast group membership information and thus the router is able to forward multicast packets based upon the information. IPTV settings allows you to enable Internet/IPTV/Phone service provided by your ISP.

Configuration

  1. Select a site from the drop-down list of Organization. Go to Settings > Services > IPTV > IGMP, configure the parameters. If you want to configure the IPTV settings, go to next step; if you don't want to configure the IPTV settings, click Apply.

IGMP

IGMP Proxy:

TP-LINK Omada SDN Controller - IGMP - 1

IGMP Version:

v2

TP-LINK Omada SDN Controller - IGMP - 2

IGMP Interface:

Please Select...

TP-LINK Omada SDN Controller - IGMP - 3

IGMP Proxy Enable IGMP Proxy.

IGMP Proxy sends IGMP querier packets to the LAN ports to detect if there is any multicast member connected to the LAN ports.

IGMP Version Select the IGMP version as V2 or V3. The default is IGMP V2.

IGMP Interface Select the WAN port on which the IGMP Proxy takes effect.

  1. Go to Settings > Services > IPTV > IPTV, enable the IPTV features and choose the mode as Bridge or Custom according to your ISP. Then configure the corresponding parameters. Click Apply.

Note that the IPTV section will be hidden if your device is an earlier version that does not support this feature.

IPTV

IPTV:

TP-LINK Omada SDN Controller - IPTV - 1

Mode:

TP-LINK Omada SDN Controller - IPTV - 2

Bridge

TP-LINK Omada SDN Controller - IPTV - 3

Custom

TP-LINK Omada SDN Controller - IPTV - 4

WAN Port:

Please Select...

TP-LINK Omada SDN Controller - IPTV - 5

WAN/LAN1 Mode:

Internet

TP-LINK Omada SDN Controller - IPTV - 6

WAN/LAN2 Mode:

Internet

TP-LINK Omada SDN Controller - IPTV - 7

LAN1 Mode:

Internet

TP-LINK Omada SDN Controller - IPTV - 8

LAN2 Mode:

Internet

TP-LINK Omada SDN Controller - IPTV - 9

IPTV Enable IPTV feature.

Mode Select the appropriate Mode according to your ISP.

Bridge: Select this mode if your ISP requires no other parameters.

Custom: Select this mode if your ISP provides necessary parameters, and configure the parameters according to the requirements of your ISP.

WAN Port Select the WAN port on which the IPTV settings take effect.

Port Mode Select the appropriate Port Mode of the LAN ports to determine which port is used to support Internet service, IPTV service, or IP Phone service.

4. 10. 10 Upgrade Schedule

Overview

Upgrade Schedule allows you to schedule the device upgrade as desired. You can set recurring upgrades or a one-time schedule. When configuring multiple schedules, set different execution times if possible. If execution times overlap, new schedule will not be executed before the current task completes.

Configuration

Select a site from the drop-down list of Organization. Go to Settings > Services > Upgrade Schedule. Set the upgrade schedule and select devices. Click Apply.

Add Upgrade Schedule Name: Status: Enable Type: Execute Auto Upgrade Once Repeat Occurrence: at 2023-09-15 at 12:00 in Coordinated Universal Time Device List: DEVICE NAME STATUS MODEL FIRMWARE VERSION CONNECTED CONNECTED CONNECTED Select 2 of 3 items Showing 1-3 of 3 records < 1 > 5 iPage Go To page: Save Cancel

Name Enter the name to identify the schedule entry.

Status Enable or disable the upgrade schedule.

Type Specify whether to execute auto upgrade once or repeat it.

Occurrence Specify the time for automatic upgrade.

Devices List Select the devices that will upgrade according to the set schedule.

4. 10. 11 DNS Proxy

Overview

DNS Proxy provides the LAN side clients with the DNS query service. It forwards the DNS request from the LAN side clients to the selected upstream DNS server and forwards the DNS reply accordingly.

DNSSEC (DNS Security Extensions), DoT (DNS over TLS), and DoH (DNS over Https) are three security options for DNS Proxy. DNSSEC will verify the integrity of DNS records, and DoT / DoH will encrypt the query.

All of the three options need an upstream DNS server that supports them.

Configuration

  1. Select a site from the drop-down list of Organization. Go to Settings > Services > DNS Proxy.
  2. Configure the parameters, then save the settings.

DNS Proxy DNS Proxy : Enable Proxy Type : DNSSEC DoH DoT DNS Server: . . . Add Bogus DNS Reply : Pass Save Cancel

DNS Proxy Enable or disable the DNS Proxy.

Proxy Type Specify a security option to apply.

DNS Server Specify the upstream DNS server which the DNS requests will be forwarded to. For DoT and DoH, the system provides some known public DNS servers that support these security options. For DoH, the upstream DNS servers are usually websites with https URLs. For DNSSEC and DoT, servers are usually IP address.

Bogus DNS Reply This is an special option for DNSSEC. Choose to pass/drop the bogus reply if the integrity of DNS records failed to be verified (which means the DNS record may be modified and is not trustable).

4. 10. 12 DNS Cache

Overview

DNS caching further speeds up domain name translation/resolution by handling it for recently visited addresses before the request is sent to the internet. Even if your network can use a large number of public DNS servers for translation/resolution, it's still faster to have a local copy.

Configuration

  1. Select a site from the drop-down list of Organization. Go to Settings > Services > DNS Cache.

  2. Enable DNS Cache, configure the parameters, then save the settings.

DNS Cache Enable DNS Cache: ✓ Enable TTL: seconds (Optional, 1 - 85400) Save Cancel

Enable DNS Cache Enable or disable DNS Cache.

TTL Specify the time to live (TTL) value in seconds. When the life cycle of the DNS entry exceeds the TTL value, the DNS cache will be automatically cleared. The range is 1-86400. If it's not specified, the system will use the default TTL value of each DNS message.

4. 10. 13 Export Data

Overview

You can export data of a site to monitor or debug your devices.

Configuration

  1. Select a site from the drop-down list of Organization. Go to Settings > Services > Export Data. Select the type of data from the export list and click Export.

Export Data Export List: Device List Mode: Default Columns All Columns Current Display Columns If you select All or Current Display Columns, data exporting will be time-consuming if there are lots of devices. Site: Default Format: XLSX Send Email: Enable Apply Cancel Export

Export List Device List: Export the list of managed devices.

Client List: Export the list of all clients that are connected to the networks.

Insight-Rogue AP List: Export the list of the rogue APs scanned before.

Log List: Export the list of the logs generated by the controller.

Authorized Client List: Export the list of authorized clients.

Voucher Codes: Export the list of the voucher codes.

Mode Select the columns to export. We recommend selecting Default Columns, which include commonly needed columns such as DEVICE NAME, MAC ADDRESS, MODEL, etc. If you select All Columns or Current Display Columns, data exporting will be time-consuming if there are lots of devices.

Format The data can be exported to the file in the format of .CSV or .XLSX.

Send Email If you want to send the exported data via email, enable Send Email and configure the parameters below:

Report Name: Specify the report name of the email to send.

Occurrence: Specify when to send the email.

Send to: Specify the email addresses to send the exported data to.

4.11 SIM

If your network has devices that connect to the internet via the SIM card, such as the 4G Wi-Fi router, you can configure SIM settings.

4.11.1 Statistics

Launch your controller and select a site from the drop-down list of Organization. Go to Settings > SIM > Statistics.

Statistics Overview

In the upper cards on the Statistics page, you can have a overview of the total/monthly statistics calculated according to the billing/counting method you set. You can click the edit icon to correct the statistics.

Note that the data statistics is for reference only, and the actual data shall be subject to your carrier. You can send messages to your carrier for the most accurate data usage statistics.

Monthly Data Usage 20 MB Monthly SMS Messages 200

Manage SIM Data

In the SIM Data section, you can view the data statistics and set a data limit to better control your data usage so that you will not exceed the data package provided by your carrier.

SIM Data Billing Method: Total Monthly Data Limit: Total Allowance: 0 MB Data Limit Alert: Usage Alert: 0 % Alert SMS Phone Number: (Optional) Send Test Message

Billing Method

Select the billing method, Total count or Monthly count.

If you select the Monthly count, select a Start Date for each monthly count cycle. For example, 2nd indicates that the monthly count cycle is from the 2nd of this month to the 1st of the next month.

Data Limit Specify whether to enable the data limit function.

If turned on, the network will be disconnected when your data usage reaches the allowance.

Total Allowance/ Monthly AllowanceEnter the total/monthly allowance provided by your carrier.The device will automatically disconnect from the internet when your data usage reaches the allowance.
Data Limit Alert Specify whether to enable the SMS alert of data limit.If turned on, the alert message will be sent when your data usage reaches the set allowance percentage or the set allowance.
Usage Alert Set the usage alert percentage.The alert message will be sent when your data usage reaches the set allowance percentage.
Alert SMS Phone NumberEnter the phone number to receive the SMS alert message when your data usage reaches the set allowance percentage or the set allowance.
Send Test Message Send a test SMS to confirm that the number can receive the SMS alert message.

Manage SMS Messages

In the SMS Messages section, you can set SMS quota to better manage SMS usage so that it does not exceed your set quota.

SMS Messages Counting Method: Total Monthly Start Date: 11 th (1.31) SMS Quota Limit: Monthly Allowance: 400 SMS Quota Alert: Usage Alert: 0 % Alert SMS Phone Number: (Optional) Send Test Message.

Counting MethodSelect the counting method, Total count or Monthly count.
If you select the Monthly count, select a Start Date for each monthly count cycle. For example, 2nd indicates that the monthly count cycle is from the 2nd of this month to the 1st of the next month.
SMS Quota Limit Specify whether to enable the SMS quota limit function.
If turned on, your device will be unable to send SMS messages when your SMS quantity reaches the allowance.
Total Allowance/ Monthly AllowanceEnter the total/monthly allowance provided by your carrier.
Your device will be unable to send SMS messages when your SMS quantity reaches the allowance.

SMS Quota Alert Specify whether to enable the SMS alert of SMS limit.

If turned on, the alert message will be sent when your SMS quantity reaches the set allowance percentage.

Note that the alert messages will also be counted in your SMS quantity.

Usage Alert Set the usage alert percentage.

The alert message will be sent when your SMS quantity reaches the set allowance percentage.

Alert SMS Phone Number

Enter the phone number to receive the SMS alert message when your SMS quantity reaches the set allowance percentage.

Send Test Message Send a test SMS to confirm that the number can receive the SMS alert message.

4.11.2 SMS Message

■ SMS Inbox Message

SMS Inbox displays the messages you have received.

Click the Detail icon to view the SMS details. Click the Delete icon to delete the SMS. You can also batch read or delete entries.

SMS Inbox Message FROM MESSAGE Date ACTION Jul 21, 2023 06:34 27 am Jul 21, 2023 09:21 07 am Jun 28, 2023 04:54 27 pm Showing 1-3 of 3 records < 1 > 10 / page Go to page: Go

■ SMS Outbox Message

SMS Outbox displays the messages you have successfully sent.

Click the Detail icon to view the SMS details. Click the Delete icon to delete the SMS. You can also batch delete entries.

SMS Outbox Message TO MESSAGE Data ACTION Jul 21, 2023 06:34:27 am Jul 21, 2023 07:41:07 am Jul 21, 2023 06:34:57 am Showing 1-3 of 3 records < 1 > 10 / page Go to page: Go

Click Export to save outbox messages of specific time period locally.

Export Outbox Messages Date: Oct 29, 2023 ~ Oct 30, 2023 Format: XLSX Export Cancel

Click Create New Message to send a message.

Create New Message Recipient Number: (Optional) Content: Send Message Cancel

4. 11. 3 SMS Settings

■ SMS Inbox/Outbox Policy

In this section, you can set policies related to receiving inboxes.

SMS Inbox/Outbox Policy

SMS Inbox/Outbox:

If SMS inbox/outbox is full, delete the oldest read SMS
If SMS inbox/outbox is full, send e-mail alert to Administrator
If SMS inbox/outbox is full, Forward new SMS with e-mail to Administrator

TP-LINK Omada SDN Controller - SMS Inbox/Outbox Policy - 1

To ensure e-mail sending, please configure the Mail Server.

Apply

Cancel

SMS Inbox/Outbox Select the SMS Inbox/Outbox Policy.

If SMS inbox/outbox is full, delete the oldest read SMS: When the inbox/outbox is full, delete the oldest read SMS to receive the new SMS.

If SMS inbox/outbox is full, send e-mail alert to Administrator: When the inbox/outbox is full, send an email to the administrator, and does not receive the new SMS. To ensure email sending, please configure the Mail Server.

If SMS inbox/outbox is full, forward new SMS with e-mail to Administrator: When the inbox/outbox is full, forward the new SMS to the administrator via email. To ensure email sending, please configure the Mail Server.

Mail Server

In this section, you can configure mail-related parameters. The SMS Inbox/Outbox Policy module will use the configuration information to send emails.

Mail Server

FROM:

TO:

SMTP Server:

SSL:

SMTP Port:

Authentication:

Apply

Cancel

TP-LINK Omada SDN Controller - Mail Server - 1

TP-LINK Omada SDN Controller - Mail Server - 2

TP-LINK Omada SDN Controller - Mail Server - 3

Enable

25

(1-65535)

TP-LINK Omada SDN Controller - Mail Server - 4

Enable

FROM Enter the email address of the sender.

TO Enter the email address of the receiver, which can be the same as or different from the sender's email address.
SMTP Server Enter the domain name or IP address of the SMTP server.
SSL When enabled, the data will be transmitted based on the SSL protocol.
SMTP PortEnter the port used by the SMTP server according to the instructions of your email service provider.
AuthenticationIf the login of the mailbox requires a username and authorization code, enable this option and configure the following parameters:User Name: Enter your email address as the username.Authorization Code: Enter the authorization code that enables a third party to log into the mailbox according to the instructions of your email service provider. Note that the authorization code is not the mailbox's password.

■ Router Command

In this section, you can send specific commands via SMS to interact with the router, and only specific users are allowed to perform these interactions.

Router Command Reboot On Message: Password/PIN: To reboot the router via SMS, send a message starting with "LTE Router Reboot", followed by Password/PIN(e.g. LTE Router Reboot 1234). Query Status On Message: Password/PIN: Query Contents Router Name Router Up-Time Firmware Version MAC Address To get status information from the router, send a message starting with "LTE Router Status", followed by Password/PIN(e.g. LTE Router Status 1234). Access Control List: Phone Number: (Optional) Add Phone Number

Reboot On Message This feature is used to reboot the router via SMS.

Enable this feature and enter the router’s Password/PIN. Then you can send a message starting with “LTE Router Reboot”, followed by the router’s Password/PIN (e.g. LTE Router Reboot 1234) to reboot the router.
Query Status On MessageThis feature is used to get status information from the router via SMS. Enable this feature, enter the router’s Password/PIN, and choose the query contents. Then you can send a message starting with “LTE Router Status”, followed by the router’s Password/PIN (e.g. LTE Router Status 1234) to get status information from the router.

Access Control List

This feature is used to configure the allow phone number list of the above functions.

Enable this feature, select the international telephone area code, and enter the phone number. You can add one or more phone numbers, and only these phone numbers can interact with the router via SMS.

4.12 CLI Configuration

CLI configuration is essentially to configure devices via command lines. It is a supplementary means of GUI configuration. CLI configuration may conflict with GUI configuration.

The Controller supports two types of CLI configuration: Site CLI and Device CLI.

Site CLI

Site CLI supports batch configuration of devices that support CLI configuration on the site.

■ Device CLI

Device CLI supports batch configuration of selected devices.

Currently, CLI configuration only supports switches. Please refer to CLI Reference Guide to understand the CLI commands of TP-Link switches.

If you need to use CLI configuration, please read the precautions and User Guide carefully. You can contact TP-Link technical support if necessary.

After applying the CLI configuration, you can go to Devices > Application Result to view the configuration results.

General Precautions

  1. The GUI and CLI configuration should be planned globally according to the actual network topology and requirements.
  2. To avoid conflicts, it is recommended not to use the CLI to configure the existing functions of the GUI.
    a. When adopting a new device, the Controller will apply configurations to the device in the order of GUI, Site CLI, and then Device CLI. If there is a configuration conflict, the configuration applied last takes effect.
    b. CLI profiles (including Site CLI profiles and Device CLI profiles) will only be sent to devices once after applied, unless the "Apply Again" button in the Application Result is clicked to trigger the full configurations application.
    c. When a device upgrades its firmware, the Controller will apply the full configurations to the device in the order of GUI, Site CLI, and then Device CLI.
    d. Since the configurations applied later will overwrite the previous configurations, the configuration results of different devices may be different after the same function has been modified repeatedly via GUI, Site CLI and Device CLI.
  3. The Controller will not verify the existing GUI and CLI configurations of devices. Be sure to check the existing configurations before performing new configurations. Otherwise, unexpected results may occur after the configurations are applied, and the devices may even go offline.
  4. To avoid configuration conflicts, if you really need to use the CLI to configure a certain function, it is recommended not to configure it via GUI at the same time.

  5. To avoid disconnection of devices from the Controller due to configuration errors or conflicts, it is recommended to configure VLAN, VLAN Interface, IP Address, ACL, etc. via GUI, and avoid modifying related configurations via CLI.

Repeated Configurations

When the same function is configured via CLI multiple times, the previous configuration may be overwritten, and the last configuration shall prevail.

a. It is recommended to confirm the currently effective commands via the CLI configuration viewing function "Show Running Config".
b. If you need to cancel a certain configuration, use the "no" command.
c. If you need to modify a certain configuration, you can enter a new command to overwrite the configuration.
d. Apply the final configuration, and confirm that the function is configured correctly and takes effect via the CLI configuration viewing function.

Execution Failures

If a CLI command fails to be executed, an error will be reported and subsequent commands will be executed. You can view the error details via the error message, and the commands that have been successfully executed before will not be undone. It is recommended to follow the steps below:

a. Use the CLI configuration viewing function (Show Running Config) to confirm the commands that have taken effect. If you need to cancel them, you can enter "no" commands and apply them to devices.
b. Troubleshoot and correct the command error, regenerate the CLI configuration, and apply it to devices.

Command Modification

If you need to modify the commands issued via CLI, please follow the steps below:

a. Use the CLI configuration view function (Show Running Config) to confirm the commands that have taken effect, and sort out the commands that need to be canceled.
b. Enter "no" commands to cancel the configurations, and apply them to devices.

Prohibited Commands

  1. CLI commands such as modifying user name and password, managing VLAN, SDM profile, reboot, reset, upgrade, import and export configurations have been prohibited. When using other CLI commands, please also pay attention to avoid affecting the management of the Controller.
  2. Device CLI supports the variable function. The variable content does not have too many restrictions, for example, you can enter CLI commands, but it is not recommended to use it in this way.

4.12.1 Site CLI

Overview

Site CLI enables batch configurations of all devices that support CLI configuration on the site via command lines.

Configuration

  1. Go to Settings > CLI Configuration > Site CLI.
  2. Click Create New Site CLI Profile and create a CLI profile according to your needs.

Create New Site CLI Profile Name: Loopback Interval Description: Shorten the loopback detection int (Optional) CLI: loopback-detection interval 5 loopback-detection recovery-time 60 Import CLI from Device Import CLI from File Note: 1. The # character is a special command, which indicates entering the configure mode. Please use it in a separate line. If you add other commands after it 2. if a command starts with the ! character, the command will be ignored. Save Cancel

Note:

  • The # character is a special command, which indicates entering the configure mode. Please use it in a separate line. If you add other commands after it in the same line, they will be ignored.
  • If a command starts with the ! character, the command will be ignored.

Name Specify the name of the CLI profile.

Description (Optional) Enter a description for identification.

CLI Enter the command lines manually.

Import CLI from Device Click and select a device that supports CLI configuration to import its running config.

Import CLI from File Click and select an existing command file to import command lines.

  1. Click Save to add the profile. The new profile is in inactive state and will not be applied to devices.

Search Name NAME DESCRIPTION STATUS ACTION Loopback Interval Modify the loopback detection interval Inactive Apply Showing 1-1 of 1 records 10 / page Go To page: Go + Create New Site CLI Profile

  1. Click Apply to apply the CLI. The profile will change to active state and apply configurations to all devices that support CLI configuration on the site.

TP-LINK Omada SDN Controller - Note: - 2

Note:

Once the profile becomes active, you will be unable to edit it.

Configurations applied. Please go the device list to view the CLI application results. View CLI Details Cancel

To check whether the profile is successfully applied to devices and takes effect, click View CLI Details to view the configuration results on the Devices > Application Result page.

TP-LINK Omada SDN Controller - Note: - 2

Note:

Deleting a CLI profile will not take effect on existing configurations on devices. To delete the configurations, use the "no" command.

Device List Application Result Search MAC Name or IP All (5) Gateway/Switches (2) APs (4) All (3) Succeeded (1) Failed (0) Alert (1) Configuration (3) Preconfigured (2) Device NAME IP ADDRESS MAC ADDRESS DEVICE TYPE STATUS ACTION Gateway 192.168.0.1 14-25-05-05-A6-5C Gateway Alert Switch 192.168.0.109 00-5F-67-06-75-34 Switch Succeeded Apply Again Ded: 0 of 2 tests Select/All Showing 1-2 of 2 records < 1 > 10 / page Go To page: Go

4.12.2 Device CLI

Overview

Device CLI enables batch configuration of specific devices via command lines.

Device CLI supports variables. You can use the %x% format to define a variable x, and then set different values for different switches. When the Controller applies the Device CLI configuration to switches, it will automatically modify the variable %x% to the values you set.

Configuration

  1. Go to Settings > CLI Configuration > Device CLI. Click Create New Device CLI Profile and create a CLI profile according to your needs.

Create New Device CLI Profile 1 CLI Template 2 Device Variable Settings Name: Multicast Snooping Description: Drop Unknown Groups (Optional) CLI: to ipv6 snooping to ipv6 snooping drop-unknown ipv6 mid snooping ipv6 mid snooping drop-unknown Variables: ⑧ Note: 1. The if character is a special command, which indicates entering the configure mode. Please use it in a separate line. If you add other commands after it in the same line, they will be ignored. 2. If a command starts with the I character, the command will be ignored. Import CLI from Device Import CLI from File Next Cancel

TP-LINK Omada SDN Controller - Configuration - 2

Note:

  • The # character is a special command, which indicates entering the configure mode. Please use it in a separate line. If you add other commands after it in the same line, they will be ignored.
  • If a command starts with the ! character, the command will be ignored.

Name Specify the name of the CLI profile.

Description (Optional) Enter a description for identification.

CLI Enter the command lines manually. You can enter %xxx% in the CLI template to define variables.

Import CLI from Device Click and select a device that supports CLI configuration to import its running config.

Import CLI from File Click and select an existing command file to import command lines.

  1. Click Next. Select the devices to apply the CLI profile.

Choose Device: Please Select... Save ← Back

  1. Click Save to add the profile. The new profile is in inactive state and will not be applied to devices.

Switch CLI CLI Configuration Precautions View CLI Details > Search Name or Device Name: 0. NAME DEVICE NAME DESCRIPTION STATUS ACTION Multicast Snooping Switch Drop Unknown Groups Inactive Apply Showing 1-1 of 1 records < 1 > 10 / page Go To page Go + Create New Device CLI Profile

  1. Click Apply to apply the CLI. The profile will change to active state and apply configurations to the devices you selected.

① Note:

Once the profile becomes active, you will be unable to edit it.

Configurations applied. Please go the device list to view the CLI application results. View CLI Details Cancel

To check whether the profile is successfully applied to devices and takes effect, click View CLI Details to view the configuration results on the Devices > Application Result page.

① Note:

Deleting a CLI profile will not take effect on existing configurations on devices. To delete the configurations, use the "no" command.

Device List Application Result Search MAC Name is IP All (G) Gateway/Switches (S) APs (A) All (L) Succeeded (1) Failed (0) Alert (1) Configuration (0) Preconfigured (0) Switch Apply DEVICE NAME IP ADDRESS MAC ADDRESS DEVICE TYPE STATUS ACTION Gateway 192.168.0.1 14-EB-B6-B6-A6-5C Gateway Alert Switch 192.168.0.109 00-5F-67-0E-75-34 Switch Succeeded Apply Again Select 6 or 2 items Select All Showing 1-2 of 2 records < 1 > 10 / page Go To page Go

5

Configure the SDN Controller

Controller Settings control the appearance and behavior of the controller and provide methods of data backup, restore and migration:

• 5.1 System Settings
• 5.2 Controller Settings
• 5.3 Server Settings
• 5.4 Account Security
• 5.5 Cloud Access
• 5.6 Maintenance
• 5.7 Migration

TP-LINK Omada SDN Controller - Configure the SDN Controller - 1

5.1 System Settings

Select Global from the drop-down list of Organization in the upper right corner. Go to Settings > System Settings.

5.1.1 Controller Status

In Controller Status, you can view the controller-related information and status.

Controller Status

Controller Name:

Controller_D10410

MAC Address:

58-11-22-0F-70-8C

System Time:

Mar 4, 2024 10:04:22 am

Uptime:

9day(s) 23h 34m 41s

Controller Version:

TP-LINK Omada SDN Controller - Controller Status - 1

Check for Updates

Controller Name

Displays the controller name, which identifies the controller. You can specify the controller name in 5.2.1 General Settings.

MAC Address Displays the MAC address of the controller.

System Time

Displays the system time of the controller. The system time is based on the time zone which you configure in 5.2.1 General Settings.

Uptime Displays how long the controller has been working.

Controller Version Displays the software version of the controller.

5.1.2 HTTPS Certificate

If you have assigned a domain name to the controller for login, to eliminate the "untrusted certificate" error message in the login process, import the corresponding SSL certificate and private key issued by the certificate authority in HTTPS Certificate.

Note:

  • HTTPS Certificate configuration is only available for the Software Controller and Hardware Controller.
  • You need to restart you controller for the imported SSL certificate to take effect.

HTTPS Certificate

TP-LINK Omada SDN Controller - HTTPS Certificate - 1

  • If you have assigned a domain name to the controller for login, to eliminate the "untrusted certificate" error message in the login process, import the corresponding SSL certificate and private key issued by the certificate authority. Then restart your controller for the SSL certificate to take effect.
  • If you cannot access the controller through the assigned domain name after you delete the certificate, please clear your browser cache.
  • When Redirect HTTP to HTTPS is enabled, if you access the Controller http port through a domain name, you will not be automatically redirected. Please delete the HSTS cache.

File Format:

JKS

SSL Certificate:

Import

Keystore Password:

TP-LINK Omada SDN Controller - HTTPS Certificate - 2

TP-LINK Omada SDN Controller - HTTPS Certificate - 3

File Format Select the format of your certificate, and import the certificate file.

SSL Certificate

Import the SSL certificate to create an encrypted link between the controller and server.

JKS: Import your SSL certificate and enter the Keystore Password if your SSL certificate has the password. Otherwise, leave it blank.

PFX: Import your SSL certificate and enter the Private Key Password if your SSL certificate has the password. Otherwise, leave it blank.

PEM: Import your SSL certificate and SSL Key.

TP-LINK Omada SDN Controller - SSL Certificate - 1

Note:

For the PEM-formatted certificate:

  • Starts with: ----BEGIN CERTIFICATE----
  • Ends with: ----END CERTIFICATE----
  • Certificate chain is supported and no blank line is allowed between two certificate chains.

For the PEM-formatted key:

• RSA encryption is required.
- Starts with: ----BEGIN RSA PRIVATE KEY----
- Ends with: ----END RSA PRIVATE KEY ----

- The key can be placed behind certificate file, and they can be imported together.

5.1.3 System Logging

In System Logging, you can customize the log level if needed.

System Logging

Logging Level Type

Custom

TP-LINK Omada SDN Controller - System Logging - 1

  1. The default auto logging level is Info.

  2. Debug logging will generate a lot of logs, which may affect the controller performance. If you need to collect debug logs of certain modules, adjust the logging level of the modules only, and reset the level in time after log collection.

Manager Logs:

Info

Client Info Logs

Info

Network Monitoring Logs:

info

System Setting Logs:

Info

Account Logs:

Info

Log-related Operation Logs:

Info

Others:

Info

Logging Level Type Choose whether to customize the log level.

Manager LogsSelect the log level of the manager module, which mainly includes device management and site-related configurations.
Client Info LogsSelect the log level of the client info module, which mainly includes functions related to client monitoring.
Network Monitoring LogsSelect the log level of the network monitoring module, which mainly includes functions related to data monitoring.
System Setting LogsSelect the log level of the system setting module, which mainly includes system data related functions.
Account Logs Select the log level of the account module, which mainly includes account-related functions.
Log-related Operation LogsSelect the log level of the log-related operation module, which mainly includes related functions of the log page.
Others Select the log level of other modules.

5.1.4 Access Config

In Access Config, you can specify the port used by the controller for management and portal.

① Note:

  • Access Config is only available on the Software Controller and Hardware Controller.
  • Once applying the change of HTTPS and HTTP port, restart the controller to make the change effective.
  • For security, the HTTPS and HTTP port for Potal should be different from that for controller management.

Access Config

Controller Hostname/IP:

172.28.65.72

TP-LINK Omada SDN Controller - Access Config - 1

Auto Refresh IP:

TP-LINK Omada SDN Controller - Access Config - 2

TP-LINK Omada SDN Controller - Access Config - 3

Redirect HTTP to HTTPS:

TP-LINK Omada SDN Controller - Access Config - 4

TP-LINK Omada SDN Controller - Access Config - 5

HTTPS Port for Controller Management:

8043

(443 or 1024-65535)

HTTP Port for Controller Management:

8088

(80 or 1024-65535)

TP-LINK Omada SDN Controller - Access Config - 6

Once applying the change of HTTPS port, HTTP port and HTTP Redirect, restart the controller to make the change effective. After restart, visit the following URLs to log in to the Omada Controller: http://[Omada Controller Host's IP address or URL]:[HTTP Port] https://[Omada Controller Host's IP address or URL]:[HTTPS Port]

Auto Refresh Portal IP:

TP-LINK Omada SDN Controller - Access Config - 7

TP-LINK Omada SDN Controller - Access Config - 8

HTTP redirect to HTTPS for Portal:

TP-LINK Omada SDN Controller - Access Config - 9

TP-LINK Omada SDN Controller - Access Config - 10

HTTPS Port for Portal:

8843

(1024-65535)

HTTP Port for Portal:

8088

(80 or 1024-65535)

TP-LINK Omada SDN Controller - Access Config - 11

Once applying the change of HTTPS and HTTP port, restart the controller to make the change effective. For security, the HTTPS and HTTP port for Portal should be different from that for controller management.

Device Management:

TP-LINK Omada SDN Controller - Access Config - 12

Enable

TP-LINK Omada SDN Controller - Access Config - 13

Controller Hostname/IPEnter the hostname or IP address of the controller which will be used as the Controller URL in the notification email for resetting your controller password. You can keep it default and IP address recognized by the controller will be used as the Controller URL.
Auto Refresh IP(Only for hardware controller) Enable the feature and the hardware controller will refresh its IP address automatically.
Redirect HTTP to HTTPSWith this option enabled, HTTP requests will be redirected to HTTPS connections.
HTTPS Port for Controller ManagementSpecify the HTTPS port used by the controller for management. After setting the port, you can visit https://[Controller Host's IP address or URL]:[HTTPS Port] to log in to the Controller.
HTTP Port for Controller ManagementSpecify the HTTP port used by the controller for management. After setting the port, you can visit https://[Controller Host's IP address or URL]:[HTTP Port] to log in to the Controller.
Auto Refresh Portal IPWhen enabled, the device will automatically use the actual IP address of the Controller as the portal redirection destination. When disabled, you need to enter a domain name or IP address that clients can access.
HTTP redirect to HTTPS for PortalIf enabled, clients will be redirected to Captive Portal using HTTPS instead of HTTP.
HTTPS Port for Portal Specify the HTTPS port used by the controller for Portal.
HTTP Port for Portal Specify the HTTP port used by the controller for Portal.
Device ManagementWhen enabled, the controller will apply the Device Management Hostname/IP you specified to managed devices for remote management.

TP-LINK Omada SDN Controller - Access Config - 14

5.2 Controller Settings

Select Global from the drop-down list of Organization in the upper right corner. Go to Settings > Controller Settings.

5.2.1 General Settings

In General Settings, you can configure general settings of the controller.

■ For Hardware Controller

General Settings

Controller Name:

TP

Country/Region

United States

TP-LINK Omada SDN Controller - General Settings - 1

Time Zone

(UTC-08:00) Pacific Time (US & Canada)

TP-LINK Omada SDN Controller - General Settings - 2

Time Settings:

Auto

○ Get from External NTP Server

Set Manually

Daylight Saving Time:

Enable

Reset Button

TP-LINK Omada SDN Controller - General Settings - 3

Network Settings

Static

DHCP

IP Address:

      1. 242

Netmask:

255.255.255.0

Gateway:

192 . 168 . 0 . 1

Primary DNS

192 . 168 . 10 . 13

Secondary DNS

0 . 0 . 0 . 0

(Optional)

Controller Name Specify the Controller Name to identify the controller.

Country/Region Select the location of the controller.

The configuration here only takes effect on the controller. To configure the Country/Region for sites, go to the Site Configuration.

Time Zone

Select the Time Zone of the controller according to your region. For controller settings and statistics, time is displayed based on the Time Zone.

The configuration here only takes effect on the controller. To configure the Time Zone for sites, go to the Site Configuration.

Time Settings Choose a method to set the system time.
Auto: Get the time automatically from the built-in NTP server.
Get from External NTP Server: Specify one or multiple NTP servers to get time from. The NTP server will be applied to all APs under the site. The controller will first use the specified external NTP server to get time; if that fails, it will then use the built-in NTP server.
Set Manually: Set the system time manually.
Daylight Saving TimeEnable the feature if your country/region implements DST. When it is enabled, the iconDSTwill appear on the upper right, showing the DST settings and status.
Time Offset Select the time added in minutes when Daylight Saving Time starts.
Starts OnSpecify the time when the DST starts. The clock will be set forward by the time offset you specify.
Ends On Specify the time when the DST ends.The clock will be set back by the time offset you specify.
Primary NTP Server/Secondary NTP ServerEnter the IP address of the primary and secondary NTP (Network Time Protocol) server.NTP servers assign network time to the controller.
Reset Button With this feature enabled, the controller can be reset via reset button.
Network Settings Select one way for the controller to get IP settings.
Static: You need to specify theIP address, Netmask, Gateway, Primary DNS, and SecondaryDNS for the controller.
DHCP: The controller get IP settings from the DHCP server. If the controller fails to get IP settings from the DHCP server, it will use theFallback IP AddressandFallback Netmask.

■ For Software Controller / Cloud-Based Controller

General Settings

Controller Name:

TP

Country/Region:

United States

TP-LINK Omada SDN Controller - General Settings - 1

Time Zone :

(UTC) Coordinated Universal Time

TP-LINK Omada SDN Controller - General Settings - 2

Daylight Saving Time:

TP-LINK Omada SDN Controller - General Settings - 3

Enable

TP-LINK Omada SDN Controller - General Settings - 4

  • DST is applicable only when the device supports the feature. To make DST work properly, it is recommended to upgrade your devices to the latest firmware version.
    • The DST configuration here only takes effect on the controller. To configure the DST for sites, go to the Site Configuration.
  • With DST configured, the valid duration of Local User will be influenced accordingly.

Time Offset :

60 Minutes

Starts On:

Week

Day

Time

1st

Sunday

January

00:00

TP-LINK Omada SDN Controller - General Settings - 5

Ends On:

Week

Day

Month

Time

1st

Sunday

January

00:00

TP-LINK Omada SDN Controller - General Settings - 6

Controller Name Specify the Controller Name to identify the controller.

Country/Region Select the location of the controller.

The configuration here only takes effect on the controller. To configure the Country/Region for sites, go to the Site Configuration.

Time Zone

Select the Time Zone of the controller according to your region. For controller settings and statistics, time is displayed based on the Time Zone.

The configuration here only takes effect on the controller. To configure the Time Zone for sites, go to the Site Configuration.

Daylight Saving Time Enable the feature if your country/region implements DST.

Time Offset Select the time added in minutes when Daylight Saving Time starts.

Starts On

Specify the time when the DST starts. The clock will be set forward by the time offset you specify.

Ends On Specify the time when the DST ends. The clock will be set back by the time offset you specify.

5.2.2 User Interface

In User Interface, you can customize the User Interface settings of the controller according to your preferences.

User Interface

Language:

English

Use 24-Hour Time:

TP-LINK Omada SDN Controller - User Interface - 1

Statistic/Dashboard Timezone

Site's

Fixed Menu:

TP-LINK Omada SDN Controller - User Interface - 2

Dark Settings:

TP-LINK Omada SDN Controller - User Interface - 3

Show Pending Devices:

TP-LINK Omada SDN Controller - User Interface - 4

Refresh Button:

TP-LINK Omada SDN Controller - User Interface - 5

Refresh Interval:

2 Minutes

Enable WebSocket Connection:

TP-LINK Omada SDN Controller - User Interface - 6

Controller Update Notification:

TP-LINK Omada SDN Controller - User Interface - 7

Cloud Firmware Detection:

TP-LINK Omada SDN Controller - User Interface - 8

Devices Update Notification:

TP-LINK Omada SDN Controller - User Interface - 9

Language Select the language to display the user interface.

Use 24-Hour Time

With Use 24-Hour Time enabled, time is displayed in a 24-hour format. With Use 24-Hour Time disabled, time is displayed in a 12-hour format.

Statistic/Dashboard Timezone

Select which Timezone the time of statistics and the dashboard is based on.

Site's: Site's Timezone is set in Site Configuration of the corresponding site.

Browser's: Browser's Timezone is synchronized with the browser configuration.

Controller's: Controller's Timezone is set in General Settings of the controller.

UTC: UTC (Coordinated Universal Time) is the common time standard across the world.

Fixed Menu With Fixed Menu enabled, the menu icons are fixed and do not prompt menu texts when your mouse hovers on them.

Dark Settings When enabled, the system will switch to a dark theme.

Show Pending DevicesWith this option enabled, the devices in Pending status will be shown, and you can determine whether to adopt them. With this option disabled, they will not be shown, thus you cannot adopt any new devices.
Refresh Button Enable or disable Refresh Button in the upper right corner of the configuration page.
Refresh IntervalSelect how often the controller automatically refreshes the data displayed on the page.
Enable WebSocket ConnectionWith WebSocket Connection enabled, the controller updates in real time some part of its data on the web interface, which is transmitted using the WebSocket service, so that you don't need to refresh them manually.
Controller Update NotificationWith this feature enabled, you will receive an update notification when a new controller version is available.
Cloud Firmware DetectionThis option is a global switch. If it is turned off, all cloud firmware detections will not be executed and prompted, including all upgrade schedule functions in the site.
Devices Update NotificationWith this feature enabled, you will receive an update notification when a new firmware version for your device is available.

5.2.3 Services

In Services, you can configure remote logging and client idle threshold.

Services Remote Logging: Enable ⓘ Client Idle Threshold: 5 Minutes (3-10) ⓘ

Remote LoggingWith this feature configured, Omada Controller will send the system log to the log server once it is generated.When enabled, you need to specify the Syslog Server IP/Hostname and Syslog Server Port.
Client Idle ThresholdThe controller will consider a client offline (thus disconnect it) when it is idle for longer than the specified threshold. If the specified threshold is too short, clients may be disconnected frequently.

5.2.4 History Data Retention

In History Data Retention, you can specify how the controller retains its data.

History Data Retention

Clients' History Data

Enable

TP-LINK Omada SDN Controller - History Data Retention - 1

When enabled, known clients, client history and client logs will be recored. This will occupy much storage space.

Client History:

1 Month

Known Client:

1 Month

Time-Based Settings

TP-LINK Omada SDN Controller - Time-Based Settings - 1

The settings below will affect the graphical display of Statistics and Network Report.

Time Series with 5 Minutes Granularity:

2 Days

Time Series with Hourly Granularity:

7 Days

Time Series with Daily Granularity:

3 Months

Time Series with Weekly Granularity:

6 Months

Others

Portal Authentication Records:

1 Month

Log:

1 Month

Rogue AP

1 Month

Clients' History DataWhen enabled, known clients, client history and client logs will be recorded. This will occupy much storage space.
Client HistorySpecify the retention time of client online and offline records. Corresponding to Insight-Past Connection.
Known ClientSpecify the retention time of known client data. Corresponding to Insight-Known Clients.
Time Series with 5 Minutes GranularityDisplays the retention time of AP, switch, gateway, and client data. Corresponding to 5-minute statistics.
Time Series with Hourly GranularityDisplays the retention time of AP, switch, gateway, and client data. Corresponding to hourly statistics.
Time Series with Daily GranularitySpecify the retention time of AP, switch, gateway, and client data. Corresponding to daily statistics.
Time Series with Weekly GranularitySpecify the retention time of client data. Corresponding to weekly statistics.
Portal Authentication RecordsSpecify the retention time of portal authorization records. Corresponding to Insight-Past Portal Authorization.

Log Specify the retention time of logs.

Rogue AP Specify the retention time of scanned Rogue APs. Corresponding to Insight-Rogue APs.

5.2.5 Join User Experience Improvement Programm

You can participate in the user experience improvement program and help improve the quality and performance of TP-Link products by sending statistics and usage information.

Join User Experience Improvement Program

TP-LINK Omada SDN Controller - Join User Experience Improvement Programm - 1

By joining this program, you have fully read and understood our User Experience Improvement Program Policy. You can opt out of the program at any time.

5.3 Server Settings

Select Global from the drop-down list of Organization in the upper right corner. Go to Settings > Server Settings.

5.3.1 Mail Server

With the Mail Server, the controller can send emails for resetting your password, pushing notifications, and delivering the system logs. The Mail Server feature works with the SMTP (Simple Mail Transfer Protocol) service provided by an email service provider.

Configuration

  1. Log in to your email account and enable the SMTP (Simple Mail Transfer Protocol) Service. For details, refer to the instructions of your email service provider.
  2. Select Global from the drop-down list of Organization in the upper right corner. Go to Settings > Server Settings. In Mail Server, enable SMTP Server and configure the parameters. Then apply the settings.

Mail Server With the Mail Server, the controller can send emails for resetting your password, pushing notifications, and delivering the system logs. For security reasons, we recommend that you configure Mail Server carefully. SMTP Server: Enable SMTP: Port: 465 (1-65535) SSL: Enable Authentication: Enable Username: Password: Sender Address: (Optional) Test SMTP Server: Send Test Email to Send

SMTP Enter the URL or IP address of the SMTP server according to the instructions of the email service provider.

Port Configure the port used by the SMTP server according to the instructions of the email service provider.
SSL Enable or disable SSL according to the instructions of the email service provider. SSL (Secure Sockets Layer) is used to create an encrypted link between the controller and the SMTP server.
AuthenticationEnable or disable Authentication according to the instructions of the email service provider. If Authentication is enabled, the SMTP server requires the username and password for authentication.
Username When Authentication is enabled, enter your email address as the username.
Password When Authentication is enabled, enter the authentication code as the password, which is provided by the email service provider when you enable the SMTP service.
Sender Address(Optional) Specify the sender address of the email. If you leave it blank, the controller uses your email address as the Sender Address.
Test SMTP ServerTest the Mail Server configuration by sending a test email to an email address that you specify.

5.3.2 Built-in RADIUS

A RADIUS server maintains a database which stores the identity information of legal users. It authenticates users against the database when the users are requesting to access the network, and provides authorization and accounting services for them.

For the Software Controller and Hardware Controller, you can set up the built-in RADIUS server for user authentication.

TP-LINK Omada SDN Controller - Built-in RADIUS - 1

Note:

Built-in RADIUS server is only available for the Software Controller and Hardware Controller.

Built-in RADIUS Built-in RADIUS: Status: Disabled Server Address Type: Manually Auto Secret: Password Authentication Port: 1812 (1-65535) Enable Tunneled Reply: Enable

Built-in RADIUS Toggle on to enable the built-in RADIUS server.

Status Displays the current status of the server.

Server Address Type Specify the built-in server address type.

When the controller is on a computer with multiple network adapters, and the type is configured as Auto, the server address will be sent to the device according to the ports connected to the device.

When the type is configured as Manual, the user needs to manually configure the server's IP address, which should be the address the device can communicate with.

Secret Specify the RADIUS server key.

Authentication Port Specify the RADIUS server authentication port.

Enable Tunneled Reply

Enable this option if you want to allow the reply of the Tunneled Reply-related attributes to the device. Only after this option is enabled can the client be assigned a VLAN.

5.3.3 Radius Proxy Server

A Radius proxy authenticates and authorizes users or devices and also tracks the usage of those services. You can configure the Radius Proxy Server for user authentication.

Radius Proxy Server

Radius Proxy Server:

TP-LINK Omada SDN Controller - Radius Proxy Server - 1

Status:

Disabled

Authentication Port:

1812

(1-65535)

Radius Proxy Server Toggle on to enable the Radius Proxy Server.

Status Displays the current status of the server.

Authentication Port

Specify the port that the controller listens for to receive radius messages from devices.

5.4 Account Security

You can enable Two-Factor Authentication (2FA) to improve the security of the controller.

Select Global from the drop-down list of Organization in the upper right corner. Go to Settings > Account Security. Enable or disable the Two-Factor Authentication (2FA) according to your needs.

Security

Two-Factor Authentication (2FA):

TP-LINK Omada SDN Controller - Account Security - 1

TP-LINK Omada SDN Controller - Account Security - 2

With this function enabled on the controller, all accounts will be forced to enable Two-Factor Authentication (2FA).

Two-Factor Authentication (2FA)

This function improves the security of the controller by requiring two factors of identification to access resources and data. With this function enabled, all accounts will be forced to enable 2FA upon user login. You can also enable 2FA for accounts on the Admin > User page.

TP-LINK Omada SDN Controller - Account Security - 3

5.5 Cloud Access

Overview

With Cloud Access, it's convenient for you to manage your controller from anywhere, as long as you have access to the internet.

Configuration

To manage your controller from anywhere, follow these steps:

  1. Prepare your controller for Cloud Access

■ For Software Controller / Hardware Controller:

Note:

  • Before you start, make sure your Software Controller Host or Hardware Controller has access to the internet.
  • If you have enabled cloud access and bound your TP-Link ID in the quick setup wizard, skip this step.

1) Select Global from the drop-down list of Organization in the upper right corner. Go to Settings > Cloud Access. Enable Cloud Access.

Cloud Access Cloud Access: Cloud Access Status: CONNECTED

2) Enter your TP-Link ID and password. Then click Log In and Bind.

Log In and Bind Your TP-Link ID Enter the email address and password of your TP-Link ID. Note that it is not the account that you have used to log in to this controller. TP-Link ID: Email Address No TP-Link ID? Register Now Password: Log In and Bind Cancel

■ For Cloud-Based Controller

Your Cloud-Based Controller is based on the Cloud, so it's naturally accessible through Cloud Service. No additional preparation is needed.

2. Access your controller through Cloud Service

Go to https://omada.tplinkcloud.com and login with your TP-Link ID and password. A list of controllers that have been bound with your TP-Link ID will appear. Then click → Launch to manage the controller.

All OC200 Software Controller Add hardware controller NAME MAC ADDRESS LOCAL IP STATUS SITES DEVICES CLIENTS ALERTS VERSION FIRMWARE ACTION Omada Controller_381C5F - 10.0.5.23 Online 2 1 0 37 4.0.7 - Launch Unprd Page Size: 10 < < 1 > >

5.6 Maintenance

You can back up the configuration and data of your controller to prevent any loss of important information.

If necessary, restore the controller to a previous status using the backup file.

5.6.1 Backup

■ Manual Backup

Select Global from the drop-down list of Organization in the upper right corner. Go to Settings > Maintenance. In Backup, click Export to export and save the backup file.

If you want to export the data to a file server, configure the parameters accordingly and click Export.

Backup & Restore

Backup

Retained Data Backup:

Settings Only

TP-LINK Omada SDN Controller - Backup &amp; Restore - 1

TP-LINK Omada SDN Controller - Backup &amp; Restore - 2

Retained Data Backup has been set as Settings Only, no data will be backed up. Note that all configurations and data about licenses will not be backed up, including Auto-Activation, Auto-Renewal and license logs.

Retain User Info:

TP-LINK Omada SDN Controller - Backup &amp; Restore - 3

Enabled

TP-LINK Omada SDN Controller - Backup &amp; Restore - 4

Export:

TP-LINK Omada SDN Controller - Backup &amp; Restore - 5

Export to Local File

TP-LINK Omada SDN Controller - Backup &amp; Restore - 6

Export to File Server

Export

Retained Data Backup Select the time range in the drop-down menu of Retained Data Backup. Only configuration and data within the time range is backed up. If you select Settings Only, only configuration (no data) is backed up.

Retain User Info

With this option enabled, all local and cloud user information except for the main admin will be retained. Make sure Cloud Access is enabled on the Controller to be restored. Otherwise the Cloud account will not be retained correctly.

Export Select where you want to export the data to.

Export to Local File: Export and save the data locally. It is not supported when accessing the controller via cloud.

Export to File Server: Export and save the data to a file server. Select the desired file server type (FTP / TFTP / SFTP / SCP) and configure the parameters.

■ Auto Backup

With Auto Backup enabled, the controller will be scheduled to back up the configurations and data automatically at the specified time. You can easily restore the configurations and data when needed.

TP-LINK Omada SDN Controller - ■ Auto Backup - 1

Note:

• For OC200, Auto Backup is available only when it is powered by a PoE device and a storage device is connected to its USB port.
- On the Cloud-Based Controller, you have no need to configure Auto Backup. It will automatically save your configurations and data on the cloud.

Select Global from the drop-down list of Organization in the upper right corner. Go to Settings > Maintenance. In Auto Backup, enable Auto Backup and configure the parameters. Click Apply.

Auto Backup Auto Backup: Auto Backup is available only when it is powered by a PoE device and a storage device is connected to its USB port. Occurrence: Every Day at 00:00 in Beijing, Chongqing, Hong Kong, Urumqi Retained Data Backup: All Time Retained Data Backup has been set as All Time, all data will be backed up. Retain User Info: Enable Storage: Save to Local File (the same path as the controller software) Save to File Server Saving Path: Maximum Number of Files: 7 (1-50)

OccurrenceSpecify when to perform Auto Backup regularly. Select Every Day, Week, Month, or Year first and then set a time to back up files.Note the time availability when you choose Every Month. For example, if you choose to automatically backup the data on the 31st of every month, Auto Backup will not take effect when it comes to the month with no 31st, such as February, April, and June.
Retained Data Backup Select the length of time in days that data will be backed up.
Settings Only: Back up controller settings only.7 Days/30 Days/60 Days/90 Days/180 Days/365 Days: Back up the data in the recent days.All Time: (Only for Software Controller) Back up all data in the controller.
Retain User InfoWith this option enabled, all local and cloud user information except for the main admin will be retained. Make sure Cloud Access is enabled on the Controller to be restored. Otherwise the Cloud account will not be retained correctly.

Storage Select where you want to save the backup file.

Save to Local File: The backup file will be saved as a local file.

Save to File Server: The backup file will be saved in the specified file server. Four types of file server are available: FTP, TFTP, SFTP, and SCP.

Saving Path (Only for Hardware Controller) Select a path to save the backup files.

Maximum Number of Files Specify the maximum number of backup files to save.

You can view the name, backup time and size of backup files in Backup Files List.

Backup Files List

FILE NAMEBACKUP TIMESIZEACTION
autobackup_30days_20230525_1026.cfg2023-05-2510:26:00 am7.37 KB

To restore, export or delete the backup file, click the icon in the Action column.

TP-LINK Omada SDN Controller - Note: - 2

Restore the configurations and data in the backup file. All current configurations will be replaced after the restoration.

To keep the backup data safe, please wait until the operation is finished. This will take several minutes.

TP-LINK Omada SDN Controller - Note: - 3

Export the backup file. The exported file will be saved in the saving path of your web browser.

TP-LINK Omada SDN Controller - Note: - 4

Delete the backup file.

TP-LINK Omada SDN Controller - Note: - 5

Note:

If the backup file is saved to file server and the type SCP / TFTP is selected, it will not included in the Backup Files List, and it cannot be exported, restored, or deleted.

5.6.2 Restore

Select Global from the drop-down list of Organization in the upper right corner. Go to Settings > Maintenance. In Restore, click Browse and select a backup file from your computer or file server. Click Restore.

Restore

Import:

TP-LINK Omada SDN Controller - Restore - 1

Import from Local File

TP-LINK Omada SDN Controller - Restore - 2

Import from File Server

Retain Device Info:

TP-LINK Omada SDN Controller - Restore - 3

Enable

Restore :

Please select a file.

Browse

Restore

TP-LINK Omada SDN Controller - Restore - 4

TP-LINK Omada SDN Controller - Restore - 5

Note:

  • The controller will be restored to the selected file and all current configurations will be lost.
  • Only the configuration file of controller v4.1.5 or above is supported.
  • The current controller only supports the configuration file of the controller with the same or a smaller first-three-part version number (Major.Minor.Patch).

Import Select where you store the restore file.

Import from Local File: Import the data locally. It is not supported when accessing the controller via cloud.

Import from File Server: Import the data from a file server. Select the desired file server type (FTP / TFTP / SFTP / SCP) and configure the parameters.

Retain Device Info Select this option if you want to retain device information.

Restore Select the backup file to restore the information.

5.6.3 Export for Support

Select Global from the drop-down list of Organization in the upper right corner. Go to Settings > Maintenance. In Export for Support, you can export configuration data and running logs for technical support to diagnose network problems. The exported data will not contain users' personal information.

Export for Support

Export configuration data and running logs for technical support to diagnose network problems. The exported data will not contain users' personal information.

Export Running Logs

Export Configuration Data

Export Running Logs Click to export running logs.

Export Configuration Data Click to export configuration data.

TP-LINK Omada SDN Controller - Export Configuration Data - 1

Note:

Configuration data cannot be imported into the controller through restore.

5.6.4 Export Data

You can export data to monitor or debug your devices.

Select Global from the drop-down list of Organization in the upper right corner. Go to Settings > Export Data. Select the type of data from the export list and click Export.

Export Data Export List: Device List Mode: Default Columns All Columns Current Display Columns If you select All or Current Display Columns, data exporting will be time-consuming if there are lots of devices. Format: XLSX Send Email: Enable Apply Cancel Export

Export List Device List: Export the list of managed devices.

Client List: Export the list of all clients that are connected to the networks.

Insight-Rogue AP List: Export the list of the rogue APs scanned before.

Log List: Export the list of the logs generated by the controller.

Authorized Client List: Export the list of authorized clients.

Voucher Codes: Export the list of the voucher codes.

Mode Select the columns to export. We recommend selecting Default Columns, which include commonly needed columns such as DEVICE NAME, MAC ADDRESS, MODEL, etc. If you select All Columns or Current Display Columns, data exporting will be time-consuming if there are lots of devices.

Format The data can be exported to the file in the format of .CSV or .XLSX.

Send Email If you want to send the exported data via email, enable Send Email and configure the parameters below:

Report Name: Specify the report name of the email to send.

Occurrence: Specify when to send the email.

Send to: Specify the email addresses to send the exported data to.

TP-LINK Omada SDN Controller - Export Data - 2

5.7 Migration

Migration services allow users to migrate the configurations and data to any other controller. Migration services include Site Migration and Controller Migration, covering all the needs to migrate both a single site and the whole controller.

5.7.1 Site Migration

Overview

Site Migration allows the administrators to export a site from the current controller to any other controller that has the same version. All the configurations and data of the site will be migrated to the target controller.

The process of migrating configurations and data from a site to another controller can be summarized in three steps: Export Site, Migrate Site and Migrate Devices.

Site Migration

TP-LINK Omada SDN Controller - Site Migration - 1

flowchart
graph LR
    A["Site A on Controller A"] --> B["Site A on Controller B"]
    B --> C["1"]
    B --> D["2"]
    B --> E["3"]

Export Site Migrate Site Migrate Devices

Export the configurations and data of Site A on Controller A

Import the configurations and data of Site A to Controller B

Migrate the devices on Site A to Controller B

Step1: Export Site

Export the configurations and data of the site to be migrated as a backup file.

Step2: Migrate Site

In the target controller, import the backup file of the original site.

Step3: Migrate Devices

Migrate the devices which are on the original site to the target controller.

Configuration

To migrate a site to another controller, follow these steps below.

Note:

The connection to internet will be lost for several minutes during the migration. Clients need to connect the wireless network again after the migration is completed. Please choose the time to start migration operation carefully.

Export Site Migrate Site Migrate Devices

  1. Select Global from the drop-down list of Organization in the upper right corner. Go to Settings >Migration. On the Site Migration tab, click start button on the following page.

Site Migration Controller Migration Site Migration Site Migration allows Omada administrators to export a site from the current controller to any other controller that has the same version. All the configurations and data of the site will be migrated to the target controller. Warning: The connection to internet will lost for several minutes during the migration. Clients need to connect the wireless network again after the migration is completed. Please choose the time to start migration operation carefully. Start

  1. Select the site to be imported into the second controller in the Select Site drop-down list. Select where you want to export and save the backup file. Click Export to download the file of the current site. If you have backed up the file, click Skip.

Select a site and export its configurations as a backup file. The file can be imported to any other controller that has the same version. Select Site: Default Export: Export to Local File Export to File Server Export Skip

Export Site Migrate Site Migrate Devices

  1. Start and log in to the target controller, click the top-right corner of the

screen and select ↑ Import Site, and then the following window will pop up. Note that for controller v 4.3.0 and above, only the file from the controller with the same major and minor version number can be imported.

Import Site Site Name: Choose File: Please select a file. Browse For controller v 4.3.0 and above, only the file from the controller with the same major and minor version number can be imported. Import Cancel

  1. Enter a unique name for the new site. Click Browse to upload the file of the site to be imported and click Import to import the site.
  2. After the file has been imported to the target controller, go back to the previous controller and click Confirm.

Site Migration Controller Migration ✓ Export Site —— 2 Migrate Site —— 3 Migrate Devices —— 4 Done To migrate your site, import the backup file into your target controller. Log into the target controller and go to Site Management to click the Import Site in the Site Management drop-down menu and upload the backup file of your site. Confirm Skip

Export Site Migrate Site Migrate Devices

  1. Enter the IP address or URL of your target controller into Controller IP/Inform URL input filed. In this case, the IP address of the target controller is 10.0.3.23.

Site Migration Controller Migration ✓ Export Site —— ✓ Migrate Site —— 3 Migrate Devices —— 4 Done Select the devices to be migrated and enter the URL or IP address of your target controller. The selected devices will try to discover the target controller. Controller IP/Inform URL: 10.0.3.23

TP-LINK Omada SDN Controller - Export Site Migrate Site Migrate Devices - 2

Note:

Make sure that you enter the correct IP address or URL of the target controller to establish the communication between managed devices and your target controller. Otherwise the managed devices cannot be adopted by the target controller.

  1. Select the devices that are to be migrated by clicking the box next to each device. By default, all the devices are selected. Click Migrate Devices to migrate the selected devices to the target controller.

Site Migration Controller Migration ✓ Export Site ✓ Migrate Site 3 Migrate Devices 4 Done Select the devices to be migrated and enter the URL or IP address of your target controller. The selected devices will try to discover the target controller. Controller IP/Inform URL: 10.0.3.23 Device List: ✓ DEVICE NAME STATUS MODEL ✓ CC-32-E5-A4-B1-AC CONNECTED TL-ER7206 V1.0 ✓ switch CONNECTED TL-SG2008P V1.0 Select 2 of 2 items select all Showing 1-2 of 2 records < 1 > 10 /page Go To page: GO Migrate Devices

  1. Verify that all the migrated devices are visible and connected on the target controller. When all the migrated devices are in Connected status on the Device page on the target controller, click Forget Devices to finish the migration process.

Site Migration Controller Migration ✓ Export Site ✓ Migrate Site ✓ Migrate Devices 4 Done Migration succeeded! We suggest you forget the successfully migrated devices. Go to the Device page of your target controller and check if the migrated devices are visible and connected. This process may take several minutes. Device List: ✓ DEVICE NAME STATUS MODEL ✓ CC-32-E5-A4-B1-AC CONNECTED TL-ER7206 V1.0 ✓ CC-32-E5-G9-B5-B0 CONNECTED TL-SG2008P V1.0 Select 2 of 2 items select all Showing 1-2 of 2 records < 1 > 10 /page Go To page GO Forget Devices

  1. When the migration process is completed, all the configuration and data are migrated to the target controller. You can delete the previous site if necessary.

5.7.2 Controller Migration

Overview

Controller Migration allows administrators to migrate the configurations and data from the current controller to any other controller that has the same version.

The process of migrating configurations and data from the current controller to another controller can be summarized in three steps: Export Controller, Migrate Controller and Migrate Devices.

Controller Migration
TP-LINK Omada SDN Controller - Overview - 1

flowchart
graph LR
    A["Controller A"] -->|dashed arrow| B["Controller B"]
    B -->|dashed arrow| A
    style A fill:#cce5ff,stroke:#333
    style B fill:#cce5ff,stroke:#333

Export Controller Migrate Controller Migrate Devices

Export the configurations and data of Controller A

Import the configurations and data of Controller A to Controller B

Migrate the devices on Controller A to Controller B

Step1: Export Controller

Export the configurations and data of the current controller as a backup file.

Step2: Migrate Controller

In the target controller, import the backup file of the current controller.

Step3: Migrate Devices

Migrate the devices on the current controller to the target controller.

Configuration

To migrate your controller, follow these steps below.

Note:

The connection to internet will be lost for several minutes during the migration. Clients need to connect the wireless network again after the migration is completed. Please choose the time to start migration operation carefully.

Export Controller Migrate Controller Migrate Devices

  1. Select Global from the drop-down list of Organization in the upper right corner. Go to Settings >Migration. On the Controller Migration tab, click start button on the following page.

TP-LINK Omada SDN Controller - Export Controller Migrate Controller Migrate Devices - 1

Site Migration

TP-LINK Omada SDN Controller - Export Controller Migrate Controller Migrate Devices - 2

Controller Migration

TP-LINK Omada SDN Controller - Export Controller Migrate Controller Migrate Devices - 3

flowchart
graph TD
    A["服务器设备"] --> B["服务器设备"]
    B --> A

Controller Migration

Controller Migration allows Omada administrators to migrate your configurations and data from the current controller to any other controller that has the same version.

Warning: The connection to internet will lost for several minutes during the migration. Clients need to connect the wireless network again after the migration is completed. Please choose the time to start migration operation carefully.

Start

  1. Select the length of time in days that data will be backed up in the Retained Data Backup, and where you want to export and save the data. Click Export to export the configurations and data of your current controller as a backup file. If you have backed up the file, click Skip.

TP-LINK Omada SDN Controller - Controller Migration - 1

Export the configurations and data of your current controller as a backup file.

The file can be imported to any other controller that has the same version.

Retained Data Backup:

Settings Only

TP-LINK Omada SDN Controller - Export the configurations and data of your current controller as a backup file. - 1

TP-LINK Omada SDN Controller - Export the configurations and data of your current controller as a backup file. - 2

Retained Data Backup has been set as Settings Only, no data will be backed up. Note that all configurations and data about licenses will not be backed up, including Auto-Activation, Auto-Renewal and license logs.

Export:

TP-LINK Omada SDN Controller - Export the configurations and data of your current controller as a backup file. - 3

Export to Local File

TP-LINK Omada SDN Controller - Export the configurations and data of your current controller as a backup file. - 4

Export to File Server

Export

Skip

Export Controller Migrate Controller Migrate Devices

  1. Log in to the target controller. Select Global from the drop-down list of Organization in the upper right corner. Go to Settings > Maintenance > Backup & Restore. Click Browse to locate and choose the backup file of the previous controller. Then click Restore to upload the file.

Backup & Restore Backup Retained Data Backup: Settings Only Retained Data Backup has been set as Settings Only, no data will be backed up. Note that all configurations and data about licenses will not be backed up, including Auto-Activation, Auto-Renewal and license logs. Export: Export to Local File Export to File Server Export Restore Import: Import from Local File Import from File Server Restore: Browse Restore

  1. After the file has been imported to the target controller, go back to the previous controller and click Confirm.

Site Migration Controller Migration Export Controller —— 2 Migrate Controller —— 3 Migrate Devices —— 4 Done Log into the target controller and go to Maintenance- Backup & Restore and upload the backup file of your controller. Confirm Skip

Export Controller Migrate Controller Migrate Devices

  1. Enter the IP address or URL of your target controller into Controller IP/Inform URL input filed. In this case, the IP address of the target controller is 10.0.3.23.

Site Migration Controller Migration ✓ Export Controller ✓ Migrate Controller 3 Migrate Devices 4 Done Select the devices to be migrated and enter the URL or IP address of your target controller. The selected devices will try to discover the target controller. Controller IP/Inform URL: 10.0.3.23

TP-LINK Omada SDN Controller - Export Controller Migrate Controller Migrate Devices - 2

Note:

Make sure that you enter the correct IP address or URL of the target controller to establish the communication between managed devices and your target controller. Otherwise the managed devices cannot be adopted by the target controller.

  1. Select the devices that are to be migrated by clicking the box next to each device. By default, all the devices are selected. Click Migrate Devices to migrate the selected devices to the target controller.

Site Migration Controller Migration ✓ Export Controller ✓ Migrate Controller 3 Migrate Devices 4 Done Select the devices to be migrated and enter the URL or IP address of your target controller. The selected devices will try to discover the target controller. Controller IP/Inform URL: 10.0 3.23 Device List: ✓ DEVICE NAME STATUS MODEL ✓ CC-32-E5-A4-B1-AC CONNECTED TL-ER6120 v3.0 ✓ CC-32-E5-69-B5-B0 CONNECTED T1500G-10MPS v2. Select 2 of 2 items select all Showing 1-2 of 2 records < 1 > 10 /page Go To page: GO Migrate Devices

  1. Verify that all the migrated devices are visible and connected on the target controller. When all the migrated devices are in Connected status on the Device page on the target controller, click Forget Devices to finish the migration process.

Site Migration Controller Migration ✓ Export Controller ✓ Migrate Controller 3 Migrate Devices 4 Done Select the devices to be migrated and enter the URL or IP address of your target controller. The selected devices will try to discover the target controller. Controller IP/Inform URL: 10.0 3.23 Device List: ✓ DEVICE NAME STATUS MODEL ✓ CC-32-E5-A4-B1-AC CONNECTED TL-ER6120 v3.0 ✓ CC-32-E5-69-B5-B0 CONNECTED T1500G-10MPS v2. Select 2 of 2 items select all Showing 1-2 of 2 records < 1 > 10 /page Go To page: GO Forget Devices

When the migration process is completed, all the configuration and data are migrated to the target controller. You can uninstall the previous controller if necessary.

6

Configure and Monitor Controller-Managed Devices

This chapter guides you on how to configure and monitor controller-managed devices, including gateways, switches and APs. You can configure the devices individually or in batches to modify the configurations of certain devices. The chapter includes the following sections:

• 6.1 Introduction to the Devices Page
• 6.2 Configure and Monitor the Gateway
• 6.3 Configure and Monitor Switches
• 6.4 Configure and Monitor APs

TP-LINK Omada SDN Controller - Configure and Monitor Controller-Managed Devices - 1

6.1 Introduction to the Devices Page

The Devices page is further divided into Device List, Device Group, and Configuration Result.

Overview

This page displays all TP-Link devices discovered by the controller and their general information.

For an easy monitoring of the devices, you can customize the column and filter the devices for a better overview of device information. Also, quick operations and Batch Edit are available for configurations.

Search or select tag All Gateway Switches APs Device NAME IP ADDRESS STATUS Y MODEL VERSION UPTIME ACTION 192.168.0.1 CONNECTED 2.0.0 23h 16m 25s 192.168.0.103 CONNECTED 1.0.3 10days(0) 0h 1m 2. - PENDING - MANAGED BY OTHERS - 192.168.0.101 CONNECTED 3.1.0 22h 31m 24s - MANAGED BY OTHERS - 192.168.0.100 CONNECTED 5.0.4 22h 36m 50s 192.168.0.105 CONNECTED 5.0.7 21h 39m 50s Showing 1-6 of 8 records < 1 > 10 /page Go to page: GO

According to the connection status, the devices have the following status: Pending, Isolated, Connected, Managed by Others, Heartbeat Missed, and Disconnected. The icons in the Status column are explained as follows:

PENDINGThe device is in Standalone Mode or with factory settings, and has not been adopted by the controller. To adopt the device, click and the controller will use the default username and password to adopt it. When adopting, its status will change from Adopting, Provisioning, Configuring, to Connected eventually.
ISOLATED(For APs in the mesh network) The AP once managed by the controller via a wireless connection now cannot reach the gateway. You can rebuild the mesh network by connecting it to an AP in the Connected status, then the isolated AP will turn into a connected one. For detailed configuration, refer to Mesh.
CONNECTEDThe device has been adopted by the controller and you can manage it centrally. A connected device will turn into a pending one after you forget it.
MANAGED BY OTHERSTP-LINK Omada SDN Controller - Overview - 2The device has already been managed by another controller. You can reset the device or provide the username and password to unbind it from another controller and adopt it in the current controller.A transition status between Connected and Disconnected.Once connected to the controller, the device will send inform packets to the controller in a regular interval to maintain the connection. If the controller does not receive its inform packets in 30 seconds, the device will turn into the Heartbeat Missed status. For a heartbeat-missed device, if the controller receives an inform packet from the device in 5 minutes, its status will become Connected again; otherwise, its status will become Disconnected.
TP-LINK Omada SDN Controller - Overview - 3The connected device has lost connection with the controller for more than 5 minutes.
[24X5H](For APs in the mesh network) When this icon appears with a status icon, it indicates the AP with mesh function and no wired connection is detected by the controller. You can connect it to an uplink AP throughMesh.
TP-LINK Omada SDN Controller - Overview - 4When this icon appears with a status icon, it indicates the device in the Connected, Heartbeat Missed, Isolated, or Disconnected status is migrating. For more information about Migration, refer to5.7 Migration.

Configuration

■ Customize the Column

To customize the columns, click next to Action and check the boxes of information type.

To change the list order, click the column head and will appear to indicate the ascending or descending order.

Search or select tag All Delivery/Switches APs Device NAME IP ADDRESS STATUS T MODEL VERSION UPTIME ACTION 04-B0.24-59-F5-80 192.168.0.1 CONNECTED EINOS v2.0 2.0.0 23h 16m 20s 00-GA-EB-45-F7-81 192.168.0.103 CONNECTED TL-5G2210MP v1.0 1.0.3 15day(s) 5h 1m 2. 00-00-PF-FF-05-8C - PENDING EAP245 v4.0 - 00-00-PF-FF-20-6F - MANAGED BY OTHERS T EAP670 v1.0 - 00-5F-67-DF-56.46 192.168.0.101 CONNECTED EAP235-Wall(US) v1.0 3.1.0 22h 31m 24s

■ Filter the Devices

Use the search box and tab bar above the table to filter the devices.

To search the devices, enter the text in the search box or select a tag from the drop-down list. As for the device tag, refer to the general configuration of switches and APs.

Search or select tag Group 1

To filter the devices, a tab bar is above the table to filter the devices by device type. You can also filter the devices by their status by clicking in the Status column.

If you select the APs tab, another tab bar Overview Mesh Performance Config will be available to change the column quickly.

OverviewDisplays the device name, IP address, status, model, firmware version, uptime, channel, and Tx power by default.
Mesh Displays the information of devices in the mesh network, including the device name, IP address, status, model, uplink device, channel, Tx power, and the number of downlink devices, clients and hops by default.
PerformanceDisplays the device name, IP address, status, uptime, channel, Tx power, the number of 2.4 GHz and 5 GHz clients, Rx rate, and Tx rate by default.
Config Displays the device name, status, version, WLAN group, and the radio settings for 2.4 GHz and 5 GHz by default.

■ Quick Operations

Click the icons in Header or the Action column to quickly adopt, locate, upgrade, or reboot the device.

Start Rolling UpgradeClick to upgrade the managed devices in batches.
Click to check if there is new firmware for the managed devices.
(For pending devices) Click to adopt the device.
(For connected switches and APs) Click this icon and the LEDs of the device will flash to indicate the device's location. The LEDs will keep flashing for 10 minutes, or you can click theicon to stop the flashing.
(For connected devices) Click to reboot the device.
Click to upgrade the device's firmware version. This icon appears when the device has a new firmware version.

■ Batch Edit (for Switches and APs)

After selecting the Gateway/Switches or APs tab, you can adopt or configure the switches or APs in batches. Batch Config is available only for the devices in Connected/Disconnected/Heartbeat

Missed/Isolated status, while Batch Adopt is available for the devices in the Pending/Managed By Others status.

Search or select tag All Gateway Switches APs Device NAME IP ADDRESS STATUS MODEL VERSION UPTIME Batch Config Batch Adopt TP-Link_Test_Gatew... 192.168.0.1 CONNECTED TL-CR7206 V1.0 1.1.0 1 days 00:35:44 TP-Link_Test_Swiic... 192.168.0.37 CONNECTED TL-SG2210MP V1.0 1.0.0 10 days 16:57:04 TP-Link_Test_Swiic... 192.168.0.41 CONNECTED TL-SG2210MP V1.0 1.0.0 11 days 19:56:36 TP-Link_Test_Swiic... 192.168.0.21 CONNECTED TL-SG3428X V1.0 1.0.1 0 days 01:20:48 TP-Link_Test_Swiic... 192.168.0.77 CONNECTED TL-SG3428XMP V1.0 1.0.1 0 days 00:33:34

Click Batch Action. select Batch Adopt, click the checkboxes of devices, and click Done. If the selected devices are all in the Pending status, the controller will adopt then with the default username and password. If not, enter the username and password manually to adopt the devices.

Search or select tag All Gateway/Switches APs Overview Mesh Performance Config Device NAME IP ADDRESS STATUS MODEL VERSION UPTIME CLIENTS DOWN UP CHANNEL ACTION TP-Link_Test_Eap_4 192.160.0.104 ADOPT FAILED EA235-WaW(US) v1.0 1.0.2 16 days 18:42:33 0 0 Bytes 0 Bytes - Retry TP-Link_Test_Eap_5 192.160.0.105 ADOPT FAILED EA235-WaW(US) v1.0 1.0.2 16 days 23:14:11 0 0 Bytes 0 Bytes - Retry

Click Batch Action, select Batch Config, click the checkboxes of devices, and click Done. Then the Properties window appears. There are two tabs in the window: Devices and Config.

In Devices, you can click ✗ to remove the device from the current batch configuration.

In Config, all settings are Keep Existing by default. For detailed configurations, refer to the configuration of switches and APs.

Search or select tag All Gateway/Switches APs Overview Mesh Performance Config Device NAME IP ADDRESS STATUS MODEL VERSION UPTIME CLIENTS DOWN UP CHANNEL ACTION EA-23-51-06-22-52 10.0.1.70 CONNECTED EAP225- Outdoor(EU) v1.0 2.0.0 1 days 07:54:08 0 2.11 GB 369.62 MB 11(2.4G), 36(5G) (1) EA-33-51-A8-22-A0 10.0.0.196 CONNECTED EAP225- Outdoor(EU) v1.0 2.0.0 0 days 06:15:18 1 13.61 MB 3.00 MB 11(2.4G), 36(5G) (1)

>Click to minimize the Properties window to an icon. To reopen the minimized Properties window, click ☐.
Click to maximize the Properties window. You can also use the icon on pages other than the Devices page.
×Click to close the Properties window of the chosen device(s). Note that the unsaved configuration will be lost.
...The number on the lower-right shows the number of devices in the batch configuration.

6.2 Configure and Monitor the Gateway

In the Properties window, you can configure the gateway managed by the controller and monitor the performance and statistics. By default, all configurations are synchronized with the current site.

To open the Properties window, click the entry of a router. A monitor panel and several tabs are listed in the Properties window. Most features to be configured are gathered in the Config tab, such as IP, SNMP, and Hardware Offload, while other tabs are mainly used to monitor the devices.

Search or select tag A0 Gateway Switches APs DEVICE NAME IP ADDRESS STATUS MODEL VVERSION UPTIME DOWN CC-32-E5-A4-B1-AC 192.168.0.1 CONNECTED TL-ERT206 v1.0 1.0.0 4 days 10:27:40 - CC-32-E5-45-B5-B0 192.168.0.135 CONNECTED TL-SQ2210P v1.0 1.0.3 8 days 21:58:16 949.25 MB 1.06 G Showing 1-2 at 2 records < 1 > 5/page Go To page: GO + Add Devices CC-32-E5-A4-B1-AC Model GG-32-E5-A4-B1-AC TL-ERT206 v1.0 Firmware Version: CPU Utilization: 1.0.0 Build 20200509 1% Rel.T1443 Memory Utilization: LAN IP Address: 13% 192.168.0.1 Uptime: 4 days 18:27:40 WAN

TP-LINK Omada SDN Controller - Configure and Monitor the Gateway - 2

Note:

  • You can adopt only one router in one site.
  • The available functions in the window vary due to the model and status of the device.

6.2.1 Configure the Gateway

In the Properties window, you can view and configure the ports in Ports, and configure the gateway features in Config.

Monitor Panel

The monitor panel displays the router's ports, and it uses colors and icons to indicate different connection status and port types. When the router is pending or disconnected, all ports are disabled.

Disabled 10/100 Mbps 10 Gbps Disconnected 2.5 Gbps WAN 1000 Mbps 5 Gbps LAN

You can hover the cursor over the port icon for more details.

Port1
Status1000 Mbps
Tx Bytes34.70 MB
Rx Bytes59.61 MB

Details

In Details, you can view the basic information of the router and statistics of WAN ports to know the device's running status briefly. The listed information varies with devices.

Overview
MAC Address:Public IP Address:
40-ED-00-52-BB-E5192.168.0.1
Model:Firmware Version:
ER706W v1.01.0.0 Build 20230712 Rel.61 639(4555)
CPU Utilization:Memory Utilization:
3%40%
LAN IP Address:Uptime:
192.168.0.13day(s) 2h 1m 28s
Temperature:
56°C
Radios
SFP WAN/LAN1Link Down
WAN2Online

Networks

In Networks, you can view the network information of the router.

NetworkIP AddressTx BytesRx BytesClients
LAN192.168.0.1596.1 MB1.0 GB0

Ports

In Ports, you can view the status and edit settings of the ports.

Name Status ACTION WAN WAN/LAN1 WAN/LAN2 LAN1 LAN2 USB Modem Showing 1-6 of 6 records < 1 >

To configure a port, click ☐ in the table.

Details Networks Ports Config Statistics Edit WAN/LAN2 Status: Enable Link Speed: Auto Manual Mirroring: Enable Unselected Selected Mirror Mode: Ingress Ingress Egress Ingress and Egress Apply Cancel

Status Check the box to enable the port.

Link Speed Select the speed mode for the port.

Auto: The port negotiates the speed and duplex automatically.

Manual: Specify the speed and duplex from the drop-down list manually.

Mirroring Mirroring is used to analyze network traffic and troubleshoot network problems.

Enable this option to set the edited port as the mirroring port, then specify one or multiple mirrored ports. The gateway will send a copy of traffics passing through the mirrored ports to the mirroring port.

Mirror Mode Specify the directions of the traffic to be mirrored.

Ingress and Egress: Both the incoming and outgoing packets through the mirrored port will be copied to the mirroring port.

Ingress: The packets received by the mirrored port will be copied to the mirroring port.

Egress: The packets sent by the mirrored port will be copied to the mirroring port.

Clients

In Clients, you can view the clients of the router.

All (1) Users (1) Guests (0) History > Client name or MAC NAME MAC SSID/N DESKTOP-STTAJ... EC-F4-BB-35-D4-06 LAN Showing 1-1 of 1 records < 1 >

Mesh (for wireless routers only)

In Mesh, you can view the mesh downlinks of the router.

All (1) Users (1) Guests (0) History > Client name or MAC NAME MAC SSID/N DESKTOP-STTAJ... EC-F4-BB-35-D4-06 LAN Showing 1-1 of 1 records < 1 >

Config

In the Properties window, click Config and then click the sections to configure the features applied to the router.

■ General

In General, you can specify general settings of the router.

General Name: 3C-84-6A-B8-51-4D LED: Use Site Settings On Off Device Tags: Please Select... Longitude: -73.88876438140869 (Optional, -180~180, with a maximum of 16 decimal places.) Latitude: 40.69552572315652 (Optional, -90~90, with a maximum of 16 decimal places.) Address: 80-21 64th Lane, Queens, New Yor Refresh (Optional) Remember Device: Enable i Apply Cancel

Name Specify a name of the device.

LED Select the way that device's LEDs work.

Use Site Settings: The device's LED will work following the settings of the site.

On/Off: The device's LED will keep on/off.

Device Tags Select a tag from the drop-down list or create a new tag to categorize the device.

Longitude / Latitude / Address Configure the parameters according to where the site is located. These fields are optional.

Remember Device When enabled, the controller will remember this device. After device reset and power-on, the controller will automatically adopt the device if the controller can find it.

■ Radios (for wireless routers only)

In Radios, you can control how and what type of radio signals the router emits. Select each frequency band and configure the parameters. Different models support different bands.

Radios 2.4 GHz 5 GHz Status: Enable Wireless Mode: Auto Channel Width: Auto Channel Auto Tx Power (EIRP): Auto Note : The EIRP transmit power includes the antenna gain. Apply Cancel

Status If you disable the frequency band, the radio on it will turn off.
Wireless ModeSpecify the wireless mode of the band. Different bands have different available options. We recommend using the default value.
Channel WidthSpecify the channel width of the band. Different bands have different available options. We recommend using the default value.
ChannelSpecify the operation channel of the router to improve wireless performance. If you selectAutofor the channel setting, the router scans available channels and selects the channel where the least amount of traffic is detected.
Tx Power Specify the Tx Power (Transmit Power) in the 4 options: Low, Medium, High and Custom.The actual power of Low, Medium and High are based on the minimum transmit power (Min. Txpower) and maximum transmit power (Max. TxPower), which may vary in different countries and regions.Low: Min. TxPower + (Max. TxPower-Min. TxPower) * 20% (round off the value)Medium: Min. TxPower + (Max. TxPower-Min. TxPower) * 60% (round off the value)High: Max. TxPowerCustom: Specify the value manually.

■ WLANs

In WLANs, you can apply the WLAN group to the router and specify a different SSID name and password to override the SSID in the WLAN group. After that, clients can only see the new SSID and use the new password to access the network. To create or edit WLAN groups, refer to 4.4 Configure Wireless Networks.

WLANs WLAN Group: Default Name Band Overri des Enable 123 2.4 GHz, 5 GHz Showing 1-1 of 1 records < 1 > Apply Cancel

(Only for configuring a single device) To override the SSID, select a WLAN group, click in the entry and then the following page appears.

WLANs>SSID Override SSID Override: ✓ Enable SSID: tp-link Password: ............ Ø VLAN: ✓ Enable VLAN ID: 1 (1-4094) Save Cancel

SSID Override

Enable or disable SSID Override on the AP. If SSID Override enabled, specify the new SSID and password to override the current one.

VLAN Enable or disable VLAN. If VLAN enabled, enter a VLAN ID to add the new SSID to the VLAN.

■ Services

In Services, you can configure SNMP to write down the location and contact detail. You can also click Manage to jump to Settings > Services > SNMP.

Services SNMP Manage Location: Contact: Apply Cancel

■ Advanced

In Advanced, you can configure advanced settings to make better use of network resources.

Advanced Hardware Offload: ✓ Enable i LLDP: □ Enable Echo Server: ● Auto ○ Custom 2.4 GHz 5 GHz Load Balance Maximum Associated Clients: □ Enable RSSI Threshold: □ Enable i QoS No Acknowledgement: □ Enable i Unscheduled Automatic Power Save Delivery: ✓ Enable i OFDMA OFDMA: □ Enable i Apply Cancel

Hardware OffloadHardware Offload can improve performance and reduce CPU utilization by using the hardware to offload packet processing.Note that this feature cannot take effect if QoS, Bandwidth Control, or Session Limit is enabled. To configure Bandwidth Control and Session Limit for the router, refer to 4.6 Transmission.
LLDP LLDP (Link Layer Discovery Protocol) can help discover devices.
Echo ServerEcho Server is used to test the connectivity and monitor the latency of the network automatically or manually. If you click Custom, enter the IP address or hostname of your custom server.
Maximum Associated ClientsEnable this function and specify the maximum number of connected clients. If the connected client reaches the maximum number, the router will disconnect those with weaker signals to make room for other clients requesting connections.
RSSI Threshold Enable this function and enter the threshold of RSSI (Received Signal Strength Indication). If the client's signal strength is weaker than the threshold, the client will lose connection with the router.
No AcknowledgementEnable this function to specify that the router will not acknowledge frames with QoS No Ack. Enabling No Acknowledgment can bring more efficient throughput, but it may increase error rates in a noisy Radio Frequency (RF) environment.
Unscheduled Automatic Power Save DeliveryWhen enabled, this function can greatly improve the energy-saving capacity of clients.
OFDMA (Only for models supporting 802.11 ax or later standards) Enable this feature to enable multiple users to transmit data simultaneously, and it will greatly improves speed and efficiency. Note that the benefits of OFDMA can be fully enjoyed only when the clients support OFDMA.

■ Manage Device

In Manage Device, you can upgrade the device's firmware version manually, move it to another site, synchronize the configurations with the controller, and forget the router.

Manage Device Custom Upgrade Choose the firmware file and upgrade the device. ↑ Browse Move to Site Move this device to another site of this controller. Please Select... Move Force Provision Click Force Provision to synchronize the configurations of the device with the controller. The device will be disconnected from the controller temporarily, and be adopted again to get the configurations from the controller. Force Provision Forget This Device If you no longer wish to manage a device, you may forget it. After forgotten, the device will be removed from the controller and get reset. Forget Download Device Info If the device has an abnormality, you can download the device information and provide it to our R&D personnel to analyze the problem. Download

Custom UpgradeClick Browse and choose a file from your computer to upgrade the device. When upgrading, the device will be reboot and readopted by the controller. You can also check the box of Upgrade all devices of the same model in the site after the firmware file is uploaded.
Move to SiteSelect a site which the device will be moved to. After moving to another site, device configurations on the prior site will be replaced by that on the new site, and its traffic history will be cleared.
Force ProvisionClickForce Provisionto synchronize the configurations of the device with the controller. The device will lose connection temporarily, and be adopted to the controller again to get the configurations from the controller.
Forget This DeviceClickForgetand then the device will be removed from the controller. Once forgotten, all configurations and history related to the device will be wiped out.
Download Device InfoIf the device has an abnormality, you can download the device information and provide it to our R&D personnel to analyze the problem.⚠ Note:Firmware updates are required for earlier devices to obtain complete information.

■ Common Settings

In Common Settings, you can click the path to jump to corresponding modules quickly.

Common Settings
Settings->Wired Networks->Internet
To configure the network of the WAN port, go to the Settings->Wired Networks->Internet page.
Settings->Wired Networks->LAN
To view and configure the settings of the network interfaces, go to the Settings->Wired Networks->LAN page.
Settings->VPN
To view and configure the VPN network, go to the Settings->VPN page.
Settings->Network Security
To view and configure the Firewall and ACL rules for the network, go to the Settings->Network Security page.
Settings->Transmission->Routing
To view and configure Routing on the gateway, go to the Settings->Transmission->Routing page.
Settings->Transmission->NAT
To view and configure NAT on the gateway, go to the Settings->Transmission->NAT page.
Settings->Services
To view and configure the network services, go to the Settings->Services page.

6.2.2 Monitor the Gateway

One panel and three tabs are provided to monitor the device in the Properties window: Monitor Panel, Details, Networks, and Statistics.

Statistics

In Statistics, you can monitor the CPU and memory of the device in last 24 hours via charts. To view statistics of the device in a certain period, click the chart.

TP-LINK Omada SDN Controller - Statistics - 1

line | Time | CPU | Memory | | ---------- | ---- | ------ | | 11:15 am | ~0% | 12% | | 04:40 pm | ~0% | 12% | | 10:05 pm | ~0% | 12% | | 03:30 am | ~0% | 12% | | 11:10 am | ~0% | 12% |

6.3 Configure and Monitor Switches

In the Properties window, you can configure one or some switches connected to the controller and monitor the performance and statistics. Configurations changed in the Properties window will be applied only to the selected switch(es). By default, all configurations are synchronized with the current site.

To open the Properties window, click the entry of a switch, or click Batch Action, and then Batch Config to select switches for batch configuration. A monitor panel and several tabs are listed in the Properties window. Most features to be configured are gathered in the Ports and Config tab, such as the port mirroring, IP address, and Management VLAN, while other tabs are mainly used to monitor the devices.

Device List Application Result Search Name, IP: Status, Model or Tag 00-FF-00-05- CONNECTED All Gateway/Switches APs DEVICE NAME IP ADDRESS STATUS MODEL VERSION UPTIM 1C-61-B4-C5-48-83 192.168.0.1 CONNECTED ER605 v2.0 2.1.0 4day(s) 00-FF-00-05-40-5D 192.168.0.18 CONNECTED TL-SG2428P v1.0 1.1.7 22day(s) Showing 1-2 of 2 records < 1 > 10 /page Go To page GO Details Ports Clients Config Statistics Overview Serial Number: Model TL-SG2428P v1.0 MAC Address: IP Address IPv6 Address: 192.168.0.18 Firmware Version: CPU Utilization: Memory Utilization. 10% 47% Uptime: Remaining PoE Power: 22day(s) 17h 16m 40s 97.80% / 244.50W Fan Status Normal

Note:

  • The available functions in the window vary due to the model and status of the device.
    • In Batch Config, you can only configure the selected devices, and the unaltered configurations will keep the current settings.

6.3.1 Configure Switches

In the Properties window, you can view and configure the profiles applied to ports in Ports, and in Config, you can configure the switch features.

Ports

Port and LAG are two tabs designed for physical ports and LAGs (Link Aggregation Groups), respectively. Under the Port tag, all ports are listed but you can configure physical ports only, including overriding the applied profiles, configuring Port Mirroring, and specifying ports as LAGs. Under the LAG tag, all LAGs are listed and you can view and modify the configurations of existing LAGs.

Port

In Port, you can view and configure all ports' names and applied profiles.

Port LAG Edit Selected Name Status Profile ACTION 1 Port1 All 2 Port2 All 3 Port3 All 4 Port4 All 5 Port5 All 6 Port6 All 7 Port7 All 8 Port8 All 9 Port9 All 10 Port10 All

Status Displays the port status in different colors.

The port profile is Disabled. To enable it, click to change the profile.
■: The port is enabled, but no device or client is connected to it.
The port is running at 1000 Mbps.
■: The port is running at 10/100 Mbps.

Profile Displays the profile applied to the port.

Action

☑: Click to edit the port name and configure the profile applied to the port.

(For PoE ports) Click to reboot the connected powered devices (PDs).

To configure a single port, click In the table. To configure ports in batches, click the checkboxes and then click Edit Selected. Then you can configure the port name and profile. By default, all settings are Keep Existing for batch configuration.

Edit Port1 Name: Port1 Profile: All Manage Profiles Profile Overrides Apply Cancel

Name Enter the port name.

ProfileSelect the profile applied to the port from the drop-down list. Click Manage Profiles to jump to view and manage profiles. For details, refer to 4.3 Configure Wired Networks.
Profile OverridesClick the checkbox to override the applied profile. The parameters to be configured vary in Operation modes,

With Profile Overrides enabled, select an operation mode and configure the following parameters to override the applied profile, configure a mirroring port, or configure a LAG.

- Override the Applied Profile

If you select Switching for Operation, configure the following parameters and click Apply to override the applied profile. To discard the modifications, click Remove Overrides and all profile configurations will become the same as the applied profile.

Edit Port1 Name: Port1 Profile: All Manage Profiles ✓ Profile Overrides Operation: ● Switching ○ Mirroring i ○ Aggregating PoE Mode: ○ Off ● 802.3at/af 802.1X Control: ○ Auto ● Force Authorized ○ Force Unauthorized Link Speed: ○ Auto ● Manual Auto / Auto Port Isolation: Enable i Flow Control: Enable EEE: Enable Loopback Control: ○ Off ○ Loopback Detection Port Based ● Loopback Detection VLAN Based ○ Spanning Tree LLDP-MED: ✓ Enable Bandwidth Control: i ● Off ○ Rate Limit ○ Storm Control DHCP L2 Relay: ✓ Enable Format: Normal Circuit ID: (Optional) Remote ID: (Optional) Apply Cancel Remove Overrides

PoE Mode (Only for PoE ports) Select the PoE (Power over Ethernet) mode for the port.
Off: Disable PoE function on the PoE port.
802.3at/af: Enable PoE function on the PoE port.
802.1X ControlSelect 802.1X Control mode for the ports. To configure the 802.1X authentication globally, go to Settings > Authentication > 802.1X.
Auto: The port is unauthorized until the client is authenticated by the authentication server successfully.
Force Authorized: The port remains in the authorized state, sends and receives normal traffic without 802.1X authentication of the client.
Force Unauthorized: The port remains in the unauthorized state, and the client connected to the port cannot authenticate with any means. The switch cannot provide authentication services to the client through the port.
Link Speed Select the speed mode for the port.
Auto: The port negotiates the speed and duplex automatically.
Manual: Specify the speed and duplex from the drop-down list manually.
Port IsolationClick the checkbox to enable Port Isolation. An isolated port cannot communicate directly with any other isolated ports, while the isolated port can send and receive traffic to non-isolated ports.
Flow Control With this option enabled, when a device gets overloaded it will send a PAUSE frame to notify the peer device to stop sending data for a specified period of time, thus avoiding the packet loss caused by congestion.
EEE Click the checkbox to enable EEE (Energy Efficient Ethernet) to allow power reduction.
Loopback ControlLoopback refers to the routing of data streams back to their source in the network. You can disable loopback control for the network or choose a method to prevent loopback happening in your network.
Off: Disable loopback control on the port.
Loopback Detection Port Based: Loopback Detection Port Based helps detect loops that occur on a specific port. When a loop is detected on a port, the port will be blocked.
Loopback Detection VLAN Based: Loopback Detection VLAN Based helps detect loops that occur on a specific VLAN. When a loop is detected on a VLAN, the current port will be removed from the VLAN.
Spanning Tree: Select STP (Spanning Tree Protocol) to prevent loops in the network. STP helps block specific ports of the switches to build a loop-free topology and detect topology changes and automatically generate a new loop-free topology. To make sure Spanning Tree takes effect on the port, go to the Config tab and enable Spanning Tree on the switch.
LLDP-MED Click the checkbox to enable LLDP-MED (Link Layer Discovery Protocol-Media Endpoint Discovery) for device discovery and auto-configuration of VoIP (Voice over Internet Protocol) devices.
Bandwidth ControlSelect the type of Bandwidth Control functions to control the traffic rate and specify traffic threshold on each port to make good use of network bandwidth.Off: Disable Bandwidth Control for the port.Rate Limit: Select Rate limit to limit the ingress/egress traffic rate on each port. With this function, the network bandwidth can be reasonably distributed and utilized.Storm Control: Select Storm Control to allow the switch to monitor broadcast frames, multicast frames and UL-frames (Unknown unicast frames) in the network. If the transmission rate of the frames exceeds the specified rate, the frames will be automatically discarded to avoid network broadcast storm.
Ingress Rate LimitWith Rate Limit selected, click the checkbox and specify the upper rate limit for receiving packets on the port.
Egress Rate LimitWhen Rate Limit selected, click the checkbox and specify the upper rate limit for sending packets on the port.
Broadcast ThresholdWith Storm Control selected, click the checkbox and specify the upper rate limit for receiving broadcast frames. The broadcast traffic exceeding the limit will be processed according to the Action configurations.
Multicast ThresholdWith Storm Control selected, click the checkbox and specify the upper rate limit for receiving multicast frames. The multicast traffic exceeding the limit will be processed according to the Action configurations.
Unknown Unicast ThresholdWith Storm Control selected, click the checkbox and specify the upper rate limit for receiving unknown unicast frames. The traffic exceeding the limit will be processed according to the Action configurations.
Action When Storm Control selected, select the action that the switch will take when the traffic exceeds its corresponding limit.Drop: With Drop selected, the port will drop the subsequent frames when the traffic exceeds the limit.Shutdown: With Shutdown selected, the port will be shutdown when the traffic exceeds the limit.
Recover Time With Shutdown selected as the Action, specify the recover time, and the port will be opened after the specified time.
DHCP L2 Relay Click the checkbox to enable DHCP L2 Relay for the network.
Format Select the format of option 82 sub-option value field.Normal: The format of sub-option value field is TLV (type-length-value).Private: The format of sub-option value field is just value.

Circuit ID (Optional) Enter the customized circuit ID. The circuit ID configurations of the switch and the DHCP server should be compatible with each other. If it is not specified, the switch will use the default circuit ID when inserting Option 82 to DHCP packets.

Remote ID (Optional) Enter the customized remote ID. The remote ID configurations of the switch and the DHCP server should be compatible with each other. If it is not specified, the switch will use its own MAC address as the remote ID.

- Configure a Mirroring Port

If you select Mirroring as Operation, the edited port can be configured as a mirroring port. Specify other ports as the mirrored port, and the switch sends a copy of traffics passing through the mirrored port to the mirroring port. You can use mirroring to analyze network traffic and troubleshoot network problems.

To configure Mirroring, select the mirrored port or LAG, specify the following parameters, and click Apply. To discard the modifications, click Remove Overrides and all profile configurations become the same as the applied profile.

Note that the mirroring ports and the member ports of LAG cannot be selected as mirrored ports.

Profile Overrides Operation: ○ Switching ● Mirroring ① ○ Aggregating Unselected Selected 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 LAG: □ LAG1 PoE Mode: ○ Off ● 802.3at/af Link Speed: ○ Auto ● Manual Auto / Auto Bandwidth Control: ○ Off ● Rate Limit Ingress Rate Limit: □ Enable Egress Rate Limit: □ Enable Apply Cancel Remove Overrides

PoE Mode (Only for PoE ports) Select the PoE mode for the port.

Off: Disable PoE on the PoE port.

802.3at/af: Enable PoE on the PoE port.

Link Speed Select the speed mode for the port.

Auto: The port negotiates the speed and duplex automatically.

Manual: Specify the speed and duplex from the drop-down list manually.

Bandwidth Control Bandwidth control optimizes network performance by limiting the bandwidth of specific sources.
Off: Disable bandwidth control on the port.
Rate Limit: Enable bandwidth control on the port, and you need to specify the ingress and/or egress rate limit.
Ingress Rate LimitWith Rate Limit selected, click the checkbox and specify the upper rate limit for receiving packets on the port. With this function, the network bandwidth can be reasonably distributed and utilized.
Egress Rate LimitWith Rate Limit selected, click the checkbox and specify the upper rate limit for sending packets on the port. With this function, the network bandwidth can be reasonably distributed and utilized.

- Configure a LAG

If you select Aggregating as Operation, you can aggregate multiple physical ports into a logical interface, which can increase link bandwidth and enhance the connection reliability.

TP-LINK Omada SDN Controller - - Configure a LAG - 1

Configuration Guidelines:

  • Ensure that both ends of the aggregation link work in the same LAG mode. For example, if the local end works in LACP mode, the peer end should also be set as LACP mode.
  • Ensure that devices on both ends of the aggregation link use the same number of physical ports with the same speed, duplex, jumbo and flow control mode.
  • A port cannot be added to more than one LAG at the same time.
  • LACP does not support half-duplex links.
    • One static LAG supports up to eight member ports. All the member ports share the bandwidth evenly. If an active link fails, the other active links share the bandwidth evenly.
  • One LACP LAG supports multiple member ports, but at most eight of them can work simultaneously, and the other member ports are backups. Using LACP protocol, the switches negotiate parameters and determine the working ports. When a working port fails, the backup port with the highest priority will replace the faulty port and start to forward data.
  • The member port of an LAG follows the configuration of the LAG but not its own. Once removed, the LAG member will be configured as the default All profile and Switching operation.
  • The port enabled with Port Security, Port Mirror, MAC Address Filtering or 802.1X cannot be added to an LAG, and the member port of an LAG cannot be enabled with these functions.

To configure a new LAG, select other ports to be added to the LAG, specify the LAG ID, and choose a LAG type. Click Apply. To discard the modifications, click Remove Overrides and all

profile configurations become the same as the applied profile. For other parameters, configure them under the LAG tab.

Profile Overrides Operation: Switching Mirroring Aggregating Unselected Selected 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 LAG ID: Please Select... (1-8) Static LAG Active LACP Passive LACP Apply Cancel Remove Overrides

LAG ID Specify the LAG ID of the LAG. Note that the LAG ID should be unique.

The valid value of the LAG ID is determined by the maximum number of LAGs supported by your switch. For example, if your switch supports up to 14 LAGs, the valid value ranges from 1 to 14.

Static LAG In Static LAG mode, the member ports are added to the LAG manually.

Active LACP/

Passive LACP

LACP extends the flexibility of the LAG configurations. In LACP, the switch uses LACPDU (Link Aggregation Control Protocol Data Unit) to negotiate the parameters with the peer end. In this way, the two ends select active ports and form the aggregation link.

Active LACP: In this mode, the port will take the initiative to send LACPDU.

Passive LACP: In this mode, the port will not send LACPDU before receiving the LACPDU from the peer end.

■LAG

LAGs (Link Aggregation Groups) are logical interfaces aggregated, which can increase link bandwidth and enhance the connection reliability. You can view and edit the LAGs under the LAG tab. To configure physical ports as a LAG, refer to Configure a LAG.

Port LAG LAG ID Name Status Ports Profile ACTION 1 LAG1 Port 9,Port 10 All

Status Displays the status in different colors.

The LAG profile is Disable. To enable it, click to change the profile.
The port is enabled, but no device or client is connected to it.
The LAG ports are running at 1000 Mbps.
The LAG port are running at 10/100 Mbps.

Ports Displays the port number of LAG ports.

Profile Displays the profile applied to the port.

Action

☑: Click to edit the port name and configure the profile applied to the port.

: Click to delete the LAG. Once deleted, the ports will be configured as the default All profile and Switching operation. You can configure the ports under the Port tab.

Click to configure the LAG name and the applied profile.

Edit LAG1 Name: LAG1 Profile: All Manage Profiles Configurations of PoE, 802.1x and LLDP-MED in the profile do not take effect on LAG ports. Profile Overrides Apply Cancel

Name Enter the port name.
ProfileSelect the profile applied to the port from the drop-down list. Click Manage Profiles to jump to view and manage profiles. For details, refer to 4.3 Configure Wired Networks.
Profile OverridesClick the checkbox to override the applied profile. The parameters to be configured vary in Operation modes.

With Profile Overrides enabled, you can reselect the LAG members and configure the following parameters.

Profile Overides Unselected Selected 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 LAG ID: 1 (1-0) ● Static LAG ○ Active LACP ○ Passive LACP Link Speed: ○ Auto ● Manual 1000 Mbps / Full Duplex Port Isolation: ○ Enable ⓘ Flow Control: ○ Enable EEE: ○ Enable ⓘ Loopback Control: ○ Off ○ Loopback Detection Port Based ○ Loopback Detection VLAN Based ○ Spanning Tree Bandwidth Control: ○ Off ○ Rate Limit ○ Storm Control DHCP L2 Relay: ○ Enable

Link Speed Select the speed mode for the port.

Auto: The port negotiates the speed and duplex automatically.

Manual: Specify the speed and duplex from the drop-down list manually.

Port Isolation Click the checkbox to enable Port Isolation. An isolated port cannot communicate directly with any other isolated ports, while the isolated port can send and receive traffic to non-isolated ports.

Flow Control With this option enabled, when a device gets overloaded it will send a PAUSE frame to notify the peer device to stop sending data for a specified period of time, thus avoiding the packet loss caused by congestion.

EEE Click the checkbox to enable EEE (Energy Efficient Ethernet) to allow power reduction.

Loopback Control Loopback refers to the routing of data streams back to their source in the network. You can disable loopback control for the network or choose a method to prevent loopback happening in your network.
Off: Disable loopback control on the port.
Loopback Detection Port Based: Loopback Detection Port Based helps detect loops that occur on a specific port. When a loop is detected on a port, the port will be blocked.
Loopback Detection VLAN Based: Loopback Detection VLAN Based helps detect loops that occur on a specific VLAN. When a loop is detected on a VLAN, the current port will be removed from the VLAN.
Spanning Tree: Select STP (Spanning Tree Protocol) to prevent loops in the network. STP helps block specific ports of the switches to build a loop-free topology and detect topology changes and automatically generate a new loop-free topology. To make sure Spanning Tree takes effect on the port, go to the Config tab and enable Spanning Tree on the switch.
Bandwidth ControlSelect the type of Bandwidth Control functions to control the traffic rate and traffic threshold on each port to ensure network performance.
Off: Disable Bandwidth Control for the port.
Rate Limit: Select Rate limit to limit the ingress/egress traffic rate on each port. With this function, the network bandwidth can be reasonably distributed and utilized.
Storm Control: Select Storm Control to allow the switch to monitor broadcast frames, multicast frames and UL-frames (Unknown unicast frames) in the network. If the transmission rate of the frames exceeds the specified rate, the frames will be automatically discarded to avoid network broadcast storm.
Ingress Rate LimitWith Rate Limit selected, click the checkbox and specify the upper rate limit for receiving packets on the port.
Egress Rate LimitWith Rate Limit selected, click the checkbox and specify the upper rate limit for sending packets on the port.
Broadcast ThresholdWith Storm Control selected, click the checkbox and specify the upper rate limit for receiving broadcast frames. The broadcast traffic exceeding the limit will be processed according to the Action configurations.
Multicast ThresholdWith Storm Control selected, click the checkbox and specify the upper rate limit for receiving multicast frames. The multicast traffic exceeding the limit will be processed according to the Action configurations.
Unknown Unicast ThresholdWith Storm Control selected, click the checkbox and specify the upper rate limit for receiving unknown unicast frames. The traffic exceeding the limit will be processed according to the Action configurations.
DHCP L2 Relay Click the checkbox to enable DHCP L2 Relay for the network.

Action With Storm Control selected, select the action that the switch will take when the traffic exceeds its corresponding limit.

Drop: With Drop selected, the port will drop the subsequent frames when the traffic exceeds the limit.

Shutdown: With Shutdown selected, the port will be shutdown when the traffic exceeds the limit.

Recover Time With Shutdown selected as the Action, specify the recover time, and the port will be opened after the specified time.

Config

In Config, click the sections to configure the features applied to the selected switch(es), including the general settings, services, and networks.

■ General

In General, you can specify general settings of the switch.

General Name: 78-8C-B5-44-26-AF LED: Use Site Settings On Off Devices Tags: Please Select... Jumbo: 1518 Bytes (1518-9216) Hash Algorithm: SRC MAC+DST MAC Longitude: -73.73049259185791 (Optional, -180~180, with a maximum of 16 decimal places.) Latitude: 40.76837048078025 (Optional, -90~90, with a maximum of 16 decimal places.) Address: 49-34 Little Neck Parkway, Queens Refresh (Optional) Remember Device: Enable i Apply Cancel

Name (Only for configuring a single device) Specify a name of the device.

LED Select the way that device's LEDs work.

Use Site Settings: The device's LED will work following the settings of the site.

On/Off: The device's LED will keep on/off.

Device Tags Select a tag from the drop-down list or create a new tag to categorize the device.
Jumbo Configure the size of jumbo frames. By default, it is 1518 bytes.Generally, the MTU (Maximum Transmission Unit) size of a normal frame is 1518 bytes.If you want the switch supports to transmit frames of which the MTU size is greater than 1518 bytes, you can configure the MTU size manually here.
Hash AlgorithmSelect the Hash Algorithm, based on which the switch can choose the port to forward the received packets. In this way, different data flows are forwarded on different physical links to implement load balancing.SRC MAC: The computation is based on the source MAC addresses of the packets.DST MAC: The computation is based on the destination MAC addresses of the packets.SRC MAC+DST MAC: The computation is based on the source and destination MAC addresses of the packets.SRC IP: The computation is based on the source IP addresses of the packets.DST IP: The computation is based on the destination IP addresses of the packets.SRC IP+DST IP: The computation is based on the source and destination IP addresses of the packets.
Longitude / Latitude / AddressConfigure the parameters according to where the site is located. These fields are optional.
Remember DeviceWhen enabled, the controller will remember this device. After device reset and power-on, the controller will automatically adopt the device if the controller can find it.

■ VLAN Interface

In VLAN Interface, you can configure Management VLAN and different VLAN interface for the switch. The general information of the existing VLAN interface are displayed in the table.

VLAN Interface Name ▲ VLAN Enable LAN 1 Test A 10 Test B 101 Showing 1-3 of 3 records < 1 > Apply Cancel

To configure a single VLAN interface, hover the mouse on the entry and click to edit the settings.

VLAN Interface > Edit Interface Management VLAN: Enable The controller will fail to manage your devices with wrong Management VLAN configurations. If you are not sure about your network conditions and the potential impact of any configurations, we recommend that you keep the default configurations. Refer to the Configuration Guide before you configure this feature. IP Address Mode: Static DHCP Use Fixed IP Address: Enable Gateway Required Network: Please Select... IP Address: Fallback IP Address: Enable Fallback IP Address: 192 . 168 . 0 . 1 Fallback IP Mask: 255 . 255 . 255 . 0 Fallback Gateway: (Optional) DHCP Option12: (Optional) DHCP Mode: None DHCP Server DHCP Relay Apply Cancel

Management VLANClick the checkbox if you want to use the VLAN interface as Management VLAN. Note that the controller will fail to manage your devices with wrong Management VLAN configurations. If you are not sure about your network conditions and the potential impact of any configurations, we recommend that you keep the default configurations.The management VLAN is a VLAN created to enhance the network security. Without Management VLAN, the configuration commands and data packets are transmitted in the same network. There are risks of unauthorized users accessing the management page and modifying the configurations. A management VLAN can separate the management network from the data network and lower the risks.
IP Address Mode (when Management VLAN enabled)Select a mode for the interface to obtain its IP address, and the VLAN will communicate with other networks including VLANs with the IP address.Static: Assign an IP address to the interface manually, specify the IP Address and Subnet Mask for the interface.When the VLAN interface is set as the Management VLAN, it is optional for you to specify the Default Gateway and Primary/Secondary DNS for the interface.DHCP: Assign an IP address to the interface through a DHCP server.When you want to let device use a fixed IP address, enable Use Fixed IP Address and specify the Network and IP Address based on needs.When the VLAN interface is set as the Management VLAN, you can further enable Fallback IP Address, and specify the Fallback IP Address, Fallback IP Mask, and Fallback Gateway (optional). If the VLAN interface fails to get an IP address from the DHCP server, the fallback IP address will be used for the interface.
DHCP Option 12When DHCP is selected as the IP Address Mode, you can specify the hostname of the DHCP client in the field. The DHCP client will use option 12 to tell the DHCP server their hostname.
DHCP Mode Select a mode for the clients in the VLAN to obtain their IP address.None: Do not use DHCP to assign IP addresses.DHCP Server: Assign an IP address to the clients through a DHCP server.When DHCP Server is selected, you can specify the DHCP Range, and the IP addresses in the range can be assigned to the clients in the VLAN. Also, it is optional for you to specify the DHCP Option 138, Primary/Secondary DNS, Default Gateway, and Lease Time. DHCP Option 138 informs the DHCP client of the controller's IP address when the client sends a request to the DHCP server, and specify Option 138 as the controller's IP address here. Lease Time decides how long the client can use the assigned IP address.DHCP Relay: It allows clients in the VLAN to obtain IP addresses from a DHCP server ion different subnet. When DHCP Relay is selected, specify the IP address of the DHCP server in Server Address.

■ Static Route

In Static Route, you can configure entries of static route for the switch. The general information of the existing static route entries are displayed in the table. For an existing static route, click ☑ to edit the settings, and click 📋 to delete it.

Static Route + Add Destination IP Enabled Next Hop ACTION 192.168.0.3/32 10.0.0.1 Showing 1-1 of 1 records < 1 >

To add a new static route entry, click and configure the parameters.

Static Route > Add New Route Status: Enable IP Version: IPv4 IPv6 Destination IP/Subnet: Add Subnet Next Hop: Distance: (1-255) Apply Cancel

Status Click the checkbox to enable or disable the static route.

IP Version Select IPv4 or IPv6.

Destination IP/Subnet /When IP Version is IPv4, specify Destination IP/Subnet. When IP Version is IPv6, specify Destination IP/Prefix Length. They identify the network traffic which the Static Route entry controls.
Destination IP/ Prefix LengthYou can click + Add Subnet to specify multiple entries or click 📄 to delete them.

Next Hop Specify the IP address for your devices to forward the corresponding network traffic.

Distance

Specify the priority of a static route. It is used to decide the priority among routes to the same destination. Among routes to the same destination, the route with the lowest distance value will be recorded into the routing table.

■ Services

In Services, you can configure Management VLAN, Loopback Control and SNMP.

Services

TP-LINK Omada SDN Controller - Services - 1

VLAN

Management VLAN:

LAN

TP-LINK Omada SDN Controller - VLAN - 1

To configure the Management VLAN, please go to VLAN Interface. Note that the controller will fail to manage your devices with wrong Management VLAN configurations. If you are not sure about your network conditions and the potential impact of any configurations, we recommend that you keep the default configurations. Refer to the Configuration Guide before you configure this feature.

Loopback Control

Loopback Detection:

TP-LINK Omada SDN Controller - Loopback Control - 1

Enable

Spanning Tree:

TP-LINK Omada SDN Controller - Loopback Control - 2

Off

TP-LINK Omada SDN Controller - Loopback Control - 3

STP

TP-LINK Omada SDN Controller - Loopback Control - 4

RSTP

SNMP

Manage

Location:

Contact:

Apply

Cancel

Management VLAN Display the name of the current Management VLAN.
To configure the Management VLAN, please go to Config > VLAN Interface. Note that the controller will fail to manage your devices with wrong Management VLAN configurations. If you are not sure about your network conditions and the potential impact of any configurations, we recommend that you keep the default configurations.The management VLAN is a VLAN created to enhance the network security. Without Management VLAN, the configuration commands and data packets are transmitted in the same network. There are risks of unauthorized users accessing the management page and modifying the configurations. A management VLAN can separate the management network from the data network and lower the risks.
Loopback DetectionWhen enabled, the switch checks the network regularly to detect the loopback.Note that Lopback Detection and Spanning Tree are not available at the same time.
Spanning TreeSelect a mode for Spanning tree. This feature is available only when Loopback Detection is disabled.Off: Disable Spanning Tree on the switch.STP: Enable STP (Spanning Tree Protocol) to prevent loops in the network. STP helps to block specific ports of the switches to build a loop-free topology and detect topology changes and automatically generate a new loop-free topology.RSTP: Enable RSTP (Rapid Spanning Tree Protocol) to prevent loops in the network. RSTP provides the same features as STP with faster spanning ree convergence.Priority: When STP/RSTP enabled, specify the priority for the swith in Spanning Tree. In STP/RSTP, the switch with the highest priority will be selected as the root of the spanning tree. The switch with the lower value has the higher priority.

SNMP (Only for configuring a single device) Configure SNMP to write down the location and contact detail. You can also click Manage to jump to Settings > Services > SNMP.

■ IP Settings (Only for configuring a single device)

In IP Settings, select an IP mode and configure the parameters for the device.

If you select DHCP as the mode, make sure there is a DHCP server in the network and then the device will obtain dynamic IP address from the DHCP server automatically. You can set a fallback IP

address to hold an IP address in reserve for the situation in which the device fails to get a dynamic IP address. Enable Fallback IP and then set the IP address, IP mask and gateway.

IP Settings Mode: DHCP Static Fallback IP: Enable i Fallback IP Address: 192 . 168 . 0 . 25 Fallback IP Mask: 255 . 255 . 255 . 0 Fallback Gateway: . . . . (Optional) Apply Cancel

If you select Static as the mode, set the IP address, IP mask, gateway, and DNS server for the static address.

IP Settings Mode: DHCP Static IP Address: IP Mask: Gateway: Primary DNS Server: (Optional) Secondary DNS Server: (Optional) Apply Cancel

■ Manage Device

In Manage Device, you can upgrade the device's firmware version manually, move it to another site, synchronize the configurations with the controller and forget the switch.

Manage Device Custom Upgrade Please choose the firmware file and upgrade the device. Browse Copy Configuration Select another device at the current site to copy its configurations. Please Select... Copy Move to Site Move this device to another site of this controller. Please Select... Move Force Provision Click Force Provision to synchronize the configurations of the device with the controller. The device will be disconnected from the controller temporarily, and be adopted again to get the configurations from the controller. Force Provision Forget This Device If you no longer wish to manage a device, you may forget it. After forgotten, the device will be removed from the controller and get reset. Forget Download Device Info If the device has an abnormality, you can download the device information and provide it to our R&D personnel to analyze the problem. Download

Custom UpgradeClickBrowseand choose a file from your computer to upgrade the device. When upgrading, the device will be reboot and readopted by the controller. You can also check the box ofUpgrade all devices of the same modelin the site after the firmware file is uploaded.
Copy Configuration Select another device at the current site to copy its configurations.
Move to SiteSelect a site which the device will be moved to. After moving to another site, device configurations on the prior site will be replaced by that on the new site, and its traffic history will be cleared.
Force Provision(Only for configuring a single device) ClickForce Provisionto synchronize the configurations of the device with the controller. The device will lose connection temporarily, and be adopted to the controller again to get the configurations from the controller.
Forget This DeviceClick Forgetand then the device will be removed from the controller. Once forgotten, all configurations and history related to the device will be wiped out.
Download Device InfoIf the device has an abnormality, you can download the device information and provide it to our R&D personnel to analyze the problem.⚠ Note:Firmware updates are required for earlier devices to obtain complete information.

6.3.2 Monitor Switches

One panel and four tabs are provided to monitor the device in the Properties window: Monitor Panel, Details, Clients, and Statistics.

Monitor Panel

The monitor panel displays the switch's ports and uses colors and icons to indicate the connection status and port type. When the switch is pending or disconnected, all ports are disabled.

TP-LINK Omada SDN Controller - Monitor Panel - 1

bar | Category | Value | |---|---| | Disabled | 1 | | Disabled | 2 | | Disconnected | 3 | | Disconnected | 4 | | 10/100 Mbps | 5 | | 10 Gbps | 6 | | PoE | 7 | | 2.5 Gbps | 8 | | 5 Gbps | 9 | | Uplink | 10 | | STP Blocking | 10 | The chart displays a grid of nine labeled rows (1-10) with corresponding color-coded icons representing traffic conditions: gray for Disabled, dark gray for Disconnected, green for 1000 Mbps, cyan for 2.5 Gbps, blue for 5 Gbps, and red for Uplink.
PoEA PoE port connected to a powered device (PD).
UplinkAn uplink port connected to WAN.
MirroringA mirroring port that is mirroring another switch port.
STP BlockingA port in the Blocking status in Spanning Tree. It receives and sends BPDU (Bridge Protocol Data Unit) packets to maintain the spanning tree. Other packets are dropped.

You can hover the cursor over the port icon (except disabled ports) for more details. The displayed information varies due to connection status and port type.

Port3
NamePort3
Status1000 Mbps Full Duplex
Tx Bytes343.59 MB
Rx Bytes353.98 MB
ProfileAll
PoE Power4.3 W

Status Displays the negotiation speed of the port.

Tx Bytes Displays the amount of data transmitted as bytes.

Rx Bytes Displays the amount of data received as bytes.

Profile Displays the name of profile applied to the port, which defines how the packets in both ingress and egress directions are handled. For detailed configuration, refer to 4.8 Create Profiles.

PoE Power Displays the PoE power supply for the PD device.

Uplink Displays the name of device connected to the uplink port.

Mirroring From Displays the name of port that is mirrored.

LAG ID Displays the name of ports that are aggregated into a logical interface.

Details

In Details, you can view the basic information, traffic information, and radio information of the device to know the device's running status.

Overview

In Overview, you can view the basic information of the device. The listed information will be varied due to the device's model and status.

Overview S/N: Model: TL-SG3428XMP v1.0 MAC Address: IP Address: 192.168.0.11 Firmware Version: CPU Utilization: 1.0.2 Build 20210119 5% Rel.75169 Memory Utilization: Uptime: 30% 5 days 23:14:42 Remaining PoE Power: Fan Status: 97.53% / 374.50W Normal

■ Uplink (Only for the switch connected to a controller-managed router/switch in Connected status) Click Uplink to view the uplink information, including the uplink port, the uplink device, the negotiation speed, and transmission rate.

Uplink Port: Uplink Device: 8 CC-32-E5-A4-B1-AC Model: Speed & Duplex: TL-ER7206 v1.0 1000 Mbps Full Duplex Rx Bytes: Tx Bytes: 491.79 MB 497.95 MB

■ Downlink (Only for the switch connected to controller-managed devices in Connected status)

Click Downlink to view the downlink information, including the downlink ports, devices name and model as well as negotiation speed.

Downlink Port Device Name Model Device-MAC Status 3 TP-Link_Test_Eap_1 40-3F-8C-00-01-11 1000 Mbps Full Duplex Showing 1-1 of 1 records < 1 >

Clients

In Clients, you can view the information of clients connected to the switch, including the client name, IP address and the connected port. You can click the client name to open its Properties window.

#NameIP Address
7OC200_72C6FB192.168.0.132
8TP-Link-PC192.168.0.145
Showing 1-2 of 2 records< 1 >

Statistics

In Statistics, you can monitor the CPU and memory of the device in last 24 hours via charts. To view statistics of the device in certain period, click the chart to jump to 8. 2 View the Statistics of the Network.

TP-LINK Omada SDN Controller - Statistics - 1

line | Time | CPU | Memory | | ---------- | ---- | ------ | | 11:15 am | ~0% | 12% | | 04:40 pm | ~0% | 12% | | 10:05 pm | ~0% | 12% | | 03:30 am | ~0% | 12% | | 11:10 am | ~0% | 12% |

6.4 Configure and Monitor APs

In the Properties window, you can configure one or some APs connected to the controller and monitor the performance and statistics. Configurations changed in the Properties window will be applied only to the selected AP(s). By default, all configurations are synchronized with the current site.

To open the Properties window, click the entry of an AP, or click Batch Action, and then Batch Config to select APs for batch configuration. A monitor panel and several tabs are listed in the Properties window. Most features to be configured are gathered in the Config tab, such as IP, radios, SSID, and VLAN, while other tabs are mainly used to monitor the device.

Search or selected log AB Getaway/Switches APs Overview Mesh Performance Config DEVICE NAME IP ADDRESS STATUS TP-Link_Test_Eap_5 192.168.6.104 CONNECTED SP EAP900E HD(EU) v1.0 1.0.2 16 days 23:14:38 4 125.76 GB TP-Link_Test_Eap_1 192.168.6.101 CONNECTED EAP245(EU) v4.0 1.0.2 16 days 23:13:29 3 210.87 GB TP-Link_Test_Eap_2 192.168.6.102 DISCONNECTED EAP235-Wal(US) v1.0 1.0.2 - 5 210.87 GB TP-Link_Test_Eap_3 192.168.6.103 DISCONNECTED EAP235-Wal(US) v1.0 1.0.2 - 5 210.87 GB TP-Link_Test_Eap_4 192.168.6.104 ADOPT FAILED EAP235-Wal(US) v1.0 1.0.2 16 days 10:42:33 5 9 Bytes TP-Link_Test_Eap_5 192.168.6.105 ADOPT FAILED EAP235-Wal(US) v1.0 1.0.2 10 days 23:14:11 5 9 Bytes TP-Link_Test_Eap_6 192.168.6.104 CONNECTED EAP235-Wal(US) v1.0 1.0.2 15 days 11:14:38 3 210.87 GB Showing 1-T of 7 records < 1 > 10/page Go to page

To configure a port, click ☑ in the table. ![](images/a94fc7c388680a68c98eb1d1661cdf30780246944d93287a5fe9676db15816ae.jpg) Name Specify the name of the port. Status Click the box to enable or disable the port. VLAN Configure the uplink port VLAN corresponding to the SSID. Default: Using untagged transmission. Custom: Enter the PVID (Port VLAN Identifier). When a port receives an untagged frame, the EAP inserts a VLAN tag to the frame based on the PVID before forwarding it. PoE Out (Only for APs with the PoE out port) Enable this function to supply power to the connected device on this port.

Config

In the Properties window, click Config and then click the sections to configure the features applied to the selected AP(s).

■ General

In General, you can specify general settings of the AP. ![](images/aa04f701107a1fd0b4c8638cbc1a58b29f3340233b0762cca8c405b149d778b2.jpg) Name (Only for configuring a single device) Specify a name of the device.
LEDSelect the way that device's LEDs work.
Use Site Settings: The device's LED will work following the settings of the site. To view and modify the site settings, refer to 4.2.2 Services.
On/Off: The device's LED will keep on/off.
Wi-Fi Control(Only for Certain APs) Enable Wi-Fi Control, and it will take effect only when the LED feature is enabled. After enabling Wi-Fi Control, you can press the LED button on the AP to turn on/off the Wi-Fi and LED at the same time.
Device Tags Select a tag from the drop-down list or create a new tag to categorize the device.
Longitude / Latitude / AddressConfigure the parameters according to where the site is located. These fields are optional.
Remember DeviceWhen enabled, the controller will remember this device. After device reset and power-on, the controller will automatically adopt the device if the controller can find it.

■ IP Settings (Only for configuring a single device)

In IP Settings, select an IP mode and configure the parameters for the device. If you select DHCP as the mode, make sure there is a DHCP server in the network and then the device will obtain dynamic IP address from the DHCP server automatically. If you want to let the device use a fixed IP address, you can enable Use Fixed IP Address, and set the network and IP address based on needs. Also, you can set a fallback IP address to hold an IP address in reserve for the situation in which the device fails to get a dynamic IP address. Enable Fallback IP and then set the IP address, IP mask and gateway. ![](images/6044a3882d11a09389a6bff4bf0aa1362b1350c1874a2763474f4a2e750de4a0.jpg) If you select Static as the mode, set the IP address, IP mask, gateway, and DNS server for the static address. ![](images/da3b3dc7ff9310d6253638564482a91b67df23f9545fcfa75fbd2c779da82e33.jpg)

■ Radios

In Radios, you can control how and what type of radio signals the AP emits. Select each frequency band and configure the parameters. Different models support different bands.

Note:

The 6 GHz band is only available for certain devices. ![](images/95f3db72f6d807778420e401d27ca851938e996562d884d5df04865e3c0ecd21.jpg) Status If you disable the frequency band, the radio on it will turn off. Channel Width Specify the channel width of the band. Different bands have different available options. We recommend using the default value. Channel Specify the operation channel of the AP to improve wireless performance. If you select Auto for the channel setting, the AP scans available channels and selects the channel where the least amount of traffic is detected. Tx Power Specify the Tx Power (Transmit Power) in the 4 options: Low, Medium, High and Custom. The actual power of Low, Medium and High are based on the minimum transmit power (Min. Txpower) and maximum transmit power (Max. TxPower), which may vary in different countries and regions. Low: Min. TxPower + (Max. TxPower-Min. TxPower) \* 20% (round off the value) Medium: Min. TxPower + (Max. TxPower-Min. TxPower) \* 60% (round off the value) High: Max. TxPower Custom: Specify the value manually.

■ WLANs

In WLANs, you can apply the WLAN group to the AP and specify a different SSID name and password to override the SSID in the WLAN group. After that, clients can only see the new SSID and use the new password to access the network. To create or edit WLAN groups, refer to 4. 4 Configure Wireless Networks.

① Note:

The 6 GHz band is only available for certain devices. ![](images/8d1e3b1747428df25645e3f685ab177aaa546066588436ed33f5201aceef92a4.jpg) (Only for configuring a single device) To override the SSID, select a WLAN group, click in the entry and then the following page appears. ![](images/e71b7102e8e6893cb9c002e853a948862518bce614ec3beed5efc0c1f860c703.jpg) SSID Override Enable or disable SSID Override on the AP. If SSID Override enabled, specify the new SSID and password to override the current one. VLAN Enable or disable VLAN. If VLAN enabled, enter a VLAN ID to add the new SSID to the VLAN.

■ Services

In Services, you can enable Management VLAN to protect your network and configure SNMP and web server parameters. ![](images/87486bae75bc54ee8b68b7cff88ed6a64fa65f4d802b44b670a35597ac0ec628.jpg)
Management VLANTo configure Management VLAN, create a network in LAN first, and then select it as the management VLAN on this page. For details, refer to 4.3 Configure Wired Networks.The management VLAN is a VLAN created to enhance the network security. Without Management VLAN, the configuration commands and data packets are transmitted in the same network. There are risks of unauthorized users accessing the management page and modifying the configurations. A management VLAN can separate the management network from the data network and lower the risks.
SNMP(Only for configuring a single device) Configure SNMP to write down the Location and Contact detail. You can also click Manage to jump to Settings > Services > SNMP.
Loopback Control (Only for EAPs with multiple LAN ports)
Loopback refers to the routing of data streams back to their source in the network. You can disable loopback control for the network or enable Loopback Detection to help detect loops that occur on a specific port. When a loop is detected on a port, the port will be blocked.
Layer-3 AccessibilityWith this feature enabled, devices from a different subnet can access controller-managed devices.
LLDP LLDP (Link Layer Discovery Protocol) can help discover devices.

■ Smart Antenna (Only for certain models)

In Smart Antenna, you can turn on the function to improve Wi-Fi performance for user-heavy scenarios through antenna array and intelligent algorithm. This help overcome obstacles and signal interference. ![](images/8c9276128cd6bcaf15d61512c88c5d2a4595ef6040036f0e904d12f2d060b764.jpg)

■ Advanced

In Advanced, configure Load Balance and QoS to make better use of network resources. Load Balance can control the client number associated to the AP, while QoS can optimize the performance when handling differentiated wireless traffics, including traditional IP data, VoIP (Voice-over Internet Protocol), and other types of audio, video, streaming media. Select each frequency band and configure the following parameters and features. ![](images/6b81b2190202334fbf7dccaf0a5ca5ce9cbf0fa69e951c1fb1d43993733d8251.jpg)
Max Associated ClientsEnable this function and specify the maximum number of connected clients. If the connected client reaches the maximum number, the AP will disconnect those with weaker signals to make room for other clients requesting connections.
RSSI Threshold Enable this function and enter the threshold of RSSI (Received Signal Strength Indication). If the client's signal strength is weaker than the threshold, the client will lose connection with the AP.
ETH VLAN/ETH2 VLAN/ETH3 VLAN(Only for APs with multiple LAN ports) Enable this function and add the corresponding AP's LAN port to the VLAN specified here. Then the hosts connected to this AP can only communicate with the devices in this VLAN.
ETH3 PoE Out (Only for APs with the PoE out port) Enable this function to supply power to the connected device on this port.
Wi-Fi Multimedia (WMM)With WMM enabled, the AP maintains the priority of audio and video packets for better media performance.
No AcknowledgmentEnable this function to specify that the APs will not acknowledge frames with QoS No Ack. Enabling No Acknowledgment can bring more efficient throughput, but it may increase error rates in a noisy Radio Frequency (RF) environment.
Unscheduled Automatic Power Save DeliveryWhen enabled, this function can greatly improve the energy-saving capacity of clients.
Non-PSC Channels (Only for AP supporting 6GHz band) When enabled, the AP can use both non-PSC channels and PSC channels. Note that some clients may not discover 6GHz networks using non-PSC channels.
OFDMA (Only for AP supporting 802.11 ax or later standards) Enable this feature to enable multiple users to transmit data simultaneously, and it will greatly improves speed and efficiency. Note that the benefits of OFDMA can be fully enjoyed only when the clients support OFDMA.

■ Manage Device

In Manage Device, you can upgrade the device's firmware version manually, move it to another site, synchronize the configurations with the controller and forget the AP. ![](images/bbceee7d9915722a68ff6c85b4b256c97b9ba5a358f44160ec240d806de3f22d.jpg)
Custom UpgradeClick Browse and choose a file from your computer to upgrade the device. When upgrading, the device will be reboot and readopted by the controller. You can also check the box of Upgrade all devices of the same model in the site after the firmware file is uploaded.
Copy Configuration Select another device at the current site to copy its configurations.
Move to SiteSelect a site which the device will be moved to. After moving to another site, device configurations on the prior site will be replaced by that on the new site, and its traffic history will be cleared.
Force Provision(Only for configuring a single device) ClickForce Provisionto synchronize the configurations of the device with the controller. The device will lose connection temporarily, and be adopted to the controller again to get the configurations from the controller.
Forget this APClickForgetand then the device will be removed from the controller. Once forgotten, all configurations and history related to the device will be wiped out.
Download Device InfoIf the device has an abnormality, you can download the device information and provide it to our R&D personnel to analyze the problem.⚠ Note:Firmware updates are required for earlier devices to obtain complete information.

6.4.2 Monitor APs

One panel and four tabs are provided to monitor the device in the Properties window: Monitor Panel, Details, Clients, Mesh, and Statistics.

Monitor Panel

The monitor panel illustrates the active channel information on each radio band, including the AP's operation channel, radio mode and channel utilization. Four colors are used to indicate the percentage of Rx Frames (blue), Tx Frames (green), Interference (orange), and Free bandwidth (gray). ![](images/efa0c663953370dcbdc79cf36e9e909944999a32189b17984c17c8c2d9db539a.jpg)
bar_stacked | Category | Rx Frames | Tx Frames | Interference | Free | |---|---|---|---|---| | b/g/n/ax mixed 2.4 GHz | 6 | 0 | 0 | 88% Utilized | | High | 0 | 1 | 0 | 0 | | a/n/ac/ax mixed 5 GHz-1 | 40 | 0 | 0 | 20% Utilized | | Acceptable | 0 | 1 | 0 | 0 | | a/n/ac/ax mixed 5 GHz-2 | 100 | 1 | 0 | 6% Utilized | | Good | 0 | 0 | 0 | 0 | | ax only 6 GHz | 37 | 0 | 0 | 0% Utilized | | Good | 0 | 0 | 0 | 0 |
You can hover the cursor over the channel bar for more details.
Ch.Util.(Busy/Rx/Tx)51% / 32% / 4%
Tx Pkts/Bytes4195 / 847.04 KB
Rx Pkts/Bytes24247 / 6.47 MB
Tx Error/Dropped0.0% / 0.0%
Rx Error/Dropped0.0% / 0.0%
Ch.Util.(Busy/Rx/Tx) Displays channel utilization statistics. Busy: Displays the sum of Tx, Rx, and also non-WiFi interference, which indicates how busy the channel is. Rx: Indicates how often the radio is in active receive mode. Tx: Indicates how often the radio is in active transmit mode. Tx Pkts/Bytes Displays the amount of data transmitted as packets and bytes. Rx Pkts/Bytes Displays the amount of data received as packets and bytes.
Tx Error/DroppedDisplays the percentage of transmit packets that have errors and the percentage of packets that were dropped.
Rx Error/DroppedDisplays the percentage of receive packets that have errors and the percentage of packets that were dropped.

Details

In Details, you can view the basic information, traffic information, and radio information of the device to know the device's running status.

Overview

In Overview, you can view the basic information of the device. The listed information varies due to the device's status.
Overview
MAC Address:IP Address:
40-3F-8C-00-01-10192.168.0.100
Model:Firmware Version:
EAP690E HD(EU) v1.01.0.0 Build 20220708 Rel. 3 6560
CPU Utilization:Memory Utilization:
4%22%
Uptime:
--

■ LAN (Only for devices in the Connected status)

Click LAN to view the traffic information of the LAN port, including the total number of packets, the total size of data, the total number of packets loss, and the total size of error data in the process of receiving and transmitting data.
LAN
Rx Packets:Rx Bytes:
4724936.73 KB
Rx Dropped Packets:Rx Errors:
00
Tx Packets:Tx Bytes:
822647.23 KB
Tx Dropped Packets:Tx Errors:
00
■ Uplink (Only for devices in the Connected status) Click Uplink to view the traffic information related to the uplink device.
Uplink (Wireless)
Uplink Device:Signal:
CC-32-E5-F7-DD-1C-22 dBm
Tx Rate:Rx Rate:
104Mbps526Mbps
Down Pkts/Bytes:Up Pkts/Bytes:
29 / 9.11 KB18 / 2.50 KB
Activity Speed: i
1.16 KB /s
■ Downlink (Only for devices in the Connected status) Click Downlink to view the information related to the downlink devices.
Downlink
PortDevice NameDevice IPDevice MACLink StatusSpeed
ETH0------Disconnected--
ETH1------Disconnected--
ETH2------Disconnected--
ETH3------Disconnected--
FXS------Connected--

■ Radios (Only for devices in the Connected status)

Click Radio to view the radio information including the frequency band, the wireless mode, the channel width, the channel, and the transmitting power. You can also view parameters of receiving/transmitting data on each radio band.

! Note:

The 6 GHz band is only available for certain devices.
2.4 GHz5 GHz-15 GHz-26 GHz
Mode:Channel Width:
802.11b/g/n/ax mixed20/40MHz
Channel:Tx Power:
6 / 2437MHz20
Rx Packets:Rx Bytes:
00
Rx Dropped Packets:Rx Errors:
00
Tx Packets:Tx Bytes:
2550726.87 KB
Tx Dropped Packets:Tx Errors:
00

Clients

In Clients, you can view the information of users and guests connecting to the AP, including client name, MAC address and the connected SSID. Users are clients connected to the AP's SSID with Guest Network disabled, while Guests are clients connected to that with Guest Network enabled. You can click the client name to open its Properties window. ![](images/1cc0b6ca864b28c79085733028b7e8b6b373cdd95145ab9444a42895389a349a.jpg) Click History to view the client history. In the History page, you can specify the date or time period to view the clients connected during specific time, and click Export to download the list of clients. ![](images/0378a82d6e7eb24c5b00be15ac3eb0ac4b51a1d06a14e1b82527cd5aac29c918.jpg)

Mesh (Only for pending/connected/isolated devices supporting Mesh)

Mesh is used to establish a wireless network or expand a wired network through wireless connection on 5 GHz radio band. In practical application, it can help users to conveniently deploy APs without requiring Ethernet cable. After mesh network establishes, the APs can be configured and managed in the controller in the same way as wired APs. Meanwhile, because of the ability to self-organize and self-configure, mesh also can efficiently reduce the configuration. Note that only certain AP models support Mesh, and the APs should be in the same site to establish a Mesh network. To understand how mesh can be used, the following terms used in the Controller will be introduced:
Root APThe AP is managed by the Controller with a wired data connection that can be configured to relay data to and from mesh APs (downlink AP).
Isolated APWhen the AP which has been managed by the Controller before connects to the network wirelessly and cannot reach the gateway, it goes into the Isolated state.
Mesh APAn isolated AP will become a mesh AP after establishing a wireless connection to the AP with network access.
Uplink AP/Downlink APAmong mesh APs, the AP that offers the wireless connection for other APs is called 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 should be no more than 3.
A common mesh network is shown as below. Only the root AP is connected by an Ethernet cable, while other 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 APs can detect the AP in range and make itself available for adoption in the controller. ![](images/62447f0a9d28e2a8a2556715495befec169a69cf342d77f4b9af17e3f5609948.jpg)
flowchart
graph TD
    A["Host A (Controller Host) Switch"] -->|Wired Connection| B["Root AP Mesh AP"]
    B -->|Wireless Uplink| C["Mesh APs (Hops: 2)"]
    B --> D["Internet"]
    B --> E["Router (DHCP Server)"]
    E --> F["Internet"]
After all the APs are adopted, a mesh network is established. The APs connected to the network via wireless connection also can broadcast SSIDs and relay network traffic to and from the network through the uplink AP. To build a mesh network, follow the steps below: 1) Enable Mesh function. 2) Adopt the Root AP. 3) Set up wireless uplink by adopting APs in Pending(Wireless) or Isolated status. 1. Go to Settings > Site to make sure Mesh is enabled. ![](images/ce93b79cbabde365b1010d708f7144163a197cce816a9b4d1fe9d5b1a6adc982.jpg) 2. Go to Devices to make sure that the Root AP has been adopted by the controller. The status of the Root AP is Connected. ![](images/2a470a81d39ce03ca57fc13d7f199051ec52fe662425d6b1605c4ee1b99624d6.jpg) 3. Install the AP that will uplink the Root AP wirelessly. Make sure the intended location is within the range of Root AP. The APs that is waiting for Wireless Uplink includes two cases: factory default APs and APs that has been managed by the controller before. Go to Devices to adopt an AP in Pending (Wireless) status or link an isolated AP. 1) For the factory default AP, after powering on the device, the AP will be in Pending (Wireless) status with the icon PENDING in the controller. Click to adopt the AP in Pending (Wireless) status in the Devices list. ![](images/b395026792b9887d28d10ff9c0ea223c192749e924348e61671217130afee39a.jpg) After adoption begins, the status of Pending (Wireless) AP will become Adopting (Wireless) and then Connected (Wireless). It should take roughly 2 minutes to show up Connected (Wireless) with the icon CONNECTED within your controller. 2) For the AP that has been managed by the Controller before and cannot reach the gateway, it goes into Isolated status when it is discovered by controller again. Click ♂ to connect the Uplink AP in the Devices list. ![](images/9ca890497cb6b4191e21103ffb3e9196309e35fd7179373c04ec4d52de862e2c.jpg) The following page will be shown as below, click Link to connect the Uplink AP. ![](images/f2481f2dba7b1c27277c055e9dcbe806ce8a758e20d9f009e468009ed6c05724.jpg) Once mesh network has been established, the AP can be managed by the controller in the same way as a wired AP. You can click the AP's name in the Devices list, and click Mesh to view and configure the mesh parameters of the AP in the Properties window. In Mesh, if the selected AP is an uplink AP, this page lists all downlink APs connected to the AP. ![](images/67b207339c8d170ba76b396784e00e4bb8d1bbd55596733f059d76e6a1c596c6.jpg) If the selected AP is a downlink AP, this page lists all available uplink APs and their channel, signal strength, hop, and the number of downlink APs. You can click Rescan to search the available uplink APs and refresh the list, and click Link to connect the uplink AP and build up a mesh network. ![](images/acd7ce816bdfc204fb793b44ccd5308f1859a26fcaf6eed003236ae0117e861a.jpg) ![](images/28b09b0822b3de140ab32d3a823087a90eba508080d56871ba90d7e8d22150a8.jpg) The icon appears before the priority uplink AP of the downlink AP. If you want to set another AP as the priority AP, click Link in Action column. ![](images/e78e9b98fad6ed37fabb6fc14724454f006aa3fa7457be91c7c019bbba0d01f5.jpg) The icon appears before the current uplink AP of the downlink AP. ![](images/cd50999d19407c8acc89ff8ff4e9989312a08009863fc219873b6c0aa445be80.jpg)

Tips:

- You can manually select the priority uplink AP that you want to connect in the uplink AP list. To build a mesh network with better performance, we recommend that you select the uplink AP with the strongest signal, least hop and least downlink AP. - Auto Failover is enabled by default, and it allows the controller automatically select an uplink AP for the isolated AP to establish Wireless Uplink. And the controller will automatically select a new uplink AP for the mesh APs when the original uplink fails. For more details about Mesh global configurations, refer to the Mesh feature in 4. 2.2 Services.

Tools

In Tools, you can enable RF Scanning to scan the RF (Radio Frequency) environments around the AP, which is useful for spectral analysis in channel selection and planning. ![](images/90efc9823a6901eb34d53ce95073b7071a2f368a633bdfeefad03fbd8c1dc88e.jpg)

Note:

- The RF scanning may take several minutes. During the scanning, all clients using this AP will be disconnected, and the AP will be offline. You should select a spare time of network to start scanning. • The APs in the mesh network do not support RF Scanning. Select each frequency band to view and analyze the scan results. ![](images/b3797eef45e455b9d981b54f48be6d631c003bc0b8ff2e9d9e1c4ed443142d17.jpg)
bar | Frequency Band | Channel Count | Value | | -------------- | ------------- | ----- | | 20 MHz | 36 | 52 | | 20 MHz | 40 | 56 | | 20 MHz | 44 | 60 | | 20 MHz | 48 | 64 | | 40 MHz | 38 | 54 | | 40 MHz | 46 | 62 | | 80 MHz | 42 | 58 | | 80 MHz | 106 | 106 |
Each colored bar graph displays the information about channel utilization and interference on a channel. The filling area of the bar represents the channel utilization. And the larger filling area means the higher utilization, which indicates the channel is busier in transmitting data. The color shade represents the level of interference. And the legend is displayed at the top. The results of different bands are displayed in different channel widths. The number below the bar graph displays the corresponding channel number for each channel width option. For example, channels 42, 58 and 106 are three of the 80 MHz channels. And the channel outline in blue is in use currently. ![](images/331ab78d1f20bc9d40c6bb8cf9a99bb82167eee7364ef989a9ae53d785449306.jpg) You can hover the cursor over a channel option for more details. ![](images/4e167403f3ac764a079831246fb98a4d1de3d4c67b25c93c0e5f2799e1bf80b8.jpg)
bar | Channel | Bandwidth (MHz) | Bandwidth (dBm) | Bandwidth (dBm) | |---------|-----------------|-----------------|-----------------| | Radio | 2.4G (b/g/n mixed) | -91 dBm | -29 dBm | | Channel Width | 20 MHz | | | | Frequency Range | 2401-2423 MHz | | | | Utilization | 37.00% | | | | Interference | -95 dBm | | | | Interference Type | | | | RF Scanning: 2.4GHz, 5GHz, Scan: The color bar reflects channel utilization (Lower is better). | Bandwidth (MHz) | 1 | 6 | 11 | | Bandwidth (MHz) | 2 | 7 | 12 | | Bandwidth (MHz) | 3 | 8 | 13 | | Bandwidth (MHz) | 4 | 9 | 10 | | Bandwidth (MHz) | 5 | | | | Bandwidth (MHz) | 6 | | | | Bandwidth (MHz) | 7 | | | | Bandwidth (MHz) | 8 | | | | Bandwidth (MHz) | 9 | | | | Bandwidth (MHz) | 10 | | | | Bandwidth (MHz) | 11 | | | | Bandwidth (MHz) | 12 | | | | Bandwidth (MHz) | 13 | | | | Bandwidth (MHz) | 14 | | | | Bandwidth (MHz) | 15 | | | | Bandwidth (MHz) | 16 | | | | Bandwidth (MHz) | 17 | | | | Bandwidth (MHz) | 18 | | | | Bandwidth (MHz) | 19 | | | | Bandwidth (MHz) | 20 | | | | Bandwidth (MHz) | 21 | | | | Bandwidth (MHz) | 22 | | | | Bandwidth (MHz) | 23 | | | | Bandwidth (MHz) | 24 | | | | Bandwidth (MHz) | 25 | | | | Bandwidth (MHz) | 26 | | | | Bandwidth (MHz) | 27 | | | | Bandwidth (MHz) | 28 | | | | Bandwidth (MHz) | 29 | | | | Bandwidth (MHz) | 30+ | -91 dBm to -29 dBm, -96 to -48 dBm, Scan: The color bar reflects channel utilization (Lower is better). RF Scanning: 40 MHz Channels, RF Scanning: 20 MHz Channels, RF Scanning: 40 MHz Channels
Radio Displays the radio that the AP uses. Channel Width Displays the width of the channel. Used Channels Displays the channels in use. Frequency Range Displays the range of frequencies. Utilization Displays the percentage of the frequency range already in use. Interference Displays the level of interference. Interference Type Displays the type of interface, including MWO (Microwave Oven), CW (Continuous Wave), WLAN (Wi-Fi signals) and FHSS (Frequency Hopping Spread Spectrum).

Statistics

In Statistics, you can monitor the utilization of the device in last 24 hours via charts, including CPU/Memory Monitor, Channel Utilization, Dropped Packets, and Retried Packets. To view statistics of the device in certain period, click the chart to jump to 8.2 View the Statistics of the Network. ![](images/d1dcf2016a6a711d9ca9663f128b1be28013a689ecc452d0840759d3ec5f54bc.jpg)
line | Time | CPU | Memory | | ---------- | ---- | ------ | | 11:15 am | ~0% | 12% | | 04:40 pm | ~0% | 12% | | 10:05 pm | ~0% | 12% | | 03:30 am | ~0% | 12% | | 11:10 am | ~0% | 12% |

6.5 Create and Manage Stack Groups

6.5.1 Introduction to Stack

Stack is a device virtualization technology that connects two and above switches supporting stack features via Ethernet cables through their stack ports, which logically virtualize them to one device as a whole to forward data in the network. Through this feature, switches can be stacked to improve reliability, expand port numbers, increase bandwidth, simplify networking, and etc. In a stack system, the switches can be categorized mainly into two roles: \- Master Switch A stack system has only one master switch. It manages and controls devices in the whole stack system. \- Member Switch A stack system may have one or several member switches. They only forward data as standby devices of the master switch. When the master switch fails, a member switch will be re-elected as the new master switch. ![](images/37972bfce74bb5c388bec65a6bcde59d8c342bfb47b9fef41d9bee5d1f494752.jpg)
flowchart
graph TD
    A["Router"] --> B["Switch"]
    A --> C["Switch"]
    B --> D["Router"]
    C --> E["Switch"]
    C --> F["Switch"]
    D --> G["Master Switch"]
    E --> G
    F --> G
    G --> H["Member Switch"]
    H --> I["Router"]
    style A fill:#4CAF50,stroke:#388E3C
    style B fill:#4CAF50,stroke:#388E3C
    style C fill:#4CAF50,stroke:#388E3C
    style D fill:#4CAF50,stroke:#388E3C
    style E fill:#4CAF50,stroke:#388E3C
    style F fill:#4CAF50,stroke:#388E3C
    style G fill:#4CAF50,stroke:#388E3C
    style H fill:#4CAF50,stroke:#388E3C
    style I fill:#4CAF50,stroke:#388E3C
    subgraph Stack
        B
        C
        D
        E
        F
    end

6.5.2 Create a Stack Group

1. Select a site from the drop-down list of Organization. Go to Devices > Device Group > Stack Group.

2. Click Create New Stack Group. Configure the parameters.

![](images/ee000718338d74a13ef9b3a0b3a77bf7dd71d44e4878b198bad35ab206abbd2b.jpg) Stack Name Enter a name to identify the stack group. Select Member Select the switches to be stacked, and configure the following parameters: Unit: Specify the unit ID of the switch. Each switch in the stack has a unique unit ID for device management. Priority: Specify the stack priority of the switch. The higher the stack priority, the more likely the switch is to be elected as the Master Switch. A smaller value means a higher priority. Config Stack Port Group: Click the port to be stacked and choose the group ID. A port can join only one group. Note: To change the stacking mode of a port, please link down it first. After a port is switched to stacking mode, it can no longer be used as a service port.

3. Apply the settings. Now you can connect the stack ports configured with the same group ID via Ethernet cables to stack the switches.

Note:

- Do not connect a stack port to a non-stack port. Otherwise, device operation may be affected. - Connect stack ports only when they are set to the same group ID.

6.5.3 Configure and Monitor the Stack Group

The stack group logically virtualizes switches to one device as a whole. You can configure and monitor stack groups in the same way as configuring and monitoring switches. For details, refer to 6.3 Configure and Monitor Switches.

6.6 Create and Manage Bridge Groups

6.6.1 Introduction to Bridge

Outdoor Bridge easily builds point-to-point and point-to-multi-point long range wireless connections. In practical application, it can help users to conveniently deploy APs over long range. In a bridge system, the APs can be categorized mainly into two roles: \- Main AP The Main AP connects to your gateway/router for network access. A bridge system generally has only one Main AP. \- Sub-AP Sub-APs connect to the Main AP via wireless bridge. A bridge system may have one or several Sub-APs. ![](images/5add86e5d66a1f8d1049430b466de13eb106a5239a4c9c08fa951d19b4a5302f.jpg)
flowchart
graph TD
    A["On-premises Controllers"] --> B["Network Video Recorder"]
    B --> C["Switch"]
    C --> D["Router"]
    D --> E["Internet"]
    F["Omada Hardware Controller"] --> G["Switch"]
    H["Omada Software Controller"] --> G
    I["Omada Cloud-Based Controller (Subscription Required)"] --> E
    J["Long-Range Outdoor Access Point"] --> K["Long-Range Outdoor Access Point"]
    L["Cloud Access"] --> M["Omada App"]
    N["Web Browser"] --> O["Omada App"]
    P["Long-Range Distance"] --> Q["Long-Range Outdoor Access Point"]

6.6.2 Create a Bridge Group

1. Obtain a bridge kit product, connect an AP to your gateway/router for network access, and power on all the APs in the kit. The AP with network access will work as the Main AP, and the other AP(s) will automatically connect to the Main AP via wireless bridge. 2. Launch your controller and select a site from the drop-down list of Organization. 3. Go to Devices > Device Group > Bridge Group. The controller will detect the bridge kit APs and show them in the list. ![](images/e5e17afb1df6375eee19f0511cb5a4ea0d651a253cd7c8b4b94829f7dc642824.jpg)

6. 6. 3 Configure and Monitor the Bridge Group

You can configure and monitor bridge groups in the same way as configuring and monitoring APs. For details, refer to 6.4 Configure and Monitor APs. ![](images/162f1c5b132cd32b6f3f6057efef2da8e0e4f934c077b3b3e39bea32c81a1773.jpg)

Monitor and Manage the Clients

This chapter guides you on how to monitor and manage the clients through the Clients page using the clients table and the properties window and the Hotspot Manager system. To view clients that have connected to the network in the past, refer to View the Statistics During the Specified Period with Insight. This chapter includes the following sections: • 7.1 Manage Wired and Wireless Clients in Clients Page • 7.2 Manage Client Authentication in Hotspot Manager ![](images/50172ca4749ba1dd5d962da091c5d4c3ab62b7c79c0291d9da3a66af4db0e84d.jpg)

7.1 Manage Wired and Wireless Clients in Clients Page

7.1.1 Introduction to Clients Page

The Clients page offers a straight-forward way to manage and monitor clients. It displays all connected wired and wireless clients in the chosen site and their general information. You can also open the Properties window for detailed information and configurations. ![](images/9f3bb3c93cc897b32e7a188dc5bd1bdece942e840df776d04a1c4829b52a6fe6.jpg)

7. 1. 2 Using the Clients Table to Monitor and Manage the Clients

To quickly monitor and manage the clients, you can customize the columns and filter the clients for a better overview of their information. Also, quick operations and batch configuration are available.

■ Customize the Information Columns

Click next to the Action column and you have three choices: Default Columns, All Columns, and Customize Columns. To customize the information shown in the table, click the checkboxes of information type. To change the list order, click the column head and the icon 🔊 appears for you to choose the ascending or descending order. ![](images/68243a7ee252256cb3c286ff022f714d0464366dd6a1e9197df4a8c3b9923881.jpg) When this icon appears in the Wireless Connection column, it indicates the client is in the power-saving mode.

■ Filter the Clients

To search specific client(s), use the search box above the table. To filter the clients by their connection type, use the tab bars above the table. For wireless clients, you can further filter them by the frequency band and the type of connected wireless network.
Search Name, IP, MAC or channelFilter clients using the search box based on username, IP address, MAC address or channel.
All (2)Wireless (1)Wired (1)Filter clients based on their connection type.
All (2)2.4 GHz (0)5 GHz (2)(For wireless clients) Filter wireless clients based on the frequency band they are using.
All (2)Users (0)Guests (2)(For wireless clients) Filter wireless clients based on the type of connected wireless network. Guests are clients connected to the guest network, which you can set during the Quick Setup, creating wireless networks, etc.

■ Quick Operations

For quick operations on a single client, click the icons in the Action column. The available icons vary according to the client status and connection type.
Click to block the client in the chosen site. You can view blocked clients in 8.5.1 Known Clients.
(With portal authentication enabled) Click to manually authorize the client that has not passed the portal authentication.
(With portal authentication enabled) Click to unauthorized the client that has passed the portal authentication.
(For wireless clients) Click to reconnect the wireless client to the wireless network.

■ Multiple Select for Batch Configuration

To select multiple clients and add them to the Properties window, click ☐ on the upper-right and then check the boxes. When you finish choosing the clients, click Edit Selected and the chosen client(s) will be added to the Properties window for batch client configuration. ![](images/53b311e15fa18c1ae5736cf7617c537139a63c28a7a1a044c9ddb77ad9901d98.jpg)

7. 1. 3 Using the Properties Window to Monitor and Manage the Clients

In Properties window, you can view more detailed information about the connected client(s) and manage them. To open the Properties window, click the entry of a single client, or click the icon to select multiple clients for batch configuration. Use the following icons for the Properties window.
Click to select multiple clients and add them to the Properties window for batch monitoring and management.
Click to minimize the Properties window to an icon. To reopen the minimized Properties window, click ☐.
Click to maximize the Properties window. You can also use the icon on pages other than the Clients page.
Click to close the Properties window of the chosen client(s). Note that the unsaved configuration for the client(s) will be lost.
The number on the lower-right shows the number of clients in the batch client configuration.

Monitor and Manage a Single Client

■ Monitor a Single Client

After opening the Properties window of a single client, you can view the basic information, traffic statistics, and connection history under the Details and History tabs. Under the Details tab, Overview and Statistics displays the basic information and traffic statistics of the client, respectively. The listed information varies due to the client's status and connection type. ![](images/c56272cf27bd9ec8bd97a59da5c28436e19db39546bee3b4992e69f382489b77.jpg) ![](images/e3e9741fb208fe9fd25a28b7f59bde1a6ec49adf9c996c7afa255761429e9e5f.jpg) Under the History tab, you can view the connection history of the client. ![](images/0e8761139559244bd75509734f67ef67276cbdfa24805d1c5b5662e803611943.jpg)

■ Manage a Single Client

In Config, you can configure the following parameters: ![](images/1a9ca3afcd901164d02249e9728cb027189e9a81999bc1ad62f92282dae65b22.jpg)
NameSpecify the client's name to better identify different clients, and the name is used as the client's username in the table on the Clients page.
Rate LimitSelect an existing rate limit profile, create a new rate limit profile or customize the rate limit for the client.Custom: Specify the download/upload rate limit based on needs.Note: Rate Limit on this page is only available for the clients connected to the APs. To limit the rate of the clients connected to the gateway or switch, go to Bandwidth Control page.
Download/Upload LimitClick the checkbox and specify the rate limit for download/upload for wireless clients using the voucher code(s). The value of the download and upload rate can be set in Kbps or Mbps.
Use Fixed IP AddressClick the checkbox to configure a fixed IP address for the client. With this function enabled, select a network and specify an IP address for the client. To view and configure networks, refer to4.3 Configure Wired Networks.Note: A gateway is required for this function. Otherwise, you cannot set a fixed IP address for the client.
Lock To APEnable the function, and select one or multiple APs, then the client will be locked to the selected APs. This feature helps prevent a static client from roaming frequently between multiple APs.

Monitor and Manage Multiple Clients

To manage multiple clients at the same time, click ☐, select multiple clients, and click Edit Selected. Then you can configure the following parameters under the Config tab. ![](images/43a668d04bf756f65973f3bc572e72c1c5b3415952e47c2070d65ff0b3b6e49e.jpg)
Rate LimitSelect an existing rate limit profile, create a new rate limit profile or customize the rate limit for the clients.Keeping Existing: The rate limit of the chosen clients will remain their current settings.Custom: Specify the download/upload rate limit based on needs.Disabled: The rate limit of the chosen clients will be disabled.Note: Rate Limit on this page is only available for the clients connected to the APs. To limit the rate of the clients connected to the gateway or switch, go to Bandwidth Control page.
Download/Upload LimitClick the checkbox and specify the rate limit for download/upload for wireless clients using the voucher code(s). The value of the download and upload rate can be set in Kbps or Mbps.
IP SettingKeeping Existing: The IP setting of the chosen clients remains their current settings.Use DHCP: The IP addresses of the clients is automatically assigned by the DHCP server, such as the Layer 3 switch and the gateway.Use Fixed IP Address: Select a network and assign fixed IP addresses to the chosen clients manually. To view and configure networks, refer to4.3 Configure Wired Networks. Note that a gateway is required for this function. Otherwise, you cannot set fixed IP addresses for the chosen clients.
Lock To APLock to AP helps prevent static clients from roaming frequently between multiple APs.Keeping Existing: Keep the current settings of the chosen clients Cooperative: Disable Lock to AP of the chosen clients.Enable: Enable Lock to AP, and select one or multiple APs, then the chosen clients will be locked to the selected APs.
You can view their names and IP addresses in the Clients tab and remove client(s) from Batch Client Configuration by clicking ✗ in the Action column. ![](images/30cdb2c5ebd4fffa46032de0655cabb3965b373412960d0e06a144b4a7036d46.jpg)

7.2 Manage Client Authentication in Hotspot Manager

Hotspot Manager is a portal management system for centrally monitoring and managing the clients authorized by portal authentication. The following four tabs are provided in the system for a easy and direct management. Dashboard Monitor portal authorizations at a glance through different visualizations. Authorized Clients View the records of the connected and expired portal clients.
VouchersCreate vouchers for Portal authentication, and view and manage the related information.
Local UsersCreate local user accounts for Portal authentication, view their information, and manage them.
Form Auth Data Customize your survey contents and publish it to collect data.
OperatorsCreate operator accounts for Hotspot management, view their information, and manage them.
To access the system, click Hotspot Manager from the drop-down list of Organization. To log out of the system, click the account icon 🔗 at the upper-right corner, then click Log Out.

7.2.1 Dashboard

In the dashboard, you can monitor portal authorizations at a glance through different visualizations. To open the dashboard, click Hotspot Manager from the drop-down list of Organization and click Dashboard in the pop-up page. Specify the time period to view portal authorization histories. ![](images/8c677b93084ce4754a6571eb1e2a5d98fef57414630f237d38c9398e6c166a12.jpg)
pie | Authentication Type | Total Hotspot (%) | | :--- | :--- | | Form | 0 (0%) | | Hotspot Radius | 0 (0%) | | Local User | 0 (0%) | | SMS | 0 (0%) | | Voucher | 0 (0%) |

7.2.2 Authorized Clients

The Authorized Clients tab is used to view and manage the clients authorized by portal system, including the expired clients and the clients within the valid period. To open the list of Authorized Clients, click Hotspot Manager from the drop-down list of Organization and click Authorized Clients in the pop-up page. You can search certain clients using the search box, view their detailed information in the table, and manage them using the action column. ![](images/0b3a0109984893d03227d92a813b45f8ee7d7e1a1cfb2a8d3fac44a2e79c6fd3.jpg)
Click to extend the valid period of the authorized client. You can choose the preset time length or set a customized period based on needs.
Click to disconnect the authorized client(s). If you disconnect an authorized client, the client needs to be re-authenticated for the next connection.
Click to delete the expired client from the list.

7.2.3 Vouchers

The Vouchers tab is used to create vouchers and manage unused voucher codes. With voucher configured and codes created, you can distribute the voucher codes generated by the controller to clients for them to access the network via portal authentication. For detailed configurations, refer to 4. 9.1 Portal.

Create vouchers

Follow the steps below to create vouchers for authentication: 1. Click Hotspot Manager from the drop-down list of Organization and click Vouchers > Voucher Groups in the pop-up page. 2. Click +Create Vouchers Group on the lower-left, and the following window pops up. Configure the following parameters and click Save. ![](images/590200fffb846e9aa44f60cc3907855a1f9dc498844c03dfe69637b570b761ee.jpg) Vouchers Group Name Enter a name to identify the group. Portal Privilege All: The vouchers will take effect for all voucher type portals, including newly created ones. Portal: Select the portal for which the vouchers will take effect. Code Length Specify the length of the code(s) from 6 to 10 digits. Code Format Choose whether the voucher code is generated by numbers, letters, or a mixture. Amount Specify the number of voucher codes you want to create.
Portal LogoutCheck the box to allow guests to log out of the portal by accessing a URL (portal. tplink.net/portal/logout by default). You can change the default URL by editing portal. logout.domain in the omada.properties file.Note: Some devices may require firmware update to support Portal Logout.
Type Select a type to limit the usage counts or the number of authorized users of a voucher code.
Limited Usage Counts: The voucher code can only be used for a limited number of times within its valid period.
Limited Online Users: The voucher code can be used for an unlimited number of times within its valid period, but only a limited number of wireless clients can access the network with this voucher code at the same time.
Unlimited For Usage: The voucher code can be used for an unlimited number of times within its valid period.
Duration Type Specify whether to limit the voucher duration or client duration.
TimingBy time: The voucher code takes effect within a fixed period of time after authentication.
By Usage: The voucher code takes effect according to the actual time used by the client.
Duration Select the valid period for the voucher code(s).
Rate LimitSelect an existing rate limit profile, create a new rate limit profile or customize the rate limit for the voucher codes.
Custom: Specify the download/upload rate limit based on needs.
Download/Upload Limit: Click the checkbox and specify the rate limit for download/upload for wireless clients using the voucher code(s). The value of the download and upload rate can be set in Kbps or Mbps. Note: Download/Upload Limit on this page are only available for wireless clients connected to the SSIDs with Portal authentication enabled. To limit the rate of wired clients connected to the switch and gateway, go to the Settings >Transmission >Bandwidth Control.
Traffic LimitClick the checkbox and specify the daily/weekly/monthly/total traffic limit for the voucher, and the value of the traffic limit can be set in MB or GB. Once the limited is reached, the client(s) can no longer access the network using the voucher. Note: Traffic Limit on this page are only available for wireless clients connected to the SSIDs with Portal authentication enabled. To limit the rate of wired clients connected to the switch and gateway, go to the Settings >Transmission >Bandwidth Control.
Voucher ValidityEnable this option and configure the start time and expiration time of the voucher. The voucher can no longer be used no matter whether it runs out of available time or reaches the expiration time
Unit Price Set the amount and currency type for the voucher (for statistical purposes only).

Description (optional)

Enter notes for the created voucher code(s), and the input description is displayed in the voucher list under the voucher tab.

3. The voucher group is generated.

![](images/6af794079ddc3a22238c39ba9926f8aad7644453bba93f2848a985637d27d820.jpg)

You can click the Details icon to view the voucher codes.

![](images/2f85e861526c35fe4219844d8e238d734bc074ca768d1239aa8c28ba3978be3d.jpg)
pie | Credit Type | Amount (RMB) | Status | Remaining Traffic | |---|---|---|---| | Credit Card | 10 | Unrated | - | | Total Amount | 0 | Unrated | - | | Credit Card | 10 | Unrated | - | | Total Amount | 0 | Unrated | - | | Credit Card | 10 | Unrated | - | | Total Amount | 0 | Unrated | - | | Credit Card | 10 | Unrated | - | | Total Amount | 0 | Unrated | - | | Credit Card | 10 | Unrated | - | | Total Amount | 0 | Unrated | - |
4. Print the vouchers. Click 📋 to print a single voucher, or click checkboxes of vouchers and click 📋 Print Selected Vouchers to print the selected vouchers. And you can click 📋 Print All Unused Vouchers to print all unused vouchers.
307690Valid for 8hLimited Usage Counts One084520Valid for 8hLimited Usage Counts One
924665Valid for 8hLimited Usage Counts One232608Valid for 8hLimited Usage Counts One
701945Valid for 8hLimited Usage Counts One473875Valid for 8hLimited Usage Counts One
141716Valid for 8hLimited Usage Counts One999934Valid for 8hLimited Usage Counts One
825813Valid for 8hLimited Usage Counts One180815Valid for 8hLimited Usage Counts One
5. Distribute the vouchers to clients, and then they can use the codes to pass authentication. If a voucher code expires, it will be automatically removed from the list. 6. To delete certain vouchers manually, click 📋 to delete a single voucher, or Delete to delete multiple voucher codes at a time. 7. On the Vouchers > Statistic page, you can view the historical statistical data of vouchers. ![](images/ebec5cdefc149698de9a3511da1ad71a2048446c70dd07463bb5fe3573e71f21.jpg)

7.2.4 Local Users

The Local Users tab is used to create user accounts for authentication. With the Local User configured, clients are required to enter the username and password to pass the authentication. You can create multiple accounts and assign them to different users. For detailed configurations, refer to 4.9.1 Portal.

Create Local Users

There are two ways to create local user accounts: create accounts on the page and import from a file. To create local user accounts, follow the steps below. 1. Click Hotspot Manager from the drop-down list of Organization and click Local Users in the pop-up page. 2. Create Local User accounts through two different ways.

■ Create Local User accounts

Click +Create User on the lower-left, and the following window pops up. Configure the following parameters and click Save. ![](images/c81bc4c461485322a54b81c68f699515cb8c82c043de009ac1abe0c66f9f3f62.jpg) Portal Select the portal for which the local users will take effect.
UsernameSpecify the username. The username should be different from the existing ones, and it is not editable once it is created.
Password Specify the password. Local users are required to enter the username and password to pass authentication and access the network.
StatusWhen the status is enabled, it means the user account is valid. You can disabled the user account, and enable it later when needed.
Authentication TimeoutSpecify the authentication timeout for local users. After timeout, the users need to log in again on the authentication page to access the network.
MAC Address Binding TypeThere are three types of MAC binding: No Binding, Static Binding and Dynamic Binding.No Binding: No MAC address is bound to the local user account.Static Binding: Bind a MAC address to this user account manually. Then only the user with the this MAC address can use the username and password to pass the authentication.Dynamic Binding: The MAC address of the first user that passes the authentication will be bound to this account. Then only this user can use the username and password to pass the authentication.
Maximum UsersSpecify the maximum number of users that can use this account to pass the authentication.
Name (optional) Specify a name for identification.
Telephone (optional) Specify a telephone number for identification.
Rate LimitSelect an existing rate limit profile, create a new rate limit profile or customize the rate limit for the local users.Custom: Specify the download/upload rate limit based on needs.
Download/Upload LimitClick the checkbox and specify the rate limit for download/upload for users of the local user account. The value of the download/upload rate can be set in Kbps or Mbps.Note: Download/Upload Limit on this page are only available for wireless clients connected to the SSIDs with Portal authentication enabled. To limit the rate of wired clients connected to the switch and gateway, go to the Settings >Transmission >Bandwidth Control.
Traffic LimitClick the checkbox and specify the daily/weekly/monthly/total traffic limit for the local user account, and the value of the traffic limit can be set in MB or GB. Once the limited is reached, the user(s) can no longer access the network using this account.Note: Traffic Limit on this page are only available for wireless clients connected to the SSIDs with Portal authentication enabled. To limit the rate of wired clients connected to the switch and gateway, go to the Settings >Transmission >Bandwidth Control.

■ Create Local User accounts from files.

Click ↑ Import Users on the upper-right, and the following window pops up. Select a file in the format of CVS or Excel, and click Import. To see required parameters and corresponding explanation, refer to Create Local User accounts. Note that the imported file will override the current user data. ![](images/d021b842907e38c6c6e62bd518107f0feb478ea09d26f1fcf520157f6ea7ff1b.jpg) Portal Select the portal to which the local users will be imported. 3. The local user account(s) will be created and displayed in the module. You can view the information of the created local users, search certain accounts through the name, and use icons for management. ![](images/019c910337ee044b0f91941c2a865bf2fec5015f7664d858cbc20b22773834d2.jpg)
Import UsersClick to add local user(s) from files in the format of CVS or Excel. It is recommended when you need to create local users in batches. Select the portals based on needs, and the local users will be imported to the chosen portal.Note that the imported file will override the current user data.
Export UsersClick to export the local user(s) to files in the format of CVS or Excel. Select the portals based on needs, and the local users of the chosen portal will be exported.
Click to edit the parameters for the local user.
Click to delete the local user.

7.2.5 Form Auth Data

The Form Auth Data tab is used to create and manage surveys. You can customize your survey contents and publish it to collect data.

Create Surveys

To create surveys, follow the steps below. 1. Click Hotspot Manager from the drop-down list of Organization and click Form Auth Data in the pop-up page. 2. Click Create New Survey and the following window pops up. ![](images/77b7e3d79f8442b1f07040a6b2c17ddaf1ea0f135e46b888c138fd56eed6d4c5.jpg) 3. Specify the survey name and duration, then customize the contents. 4. Preview and save the settings or publish the survey. 5. The surveys are created and displayed in the table. You can use icons for management and click for more management options.
FORM AUTH NAMEPORTALCREATED TIMERESPONSESACTION
Survey 1PublishedNot in UseAug 15, 2023 01:32:34 am0
Survey 2UnpublishedNot in UseAug 15, 2023 01:33:18 am0

7.2.6 Operators

The Operators tab is used to manage and create operator accounts that can only be used to remotely log in to the Hotspot Manager system and manage vouchers and local users for specified sites. The operators have no privileges to create operator accounts, which offers convenience and ensures security for client authentication.

Create Operators

To create operator accounts, follow the steps below. 1. Click Hotspot Manager from the drop-down list of Organization and click Operators in the pop-up page. 2. Click Create Operator on the lower-left, and the following window pops up. ![](images/8e25d5f0fc25b225f15707f52370a3b4af6bc0bcf1a89e16fe2ad1cf66b6241e.jpg) 3. Specify the username, password, and role for the operator account. Admin role has read and write permissions, while Viewer role has read-only permissions. 4. (Optional) Enter a description for identification. 5. Select sites from the drop-down list of Site Privileges. Click Save. 6. The operator accounts are created and displayed in the table. You can view the information of the create operator accounts on the page, search certain accounts through the name and notes, and use icons for management. ![](images/780f11b24b2375cad188a2a952fb8e960c18424917880bba697569e71f6a5b2e.jpg) 7. Then you can use an operator account to log in to the Hotspot Manager system: ■ For software controller Visit the URL https://Controller Host's IP Address:8043/ControllerID/login/#hotspot (for example: https://192.168.0.174:8043/4d4ede7983bb983545d017c628feaa3d/login/#hotspot), and use the operator account to enter the hotspot manager system.

■ For hardware controller

Visit the URL https://Controller Host's IP Address:443/ControllerID/login/#hotspot (for example: https://192.168.0.174:443/4d4ede7983bb983545d017c628feaa3d/login/#hotspot), and use the operator account to enter the hotspot manager system.

■ For cloud-based controller

Visit the URL https://URL of the controller/ControllerID/login/#hotspot, and use the operator account to enter the hotspot manager system. ![](images/7feabee915d58ed4bd4ef6af40085f72da68bfa26630cfc21eb56adf0558b6da.jpg)

Monitor the Network

This chapter guides you on how to monitor the network devices, clients, and their statistics. Through visual and real-time presentations, the SDN Controller keeps you informed about the accurate status of the managed network. This chapter includes the following sections: • 8.1 View the Status of Network with Dashboard • 8.2 View the Statistics of the Network • 8.3 Monitor the Network with Map • 8.4 Monitor the Network with Reports • 8.5 View the Statistics During Specified Period with Insight • 8.6 View and Manage Logs • 8.7 Monitor the Network with Tools

8.1 View the Status of Network with Dashboard

8.1.1 Page Layout of Dashboard

Dashboard is designed for a quick real-time monitor of the site network. An overview of network topology is at the top of Dashboard, and the below is a tab bar followed with customized widgets. ![](images/fd0863bed138692036a919b7b88f8db425f754ce406b47931ecf726fc697ed60.jpg)
pie | Category | Value | | -------- | ----- | | No Internet Internet Capacity | 1 | | 1 Gateway | 3 | | Switches | ▲ | | 6 APs | ▲ | | 1 Client | 1 | | 0 Guests | 0 | | Clients Freq Distribution | Percentage | | ------------------------ | ---------- | | 2.4 GHz | 0% | | 5 GHz | 0% | | 6 GHz | 0% | | Client Count | Total (MB) | | --------------- | ---------- | | 1C-61-B4-8D-31-55 | 82.31 |

Topology Overview

Topology Overview on the top shows the status of ISP Load and numbers of devices, clients and guests. ![](images/ce11c9bb6f21f77c71c32bfe4323c9110481cbcc06dc1dc781a5e9050e4a141b.jpg)
flowchart
graph LR
    A["No Internet\nInternet Capacity"] --> B["1\nGateway"]
    B --> C["3\nSwitches"]
    C --> D["6\nAPs"]
    D --> E["1\nClients"]
    E --> F["0\nGuests"]
You can hover the cursor over the gateway, switch, AP, client or guest icons to check their status. For detailed information, click the icon here to jump to the Devices or Clients section. ![](images/5e6fe913ac0d2df17c4ce5ac016469ca814f37686ef8c5955360f5df482095a1.jpg)
other | Category | Value | |---|---| | Total Switches | 3 | | Connected | 1 | | Disconnected | 2 | | Wired Clients | 1 | | Total Ports | 28 | | Available Ports | 26 | | Power Consumption | 0 |

Tab Bar

You can customize the widgets displayed on the tab for Dashboard page. Three tabs are created by default and cannot be deleted. ![](images/510be1c559d8a79f870be05ba7c9bd7ceb3ce0ef8cf4b5b3d316e4abb3f521ba.jpg) Overview Displays the network overview information. Network Displays network information such as Alerts, Wi-Fi Traffic Distribution, and more. Clients Displays client information such as Most Active Clients, Clients Freq Distribution, and more. In the tab bar, you can take the following action to edit the tabs and customize the widget to be displayed. ![](images/1fa84c1c2adf411a69fa720048f1db7263e42fd0d7596e8c36bbd0354d319008.jpg) ![](images/cfde3ca08dcf04f7d9432c806b0b8cc96d42d563cd371c0ed49419e6ff7ee7a8.jpg) Mar 18, 2024 - Mar 19, 2024 白 Click the icon to edit the tabs. For the default tabs, you can reset them to the default settings. For a created tab, you can edit its name or delete it. Click the icon and enter the name in the pop-up window to create a new tab. Click the date to display a calendar. To quickly display the statistics of today, yesterday, last 24 hours, or last several days, click the default date/period at the right side in the calendar. To display the statistics of a specific date, click the date twice in the calendar. To display the statistics of a specific time range, click the start date and end date in the calendar. ![](images/ce3204de111756d71b3f4f458f30043113a3b23b43a928ad8d2a65e608a1e392.jpg) Click a tab and then click a widget in the pop-up page to add it to this tab or remove it.

8.1.2 Explanation of Widgets

The widgets are divided into different categories. You can click the icon to add or remove the widgets. ![](images/2a3c93560efcca5985a76425567156cd9b01c46b6bb1dccc4968f5f4cd6a4c0c.jpg)
pie | Client Type | Uptime | Freq Distribution | |-------------|--------|-------------------| | AA/BB/CC/DD/EE/FF | -h - m > | 5 GHz | | AA/BB/CC/DD/EE/FF | -h - m > | 2.4 GHz | | AA/BB/CC/DD/EE/FF | -h - m > | 5 GHz | | AA/BB/CC/DD/EE/FF | -h - m > | 2.4 GHz |

Network

Network widgets use lists and charts to illustrate the traffic status of wired and wireless networks in the site.

- Alerts

The Alerts widget displays the total number of unarchived alerts happened in the site and details of the latest alerts. To view all the alerts and archive them, click See All to jump to Log > Alerts. To specify events appeared in Alerts, go to Log > Notifications and configure the events as the Alert level. For details, refer to 8. 6 View and Manage Logs. ![](images/70d194fbbf38dbdc14d04258ee868d1fd54f9a3547e95b733672330f7c273abb.jpg)

■ ISP Load

ISP Load use a line chart to display the throughput and latency of gateway's WAN port within the time range. Click the tab on the right to view the statistics of each WAN port and move the cursor on the line chart to view specific values of throughput and latency. For detailed statistics of certain gateway's WAN port within a time range, refer to 8.2 View the Statistics of the Network. ![](images/92291bd8925f8cf91dbe3d8d3c84f4d23ef19e8b2f2743228bd189c72a24be9e.jpg)
line | Time | Throughput (Mbps) | Latency (msec) | | -------- | ----------------- | -------------- | | -24hrs | ~0.2M | ~100 | | | ~0.3M | ~100 | | | ~0.4M | ~100 | | | ~0.5M | ~100 | | | ~0.6M | ~100 | | | ~0.7M | ~100 | | | ~0.8M | ~100 | | | ~0.9M | ~100 | | | ~1.0M | ~100 | | | ~1.1M | ~100 | | | ~1.2M | ~100 | | | ~1.3M | ~100 | | | ~1.4M | ~100 | | | ~1.5M | ~100 | | | ~1.6M | ~100 | | | ~1.7M | ~100 | | | ~1.8M | ~100 | | | ~1.9M | ~100 | | | ~2.0M | ~100 | | | ~2.1M | ~100 | | | ~2.2M | ~100 | | | ~2.3M | ~100 | | | ~2.4M | ~100 | | | ~2.5M | ~100 | | | ~2.6M | ~100 | | | ~2.7M | ~100 | | | ~2.8M | ~100 | | | ~2.9M | ~100 | | | ~3.0M | ~100 | | | ~3.1M | ~100 | | | ~3.2M | ~100 | | | ~3.3M | ~100 | | | ~3.4M | ~100 | | | ~3.5M | ~100 | | | ~3.6M | ~100 | | | ~3.7M | ~100 | | | ~3.8M | ~100 | | | ~3.9M | ~100 | | | ~4.0M | ~100 | | | ~4.1M | ~100 | | | ~4.2M | ~100 | | | ~4.3M | ~100 | | | ~4.4M | ~100 | | | ~4.5M | ~100 | | | ~4.6M | ~100 | | | ~4.7M | ~100 | | | ~4.8M | ~100 | | | ~4.9M | ~100 | | | ~5.0M | ~100 | | | ~5.1M | ~100 | | | ~5.2M | ~100 | | | ~5.3M | ~100 | | | ~5.4M | ~100 | | | ~5.5M | ~100 | | | ~5.6M | ~100 | | | ~5.7M | ~100 | | | ~5.8M | ~100 | | | ~5.9M | ~100 | | | ~6.0M | ~100 | | | ~6.1M | ~100 | | | ~6.2M | ~100 | | | ~6.3M | ~100 | | | ~6.4M | ~100 | | | ~6.5M | ~100 | | | ~6.6M | ~100 | | | ~6.7M | ~100 | | | ~6.8M | ~100 | | | ~6.9M | ~100 | | | ~7.0M | ~100 | | | ~7.1M | ~100 | | | ~7.2M | ~100 | | | ~7.3M | ~100 | | | ~7.4M | ~100 | | | ~7.5M | ~100 | | | ~7.6M | ~100 | | | ~7.7M | ~100 | | | ~7.8M | ~100 | | | ~7.9M | ~100 | | | ~8.0M | ~100 | | | ~8.1M | ~100 | | | ~8.2M | ~100 | | | ~8.3M | ~100 | | | ~8.4M | ~100 | | | ~8.5M | ~100 | | | ~8.6M | ~100 | | | ~8.7M | ~100 | | | ~8.8M | ~100 | | | ~8.9M | ~100 | | | ~9.0M | ~100 | | | ~9.1M | ~100 | | | ~9.2M | ~100 | | | ~9.3M | ~100 | | | ~9.4M | ~100 | | | ~9.5M | ~100 | | | ~9.6M | ~100 | | | ~9.7M | ~100 | | | ~9.8M | ~100 | | | ~9.9M | ~100 | | | >1.2M | 25% | | +24hrs | 25% | 25% | | - | 25% | 25% | | + | 25% | 25% | | - | 25% | 25% | | + | 25% | 25% | | - + (Now) 25% - 25% - 25% - 25% - 25% - 25% - 25% - 25% - 25% - 25% - 25% - 25% - 25% - 25% + + (Now) - (Now) - (Now) - (Now) - (Now) - (Now) - (Now) - (Now) - (Now) - (Now) - (Now) - (Now) - (Now) - (Now) - (Now) - (Now) - (Now) - (Now) - (Now) - (Now) - (Now) - (Next)
To test the current download and unload speed and the latency of WAN port, click Test Speed on the widget to display the speed test result.

■ VPNs

VPN widgets display the information of VPN servers and VPN clients. Click the corresponding tab to display the statistics. ![](images/cb10011fae13973848029e102c48cf57fe8857e72d845ada61fb9e00f069cb35.jpg)

■ Most Active EAPs/Most Active Switches

These two widgets can display most active EAPs and switches in the site based on the total number of traffic within the time range. Only the devices that has been adopted by the controller will be displayed. To view all the devices discovered by the controller, click See All to jump to the Devices section. You can also click the traffic number in the widget to open the device's Properties window for further configurations and monitoring. For details, refer to 6 Configure and Monitor Controller-Managed Devices. ![](images/576af0189bfe863ed9cbf735356cd915e6979e39d18867bf695a6cc27c97b60e.jpg)

■ Wi-Fi Traffic Distribution

The Wi-Fi Traffic Distribution widget displays channel distribution of all connected EAPs in the site. Good, Fair, and Poor are used to describe channel status which indicates channel interference from low to high. You can hover your cursor over the band to view the number of EAPs and clients on the channel. ![](images/6981f142dcfd71b60f9dd50249c0e78c299922ebe67101516b721d064216bbd5.jpg)

■ Wi-Fi Summary

The Wi-Fi Summary widget summarizes the real-time status of wireless networks in the site, including the number of connected EAPs and clients, the channel utilization, and the total number of traffic within the time range. ![](images/95167db04006a179c09471128bc9d1f2937b36d7a692bfe874c6ee4325004188.jpg)
bar_stacked | Category | Value | | -------------------- | --------- | | EAPs Online | 5 | | Clients | 8 | | Channel Utilization | 57.00% | | Traffic | 18.25 GB |

■ Traffic Distribution

The Traffic Distribution widget uses a pie chart to display the traffic distribution on EAPs and switches in the site within the time range. Click the tab to display the statistic of EAPs or switches, and click the slice to view the total number of traffic, its proportion, and the device name. ![](images/39674ad03fafa97145f64c6fbb237e3b1bbfe044215339d97c55cb1853893974.jpg)
pie Traffic Distribution | Category | Value (MB) | Percentage (%) | |---|---|---| | EAPs | 1734.8 | 9.28 | | Switches | | | | 00-31-92-A4-4E-5A | | | | 00-31-92-A | | | | E4-C3-2A-S | | | | 00-31-92-A | | | The chart displays the distribution of traffic volumes for different EAPs or switch categories. The values are estimated based on the total traffic volume.

■ Client Distribution

The Client Distribution widget uses a sunburst chart to display the real-time distribution of connected clients in the site. The chart has up to three levels. The inner circle is divided by the device category the clients connected to, the middle is by the device name, and the outer is by the frequency band. You can hover the cursor over the slice to view specific values. ![](images/efbf40829edd8dbde76c93619066e1261161bb565c9b293f17822d39625dcc67.jpg)
pie Clients Distribution | Client | Count | | :--- | :--- | | S&P 1000 | 2 | | S&P 3000 | 2 | | S&P 5000 | 2 |

■ Traffic Activities

The Traffic Activities widget displays the Tx and Rx data of EAPs and switches within the time range. Only activities of the devices in the connected status currently will be counted. Click the tab to display the statistic of EAPs or switches, and move the cursor on the line chart to view specific values of traffic. For detailed statistics of certain devices within a time range, refer to 8.2 View the Statistics of the Network. ![](images/69553076c9d5fd699ba87a798d1d4c3ca8df96293a09311dde21abd8fd607f0a.jpg)
line | Time | Tx Data | Rx Data | | ----------------- | ------- | ------- | | 2020-05-28 01:10 am | 2.94MB | 24.31MB |

■ Retried Rate/Dropped Rate

The Retried Rate/Dropped Rate widget displays the rate of retried and dropped packets of the connected EAPs within the time range. Select an AP from the list and click the tab to display the chart of retried rate or dropped rate. You can move the cursor on the point to view specific values. ![](images/c079e59fcde5cb768694bbdeff200ef13521cef0e83d757eb2933ebc11ee2523.jpg)
line | Date | Dropped Rate | Droped Rate per AP | | ---------- | ------------ | ------------------ | | 2020-05-28 03:40 am | 37.29 | 60%–100% | | 2020-05-28 04:55 am | - | - |
Retried Rate Displays the percentage of packets that needed to be re-sent because they were corrupted upon arriving at the proper destination. Dropped Rate Displays the percentage of packets that were dropped before reaching their intended destination.

■ Top Devices Usage

The Top Devices Usage widget displays the CPU utilization and memory utilization of devices within the time range. Click the tab to select the CPU or memory for display. Click the traffic number in the widget to open the device's Properties window for further configurations and monitoring. For details, refer to 6 Configure and Monitor Controller-Managed Devices. ![](images/15a85ad7040cead9ac71ecdb7439a287d35db4928a23cee983b2970755641d65.jpg)
bar Top Devices Usage | Device | CPU (%) | Memory (%) | | :--- | :--- | :--- | | EAP620_yytest_lab | 16.00 | > | | 00-31-92-A4-4E-D4 | 14.00 | > | | E4-C3-2A-57-97-76 | 6.00 | > | | E4-C3-2A-57-71-AC | 6.00 | > | | 84-D8-1B-B3-A8-76 | 5.00 | > | 1 2

■ PoE Utilization

The PoE Utilization widgets describes the PoE utilization of a switch. Select a switch from the switch list to display the ports connected to PoE devices. You can hover the cursor over a certain port to view specific values. The bar below displays the current power capacity provided by PoE and its proportion of the PoE budget. ![](images/5926cbaffbf39a751b4eee662b8345812fb3c459bfe5de19eec363f68d0ad011.jpg)
bar_line PoE Utilization | Port Number | Power Capacity (W) | | :--- | :--- | | 1 | 0 W | | 2 | 500 W | | 3 | 500 W | | 4 | 500 W | | 5 | 500 W | | 6 | 500 W | | 7 | 500 W | | 8 | 500 W | | 9 | 500 W | | 10 | 500 W | | 11 | 500 W | | 12 | 500 W | | 13 | 500 W | | 14 | 500 W | | 15 | 500 W | | 16 | 500 W | | 17 | 500 W | | 18 | 500 W | | 19 | 500 W | | 20 | 500 W | | 21 | 500 W | | 22 | 500 W | | 23 | 500 W | | 24 | 500 W | | 25 | 500 W | | 26 | 500 W | | 27 | 500 W | Switch List E4-C3-2A-57-...

■ Top Interference

The Top Interference widget displays the environment interference of wireless products. Click the tab to select the band. Click the traffic number in the widget to open the device's Properties window for further configurations and monitoring. For details, refer to 6 Configure and Monitor Controller-Managed Devices. ![](images/9708808bcb805e9ea7445690f972f51fad8f5f52981f23e3a17668fe33d67ea5.jpg)
bar Top Interference | Interference | Value (%) | | :--- | :--- | | EAP620_yytest_lab | 53.00 | | EAP620_yytest_office | 48.00 | | 00-31-92-A4-4E-5A | 47.00 | | 00-31-92-A4-4E-D4 | 45.00 | | 84-D8-1B-B3-A8-76 | 10.00 |

Client

Client widgets use lists and charts to illustrate the traffic status of wired and wireless clients in the site.

■ Most Active Clients

The Most Active Clients widget can display most active clients. Only the clients in the connected status currently will be displayed. To view all the clients connected to the network, click See All to jump to the Clients section. You can also click the traffic number in the widget to open the client's Properties window for further configurations and monitoring. For details, refer to 7.1 Manage Wired and Wireless Clients in Clients Page. ![](images/671c216209c933aa6e2858e710d8836158e7f98ffab8ffae4c153ebfb9729059.jpg)

■ Longest Client Uptime

The Longest Client Uptime widget can display top clients sorted by the uptime. Only the clients in the connected status currently will be displayed. You can also click the uptime in the widget to open the client's Properties window for further configurations and monitoring. For details, refer to 7.1 Manage Wired and Wireless Clients in Clients Page. ![](images/5650d3eef7d5a43a58eb19dbff5e9f49b973f61fa30d0bb1dbeaf53e33e86dc2.jpg)

■ Clients Freq Distribution

The Clients Freq Distribution widget uses a donut chart to display the distribution of wireless clients connected to the bands in the site. The chart has two levels. The inner circle shows the total number of wireless clients, and the outer displays the proportion of clients that connect to the two bands. You can hover the cursor over the slice to view the number of clients in a band. ![](images/7738dd3afff17ab9ed2797caad146f836e9b48daf8da02f94a9d0fd58f3d6cb6.jpg)
pie Clients Freq Distribution | Frequency | Percentage (%) | | :--- | :--- | | 5 GHz | 71.43 | | 2.4 GHz | 28.57 | 7 TOTAL

■ Clients Association Activities

The Clients Association Activities widget displays how the number of client connected to EAPs changes over time and the duration during which the clients communicate with the EAPs. In the stacked chart, you can easily compare the total number of clients and analyze the variation of each time period. The total value of a column shows the total number of clients connected to EAPs in this time period, and the segments in four colors represent the client number of different durations in specific time. ![](images/e2c669830835526de71cdb0b68dc3c7d15bc15287c40aa046497037310fcf8d4.jpg)

■ Client Activities

The Client Activities widget displays how the number of connected client changes over time within the time range. In the stacked chart, you can easily compare the total number of clients and analyze the variation of each time period. The total value of a column shows the total number of connected clients in this time period, and the segments in three colors shows the change of client number compared with the last time period. Blue represents the newly connected clients, orange is the clients have been connected in the last period, and gray is the newly disconnected clients. ![](images/efec4152abd6042578ab32cb3dfbb0f1a5c80ce12d74c8823eb8d077f122235c.jpg)
bar | Date | New | Existing | Disconnected | | ---------- | --- | -------- | ------------ | | 2020-06-02 | 1 | 4 | 3 |

■ Clients SSID Distribution

The SSID Distribution widget uses a sunburst chart to display the distribution of wireless clients connected to the different SSIDs in the site. The chart has two levels. The inner circle is divided by the EAP's SSID that the clients connected to, and the outer is by the frequency band. You can hover the cursor over the slice to view the number of clients connected to the SSID in a band. Click a certain SSID to further display the statistics of its band frequency distribution. Clients SSID Distribution ![](images/3766b322bc807f570e58f254bf8ad991cd0bd4f3ecea8b0b53c3447024c8cfde.jpg)
pie | Category | Value | |---|---| | 5GHz | 0 | | EAP62D | 0 | | PE Wi-Fi | 0 | | 2.4GHz | 0 | | 14GHz | 0 |

■ Clients with Onboarding Times

The Clients with Onboarding Times widget describes the time wireless clients uses when connecting to a certain SSID. The donut chart on the left shows the proportion of clients that uses less than 10 seconds to connect to the devices. The line graph on the right displays the number of clients according to the different time that the clients takes to connect to the SSIDs. Clients with onboarding times < 10s ≥ 10s Threshold ![](images/813ca56e489b217d8eb53f3789607186707b58321592bfaa55a35991ff318241.jpg)
pie | Time (seconds) | Value (%) | |---|---| | 0 | 100.00 | | 1 | 100.00 |
![](images/a4678f5fd21a29b12f8bf89a9635e51ca75b27b18238ff91c3474ed33c38d534.jpg)
bar | Category | Value | |---|---| | < 2 | 175 | | 2-4 | 0 | | 4-6 | 0 | | 6-8 | 0 | | 8-10 | 0 | | ≥ 10 | 0 | | Failure | 5 |

■ Clients with RSSI

The Clients with RSSI widget describes the RSSI (Received Signal Strength Indication) that wireless clients experience in the environment. RSSI is a negative value measuring the power level being received after any possible loss at the antenna and cable level. The higher the RSSI value, the stronger the signal. The donut chart on the left shows the proportion of clients whose RSSI value is bigger than -72 dBm. The line graph on the right displays the number of clients according to the different range values of RSSI. ![](images/8044277d24030b3b0536752148f2696ba1dcecd9b427391a0d9d9f0815e3d4f2.jpg) □≤72dBm Threshold

■ History Clients

This widget uses a donut chart to display the distribution of wired and wireless clients in the site. The chart has two levels. The inner circle shows the total number of clients, and the outer displays the proportion of each client type. You can hover the cursor over the slice to view the number of a client type. ![](images/68d7e722b25df8a18738b5a25283417aca7fbf4e386790fd59092b9a4c107c07.jpg) Mar 19, 2024-Mar 20, 2024

AppFlow

AppFlow widgets use lists and charts to illustrate the application information in the site.

■ Top Application Categories / Top Applications

These two widgets display top application categories and top applications in the site. To view detailed traffic information, click View All Traffic to go to the Application Analytics page. A DPI-supported gateway is required for detailed traffic information. ![](images/76384552873592fcde690f422b37889265c167c44cf1abf7d4d4959bdc4ae921.jpg)
pie | Top5 Applications Category | CATEGORY | BYTES | PERCENT | |---|---|---|---| | Total Traffic | - | - | -% | | Year All Traffic | - | - | -% | | Total Traffic | - | - | -% | | Year All Traffic | - | - | -% | | Total Traffic | - | - | -% | | Year All Traffic | - | - | -% |

8.2 View the Statistics of the Network

Statistics provides a visual representation of device data in the SDN Controller. You can easily monitor the network traffic and performance under the following tabs, Performance, Switch Statistics, and Speed Test Statistics.

8.2.1 Performance

In Performance, you can view the device performance in a specified period by graphs, such as user counts, CPU and memory usage, and transmitted and received packets. The graphs vary due to the device type and status.

Tab Bar

The tabs and calendar on the top are used to specify the displayed statistics. ![](images/32a2ae0ceb48e6067ea893bed55a5970ebe4a41c8514653dab31da91cc6dd485.jpg)
CC-32-E5-A4-B1-ACClick to select a device from the drop-down list to view its statistics. The tabs vary due to the type of the selected device.
Mar 20, 2024 - Mar 21, 2024Click the date to display a calendar. Click a specific date twice in the calendar for the widgets to display its statistics. To display the statistic of a time range, click the start date and end date in the calendar, or directly select the time range on the right. The available time range is restricted by the time interval. Before selecting a long time range, select Hourly or Daily as the time interval.
HourlySelect 5 minutes, Hourly, or Daily to specify the time interval of the data. When selecting a long time range, a longer time interval is recommended for a better view.
(For a gateway)
(For an AP) Click to select the band of the AP to view the statistics.

■ Gateway Statistics

Click to select the port of the gateway on the tab to view the statistics. ![](images/432e5b9eb7db0f4895e19f14a82b4270a1ec6436fc6716e671de9a3f231543fd.jpg)

■ Switch Statistics

Click Overview to view the general switch statistics, or click Port Performance and select a tab to view the port statistics. For a switch, you can view the current status of ports and its traffic statistics in the specified time range via a monitor panel and graphs. ![](images/27e1a06d4690f4019f2651e46267d1204dcec7ac0cf0e8e5de1c06bc1e3e2bec.jpg)

Port Status

■ Disabled The port is Disable. To enable it, go to the Devices page. ■ Disconnected The port is enabled but connects to no devices or clients. 1000 Mbps The port is running at 1000 Mbps. 10/100 Mbps The port is running at 10/100 Mbps. PoE A PoE port connected to a powered device (PD). ^ Uplink An uplink port connected to WAN. Mirroring A mirroring port that is mirroring another switch port. ∅ STP Blocking A port in the Blocking status in Spanning Tree. It receives and sends BPDU (Bridge Protocol Data Unit) packets to maintain the spanning tree. Other packets are dropped.

Tabs

Sort: Natural Select Natural, Transmitted, Received, or All to specify the graph order of ports. Natural: Displays the line graphs in ascending order of the port number. Transmitted: Displays the line graphs in descending order based on the traffic volume of transmitted packets. Received: Displays the line graphs in descending order based on the traffic volume of received packets. All: Displays the line graphs in descending order based on the total traffic volume of transmitted and received packets.
RateTrafficPacketsSpecify the data type.
Rate: Displays the traffic rate.
Traffic: Displays the traffic statistics.
Packets: Displays the total number of packets.
AllBroadcastMulticastIf you select Packet, click the tab to specify which type of packet statistics to be displayed.
All: Displays statistics of all packets, including broadcast and multicast packets.
Broadcast: Displays statistics of broadcast packets only.
Multicast: Displays statistics of multicast packets only.

Statistical Graphs

Statistical graphs vary according to the type of devices. The chart below shows the statistical graphs which correspond to the gateway, switch, and AP.
Gateway User Counts, Usage, Traffic, Packets
Switch User counts, Usage, Port Port Information Graphs
APUser Counts, Usage, Traffic, Packets, Packets, Multicast/Broadcast Packets, Dropped, Errors, Retries

■ User Counts

The User Counts graph displays the number of users connected to the devices during the selected time range. Hover the cursor over the line to display the specific values. ![](images/831992c61fb88c470a5f11f351cbd3d48bfced0919afc90accdda548f86ad4b3.jpg)
line | Date | Clients | | ---------- | ------- | | Jul 06, 2022 12:15 | 1 |

■ Usage

The Usage graph uses the orange line and yellow line to display the percentage of CPU usage and used memory during the selected time range, respectively. Hover the cursor over the lines to display the specific values. ![](images/713cdab795c0a093460afffc86292bdbb9912f3a8dc9fa45b78c7aca784685eb.jpg)
line | Date | CPU | Memory | | ---------- | ----- | ------ | | Jul 06, 2022 18:15 | 5.00% | 36.00% |

■ Traffic

The Traffic graph uses the dark blue line and light blue line to display the bytes of data transmitted and received during the selected time range, respectively. Hover the cursor over the lines to display the specific values. ![](images/86fcedfd5a054bdb9a41da84d1d680b66d731f658907ea6463d16131697e5f81.jpg)
line | Date | Transmitted (MBytes) | Received (MBytes) | | ---------- | -------------------- | ----------------- | | Jul 06, 2022 | 178.77 | 901.88 |

■ Packets

The Packets graph uses the dark blue line and light blue line to display the number of packets transmitted and received during the selected time range, respectively. Hover the cursor over the lines to display the specific values. ![](images/fe21286a18d6b422cb979468cb748f32961f294923daef1c0151b85e6a1c15c4.jpg)
line | Time | Packets | | ----------------- | ----------- | | Jul 06, 2022 | 130004 | | Jul 06, 2022 | 137003 |

■ Multicast/Broadcast Packets (Only for EAPs)

The Multicast/Broadcast Packets graph uses the colorful blue line to display the number of multicast and broadcast packets during the selected time range. Hover the cursor over the lines to display the specific values. ![](images/a9bf2dc0bb252b56ba4ca8fe5bf0c0edcbeb0ecda3e7c021857d19e7618b7ba9.jpg)
line | Date | ARP | ND | IGMP | MDNS | DHCP | DHCPv6 | Other Broadcast | Other Multicast | | ---------- | ---- | ---- | ---- | ---- | ---- | ------ | --------------- | --------------- | | Apr 10, 05:50 am | | | | | | | | | | Apr 10, 09:00 am | | | | | | | | | | Apr 10, 10:05 am | | | | | | | | | | Apr 10, 12:10 pm | | | | | | | | | | Apr 10, 02:35 pm | | | | | | | | | | Apr 10, 04:20 pm | | | | | | | | | | Apr 10, 06:25 pm | | | | | | | | | | Apr 10, 08:30 pm | | | | | | | | | | Apr 10, 10:35 pm | | | | | | | | | | Apr 11, 12:40 pm | | | | | | | | | | Apr 11, 02:45 am | | | | | | | | | | Apr 11, 05:50 am | | | | | | | | | | Apr 11, 05:50 pm | | | | | | | | | | Apr 11, 05:30 pm | | | | | | | | | | Apr 11, 05:30 pm | | | | | | | | | | Apr 11, 05:30 pm | | | | | | | | | | Apr 11, 05:30 pm | | nan| nan| nan| nan| nan | | | | Apr 11, 05:30 pm | | nan| nan| nan| nan| nan | | | | Apr 11, 05:30 pm | | nan| nan| nan| nan| nan | | | | Apr 11, 05:30 pm | | nan| 56 | nan| nan| nan | | | | Apr 11, 05:30 pm | | nan| nan| nan| nan| nan | | | | Apr 11, 05:30 pm | | nan| nan| nan| nan| nan | | | | Apr 11, 05:35 pm | | nan| nan| nan| nan| nan | | | | Apr 11, 05:35 pm | | nan| nan| nan| nan| nan | | | | Apr 11, 05:35 pm | | nan| nan| nan| nan| nan | | | | | Apr 11, 05:35 pm | | nan| nan| nan| nan| nan | | | | Apr 11, 05:35 pm | | nan| nan| nan| nan| nan | | | | Apr 11, 05:35 pm | | nan| nan| nan nan| nan| nan | | | | Apr 11, 05:35 pm | | nan| nan| nan| nan| nan | | | | Apr 11, 05:35 pm | | nan| nan| nan| nan| nan | | | | Apr 11, 05:38 pm | | nan| nan| nan| nan| nan | | | | Apr 11, 05:38 pm | | nan| nan| nan| nan| nan | | | | Apr 11, 05:38 pm | | nan| nan| nan| nan| nan | | | | | Apr 11, 05:38 pm | | nan| nan| nan| nan| nan | | | | | Apr 11, 05:38 pm | | nan| nan| nan| nan| nan | | | | | Apr 11, 05:38 pm | | nan| nan|```

■ Dropped

The Dropped graph uses the dark blue line and light blue line to display the number of dropped Tx packets and Rx packets during the selected time range, respectively. Hover the cursor over the lines to display the specific values. ![](images/3b594948fd554c99f0bd72249321ae52a794f68f83dabfe7bdde2e9e37dd7df5.jpg)
line | Date | Dropped Pits | Retro Pits | | ---------- | ------------- | ----------- | | Jul 02, 2022 | 392 | 114 |

Errors

The Errors graph uses the dark blue line and light blue line to display the number of error packets sent to AP and received by AP during the selected time range, respectively. Hover the cursor over the line to display the specific values. ![](images/24f1d14c1e577a7386f680175aba4ec052d575f58d4f6c23129f6ca6b7f55ff2.jpg)
line | Date | Te Errors | Rx Errors | | ---------- | --------- | --------- | | Jun 24, 17:15 | 0 | 0 | | Jun 24, 20:15 | 2700 | 564 | | Jun 24, 23:15 | 564 | 216 | | Jun 25, 02:15 | 0 | 0 | | Jun 25, 05:15 | 0 | 0 | | Jun 25, 08:15 | 0 | 0 | | Jun 25, 11:15 | 0 | 0 | | Jun 25, 14:15 | 564 | 0 | | Jun 25, 17:15 | 564 | 0 | | Jun 25, 20:15 | 564 | 0 | | Jun 25, 23:15 | 0 | 0 |

Retries

The Retries graph uses the dark blue line and light blue line to display the number of times that the data packets are transmitted again and received again during the selected period, respectively. Hover the cursor over the lines to display the specific values. ![](images/75e374347d668ab003d4c48096fadb54daa5c0fc46535f0a86b9723772c221a6.jpg)
line | Date | Tx Retriebs | Rx Retriebs | | ---------- | ----------- | ----------- | | Jul 01, 2022 22:15 | 104 | 42 |

Port Information Graphs (only for Switches)

Port information graphs of a switch display the traffic statistics of active ports. You can specify the data type by clicking the Rate Traffic Packets and tabs. Colorful lines are used to indicate the transmitted and received statistics. Hover the cursor over the lines to display the specific values. To view and configure the device connected to the port, click the device name beside the port number. ![](images/cebe62d73b521690918f3719be6fabcab56db6d3541adb17c971482b0baa2619.jpg)
line | Date | Transmitted (bps) | Received (bps/s) | | ---------- | ----------------- | ---------------- | | Jun 30, 2020 | 4057.00 | 1677.00 |

8.2.2 Application Analytics

In Application Analytics, you can view detailed traffic information in a specified period by graphs. ![](images/714e1f51181e4ac77b3a64bafffb5b2d957b7a5c909e5c763c50a10c8e543cbf.jpg)

8.3 Monitor the Network with Map

With the Map function, you can look over the topology and device provisioning of network in Topology, customizes a visual representation of your network in Heat Map, and visually display the geographic location of each device and site in Device Map and Site Map.

8.3.1 Topology

Go to Map > Topology, and you can view the topology generated by the controller automatically. You can click the icon of devices to open the Properties window. For detailed configuration and monitoring in the Properties window, refer to 6 Configure and Monitor Controller-Managed Devices. ![](images/3c2271ba1be958e78bcf6ea2c038bdd77101b3d9b702ee02070a03ae9b5f5628.jpg)
flowchart
graph TD
    A["Internet Connected"] --> B["TL-ER7206 WAN 1"]
    B --> C["TL-SG2210MP"]
    B --> D["TL-SG242BP"]
    B --> E["TL-SG242BP"]
    C --> F["EAP660 HD\n6 Ingl. 40 incl"]
    D --> G["EAP620 HD\n6 Ingl. 40 incl"]
    E --> H["OC200"]
    E --> I["Client Group"]
    E --> J["EAP225\n6 Ingl. 40 incl"]
For a better overview of the network topology, you can control the display of branches, the size of the diagram, and the link labels. ![](images/30ed29d84005510d608a78650076a38ea504f5ff15ffa91e8f9ba488f2af0e44.jpg)
flowchart
graph TD
    A["Internet Connected"] --> B["1000 FDX"]
    B --> C["TL-ER7206 SAN 1"]
    C --> D["TL-SG2210MP"]
    C --> E["TL-SG2428P"]
    C --> F["TL-SG2428P"]
    D --> G["EAP660 HD 6 ingl. 40 (acd)"]
    E --> H["EAP620 HD 6 ingl. 40 (acd)"]
    F --> I["OC200"]
    F --> J["Client Group"]
    F --> K["EAP225 6 ingl. 40 (acd)"]
    D --> L["#1<-"]
    D --> M["#2<-"]
    D --> N["#3<-"]
    D --> O["#5<-"]
    G --> P["User PCI"]
    H --> Q["User PCI"]
    I --> R["#7<-"]
    I --> S["#8<-"]

■ Display of Branches

The default view shows the all devices connected by solid and dotted lines. Click the icon of the client group to view clients connected to the same device. Click the nods + to unfold or ⓣ to fold the branches.

■ Diagram Size

Click the icons at the right corner to adjust the size of the topology and view the legends.
Click to fit the topology to the web page.
+Click to zoom in the topology.
-Click to zoom out the topology.
iClick to view the meaning of lines in the topology. Solid and dotted lines are used to indicate wired and wireless connections, respectively, and four colors are used to indicate the link speed.
Click Link Labels at the left corner, and labels will appear to display the link status. Information on the labels varies due to the link connections. ![](images/d3b2b140805093d787f3af69bdf4d2a707b32c3e9a284d8c3c2e94af9587e384.jpg) (For the WAN port of router connected to the internet) Displays the port name, link speed and duplex type. ![](images/91fac9921297b730a6869ca01b8a9f9aa2b532155f1a6fb2c8bdf36cca110364.jpg) (For simple wired connections) Displays the connected port number, link speed, and duplex type. Note that only the switch's port number can be displayed in the label. ![](images/40e6ad9e2ca3af3857681efcf59d270cb41b03b2ca35433c35cd291ac4cb5f13.jpg) (For Link Aggregation) Displays the LAG ID, port number of LAG members, LAG speed, and duplex type. ![](images/38063b43b387759312147ec13e283e7eaec87906f3723777654b618e7b22475f.jpg) (For wireless connections between APs) Displays the negotiation rate of uplink and downlink and the RSSI (displayed in percentage and dBm). ![](images/f4e4388e94871857bf5af55c82e43d8f2693ff5efa8692a14e749f635a3f99d3.jpg) (For wireless connections between clients) Displays the connected SSID, wireless channel of AP, and its signal strength.

8.3.2 Heat Map

Go to Map > Heat Map, and a default map is shown as below. You can upload your local map images and add devices and different types of walls to customize a visual representation of your network. ![](images/e739e8ce491bb67700c500386bde6c68d1a75850922bbc15b4a76afa9e71468d.jpg) Click the following icons to add, edit, and select the map. After selecting a map, click and drag in the devices from the Devices list to place it on the map according to the actual locations. Map: TP-Link Click to select a map from the drop-down list to place the devices.
TP-LINK Omada SDN Controller - Heat Map - 1Click to edit maps in the pop-up window.Clickto edit the description and layout of the map.Clickto delete the map.
[5G23]Click to add a map. In the pop-up window, enter the description, select the layout, and upload an image in the .jpg, .jpeg, .gif, .png, .bmp, .tiff format.
TP-LINK Omada SDN Controller - Heat Map - 2Adjust the opacity of the map.
TP-LINK Omada SDN Controller - Heat Map - 3Click to select the icon size displayed on the map.
TP-LINK Omada SDN Controller - Heat Map - 4Click to use the selection tool to select the elements including walls and devices on the map.
[VWTC]Click to use the measurement tool. Draw a line on the map to measure the actual distance according to the map scale.
[4730]TP-LINK Omada SDN Controller - Heat Map - 5Click to edit the elements including walls and devices on the map.
TP-LINK Omada SDN Controller - Heat Map - 6Click to simulate the network heat map.Note: It is required to click Simulate to generate a new heat map after editing elements on the map.
[KX26A]Click to fit the map to the web page.
[4749]Click to zoom in the map.
TP-LINK Omada SDN Controller - Heat Map - 7Click to zoom out the map.
TP-LINK Omada SDN Controller - Heat Map - 8Click to set the map scale. Draw a line on the map by clicking and dragging, and then define the distance of the line.
[KY08]Click to set the default height of the added devices and the information displayed on the map.
[A23C]Click to export the network coverage report.

Configuration

To generate a visual representation and heat map of your network, follow these steps: 1) Add a map and configure the general parameters for the map. 2) Add devices and walls, and configure the parameters. 3) View simulation results.

Add Map Add Devices and Walls View and Export Results

1. Go to Map > Heat Map and click ⊕ to add a new map. Then click Add.

![](images/e389fe0ab0119028d4de8d8942f468b42e9fa3579ecfc33774b8c3214f9fa3f6.jpg) Description Enter a description for the map. Layout Select the general layout of the map, which will make the simulation more accurate. Tip: You can upload a CAD (.dxf) file, and the controller will automatically identify the walls in the layout. Upload an image Upload the map in the .jpg, .jpeg, .gif, .png, .bmp, .tiff, .dxf format. 2. Click on the upper right to set a map scale. Draw a line on the map by clicking and dragging, and then define the distance of the line. 3. Click 🔒 to set the default height of the added devices and the information displayed on the map. Then click Confirm. ![](images/93d8457932aa52252b986a190edba95e64bcc64efe1387a520d4b722d85802e3.jpg) ![](images/1825afd6fad38e836f48c0688f33bca987f8836edafa7b1f39382bfdce63488b.jpg) Default Height Specify the default height for devices. You can change the height for individual device later. Display Information Select the information you want to see on the map.

Add Map Add Devices and Walls View and Export Results

1. Click to enter the editing status of the map. 2. Click 📋 on the upper left, and the list of adopted devices and virtual devices will appear. Drag the devices to the desired place on the map. ![](images/3633bb2ab60c78ffd7eedc48384cfc861aee8ba4a2d9d10edfa936fceb504677.jpg) 3. Click 📁 on the upper left. Select a type of wall/obstacle area and then start drawing on the map. Left click to start and right click / hit Enter to end. You can also edit the details parameters of the walls and obstacles, delete, and add walls. Adding correct obstacles will increase the accuracy of simulation results. ![](images/66f9f1990e4200579ce150f4b1047985fce427bce97848e71c0004d8baa0d490.jpg) 4. Click to exit the editing status of the map.

Add Map Add Devices and Walls View and Export Results

![](images/5b289538b5a02a9bf049e4e7222dc3ab4c9dcfc942805dd8cd42477e835bb6ac.jpg)

Note:

It is required to click Simulate to generate a new heat map after editing elements on the map. 1. Click Simulate to generate the heat map. You can adjust the receiver sensitivity, show signal strength, and view the simulation results according to your needs. ![](images/74b33efaf5a23baffcc3a5786564eb48ee2122e58f7b8281b86315a43f44a4c9.jpg) Show Signal Strength: ![](images/50eba60a936b0c561737636da05636f52cca19c8df2bce62fd295a67c0fdd8dc.jpg) Enable the feature, and you can move the cursor to view the signal strength of a specific location. Show Simulation: ![](images/9a1464e3a8556c871e8e43384278ef95075184efdf0ab29fc0d84797f7f6bde3.jpg) Enable or disable the display of simulation results on the map. 2.4GHz 5GHz Select 2.4GHz or 5GHz to view the simulation results of the band. ![](images/f39e42ceb00ea3bb666b79def947eccb7187b960edf3bea21dbbb788c9ee58e3.jpg) Click and follow the instruction to specify an area to view the signal strength and the corresponding percentage. ![](images/b37b5b863a7c128ae50b1bd9042a6b8118093b4803239e41703d50e964eb44f2.jpg) Adjust the receiver sensitivity, and the new settings will take effect after refreshing the simulation. 2. (Optional) If you want to export a network coverage report, click ☑ on the upper right to export a report in .docx format.

8.3.3 Device Map

Prerequisite

A valid Mapbox API Access Token is required to use the Device Map function. Visit https://www.mapbox.com, register an account, and obtain the default token on the account page. ![](images/18eb0cde9a2ea35bd528143a4ce66934ac604725bf367324c674ea55cbdac837.jpg)

Configuration

1. Select a site from the drop down list of Organization in the top-right corner. Go to Map > Device Map. 2. Enter the Mapbox API Access Token you obtained, then click Confirm. ![](images/7d9cbdd6ce40060a1c8ce4a973a5a53795e4bc9565a419a803b9e9a8339f6c26.jpg)

3. Select the sites that can share the token, then click Confirm.

![](images/61eabad9833dac2536c5ebc4a9172bb36c843f27b91435a363bb466f99baff65.jpg)

4. Use the map to manage your devices.

![](images/fb0464e5b6f46243f2a2351817ef76e1e58d282813508abff98747d1c31b39c3.jpg)
Unplaced Device ListDisplay a list of sites that are not marked on the map. You can drag and drop a site to add it to the map.
Search barSelect a catogary and enter the keyword to search for a site or address.
Locate to current location.
Zoom in and zoom out the map.
Right-click a device icon to edit location or remove it from the map. ![](images/04de8292583c3de411b16e9b5e54d88539a25eb3a71d5c3db721a633445bf05a.jpg) Click a device icon to view device info and edit settings. ![](images/83557715b1cd1d6135d85b9726a7a76bc340aebda590918bfed2d8909997a436.jpg)

8.3.4 Site Map

Prerequisite

A valid Mapbox API Access Token is required to use the Site Map function. Visit https://www.mapbox.com, register an account, and obtain the default token on the account page. ![](images/fcbea827e2499b64a0821b5790eee74198b8e4904e0ed4ea9af3a216f936fa44.jpg)

Configuration

1. Select Global from the drop down list of Organization in the top-right corner. Go to Dashboard > Site Map. 2. Enter the Mapbox API Access Token you obtained, then click Confirm. ![](images/5446a41774228a3466be07475b4bfc9e5ed4544938a016ce1e9a4a695ddd73a6.jpg) 3. Select the sites that can share the token, then click Confirm. ![](images/e85d4c7712710af692a86c251f9fffc706f8f35b57cb12cdd6c7adf606f73389.jpg) 4. Use the map to manage your sites. ![](images/0b56f3f5866ce285ef78aad9565a2a9880c336df0b0e1badeee21398ad5be538.jpg)
Unplaced Site ListDisplay a list of sites that are not marked on the map. You can drag and drop a site to add it to the map.
Search barSelect a catogary and enter the keyword to search for a site or address.
Locate to current location. Zoom in and zoom out the map. Right-click the map to add a new site. Right-click a site icon to edit location or remove it from the map. Click a site to view site info, and click Launch to access the site. ![](images/582c37178d3c9c8ad377d9e0ab8f912f140435166b4f35ab2131253c57f9b4bc.jpg)

8.4 Monitor the Network with Reports

Network Report shows the statistics of various network indicators and their changes over time, helping network administrators to intuitively and comprehensively understand the current and historical operating status of their network. Thus, it facilitates network administrators to decide whether the controller and devices needs to be upgraded and optimized. It also provides network administrators and SI with data support for reporting network conditions. Go to Reports, and you can view the connection data of the devices in the topology and the statistics of various network indicators and their changes over time. Click the tabs on the top to view the statistics of specific section of the network. ![](images/368ccf416a2301b5de109a0bd44838b1ec2cbe3ee7dd87598155ad5feb25d4cc.jpg)
pie | Metric | Value | | :--- | :--- | | Total Traffic | 1.75 GB (Total Traffic) | | Tx Traffic | 893.06 MB (49.61%) | | Rx Traffic | 906.94 MB (50.39%) | | Total Switches | 1 | | Connected Switches | 1 | | Disconnected Switches | 0 | | Total BAPs | 1 | | Connected EAPs | 1 | | Disconnected EAP's | 3 | | Total Clients | 50 | | Wind Clients | 19 (38.00%) | | Wireless Clients | 31 (62.00%) | | Traffic Distribution | 1.75 GB (Total Traffic) | | Total Traffic (Minutes) | 5 Minutes | | Total Traffic (Minutes) | 5 Minutes | | Wind Traffic (Minutes) | 5 Minutes | | Wireless Traffic (Minutes) | 5 Minutes |
Summary Display the statistics summary of the whole network.
Wireless SummaryDisplay the wireless statistics summary of the whole network, including data related to APs, wireless clients, and wireless traffic.
Wired SummaryDisplay the wired statistics summary of the whole network, including data related to gateway, switches, wired clients, and wired traffic.
Wireless DevicesDisplay details of APs in the network, including AP Traffic, CPU Utilization, Memory Utilization, Total Clients, Alerts, and Reboot Times.
Wired DevicesDisplay details of gateway and switches in the network, including Traffic, CPU Utilization, Memory Utilization, Total Clients, Alerts, and Reboot Times.
SSIDDisplay the statistics of SSIDs in the network, including Traffic, Total Clients, and Activities.
ClientsDisplay the statistics of Clients in the network, including Distribution, Client Activities, and Client Numbers.
When you are accessing the controller locally, you can export the network report or send the report via email by clicking the icons on the upper right. ![](images/c2ab5b79233b9c4ebbd5091b0d2924918cded8c6b1bc8ef71b76fd0465fafdf9.jpg) Click to send the report via email. Both Send Now and Send Schedule are available. ![](images/83b331a50616365d4c2401f0c2f48d19b0da23c81227d69927ff5b82510e5f9d.jpg) Click to export and the network report locally. Note that for Linux system, please install Chromium before exporting the network report and make sure you can run Chromium as root. ![](images/2169c74a0a6b09ed04d7778e078ed67d35762d204b6bf6f41aecff36cd85e1fc.jpg)

8.5 View the Statistics During Specified Period with Insight

In the Insight page, you can monitor the site history of connected clients, portal authorizations, and rouge APs. For a better monitoring, you can specify the time period and classify the clients and APs.

8.5.1 Known Clients

In Known Clients, a table lists all clients that connected to the network before in the site. In the table, you can view the client's basic information, role and connection statistics, including download and upload traffics, connection duration, and the last time it connected to the network. ![](images/592db6bc991e5415787f1e8155c67b6af90010330e933480ea15311b3f5df7f5.jpg) A search bar, a time selector and three tabs are above the table for searching and filtering. ![](images/8f6b7e813f7793948cd58ffa40a0751474a91b9cda0590fdccc8b71c68dd4c64.jpg) All Wireless Wired All Users Guests All Rate Limited Blocked Click the tabs to filter the clients listed in the table. The three tabs can take effect simultaneously. All/Wireless/Wired: Click All to display both wireless and wired clients. Click Wireless or Wired to display wireless or wired clients only. All/Users/Guests: Click All to display both users and guests. Click Users or Gusets to display users or guests only. Guests are users connected to the wireless guest network. To configure guest network, refer to 4.4 Configure Wireless Networks. All/Rate Limited/Blocked: Click All to display both rate limited and blocked clients. Click Rate Limited or Blocked to display rate limited or blocked clients only. To configure Rate Limit, refer to 4.8.3 Rate Limit. To block the clients, click the 🔒 icon in the table. You can also take actions to block or forget the client. For detailed monitor and management, click the entry in the table to open the Properties window of the client. For more details, refer to 7.1.2 Using the Clients Table to Monitor and Manage the Clients.
(For unblocked clients) Click to block the client in the site. Once blocked, the client is banned from connecting to the network in the site.
(For blocked clients) Click to unblock the client in the site.
Click to forget the client. Once forget, all statistics and history of the client in the site are dropped.

8.5.2 Past Connections

In Past Connections, a table displays information about previous client connection sessions. In the table, you can view the client's name, MAC address, association time and duration, download and upload traffic, IP address, and the network/port it connected to. ![](images/dfd07a8fa33eedb3a458dae973a0cd00a5733f2b253473677435120165b1463e.jpg) A search bar and a time selector are above the table for searching and filtering. ![](images/21415e4162e6d6bc69374f58275651bb21db724c7627f0cabcbbeb582b38caf3.jpg)

8.5.3 Past Portal Authorizations

In Past Portal Authorization, a table lists all clients that passed the portal authorization before. In the table, you can view the client's name, MAC address, authorization credential, uplink and downlink traffics, authorization time and duration, IP address, and the network/port it connected to. For detailed monitoring and management, refer to 7.2 Manage Client Authentication in Hotspot Manager. ![](images/4866acd8f34c8e329ffc1b6cd5005e893b1f5d8f6258370e0b7c804c9e96d22a.jpg) A search bar and a time selector are above the table for searching and filtering. Search Name or MAC Address Start date - End date Enter the client name or MAC address to search the clients. Filter the clients based on Start Time. Click the selector to open the calendar. Click a specific date twice in the calendar to display the clients authorized on the day. To display the clients authorized during a time range, click the start date and end date in the calendar.

8.5.4 Switch Status

In Switch Status, a table displays information about the status of the switches managed by the controller. In the table, you can view the ports, PoE status, mode, and traffic activity of the switches. ![](images/b10da38aff65a23249c9f6e888990b3e95c6acfb816951cd2480ccb38db1d082.jpg) A search bar and two tabs are above the table for searching and filtering. You can also click the icons in the Action column for quick operation.
Search Switch or NameEnter the switch or name to search.
Overview PoE CountersAll Connected DisconnectedClick the tabs to filter the switch ports listed in the table. The two tabs can take effect simultaneously.Overview/PoE/Counters: Click Overview to display the general status of each port. Click PoE to display the PoE configurations and status of each port. Click Counters to display TX and RX rates for each port.All/Connected/Disconnected: Filter the ports by their link status. Click All to display information of all ports. Click Connected or Disconnected to display all connected or disconnected ports.
Click to edit the configurations of the port.
(Only for the PoE port that is connected to a PD) Click the button and the port will stop to supply power to the connected PD momentarily in order to reboot the PD.

The listed information when you select Overview on the first tab is explained as follows.

Port Display the port number and status of the port. 10/100 Mbps: The port is running at 10/100 Mbps. 1000 Mbps: The port is running at 1000 Mbps. 2.5 Gbps: The port is running at 2.5 Gbps. 10 Gbps: The port is running at 10 Gbps. ■ Disabled: The port is disabled. \- Disconnected: The port is enabled but connects to no devices or clients. PoE: The PoE port is connected to a powered device (PD). ^Uplink: The port is an uplink port connected to WAN. \- Mirroring: The port is a mirroring port that is mirroring another switch port. STP Blocking: The port is in the Blocking status in Spanning Tree. It receives and sends BPDU (Bridge Protocol Data Unit) packets to maintain the spanning tree. Other packets are dropped. Switch Display the MAC address or the alias of the switch. Name Display the name of the port. PoE Display the PoE status of the port. --: PoE is disabled \_W: Display the power output of the port in watts. Mode Display the operation mode of the port. Switching: The default mode. Mirroring: The network traffic of this port will receive the mirrored traffic from its mirrored port. Aggregating: The port is a part of an aggregate link Profile Display the switch port profile that takes effect on the port. Link Status Display the connection speed and duplex mode of the port. STP Display the Spanning Tree Protocol (STP) mode. TX Sum Display the amount of transmitted data. RX Sum Display the amount of received data. TX Throughput Display the transmit throughput rate. RX Throughput Display the receive throughput rate.

The listed information when you select PoE on the first tab is explained as follows.

Port Display the port number and status of the port. 10/100 Mbps: The port is running at 10/100 Mbps. 1000 Mbps: The port is running at 1000 Mbps. 2.5 Gbps: The port is running at 2.5 Gbps. 10 Gbps: The port is running at 10 Gbps. ■ Disabled: The port is disabled. ■ Disconnected: The port is enabled but connects to no devices or clients. PoE: The PoE port is connected to a powered device (PD). ^ Uplink: The port is an uplink port connected to WAN. \- Mirroring: The port is a mirroring port that is mirroring another switch port. STP Blocking: The port is in the Blocking status in Spanning Tree. It receives and sends BPDU (Bridge Protocol Data Unit) packets to maintain the spanning tree. Other packets are dropped. Switch Display the MAC address or the alias of the switch. Name Display the name of the port. PoE Display the PoE status of the port. --: PoE is disabled \_W: Display the power output of the port in watts. PD Class Display the power requirement of the PD connected to the PoE port. Power Display the power output of the port in watts. Voltage Display the voltage output in volts. Current Display the current output in amperes.

The listed information when you select Counters on the first tab is explained as follows.

Port Display the port number and status of the port. 10/100 Mbps: The port is running at 10/100 Mbps. 1000 Mbps: The port is running at 1000 Mbps. 2.5 Gbps: The port is running at 2.5 Gbps. 10 Gbps: The port is running at 10 Gbps. ■ Disabled: The port is disabled. \- Disconnected: The port is enabled but connects to no devices or clients. PoE: The PoE port is connected to a powered device (PD). ^Uplink: The port is an uplink port connected to WAN. \- Mirroring: The port is a mirroring port that is mirroring another switch port. STP Blocking: The port is in the Blocking status in Spanning Tree. It receives and sends BPDU (Bridge Protocol Data Unit) packets to maintain the spanning tree. Other packets are dropped. Switch Display the MAC address or the alias of the switch. TX Bytes Display the number of transmitted bytes. TX Frames Display the number of transmitted frames. TX Multicast Display the number of transmitted multicast packets. TX Broadcast Display the number of transmitted broadcast packets. TX Errors Display the number of transmitted error packets. RX Bytes Display the number of received bytes. RX Frames Display the number of received frames. RX Multicast Display the number of received multicast packets. RX Broadcast Display the number of received broadcast packets. RX Errors Display the number of received error packets.

8.5.5 Port Forwarding Status

In Port Forwarding Status, a table displays information about the port forwarding entries used by the gateway managed by the controller. ![](images/05b93f0e66b9cbc78356ce864c895082234ca7b5ac3c8ca829b80d9ddd3e7ce2.jpg) A tab is above the table for filtering. You can also click the icons in the Action column for quick operation. ![](images/d4cf33c214666053f5d5bb8a6777238dc8f1dcc637f4b842531fd396ac779b2c.jpg) Click the tab to filter the port forwarding entries listed in the table. User-defined/UPnP: Click User Defined to display the port forwarding entries created by the user. Click UPnP to display the UPnP port forwarding entries. ![](images/12a5b6cb3b15def800cb2770672884370737a1ae7a8436ae197b4f8fa025813f.jpg) Click to edit the configurations of the port forwarding entry. The listed information is explained as follows. Name Display the name of the port forwarding entry. Interface Display the WANs used by the port forwarding entry. Source IP (Only for user-defined entries) Display the source IP address. A specific IP address/Mask: The specified source IP address. 0.0.0.0/0: All IP addresses are set as the source IP address. Source Port The traffic through the source port, also known as internal port, will be forwarded to the LAN. Destination IP Display the destination IP address, and it will receive the forwarded port traffic. Destination Port Display the destination port, also known as internal port, that will receive the forwarded traffic. Protocol Display the protocol that will be forwarded. Packets Display the number of transferred packets. Bytes Display the number of transferred bytes. Lease Duration (Only for UPnP port forwarding) Display the uptime of the port forwarding entry.

8.5.6 VPN Status

In VPN Status, a table displays the existing VPN tunnels and corresponding information. ![](images/34e3edb7b619a5b1eb0818baa4c50f255848454d5e629860b865afe32a4c6045.jpg) A tab is above the table for filtering. You can also click the icons for quick operation.
IPsec VPN OpenVPN/PPTP/L2TP SSL VPNClick the tab to filter the routing information listed in the table. When you select OpenVPN/PPTP/L2TP, you can further choose Server or Client.
Click to configure the entry.
(Only for OpenVPN/PPTP/L2TP) Filter the entries.
(Only for OpenVPN/PPTP/L2TP) Click to terminate the VPN tunnel.
(Only for OpenVPN/PPTP/L2TP) Click to choose more listed information to be displayed in the table.
(Only for SSL VPN) Click to lock out the user. You can click View Locked Out Users to manage the locked out users.
(Only for SSL VPN) Click to disconnect the user.
The listed information of IPsec VPN table is explained as follows.
Name Display the name of the IPsec VPN entry.
SPI Display the Security Parameter Index of VPN.
Direction Display the direction of the VPN process.
Tunnel IDDisplay the local and remote IP address/name. The arrow indicates the traffic direction.
Data Flow Display local and remote subnet. The arrow indicates the direction. Protocol Display the authentication and encryption protocol of the entry. AH Authentication Display checksum algorithms of the entry. ESP Authentication Display the algorithms for ESP authentication. ESP Encryption Display the algorithms for ESP encryption. ![](images/1b6203af2c1ee780eec9a3a59cb543fc0071f5106ff49d519be883a5b0bbe4ec.jpg) The listed information of OpenVPN/PPTP/L2TP (Server) table is explained as follows (some information listed below is hidden by default). You can further filter the entries based on their type. User Display the username of the remote user. Interface Display the interface that the traffic goes through. Type Display the connection type. Local IP Display the local IP address of the VPN tunnel. Remote Local IP Display the IP address of the remote user of the VPN tunnel. DNS Display the DNS address of the VPN tunnel. Download Pkts Display the amount of data downloaded as packets. Download Bytes Display the amount of data downloaded as bytes. Upload Pkts Display the amount of data uploaded as bytes. Upload Bytes Display the amount of data uploaded as bytes. Uptime Display the time duration that the VPN tunnel has been active. ![](images/96f9ab74a3b0c8f39dd08a8feab51eebb2c941dce3c1298200afac0b4d2264b7.jpg) The listed information of OpenVPN/PPTP/L2TP (Client) table is explained as follows (some information listed below is hidden by default). You can further filter the entries based on their type. Interface Display the interface that the traffic goes through. Tunnel Display the name of the VPN client. Type Display the connection type. Remote Local IP Display the IP address of the remote user of the VPN tunnel. DNS Display the DNS address of the VPN tunnel. Download Pkts Display the amount of data downloaded as packets. Download Bytes Display the amount of data downloaded as bytes. Upload Pkts Display the amount of data uploaded as bytes. Upload Bytes Display the amount of data uploaded as bytes. Uptime Display the time duration that the VPN tunnel has been active. ![](images/1a810b3cf4f203b5ff866086a132106ecef30e34b620124485035417ae89d84a.jpg) The listed information of SSL VPN table is explained as follows. Username Display the username of the remote user. Login IP Display the login IP address of the remote user. Virtual IP Display the virtual IP address of the remote user. Login Time Display the login time of the remote user. Statistics Display the upload and download traffic of the remote user.

8.5.7 Routing Table

Routing Table displays information of routing entries that have taken effect. ![](images/c8b03dafb20c0d7c2155f5653776105789e37bbf7b20ae4b74a5b25871aba327.jpg) ![](images/1fa2ce159b22feb25085e9dae7874ebd5b42733f315e86ce5d808615d30f04b2.jpg) A tab is above the table for filtering. You can also click the icons in the Action column for quick operation. ![](images/8a33f1f4dd69587f1ff3b2ad4b6def539e9a2550a00a4eb741946b4dc240cb57.jpg) Click the tab to filter the routing information listed in the table. Gateway/Switch: Click to display the routing information of the gateway or the switch. ![](images/af6a207ea966fe05c4a8bf7dae20c650393c1edc4326b983a3506c45bc475fd9.jpg) (Only for switch) Click to configure the static routes. The listed information is explained as follows. Destination IP/Subnets Display the destination IP addresses of the routing entry.. Next Hop Display the IP address of the next hop. Interface (Only for Gateway) Display the interface that the traffic of the entry goes through.
Metric(Only for Gateway) Display the number of hops before reaching the destination. Generally, if there are a few routing entries with the same destination, the routing with the lowest metric will be used.
Distance(Only for Switch) Display the administrative distance of the routing entry. It is used to decide the priority among routes to the same destination. Among routes to the same destination, the route with the lowest distance value will be used.

8.5.8 Dynamic DNS

In Dynamic DNS, a table displays information about the uses of the dynamic DNS services. You can click ☑ in the Action column to edit the entry. ![](images/90343bb79dc624ab92c12fe0f828e48380ee542b70c4d3085ac3633da26a6d9f.jpg) Service Display the name of the DDNS service. Interface Display the WANs used by the DDNS entry. Status Display the status of the latest DDNS update. Username Display the username of the DDNS account. Domain Name Display domain name registered with the DDNS service. IP Display the IP address of the domain name. Last Updated Display the time when the IP address of the domain name was last updated.

8.5.9 Rogue APs

A rogue AP is an access point that has been installed on a secure network without explicit authorization from a system administrator. In Rogue APs, you can scan rogue APs and view the rogue APs scanned before.
NAME/SSIDBSSIDCHANNELSECURITYBEACONLOCATIONSIGNALLAST SEEN
ChinaNet-gcvZ48-A7-4E-80-80-C811 (11ng)WPA-Personal100Nearest B0-95-75-E6-48-C2100% (-14dBm)May 27, 2020 02 01:20 pm
yangxinxin200-0A-EB-13-7A-FF9 (11ng)WPA-Personal100Nearest B0-95-75-E6-48-C2100% (-15dBm)May 27, 2020 02 01:20 pm
mmmmmmmmmm54-A7-03-57-C4-E56 (11ng)WPA-Personal100Nearest B0-95-75-E6-48-C2100% (-34dBm)May 27, 2020 02 01:20 pm
Xiaomi_14CDEC-41-18-E6-14-CE1 (11ng)WPA-Personal100Nearest B0-95-75-E6-48-C2100% (-43dBm)May 27, 2020 02 01:20 pm
nxcily8C-AB-8E-99-76-B013 (11ng)WPA-Personal100Nearest B0-95-75-E6-48-C2100% (-50dBm)May 27, 2020 02 01:20 pm
midea_e2_20873C-2C-94-20-C9-526 (11ng)WPA-Personal100Nearest B0-95-75-E6-48-C298% (-51dBm)May 27, 2020 02 01:20 pm
ChinaNet-eGaN80-41-26-05-15-6410 (11ng)WPA-Personal100Nearest B0-95-75-E6-48-C283% (-57dBm)May 27, 2020 02 01:20 pm
ChinaNet-y7FkDC-A3-33-B0-C2-121 (11ng)WPA-Personal100Nearest B0-95-75-E6-48-C280% (-50dBm)May 27, 2020 02 01:20 pm
ChinaNet-azsL94-BF-80-80-33-C07 (11ng)WPA-Personal100Nearest B0-95-75-E6-48-C220% (-82dBm)May 27, 2020 02 01:20 pm
Search Name or MAC AddressEnter the client name or MAC address to search the clients.
Start date - End dateFilter the rogue APs based on Last Seen.Click the selector to open the calendar. Click a specific date twice in the calendar to display the rogue APs scanned on the day. To display the scanned AP during a time range, click the start date and end date in the calendar.
All 2.4G 5GClick the tab to filter the rogue APs listed in the table based on the frequency band.
ScanClick to scan rogue APs. It may take several minutes, and the wireless service may be influenced during scanning.
BSSID A string with a similar form as MAC address to recognize access points.
Channel Displays the operation channel and standard of the rogue AP.
Security Displays the security strategy of the rogue AP.
Beacon Displays the beacon interval of the rogue AP.
Beacons are transmitted periodically by the EAP to announce the presence of a wireless network for the clients, and the interval means how often the AP send a beacon to clients.
LocationDisplays the managed AP nearest to the rogue AP. You can click the nearest AP to open its Properties window.
Signal Displays the signal strength in percentage and dBm). Last Seen Display the last time that the rogue AP was scanned by the controller.

8.6 View and Manage Logs

The controller uses logs to record the activities of the system, devices, users and administrators, which provides powerful supports to monitor operations and diagnose anomalies. In the Logs page, you can conveniently monitor the logs in 8.6.1 Alerts and 8.6.2 Events, and configure their notification levels in 8.6.3 Notifications. All logs can be classified from the following four aspects. ■ Occurred Hierarchies Two categories in occurred hierarchies are Controller and Site, which indicate the log activities happened, respectively, at the controller level and in the certain site. Only Main Administrators can view the logs happened at the controller level. \- Notifications Two categories in notifications are Event and Alert, and you can classify the logs into them by yourself. ■ Severities Three levels in severities are Error, Warning, and Info, whose influences are ranked from high to low. \- Contents Four types in contents are Operation, System, Device, and Client, which indicate the log contents relating to.

8.6.1 Alerts

Alerts are the logs that need to be noticed and archived specially. You can configure the logs as Alerts in Notifications, and all the logs configured as Alerts are listed under the Alerts tab for you to search, filter, and archive. ![](images/06c76ff9126b0746394fffab24f70ac73548055f877f14e0d665d1c01854fb83.jpg)
Click to change the view mode for a better overview.
Displays the logs in a table.
//: Displays the logs in a day/week/month. To change the time, click or .To jump back to the current one, click Today/This Week/This Month.
Type, level or contentEnter the content types, severity levels, or key words to search the logs.
UnarchivedArchivedClick the tabs to filter the logs listed in the table. The two tabs can take effect simultaneously.
AllErrorsWarningsUnarchived/Archived: Click the tab to filter the unarchived and archived logs. You can click and Archive All to archive a single log and all, respectively.
All/Errors/Warnings: Click All to display logs in both Error, Warning, and Info levels. Click Errors or Warnings to display logs in Error or Warning levels only.
ContentDisplays the log types and detailed message. You can click the device name, client name to open its Properties window for detailed information.
Time Displays when the activity happened. Archive All Click to archive all unarchived logs. ![](images/2073c0ad8e5a5de70c2b84180eb3db8de22952874fb35ca799f182e6d186621f.jpg) Click to archive the log entry. ![](images/b706dab326be98b268f211ba7f767ea549409619df40669053c3c55015731682.jpg) Click and select the log types to delete the corresponding alert logs. Once deleted the archived alerts cannot be recovered. The unarchived alerts cannot be deleted.

8.6.2 Events

Events are the logs that can be viewed but have no notifications. You can configure the logs as Events in Notifications, and all the logs configured as Events are listed under the Events tab for you to search and filter. ![](images/e0896dba85afb1ed152b0018fbe1aa7d8e472eaab53633de32c213b6742310bd.jpg) ![](images/470352858463a26ce0e7fbb5520501dacdd7617df35adc8c84e2b870f15a8260.jpg) ![](images/21751262c586ac7524768e771df3c46c6d38fa5975b09b07613ebc88f3f13d81.jpg) ![](images/731c11fb95559afc73aedbfeb90299d74ff03647a3b13715ff3c5177e111b304.jpg) ![](images/c242d25eea03032b4d5f0430351156a375d805e68d72978269e6361e10a088e3.jpg) Click to change the view mode. : Displays the logs in a table. //: Displays the logs in a day/week/month. To change the time, click or >. To jump back to the current one, click Today/This Week/This Month.
TP-LINK Omada SDN Controller - Events - 1Enter the content types, severity levels, or key words to search the logs.
TP-LINK Omada SDN Controller - Events - 2Click and select the log types to delete the corresponding event logs.
[SDY1]Click the tabs to filter the logs listed in the table. The two tabs can take effect simultaneously.
[HC65]All/Errors/Warnings/Info: Click All to display logs in both Error and Warning levels. Click Errors,Warnings or Info to display logs in the corresponding level only.All/Operation/System/Device/Client: Click All to display all types of logs. Click Operation or System or Device or Client to display the corresponding type of logs only.
Content Displays the log types and detailed message. You can click the device name, client name to open its Properties window for detailed information.
Time Displays when the activity happened.

8.6.3 Notifications

In Notifications, you can find all kinds of activity logs classified by the content and specify their notification categories as Event and Alert for the current site. Also, you can enable Email for the logs. With proper configurations, the controller will send emails to the administrators when it records the logs. ![](images/ddf70e08c523385014ea0c29250a2c89434667107f8283361d891012d31dedce.jpg) To specify the logs as Alert/Event, click the corresponding checkboxes of logs and click Apply. The following icons and tab are provided as auxiliaries.
Reset to DefaultClick to reset all notification configurations in the current site to the default.
OperationSystemDeviceClientClick the tabs to display the configurations of corresponding log types.
□ Even! □ AlertEnable the checkboxes to specify the activity logs as Events/Alerts, and then the recorded logs will be displayed under the Events/Alerts tab. If both of them are disabled, the controller will not record the activity logs.
□ EmaiEnable the checkboxes to specify the activity logs as alert logs. With proper settings in Site and Admin, the controller can send emails to notify the administrators and viewers of the site's alert logs once generated.
This icon appears when the configuration of a log is changed but has not been applied. Click it to reset the configuration of the log to the default.
The Email checkboxes are used to enable Alert Emails for the logs. To make sure the administrators and viewers can receive alert emails of the site, follow the following steps: 1) Enable Mail Server 2) Enable Alert Emails in Site 3) Enable Alert Emails in Admin 4) Enable Alert Emails in Logs Enable Mail Server Enable Alert Emails in Site Enable Alert Emails in Admin Go to Settings > Controller. In the Mail Server section, enable SMTP Server and configure the parameters. Then click Save.

Mail Server

![](images/57cca63e49cbd4ce25e7a29be232a1e6979ba4ea98e308be250ef06010c6f8c7.jpg) With the Mail Server, the controller can send emails for resetting your password, pushing notifications, and delivering the system logs. For security reasons, we recommend that you configure Mail Server carefully. SMTP Server: ![](images/8c002935edd36f69f13cc35afa4a9c5abc52e5abecd263e52d0aa18e316824d7.jpg) Enable SMTP: example.url Port: 25 (1-65535) SSL: ![](images/8dc8769bf28f0550a5f6300398d39f84cbb0d1c00279208530b7b1b4f41ff760.jpg) Enable Authentication: ![](images/20aee8784d4ce1739d3eb4e2eb8e611b562118fc3604c508699aa44f263f1596.jpg) Enable Sender Address: example@sender.address (Optional) Test SMTP Server: Send Test Email to example@tp-link.com Send
SMTPEnter the URL or IP address of the SMTP server according to the instructions of the email service provider.
PortConfigure the port used by the SMTP server according to the instructions of the email service provider.
SSLEnable or disable SSL according to the instructions of the email service provider. SSL (Secure Sockets Layer) is used to create an encrypted link between the controller and the SMTP server.
AuthenticationEnable or disable Authentication according to the instructions of the email service provider. If Authentication is enabled, the SMTP server requires the username and password for authentication.
Username Enter the username for your email account if Authentication is enabled.
Password Enter the password for your email account if Authentication is enabled.
Sender Address (Optional) Specify the sender address of the email.
Test SMTP Server Test the Mail Server configuration by sending a test email to an email address that you specify. Enable Mail Server Enable Alert Emails in Site Enable Alert Emails in Admin 5. Go to Settings > Site and enable Alert Emails in the Services section.

Services

LED: Enable Automatic Upgrades: Enable Channel Limit: Enable i Mesh: Enable i Auto Failover: Enable i Connectivity Detection: Auto (Recommended) Full-Sector DFS: Enable i Periodic Speed Test: √ Enable Speed Test History Speed Test Interval: 20 hours (10-999) Alert Emails: Enable alert emails i ![](images/eaee4f6e34dbaf2f5bd6dbb8551c91f9d19f23b19906d14710ce1d07d364ae2a.jpg) √ Send similar alerts within 60 seconds in one email. ![](images/e86ac1046c1acdbfc992e2d5cac35f5d5469490db1f5d2192f0390f5febbf7c5.jpg) Remote Logging: Enable i Syslog Server IP/Hostname: 514 (1-65535) Syslog Server Port: Enable i Client Detail Logs: Enable Advanced Features: 6. (Optional) On the same page, enable Send similar alerts within seconds in one email and specify the time interval. When enabled, the similar alerts generated in each time period are collected and sent to administrators and viewers in one email. Alert Emails: Enable alert emails i √ Send similar alerts within 60 seconds in one email. ![](images/97c744c70e234f7b9b35de2088612c1035aec671cdcdc72994c9200561a0a631.jpg)

7. Click Apply.

Enable Alert Emails in Site Enable Alert Emails in Admin Enable Alert Emails in Logs Go to Admin and configure Alert Emails for the administrators and viewers to receive the emails. Click + Add New Admin Account to create an account or click ☑ to edit an account. Enter the email address in Email and enable Alert Emails. Click Create or Apply.

Edit Account

Username: Administrator Change Password: Enable Role: Administrator Site Privileges: All (Including all new-created sites) ○ Sites Device Permissions: √ Adopt Devices √ Manage Devices (Move to Site, Restart, Upgrade and Forget) Email: example@tp-link.com Alert Emails: Enable ![](images/3e5d2e5a53d6b6bb2245ddd2850b726bcb9cdc5753754d2b78ddaba3381703e2.jpg) Save Cancel

Enable Alert Emails in Site Enable Alert Emails in Admin Enable Alert Emails in Logs

Go to Logs and click Notifications. Click a tab of content types and enable Email for the activity logs that the controller emails administrators. Click Save. ![](images/c874ab26a3efa3150ccbdb2292786d43342564e76f57daf0d8382e44e666dccb.jpg)

8.7 Monitor the Network with Tools

The controller provides many tools for you to analyze your network: ■ Network Check Test the device connectivity via ping, traceroute, or DNSLookup. ■ Packet Capture Capture packets for network troubleshooting. \- Terminal Open Terminal to execute CLI or Shell commands.

! Note:

Firmware updates are required for earlier devices to support these tools.

8.7.1 Network Check

1. In the Site view, go to Tools > Network Check. 2. Configure the test parameters. ![](images/de4ea3a751dd1e003bb7329b58eab9e3517a3f0dd20959c8f0eafa0a9e5d8b3b.jpg) Device Type Select the device type to perform a test. Test Choose a tool to test the device connectivity. Ping: Tests the connectivity between the specified sources and destination, and measures the round-trip time. Traceroute: Displays the route (path) the specified sources have passed to reach the specified destination, and measures transit delays of packets across an Internet Protocol network. DNSLookup: Helps find DNS records of a domain name. Sources Select one or multiple devices to perform a test. Destination Type Select the destination type and specify the destination to test. The options vary with the test type. For the Ping test, you can specify the Domain/IP Address or Client. Client is available only when an AP device performs the ping test. For the Traceroute test, you can specify the Domain/IP Address. For the DNSLookup test, you can specify the Domain. Advanced Test Settings (Only for the Ping test) Packet Size: Specify the size of ping packets. Count: Specify the number of ping packets. ![](images/5bf7ff54c0251f1f48c5032f9b8b25488eff4730b548269119a596d527a25b32.jpg)

Note:

• Devices which are already running commands shall not execute newly added commands. - Output history of device with buffer space issues shall be automatically cleared.

3. Click Run to perform the test. You can view the test result in the Device Output section.

![](images/16fb98baa9317d1e496dd42a9252390820b06238f8c743f953b46f19e0e30df7.jpg) ![](images/b5a73a1eb9d59d6b1537399c8d915e5f7adcc0230f14e8eda7d1e8fb1710b79f.jpg) ![](images/87ae41170ad8a9183cb4e4ba33b01b73e986d57ae3164794edd84f54c76e7d22.jpg) ![](images/b0e64b24c3857b3b83a2915690ef18f25b2733d05ddcbdc423d2cb2128869dbc.jpg) Click to email the test logs to a mailbox. Click to download the test logs locally. Zoom out and zoom in the display area.

8.7.2 Packet Capture

1. In the Site view, go to Tools > Packet Capture.

2. Configure the parameters for packet capture.

![](images/2343716a66278fb8ee16bbf3b1505cdbe270bca466ff48a2ada45857ed3f504d.jpg) Device Type Select the device type to capture packets. Sources Select one or multiple devices to capture packets. Duration Specify the duration for packet capture. Single Packet Size Specify the size of a single captured packet. It cannot exceed 1 MB. Packet Capture Filters Enter the filters to capture packets. Supported filters include: host, src, dst, tcp port, tcp src port, tcp dst port, udp port, udp src port, udp dst port, ether host, ether src, ether dst Combination of operators "and", "or", "(“ and ”)" is supported between multiple filter items. For example: (src 192.168.0.1 and tcp port 80) or (src 192.168.0.1 and tcp port 90) Note: host: host address, src: source, dst: destination, ether: ethernet address (MAC address)

3. Click Start Packet Capture to capture packets. After packets are captured, you can click Download .pcap Files to download them.

① Note:

The file will be kept for 10 minutes only and can only be downloaded three times.

8.7.3 Terminal

1. In the Site view, go to Tools > Terminal.

2. Configure the parameters.

![](images/c0bbcb2e555ab7bbe74a08a8a7070f1826b79a643fd187081e6fad85eaef6fd4.jpg) Device Type Select the device type to run CLI or Shell commands. Sources Select one or multiple devices to test.

3. Click Open Terminal. Now you can run CLI or Shell commands.

![](images/786f5ef110cf95ab58993e0ca58ffaf5845ff65c17c03cf1f6efc6eb1fc014d7.jpg) ![](images/95b8d26ab3cba18a4821c3de2ff47f523d67c1d800d93483e5b6756d35ef81e2.jpg) Click to email the test logs to a mailbox. ![](images/5ae5d2669de6026b7da9b86c96d43fcc29182c2526bc6185143bbc3b07562330.jpg) Click to download the test logs locally. ![](images/cf32619b80ad960274ec2bd5ea943a489188269aa72346e873580d82962da8e2.jpg) Zoom out and zoom in the display area. ![](images/f1127b4043a83227fce19caba2221b6a05e3a3e391d5ce15eb981708b37f3e79.jpg)

Manage Accounts of the SDN Controller

This chapter gives an introduction to different user levels of controller accounts and guides you on how to create and manage them. The chapter includes the following sections: • 9.1 Introduction to User Accounts • 9.2 Create and Manage Custom Account Roles • 9.3 Manage and Create Local User Accounts • 9.4 Manage and Create Cloud User Accounts

9.1 Introduction to User Accounts

The SDN Controller offers three levels of access available for users: main administrator, administrator, and viewer. You can also create new account roles and customize their permissions to access different features. Since the controller can be accessed both locally and via cloud access, users can be further grouped into local users and cloud users. Multi-level administrative account presents a hierarchy of permissions for different levels of access to the controller as required. This approach ensures security and gives convenience for management. Moreover, in the user accounts list of the main administrator, all accounts created by the main administrator will be displayed. The accounts created by each administrator will be hidden by default, making the interface more systematic and to the point.

■ Main Administrator

The main administrator has access to all features. The account who first launches the controller will be the main administrator. It cannot be changed and deleted.

■ Administrator

Administrators have no permission to some modules, mainly including cloud access, migration, auto-backup and global view logs. They have read-only permission to some modules, such as global view license management and custom account roles. Administrators can be created and deleted by the main administrator and administrators.

■ Viewer

Viewers can view the status and settings of the network, and change the settings in Hotspot Manager. The entrance to Account page is hidden for viewers, and they can be created or deleted by the main administrator and administrators.

■ Custom roles

Custom roles can be configured to access different features. They can be created or deleted only by the main administrator.

Note:

Please upgrade Omada APP to version 4.6 or later, otherwise you may not be able to log in with the accounts bound with customized roles.

9.2 Create and Manage Custom Account Roles

1. Select Global from the drop-down list of Organization in the top-right corner. Go to Account > Role.

2. Click Add New Role. Specify the role type name and customize the permissions for the role.

![](images/c640315afdd1c6e982a6a9f29c0c204fb9ab9ba0a19dc503fba78d218f0c1f55.jpg)

3. Click Create. The new role will be displayed in the role list.

![](images/dbc5cc5a431413c4afe6814e8d58d83416626bcd6bbeb4c94062a24f455db3f9.jpg) To edit/delete a custom role, click the / icon in the ACTION Column.

9.3 Manage and Create Local User Accounts

By default, the SDN Controller automatically sets up a local user with the role called main administrator as the primary administrator. The username and password of the main administrator are the same as that of the controller account by default. The main administrator cannot be deleted, and it can create, edit, and delete other levels of user accounts.

9.3.1 Edit the Main Administrator Account

To view basic information and edit the main administrator account, follow these steps: 1. Select Global from the drop-down list of Organization in the top-right corner. Go to Account >User. 2. Click ☑ in the Action column. Check and edit the account information. Click Save. ![](images/4e14cebb6c03ec6a78a0dc015f12d2da4e7ce44046c731d37a4a803f4b88d17c.jpg)
Permission TransferClick the button and select a new main administrator to transfer the Cloud Main Administrator permissions of the current account to the new account. The current account will be downgraded as Administrator.
Alert EmailsCheck the box if you want the current user to receive emails about alerts of the privileged sites.

9.3.2 Create and Manage Other Local Accounts

To create and manage a local user account, follow these steps: 1. Select Global from the drop-down list of Organization in the top-right corner. Go to Account >User. 2. Click Add New User. 3. Select Local User for the administrator type in the pop-out window. Specify the parameters and click Create. ![](images/4d6daf970b7c46bdaf9bc0636e0aa05f205a747d2d8187be8bd4668efff23b28.jpg) Username Specify the username. The username should be different from the existing ones. Password Specify the password. Role Select a role for the created user account. Administrator: This role has permissions to adopt and/or manage devices of the sites chosen in the site privileges, edit itself, create/edit/delete viewer accounts in its privileged sites. However, it cannot delete itself or edit/delete main administrator. Viewer: This role can view the information of the sites chosen in the site privileges. It can only edit itself. Custom roles: If you have created custom roles, they will be displayed in the list. To create custom roles, refer to 9.2 Create and Manage Custom Account Roles. Site Privileges Assign the site permissions to the created local user. All: The created user has device permissions in all sites, including all new-created sites. Sites: The created user has device permission in the sites that are selected. Select the sites by checking the box before them. Email (optional) Enter an email address for receiving alert emails. Alert Emails Check the box if you want the created user to receive emails about alerts of the privileged sites. For detailed configurations, refer to 4.2.2 Services.

9.4 Manage and Create Cloud User Accounts

For cloud-based controller, the cloud access is enabled by default, and the controller automatically sets up the cloud main administrator. Software and hardware controller automatically sets up the cloud main administrator if you have enabled cloud access and bound the controller account with a TP-Link ID in the quick setup. The username and password is the same as that of the TP-Link ID. The cloud main administrator is cannot be deleted, and it can create, edit, and delete other levels of user accounts.

9.4.1 Set Up the Cloud Main Administrator

For software and hardware controller, if you have not enabled the cloud access and bound the controller with a TP-Link ID in quick setup, to set up the cloud main administrator, follow these steps: 1. Select Global from the drop-down list of Organization in the top-right corner. Go to Settings > Cloud Access to enable Cloud Access and bind your TP-Link ID. ![](images/6b20bcc57b6b7f43495f20f8957f506e783e72525f6f67f54d75bd10ae6b1718.jpg) 2. Go to Account > User. A cloud main administrator with the same username as the TP-Link ID will be automatically created. The Cloud Main Administrator cannot be deleted. You can log in with the cloud main administrator when the cloud access is enabled.

9.4.2 Create and Manage Other Cloud Accounts

To create and manage cloud user account, follow these steps: 1. Select Global from the drop-down list of Organization in the top-right corner. Go to Account >User. 2. Click Add New User. 3. Select Cloud User for the administrator type in the pop-out window. Specify the parameters and click Invite. ![](images/336acf9cdd7317ea4f9d95ddc4501c1c6266c0206029cb67ff3e0cc60c0bf213.jpg)
TP-Link IDEnter an email address of the created cloud user, and then an invitation email will be sent to the email address.If the email address has already been registered as a TP-Link ID, it will become a valid cloud user after accepting the invitation.If the email address has not been registered, it will receive an invitation email for registration. After finishing registration, it will automatically becomes a valid cloud user.
RoleSelect a role for the created cloud user.Administrator: This role has permissions to adopt and/or manage devices of the sites chosen in the site privileges, edit itself, create/edit/delete viewer accounts in its privileged sites. However, it cannot delete itself or edit/delete main administrator and other administrator accounts.Viewer: This role can view the information of the sites chosen in the site privileges. It can only edit itself.Custom roles: If you have created custom roles, they will be displayed in the list. To create custom roles, refer to9.2 Create and Manage Custom Account Roles.
Site Privileges Assign the site permission to the created cloud user. All: The created user has permission in all sites, including all new-created sites. Sites: The created user has permission in the sites that are selected. Select the sites by checking the box before them.

Alert Emails

Check the box if you want the created user to receive emails about alerts of the privileged sites. For detailed configurations, refer to 4.2.2 Services.

10

Manage Customer Networks in MSP Mode

MSP (Managed Service Provider) mode allows you to know the status of your customers at a glance, and manage customers in the Omada platform. ■ Customer Monitoring Keep you informed of accurate, real-time status of every customer. ■ Customer Management Manage all customers to deploy the whole network. ■ Account Settings Manage all administrative accounts. This chapter will introduce how to enable MSP mode and manage customer networks in MSP view. • 10.1 Quick Start • 10.2 Add and Manage Accounts • 10.3 Manage System Settings ![](images/be3b4e49670cd693d06ef9e9267dbb60b9dac8900010112c39a1277a63fa05d3.jpg)

10.1 Quick Start

10. 1. 1 Enable the MSP Mode

1. Launch your controller. 2. In Global View, click : in the top-right corner and click Enable MSP mode. In the dialog box that pops up, confirm the operation. ![](images/44cf60cd978a6444409abcc5a46f22e700980783f5111a94e64359aa1f9d244f.jpg)

Note:

Enabling or disabling MSP mode may cause problems on the connected Cloud access page. In this case, re-enter the web page. ![](images/5768861d63b8dbb500fb8bbe11d4c17671d59a14a59e877d028f9c7c56f57e7f.jpg)

You will enter the MSP view.

![](images/e9f0be6272428582b1318fcb327f3dd3f99c996f089e5c8a7f636a3997ed9a5a.jpg)

10. 1. 2 Add and Manage Customers

1. In MSP View, go to the Customer page. 2. Add customers by using one of the following methods: \- Add a new customer Click Add New Customer above the customer list. Specify the customer name and enter a description. Then save the settings. ![](images/29b35ed1d673f33b32c598779a90d67908915aee36cf362edbd4ca05c01edf42.jpg) \- Copy an existing site Click the 📄 icon of a customer entry. Specify the customer name and enter a description. Then save the settings. ![](images/98069b694988b917d99cd3a2c587d11bfc1ce7447ba9cc471c0e5e0c2cba31d3.jpg)

- Import customers from another controller

Click Import Customer above the customer list. Specify the customer name and enter a description. Determine whether to retain device info according to your needs. Then import customer from a local file or from a file server. ![](images/4abb130ca922d684ef47ed30f796618ceb5055ba408d144bd1fcc1d01f00f763.jpg)

3. The new customers will be added to the customer list and the drop-down list of Customers.

In the customer list, you can view the customer information, and click the icons in the ACTION column to manage customer entries and launch the controller of each customer. ![](images/e7184322f78a7e41a5625b4c3159da02d70287f763a4ea3829717c366fb9f0cb.jpg)

10. 1. 3 Assign and Manage Licenses

1. Launch the Cloud-Based Controller. In MSP View, go to the License page. 2. Go to License > Licenses. Enable Auto-Active and Auto-Renewal if needed. Auto-Active will automatically apply device license to a device as soon as it is adopted by your controller. After Auto-Active is enabled on the controller, all its customers will enable Auto-Active by default. When Auto-Renewal is enabled for a customer, the licenses for active devices of the customer will be automatically renewed when they expire. ![](images/6dd94063cd1931642a751a68b2c1b803007af582f893c6ee298612f1212db191.jpg) 3. Go to License > License Assignment, and click Assign Licenses. Select the customer and assign licenses. ![](images/275eaa1138d17187f2303650918636c503bd5905a7d13bb1f96ea40cd7d7a9ba.jpg) After license assignment, you can click Revoke Licenses and select a customer to revoke licenses in case needed.

10. 1. 4 Add Sites and Devices

1. Select a customer from the drop-down list of Customers in the top-right corner. 2. Add sites and adopt devices by referring to 3 Manage Omada Pro Managed Devices and Sites. You can also add devices on the Devices page in MSP View. ![](images/c0ce7a4b863d14a703f8d3a9a09e2cdbc3a56dc3903afe6283cd36156201cdf0.jpg)

10.2 Add and Manage Accounts

10.2.1 Configure Role Settings

The system offers two types of roles: - MSP Role: for manage settings in MSP view. - Customer Role: for manage settings in global and site views. Each role type has three default levels of access permissions: Main Administrator, Administrator, and Viewer. You can also create new account roles and customize their permissions to access different features. \- Main Administrator The Main Administrator has access to all features in the corresponding view. The account who first launches the controller will be the Main Administrator. \- Administrator Administrators have access to most features in the corresponding view except for some modules. For example, they have no permission to system migration and data auto-backup and have view-only permission to system license management and custom account roles. \- Viewer Viewers can view the status and settings of some features in the corresponding view. \- Custom roles Custom roles can be configured to access different features in the corresponding view. ![](images/337833966530d61e43fb01e8ad3fb856b2ce3bcc5d2be8c28d1d74bd07553605.jpg)

Note:

Please upgrade Omada APP to version 4.6 or later, otherwise you may not be able to log in with the accounts bound with customized roles. To add a custom role, follow the steps below: 1. In MSP View, go to Account > Role. ![](images/5745236b859cc4229de2c8c73101b520948fee0bddf653397f071ccf03f6fb20.jpg) 2. MSP roles are used for manage settings in MSP view. On the MSP Role page, click Add New MSP Role. Specify the role type name and customize the permissions for the role. Parameters may vary by controller type. ![](images/789ed1a45a1b604ca331fbbcd6152819ff10dae0317b4373749f7e4ac1b67443.jpg) 3. Customer roles are used for manage settings in global view and site view. On the Customer Role page, click Add New Customer Role. Specify the role type name and customize the permissions for the role. Parameters may vary by controller type. ![](images/8e830948c2064f8133b6a53112bc0ec7c855e281e8580e81bf2c12ea4a80ce7b.jpg)

10.2.2 Manage the Main Administrator Account

The account who first launches the controller will be the MSP Main Administrator (for managing settings in MSP View) and Main Administrator (for managing settings in Global View and Site View). To edit the account settings, follow the steps below: 1. In MSP View, go to Account > User. ![](images/99ed2476823097f375362bcc83e4f7dc46dfcae3e68a5c01a58e613966d9829b.jpg) 2. Click the Edit icon to change settings. You can enable Alert Emails if you want this account to receive emails about alerts. ![](images/44ecd7fbc33678596a7254b4300f591a5a169646ef109857534b2517695f2f1c.jpg) 3. If you want to transfer the permissions to another account, click Permission Transfer and specify the new account. ![](images/7a34a9325540a8d822fcdf19d1c1a75898664b78b3e823fda100987728f90423.jpg)

10.2.3 Add New MSP User Accounts

To create and manage a local user account, follow these steps: 1. In MSP View, go to Account > User.

2. Click Add New User. Specify the parameters and click Invite.

![](images/0258d0e6d0770d4e9736c512a4bcc93dcda4dfde8bf6654d15b4190fd9d76c21.jpg) Administrator Type Specify whether to add a local user or cloud user. Local user is not supported by the cloud-based controller. TP-Link ID Enter an email address to send the invitation email. If the email address is already registered with a TP-Link ID, it will become a valid cloud user account after accepting the invitation. If not, it will be invited for registration, and automatically becomes a valid cloud user account after finishing the registration. Role Select a role for the user account. MSP Administrator: This role has access to most features in MSP View except for some modules. MSP Viewer: This role can view the status and settings of some features. Custom MSP roles: If you have created custom MSP roles, they will be displayed in the list. Customer Privileges Assign the customer permissions to the user account. All: The created user has device permissions of all customers, including all newly created ones. Customer: The created user has device permissions of only the customers you specify.
Customer Role Administrator: Compared with the Customer Main Administrator, Customer Administrators have no permission to some modules in Global View and Site View, mainly including cloud access, migration, auto-backup and global view logs. They have read-only permission to some modules in Global View and Site View, such as license management and custom account roles.Viewer: Customer Viewers can view the status and settings of the network, and change the settings in Hotspot Manager.Custom Customer roles: If you have created custom Customer roles, they will be displayed in the list.
Alert EmailsCheck the box if you want the created user to receive emails about alerts of the privileged customers.

10.3 Manage System Settings

10.3.1 Configure MSP Settings

General Settings

1. In MSP View, go to Settings > MSP Settings. 2. In General Settings, configure the parameters and save the settings. ![](images/8ac4bd7f27ee4ecae553aa6f81e2c94b46410c75817d07d89a29652f42a93002.jpg) MSP Name Specify a name to identify the controller.
Time ZoneSelect the time zone of the controller according to your region. The time of the controller settings and statistics is displayed based on the time zone.
Daylight Saving TimeEnable the feature and configure the parameters if your country/region implement DST.Time Offset: Specify the time added in minutes when Daylight Saving Time starts.Starts On: Specify the time when the DST starts. The clock will be set forward by the time offset you specify.Ends On: Specify the time when the DST ends. The clock will be set back by the time offset you specify.

User Interface

You can customize the User Interface settings of the controller according to your preferences. 1. In MSP View, go to Settings > MSP Settings.

2. In User Interface, configure the parameters and save the settings.

![](images/6b91dd2515d09949f261c2a0417b79b53f6e5976ccf425eac519a6a7de3ea6b2.jpg) Language Select the language to display the user interface.
Use 24-Hour TimeWith Use 24-Hour Time enabled, time is displayed in a 24-hour format. With Use 24-Hour Time disabled, time is displayed in a 12-hour format.
Fixed Menu With Fixed Menu enabled, the menu icons are fixed and do not prompt menu texts when your mouse hovers on them.
Dark Settings When enabled, the system will switch to a dark theme.
Show Pending DevicesWith this option enabled, the devices in Pending status will be shown, and you can determine whether to adopt them. With this option disabled, they will not be shown, thus you cannot adopt any new devices.
Refresh ButtonEnable or disable Refresh Button in the upper right corner of the configuration page.
Refresh IntervalSelect how often the controller automatically refreshes the data displayed on the page.
Enable WebSocket ConnectionWith this function enabled, the controller updates in real time some part of its data on the web interface, which is transmitted using the WebSocket service, so that you don't need to refresh them manually.
Custom Labeling of Controller This option is available on the Cloud-Based Controller. With this function enabled, you can upload your controller labeling and define the redirection URL. Controller Update Notification This option is available on the local controller. With this feature enabled, you will receive an update notification when a new controller version is available.

Configure Remote Logging

With Remote Logging configured, the controller will send generated system logs to a log server. 1. In MSP View, go to Settings > MSP Settings. 2. In Services, enable Remote Logging, configure the parameters and save the settings. Services Remote Logging: ![](images/dda9ec1970beb382c7a6f949c55c5ec791249e34c61693b041f4955a39d5d2c0.jpg) Syslog Server IP/Hostname: ![](images/7faa0ffb635b285540a782b5fc724c5047df32f240a627e7b2d027dfef800172.jpg) Syslog Server Port: 514 (1-65535) Syslog Server IP/Hostname Enter the IP address or hostname of the syslog server. Syslog Server Port Enter the port of the syslog server.

Configure the Mail Server

With the Mail Server, the controller can send emails for resetting your password, pushing notifications, and delivering the system logs. The Mail Server feature works with the SMTP (Simple Mail Transfer Protocol) service provided by an email service provider. 1. Log in to your email account and enable the SMTP (Simple Mail Transfer Protocol) Service. For details, refer to the instructions of your email service provider. 2. In MSP View, go to Settings > Server Settings.

3. In Mail Server, enable SMTP Server and configure the parameters. Then save the settings.

Mail Server

![](images/6308f45a63060c250a60fac34cdb4fb32b7e292f58227f4f4f6ef554e5f3706c.jpg) With the Mail Server, the controller can send emails for resetting your password, pushing notifications, and delivering the system logs. For security reasons, we recommend that you configure Mail Server carefully. SMTP Server: ![](images/cf1e35626ad105054cba025450088a6a83a2db7537dcec9a7e89a4a65db105c2.jpg) Enable SMTP: Port: 465 (1-65535) SSL: ![](images/d54e6bcf7be390681bb42dd35e11a728f3b8a64a42502ecde5bee51d03172740.jpg) Enable Authentication: ![](images/8d450f127799bee24239fe448e26b37573001518b618dc1c9a28ebb378672c97.jpg) Enable Username: Password: Sender Address: Test SMTP Server: ![](images/d785d89c900745223fbce167f1ea87ffc61425b251fe9ba535a9bf9d4d63577c.jpg) ![](images/5ddde7f2fd8474e456573fce282d706f6af28cb59ac4ade907f4c97ddb1a7964.jpg) Send Test Email to Send SMTP Enter the URL or IP address of the SMTP server according to the instructions of the email service provider. Port Configure the port used by the SMTP server according to the instructions of the email service provider. SSL Enable or disable SSL according to the instructions of the email service provider. SSL (Secure Sockets Layer) is used to create an encrypted link between the controller and the SMTP server. Authentication Enable or disable Authentication according to the instructions of the email service provider. If Authentication is enabled, the SMTP server requires the username and password for authentication. Username: Enter your email address as the username. Password: Enter the authentication code as the password, which is provided by the email service provider when you enable the SMTP service. Sender Address Specify the sender address of the email. If you leave it blank, the controller uses your email address as the Sender Address. Test SMTP Server Test the Mail Server configuration by sending a test email to an email address that you specify.

History Data Retention

With History Data Retention, you can specify how the controller retains its data. 1. In MSP View, go to Settings > MSP Settings. 2. In History Data Retention, configure the parameters and save the settings.

History Data Retention

Clients' History Data: ![](images/de1771489add2a86484ab58b607be63a42cdacfee7db08107cd85b47627f7032.jpg) Enable ![](images/6a86016c0916fcc5c220e3f9400fcaa6b1d789d98e106aed0879aa4c5b34a7a7.jpg) When enabled, known clients, client history and client logs will be recorded. This will occupy much storage space. Known Client: 1 Month

Time-Based Settings

![](images/e0e229b513c18c37c9f759bb766012f31aefc5916f3769c02fdc0160b8d508d0.jpg) The settings below will affect the graphical display of Statistics and Network Report. Time Series with 5 Minutes Granularity: 2 Days Time Series with Hourly Granularity: 7 Days Time Series with Daily Granularity: 1 Year Time Series with Weekly Granularity: 6 Months

Others

Portal Authentication Records : 1 Month Wireless IDS: 1 Month Rogue AP: 1 Month Clients' History Data When enabled, known clients, client history and client logs will be recorded. This will occupy much storage space. Known Client Specify the retention time of known client data. Time Series with 5 Minutes Granularity Displays the retention time of AP, switch, gateway, and client data. Corresponding to 5-minute statistics. Time Series with Hourly Granularity Displays the retention time of AP, switch, gateway, and client data. Corresponding to hourly statistics. Time Series with Daily Granularity Specify the retention time of AP, switch, gateway, and client data. Corresponding to daily statistics. Time Series with Weekly Granularity Specify the retention time of client data. Corresponding to weekly statistics. Portal Authentication Records Specify the retention time of portal authorization records. Corresponding to Insight-Past Portal Authorization. Wireless IDS Specify the retention time of wireless IDS data. Rogue AP Specify the retention time of scanned Rogue APs. Corresponding to Insight-Rogue APs.

App-Side Device Notifications (for Cloud-Based Controller)

With App-Side Device Notifications enabled, the Controller will send notifications to the app when your devices go online or offline. 1. Launch the Cloud-Based Controller. In MSP View, go to Settings > MSP Settings. 2. In App-Side Device Notifications, enable the feature and save the settings.

App-Side Device Notifications

![](images/c2a7a5372d807ce6dce501889107ea160c954856506e8c2569f42663016baeef.jpg) With this function enabled, the Controller will send notifications to the app when your devices go online or offline.

10.3.2 Export for Support

You can export configuration data for technical support to diagnose network problems. The exported data will not contain users' personal information. 1. In MSP View, go to Settings > Maintenance. 2. Click Export Configuration Data to save the data file, then you can send it for technical support.

Export for Support

Export configuration data and running logs for technical support to diagnose network problems. The exported data will not contain users' personal information. Export Running Logs Export Configuration Data Export Running Logs This option is available for local controller. Click to export running logs. Export Configuration Data Click to export configuration data.

10.3.3 Export Data

You can export data to monitor or debug your devices. 1. In MSP View, go to Settings > Export Data. 2. Configure the parameters and click Export.

Export Data

Export List: Log List ![](images/e2338681a7b4a642460887f3e4a37f506132581f505739cb8ab8da8c36039719.jpg) Format: XLSX ![](images/90b99751514e3eabb225b8bc486cf76264b8f4fb019b4028761ce070d70afde2.jpg)

Export

Export List Log List: Export the logs generated by the controller. Audit Log List: Export the audit logs generated by the controller. Format The data can be exported to the file in the format of .CSV or .XLSX. ![](images/8055753026cd557e81e11a331571910797fdf167db130168218f3410030cd354.jpg)

Configure Platform Integration

This chapter will introduce how to configure Platform Integration. • 11.1 Open API ![](images/ccda952665b26cfb069c9719fc357199edf1c1f9dd61177e5f119a370b037fd8.jpg)

11.1 Open API

Overview

Omada's Open API supports the REST API of most Controller services. This feature allows Omada users to write custom applications, embed APIs, or combine their own applications. The REST API supports HTTP GET and POST operations by providing specific URLs for each query, and the output of these operations is returned in JSON format. To access the API securely, the Omada API framework supports the OAuth protocol for authentication and authorization, and supports the authorization code mode and client mode. Access Token provides temporary and secure access to the API. For security reasons, Access Token has a limited lifespan. Access Token in authorization code mode uses the refresh API to obtain a new Access Token, and client mode obtains a new token through clientKey and clientSecret.

Configuration

1. In Global View or MSP View, go to Settings > Platform Integration > Open API. 2. Click Add New App. 3. Specify the App name, choose the access mode and configure the parameters.

• Authorization code mode

The authorization code grant type is used to obtain both access tokens and refresh tokens and is optimized for confidential clients. Since this is a redirection-based flow, the client must be capable of interacting with the resource owner's user-agent (typically a web browser) and capable of receiving incoming requests (via redirection) from the authorization server. ![](images/230b3425a0a10346ead52b2684f6b4d31582add46d05d787a34221b8a045092a.jpg) Redirect URL Specify the redirect URL for Oauth2.0 authorization flow.

- Client mode

The client can request an access token using only its client credentials (or other supported means of authentication) when the client is requesting access to the protected resources under its control, or those of another resource owner that have been previously arranged with the authorization server (the method of which is beyond the scope of this specification). ![](images/2fe3631153547af2399cb03b91993b291f072112fbd00405f2e6306a4a2f2db4.jpg) MSP Role Specify the authority MSP role of the client through the Open API. Customer Privileges Specify the customer privileges of the client through the Open API. Applicable Customer When Customer Privileges is set to Customer, select controllable customers. Customer Role Specify the authority customer role of the client through the Open API. 4. Apply the settings. The application will be added for Open API access. ![](images/dbc4e878ab355c27bbbffcd4ca7209ffd773c13c74e3ec82c16c711ec3792223.jpg) You can click API Usage to monitor the API usage. For more instructions, click Online API Document to get the Open API Access Guide.

Appendix 1: Omada APP

Omada app is a mobile application designed for Omada and Omada Pro products. It allows you to conveniently monitor and manage your network. The Omada app can be used for Standalone and Controller mode. This appendix introduces how to use Omada app to manage your network. It includes the following sections: • Install Omada App on the Mobile Device - Manage Your Network in Standalone Mode - Manage Your Network in Controller Mode

1 Install Omada App on the Mobile Device

Omada app runs on iOS and Android devices, such as smart phones and tablets. Launch the Apple App Store (iOS) or Google Play store (Android) and search "TP-Link Omada" or simply scan the QR code to download and install the app. ![](images/70222491c5edf5790f8b3e043ecbf4e74b57b0632f593dde77d5629a5d2e39bc.jpg) Scan for Omada App Download Omada App

2 Manage Your Network in Standalone Mode

For a relatively small-scale network which has a few APs (usually less than three) and only basic functions are required, standalone mode is recommended. You can use a mobile device to configure each AP individually for basic functionality without configuring an SDN Controller. Note that the AP which is managed by the SDN Controller is inaccessible in standalone mode. Refer to the topology below, make sure that the following requirements have been met: - An Ethernet connection from your AP to the LAN with a DHCP server. - The supported firmware version of the AP. To check the firmware versions of the supported APs, please refer to www.tp-link.com/omada\_compatibility\_list. - A compatible iOS or Android device with Omada app. ![](images/15107393c819071f3654b0f1046688f77ad56e6f119fb3c7e1d5bc2080979e06.jpg)
flowchart
graph LR
    A["Internet"] --> B["Router"]
    B --> C["AP"]
    B --> D["AP"]
    C --> E["Omada App"]
    D --> E
Follow the steps below to manage your network via Omada app in standalone mode. The following page is exampled with the iOS version of the app. The Android version is similar. 1. Connect your mobile device to the AP by using the default SSID (format: TP-Link 2.4GHz/5GHz\_XXXXXX) printed on the label. ![](images/9d17389112d77744fb58b21d42a23133d66eb2dc0954e468b616eefd3d78a0f8.jpg) 2. Launch the Omada app, tap Standalone APs and wait for the AP device to be discovered. Pull down to refresh if your devices do not appear. ![](images/e1216d9b663db5aebe36bc9820fffe690a49fe3aee0e8bf39b6c2766c77db906.jpg) ![](images/2f3a7a089d1c159152296e246e04c0fefe9aa3e0fe41bc5d6fdae6dce9c6b573.jpg)

Note:

All the AP devices in the same subnet will be discovered by Omada app and shown on the page. You can tap the discovered AP device to configure directly. 3. Tap on the AP device appearing on the page. Set a new username and password for your login account of the AP. ![](images/dc7d075d452321add4326c5f641608e267b561bc382e2c8d4fdf97d256a12d2c.jpg)

4. Edit the default SSID and password to keep your wireless network secure. Tap Next.

![](images/72491cd7cc7d8a881ade5cfc850ecf2791990dafa767ad8af122e89ee45da9d0.jpg) ![](images/fe7a4f316e87028e384576fcf205b310d66b40c3357f4bbbdc349b2e0fbac957.jpg)

Note:

The settings will take effect after several minutes. For operation system differences, the wireless network connection will be different. When the default SSID of the AP device is changed, normally mobile device join the new wireless network automatically. For the unsupported operation system, you should manually connect to the new SSID. 5. You can view the name of the AP device and other information including wireless parameters and clients. You can tap ☐ to change the settings of radio, SSID and device account. ![](images/1d12215a2353416cd1863b5cf6a1513ec14706527535bbd37c9372290546e02d.jpg) ![](images/f92cfb7e76d54497a1d151ba65094b550938d70cd09498f074e16a9eec276a68.jpg)

Note:

- Omada app is designed to help you quickly configure some basic settings. For advanced configuration, you can use controller mode. And when your AP is managed by the controller, you can not use standalone mode. - In standalone mode, only one user is allowed to log in to the management page of the AP at the same time. Thus the management web page of the AP cannot be logged in to when using the Omada app and vice versa. Also, only one user can log in to the AP via Omada app.

3 Manage Your Network in Controller Mode

For a large-scale network which has routers, switches and mass APs, advanced functions are required, and controller mode is recommended. Controller mode allows you to configure and manage the devices and network in a straightforward and efficient way. Omada app offers a convenient way to access the SDN Controller and adopt devices. With Local Access and Cloud Access function on the Omada app, you can manage the devices both locally and remotely while the controller is running.

3.1 Locally Manage Your Devices Using the Omada App

Local Access function on Omada app is designed for accessing the hardware/software controller which is in the same subnet with your mobile devices. Refer to the topology below, make sure that the following requirements have been met: - An Ethernet connection from your AP to the LAN with a DHCP server. - The version of the SDN Controller is 4.1.5 or above. \- A compatible iOS or Android device with Omada app (iOS: 3.0.28 and above, Android: 3.0.10 and above). ![](images/ed59f2a63abfafb0a88bf97b95a0940bacf9e8d0c16162372b5091e4c3063a7a.jpg)
flowchart
graph TD
    A["Internet"] --> B["Router"]
    B --> C["Switch"]
    C --> D["Software Controller"]
    C --> E["Hardware Controller"]
    C --> F["AP AP"]
    C --> G["AP"]
    D --> H["Mobile Device Installed with Omada App"]
    E --> H
    F --> H
    G --> H
Follow the steps below to manage your network via Omada app in controller mode locally. The following page is exampled with the iOS version of the app. The Android version is similar. 1. Connect your mobile device to the AP by using the default SSID (format: TP-Link 2.4GHz/5GHz\_XXXXXX) printed on the label. Note that the AP should be in the same subnet with the controller. ![](images/f470180bbfc271a959d688dc9ff3714d489f290a5023cd4f6f0f218a493ee6e8.jpg) 2. Launch the Omada app, go to Local Access, tap the + button on the upper-right corner to add the controller. Normally Omada app will discover the controller which is in the same subnet. If the controller cannot be found, you can add the controller by entering the IP address and port of the controller host in the manual column. ![](images/509f0304a0997e90cbc017ead8a4513d13bb6b472e1c3e025a2770869f78410f.jpg) 3. Tap the Controller, the controller login page will show. Enter the username and password of the controller, then tap Log In to launch the controller. ![](images/1b85e18ca0acc0d3b09f6294f6c43f5acc615c6653abf9c828ca0aeacc3b44e2.jpg) 4. On the Devices screen, tap the Device that is pending for the adoption. And you can use the functions at the bottom to navigate various screens of the Controller including the wireless statistics, clients information and basic settings. ![](images/eb64474c6de98f70a873ddb6ba541a811ef3da57d6ee930d425d5b7d1d276d41.jpg)

3.2 Remotely Manage Your Devices Using the Omada App

Cloud Access function on Omada app is designed for accessing the controller via Cloud Service. Thus, you can configure your controller and manage APs at any time, from anywhere.

Hardware/Software Controller

Refer to the topology for hardware/software controller below, make sure that the following requirements have been met: - Both your hardware controller/controller host and mobile device have internet access. • The version of the Controller is 4.1.5 or above. - A compatible iOS or Android device with Omada app (iOS: 3.0.28 and above, Android: 3.0.10 and above). - Cloud Access is enabled on the controller. The controller has been bound with a TP-Link ID. ![](images/012984bf34c2a643d2d948ecb0b0b78fd94361b8364e7e9b38d977924195364d.jpg)
flowchart
graph TD
    A["Mobile Device Installed with Omada App"] --> B["Internet"]
    B --> C["Router"]
    C --> D["Switch"]
    D --> E["Software Controller"]
    D --> F["Hardware Controller"]
    D --> G["AP AP"]
    D --> H["AP"]
    E --> I["Wireless"]
    F --> J["Wireless"]
    G --> K["Wireless"]
    H --> L["Wireless"]
    I --> M["Mobile Device"]
    J --> N["Mobile Device"]
    K --> O["Mobile Device"]
    L --> P["Mobile Device"]
    M --> Q["Client"]
    N --> R["Client"]
    O --> S["Client"]
    P --> T["Client"]
    Q --> U["Client"]
    R --> V["Client"]
Follow the steps below to manage your network via Omada app in controller mode remotely. The following page is exampled with the iOS version of the app. The Android version is similar. 1. Launch the Omada app, go to Cloud Access and tap Go to Log In to log in with your TP-Link ID. ![](images/998a26ddc3b390bae78257ea29a364b30d8d14ed7081105d94d2c615d0f98120.jpg) 2. All the controllers which are bound with your TP-Link ID will appear on the page. - If you want to add a hardware controller, tap + on the upper right, scan its QR code and follow the instructions to add a hardware controller. - If you want to add devices to an existing hardware/software controller, tap the controller to launch the controller. ![](images/d4fbf27ad772d75de60230b98f20a983c4eee7af793f479dffae5a6a90ca6e71.jpg) 3. On the Devices screen, tap the device that is pending for the adoption. And you can use the functions at the bottom to navigate various screens of the Controller including the wireless statistics, clients information and basic settings. ![](images/ec76238d2252505fbafabb65f774b4ab32fc942ecc668ec14e5a6a27320c865e.jpg)

Cloud-Based Controller

Refer to the topology for cloud-based controller below, make sure that the following requirements have been met: - Your mobile device has internet access. - A compatible iOS or Android device with Omada app. - The supported firmware version of the router/switch/AP. ![](images/ed773b307db329f30b5942c83b9b10eafa5ac2c6887ad5d360916b3564c99cde.jpg)
flowchart
graph TD
    A["Mobile Device Installed with Omada App"] --> B["Internet"]
    B --> C["Router"]
    C --> D["Switch"]
    D --> E["AP AP AP"]
    D --> F["AP AP AP"]
    D --> G["AP AP AP"]
    E --> H["Wireless"]
    F --> I["Wireless"]
    G --> J["Wireless"]
    H --> K["Mobile Device"]
    I --> L["Mobile Device"]
    J --> M["Mobile Device"]
    N["Cloud-Based Controller"] --> O["Cloud-Based Controller"]
    P["Clients"] --> Q["Client"]
Follow the steps below to manage your network via Omada app in controller mode remotely. The following page is exampled with the iOS version of the app. The Android version is similar. 1. Launch the Omada app, go to Cloud Access and tap Go to Log In to log in with your TP-Link ID. ![](images/409ae7411510aae179a39d0b1812bbcceef0e0cd21506cb888a7adc827d6204b.jpg) 2. All the online controller which are bound with your TP-Link ID will appear on the page. Tap the cloud-based controller to launch and configure the controller. ![](images/9e4e30d72554488a19d5a2f4780fa1675bebc1917ff101c16a10dffe464716ca.jpg) 3. On the Devices screen, tap the + on the upper right to add devices to your cloud-based controller. You can scan the barcode of the serial number of the device or enter the serial number manually. ![](images/8b5b62675f8f89184ec12ced0b7718d2772fe05c1524300950abdfe04836e46a.jpg) ![](images/ec141ed275b7239703a42c5b4b8148b6826c1d26d8e272ecf4be72c1ad86d076.jpg)

Note:

To successfully add a device to your cloud-based controller, make sure the following requirements are met: - Your device is powered on and connected to the internet. - If the device has been managed by another controller, please forget it on the previous controller and reset it to factory default. 4. On the Devices screen, the newly added device will appear. To manage and configure devices on the cloud-based controller, you need to activate them by assigning available licenses. Tap the device to load the page for device details. ![](images/6509945bff217d81d6f5c0a2ceec904440f11b45776de9874d338d76a712a3e8.jpg) 5. Tab Activate and follow the instructions to assign licenses to the devices. ![](images/f72ccfe2931f642839f7e459484ed582ecb2b8ddbf38d940abd6701d7eb2dd10.jpg) 6. After binding with licenses, the devices can be managed and configured. You can use the functions at the bottom to navigate various screens of the Controller including the wireless statistics, clients information and basic settings. ![](images/9da44370edf693c4d58c205e15a128e687ac98bb996a9f93cc29c6e165b54d15.jpg)
Table of contents Click a title to access it
Manual assistant
Powered by Anthropic
Waiting for your message
Product information

Brand : TP-LINK

Model : Omada SDN Controller

Category : Joystick