Initial setup of VLAN on switch using OC200, VLAN setup on access point and VLAN setup using mesh AP

When using a router from another company
VLAN11 192.168.11.0/24 Family
VLAN12 192.168.12.0/24 Sound
VLAN13 192.168.13.0/24 Guest
VLAN19 192.168.19.0/24 System Management
VLAN19 is used to manage the entire network device and is mainly used to synchronize the switch, router, and access point.
The router is the DHCP server.
All access points are trying to broadcast the SSID of each of VLAN11 to 13. So I would like to ask how to set it up as follows
1.
VLAN setting procedure for Port1 and 17 of OC200 controller and SG3218XP-M2 switch from the initial state
Also, setting the Management VLAN of the controller and switch
2.
Mesh connection of EAP772 (B) with EAP772 (A). Setting the Switch Profile to assign to Port 2 when the switch with EAP772 (B) connected by wire is grouped as VLAN12
3.
Setting the Switch Profile to assign to Port 3 when the PC connected to EAP655-WE is grouped as VLAN11
If the port is only used to connect an access point, I think it is fine to assign all VLAN IDs to the Tag Network and set the Native Network to 19
Thank you for your help.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content

Hi @Mt.Faith
If the port is only used to connect an access point, I think it is fine to assign all VLAN IDs to the Tag Network and set the Native Network to 19
>>>Yes, this is fine.
Below is a guide on how to configure management VLAN for Omada controller, and for your scenario, please refer to topology 2
How to configure Management VLAN in Omada SDN Controller (4.4.4 or above)
- Copy Link
- Report Inappropriate Content
You will have to add these vlans on the controller, as "switch only" vlans. That way you will be able to set up port profiles and add whatever vlans you want either native or tagged to your switch ports.
There is no way to set a port otherwise without the controller knowing about netowrks / vlans.
Since you have a non omada router, there is no need to set them as "interface" since DHCP and IP settings are taken care of on the router and anything you set for those in omada wont take effect. Switch-only is fine in this case.
- Copy Link
- Report Inappropriate Content

Hi @Mt.Faith
If the port is only used to connect an access point, I think it is fine to assign all VLAN IDs to the Tag Network and set the Native Network to 19
>>>Yes, this is fine.
Below is a guide on how to configure management VLAN for Omada controller, and for your scenario, please refer to topology 2
How to configure Management VLAN in Omada SDN Controller (4.4.4 or above)
- Copy Link
- Report Inappropriate Content
Here is one more guide on How to configure SSID VLAN on Omada AP with Third-Party Gateway, this may also help you.
- Copy Link
- Report Inappropriate Content
when you not have a to link gateway (router) than you have to set on your 3rd party router a static ip for your switch and create static routing for each vlan/network assigned to the one static ip for the switch
here I have described a setup with a fritzbox as router/modem
https://community.tp-link.com/en/business/forum/topic/572730
- Copy Link
- Report Inappropriate Content
Thank you
@Vincent-TP and @GRL
For now, regarding question 1
Setting the necessary VLANs
Set the necessary VLANs from Setting > Wired&Wireless Networks > LAN >
Networks in the site. If you don't have a TP-Link router, set the Purpose setting to VLAN instead of Interface
Setting the Switch Profile
Create a group of VLANs to assign to the port here. PVID is created in Native Network. It seems that the VLAN assigned to Native Network will always be Untag
Assign VLAN to port
Change Management VLAN
Replace LAN cable
I was able to solve the problem
As for question 2, if I set the port of the switch connected to the mesh to tag VLAN12, the terminal under the switch could be put into the VLAN12 group
Question 3 was solved because the EAP655-WE had a VLAN setting in the Config to assign to the front port.
Apart from the above three questions, is it possible to set the VLAN set in Native Network to Tag Vlan? Specifically,
Tag: 11-19
Untag: None
Native Network: 12
When I try to change the settings, it seems that the VLAN ID set in the Native Network is forced to be Untag. With a standalone switch, I was able to change the VLAN ID set in the PVID to Tag VLAN, so I thought I could do it with the controller on the following switches, but is that possible?
- Copy Link
- Report Inappropriate Content
Hi @Mt.Faith
Thanks for your sharing and glad to hear that you had configured your network as you want.
As for the latest question,
is it possible to set the VLAN set in Native Network to Tag Vlan?
>>>We can't change the native VLAN to tagged on the controller.
The Controller is designed for global management of all devices in the network, which involves simplifying certain network configuration logics.
The Native VLAN being fixed as Untagged was implemented based on these considerations.
If you can change the Native VLAN to tagged, even a minor misconfiguration could render the Controller unable to manage the devices. In such cases, the only recovery method would be to reset all devices to restore management access.
Thanks for your understanding.
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 401
Replies: 6
Voters 0
No one has voted for it yet.