How to use CPEs to build up a LAG (Link Aggregation) tunnel
CPE510 , CPE610 , CPE710 , CPE220 , CPE210 , CPE605
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.
User’s Application Scenario
With the LAG (Link Aggregation Group) function, you can aggregate multiple physical ports into a logical interface. Typical LAG setups use Ethernet cables as physical tunnels. In practice, you can also use CPEs to build point-to-point links as LAG tunnels, just as the topology shown as follows.
Configuration
Step 1. Config CPEs.
In this step, you will set up the four CPEs to establish two point-to-point wireless links. For each pair of CPEs, one should be set to Access Point and another in Client mode. For example, set CPE-A1 to AP mode and CPE-A2 to Client mode. The same thing for CPE-B1 and CPE-B2.
For CPE setup (pairing) instructions, refer to: quick_start_guide_cpe_and_wbs_ (tp-link.com).
(Optional) You can set different static IPs for each of your CPEs for management convenience. Go to CPE’s Web UI -->Network -->LAN Settings -->IP Address to set it manually. However, leaving them to default value (192.168.0.254) is also OK.
Note: Do NOT connect both CPEs to switches BEFORE setting up LAG (Step 2) to avoid loop problem.
Step 2. Set Static LAG on switches.
There are two modes of LAG: Static LAG and Dynamic LAG (LACP). In this case, we should use Static LAG because LACP mode may cause a broadcast storm in this scenario.
Create a Static LAG group of two ports on both Switch-1 and Switch-2.LAG setup instructions:
For easy smart switches, go to the switch’s Web UI -->Switching -->LAG.
For Smart/Managed switches, refer to: configuring_lag (tp-link.com).
For Omada Controller managed devices, refer to: Omada SDN Controller User Guide | TP-Link Chapter 6.3.1 – Configure Switches – Configure a LAG.
Note: While using Omada Controller to set LAG on switches for CPEs to connect, please make sure that the Link Speed is at ‘Auto’ mode.
Unmanaged switches do not support LAG.
Step 3. Connect CPEs to switches.
Connect the CPEs to the switches’ LAG ports respectively, as shown in the topology. Now the setup is done, you may need to wait a few seconds before the client gets network access.
Note:
If one CPE is down and the other three work fine, the network will still be unavailable. For example, if CPE-A1 is down, Switch-2 will lose connection to Switch-1, since the logic connection between switch 2 and CPE-A2 is still up and the switch may still transfer the data to CPE-A2.
ONLY when a pair of CPEs are down at the same time could the LAG strategy use another pair for backup. So use CPEs to build up a LAG tunnel may increase the wireless bandwidth but the connection may not stable in some situations.
Get to know more details of each function and configuration, please go to Download Center to download the manual of your product.
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
We'd love to get your feedback, please let us know how we can improve this content.
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.
We have updated our Policies. Read Privacy Policy and Terms of Use here.
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 .
We have updated our Policies. Read Privacy Policy and Terms of Use here.
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 .
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
Hotjar
OptanonConsent, _sctr, _cs_s, _hjFirstSeen, _hjAbsoluteSessionInProgress, _hjSessionUser_14, _fbp, ajs_anonymous_id, _hjSessionUser_<hotjar-id>, _uetsid, _schn, _uetvid, NEXT_LOCALE, _hjSession_14, _hjid, _cs_c, _scid, _hjAbsoluteSessionInProgress, _cs_id, _gcl_au, _ga, _gid, _hjIncludedInPageviewSample, _hjSession_<hotjar-id>, _hjIncludedInSessionSample_<hotjar-id>
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or