Home » TP-Link Manuals » Networking » TP-Link OC200 » Manual Viewer

TP-Link OC200 Omada Controller Software 4.1.5Windows/Linux User Guide - Page 36

Controller Inform URL, Discovery Utility, DHCP Option 138, SYSTEM, Controller Settings

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

Page 36 highlights

Chapter 3 Manage Omada Managed Devices and Sites 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. 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/ 34

Section	Page
About this Guide	2
Omada SDN Controller Solution Overview	3
Overview of Omada SDN Controller Solution	4
Core Components	5
Get Started with Omada SDN Controller	10
Set Up Your Software Controller	11
Determine the Network Topology	11
Install Omada Software Controller	12
Start and Log In to the Omada Software Controller	14
Set Up Your Hardware Controller	19
Determine the Network Topology	19
Deploy Omada Hardware Controller	19
Start and Log in to the Controller	20
Set up Your Cloud-Based Controller	24
Manage Omada Managed Devices and Sites	25
Create Sites	26
Adopt Devices	30
For Omada Software Controller / Omada Hardware Controller	30
For Omada Cloud-Based Controller	42
Configure the Network with Omada SDN Controller	45
Navigate the UI	46
Modify the Current Site Configuration	49
Site Configuration	49
Services	49
Advanced Features	52
Device Account	54
Configure Wired Networks	55
Set Up an Internet Connection	55
Configure LAN Networks	69
Configure Wireless Networks	78
Set Up Basic Wireless Networks	78
Advanced Settings	84
WLAN Schedule	86
802.11 Rate Control	86
MAC Filter	87
Network Security	89
ACL	89
URL Filtering	97
Attack Defense	100
Transmission	105
Routing	105
NAT	108
Session Limit	111
Bandwidth Control	112
Configure VPN	116
Create Profiles	143
Time Range	143
Groups	144
Authentication	149
Portal	149
802.1X	180
MAC-Based Authentication	183
RADIUS Profile	184
Services	187
Dynamic DNS	187
SNMP	189
UPnP	190
SSH	191
Reboot Schedule	191
PoE Schedule	192
Export Data	193
Configure the Omada SDN Controller	195
Manage the Controller	196
General Settings	196
Mail Server	197
History Data Retention	199
Customer Experience Improvement Program	199
HTTPS Certificate	200
Access Port Config	200
Manage Your Controller Remotely via Cloud Access	202
Maintenance	204
Controller Status	204
User Interface	204
Backup & Restore	206
Migration	207
Site Migration	207
Controller Migration	212
Configure and Monitor Omada Managed Devices	219
Introduction to the Devices Page	220
Configure and Monitor the Gateway	224
Configure the Gateway	224
Monitor the Gateway	228
Configure and Monitor Switches	232
Configure Switches	232
Monitor Switches	249
Configure and Monitor EAPs	253
Configure EAPs	253
Monitor EAPs	263
Monitor and Manage the Clients	270
Manage Wired and Wireless Clients in Clients Page	271
Introduction to Clients Page	271
Using the Clients Table to Monitor and Manage the Clients	271
Using the Properties Window to Monitor and Manage the Clients	273
Manage Client Authentication in Hotspot Manager	278
Authorized Clients	278
Vouchers	278
Local Users	281
Operators	284
Monitor the Network	287
View the Status of Network with Dashboard	288
Page Layout of Dashboard	288
Explanation of Widgets	290
View the Statistics of the Network	298
Performance	298
Switch Statistics	301
Speed Test Statistics	303
Monitor the Network with Map	305
Topology	305
Map	307
View the Statistics During Specified Period with Insight	310
Known Clients	310
Past Portal Authorizations	311
Rogue APs	312
View and Manage Logs	314
Alerts	315
Events	316
Notifications	317
Manage Administrator Accounts of Omada SDN Controller	323
Introduction to User Accounts	324
Manage and Create Local User Accounts	325
Edit the Master Administrator Account	325
Create and Manage Administrator and Viewer	327
Manage and Create Cloud User Accounts	330
Set Up the Cloud Master Administrator	330

Match case Limit results 1 per page

Chapter 3

Manage Omada Managed Devices and Sites

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

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/