How to configure 802.1Q VLAN for LAG ports on Smart and Managed switches using the new GUI

T1600G-18TS( V2 ) , T1500G-10PS( V2 ) , T1600G-28TS( V3 ) , T1700G-28TQ( V3 ) , T2600G-52TS( V3 ) , T2600G-18TS( V2 ) , T1500-28PCT( V3 ) , T2600G-28TS( V3 V4 ) , T2600G-28SQ( V1 ) , T1600G-28PS( V3 ) , T2500G-10TS( V2 ) , T2700G-28TQ( V3 ) , T1500G-10MPS( V2 ) , T2600G-28MPS( V3 V4 ) , T1600G-52PS( V3 V4 ) , T1500G-8T( V2 ) , T1600G-52TS( V3 V4 ) , T1700X-16TS( V3 )
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device, and check either the Datasheet or the firmware section for the latest improvements added to your product. Please note that product availability varies by region, and certain models may not be available in your region.
VLAN (Virtual Local Area Network) is a technology that can modify the broadcasting domain. A LAN can be divided into several VLANs logically, and only the hosts in the same VLAN can communicate with each other.
LAG (Link Aggregation Group) is a technology that can aggregate multiple physical ports into a logical interface, increasing link bandwidth and providing backup ports to enhance the connection reliability.
Sometimes, we may encounter the application that needs to use these two technologies at the same time; here is a configuration example.
Network Topology:
Network Requirement:
- Users need to improve the bandwidth and redundancy of the link between the switches.
- Hosts in different departments cannot communicate with each other; all hosts can access the internet.
- Both department A and department B can access the internet.
Configuration Scheme:
- Create static LAG1 and LAG2 on switch A, and create static LAG for switch B and switch C respectively.
- Create VLAN 10 and VLAN 20 for department A and department B respectively.
- Create VLAN 30 for the internet, and add the hosts in department A and department B to VLAN 30.
- Configure PVIDs for ports. With correct PVID settings, both department A and department B can access the internet, but cannot communicate with each other.
LAG Configurations on Switch A, Switch B, and Switch C:
|
LAG1 |
LAG2 |
Switch A |
Port 1,2 |
Port 3,4 |
Switch B |
Port 3,4 |
|
Switch C |
Port 1,2 |
|
VLAN Configurations on Switch A:
|
VLAN 10 |
VLAN 20 |
VLAN 30 |
Switch A |
LAG1, port 5 |
LAG2, port 5 |
LAG1, LAG2, Port 5 |
Egress Rule and PVID settings for Switch A:
Switch |
Switch A |
||
Port |
LAG1 |
LAG2 |
5 |
Egress Rule |
Untagged |
Untagged |
Untagged |
PVID |
10 |
20 |
30 |
Configurations on Switch A:
Step 1
Go to L2 Features > Switching > LAG > Static LAG, select Group ID as LAG1, select Port 1 and Port 2, click Apply; choose then Group ID as LAG2, and select Port 3 and Port 4, click Apply.
Then verify the LAGs on the LAG Table page.
Step 2
Go to L2 Features > VLAN > 802.1Q VLAN > VLAN Config, create VLAN 10, VLAN 20 and VLAN 30; add Untagged port LAG1 to VLAN 10; add Untagged port LAG2 to VLAN 20; add Untagged port LAG1, LAG2, and port5 to VLAN 30.
Note: When adding ports to VLAN 30, as VLAN 30 including LAG ports and general port, please click UNIT 1 to select general port 5 and then click LAGS to select LAG port 1and LAG port 2.
Then verify the VLANs on VLAN Config page.
Step 3
Go to L2 Features > VLAN > 802.1Q VLAN > Port Config, set the PVID value as 10, 20, 30 for LAG 1, port 2 and port 3 respectively.
Click LAGS in Port Config page and then set the PVID value as 10, 20 for LAG1 and LAG2.
Click UNIT1 in Port Config page and then set the PVID value as 30 for port 5.
Configurations on Switch B:
Only one step, go to L2 Features > Switching > LAG > Static LAG, select Group ID as LAG1, select Port 3 and Port 4, click Apply.
Configurations on Switch C:
Only one step, go to L2 Features > Switching > LAG > Static LAG, select Group ID as LAG1, select Port 1 and Port 2, click Apply.
Is this faq useful?
Your feedback helps improve this site.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.

TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy . Don’t show again
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy . Don’t show again
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Livechat
__livechat, __lc2_cid, __lc2_cst, __lc_cid, __lc_cst, CASID
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Analysis and Marketing Cookies
Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.
The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au
Meta Pixel
_fbp
Crazy Egg
cebsp_, _ce.s, _ce.clock_data, _ce.clock_event, cebs
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or