How to Configure Load Balance Function on TP-Link CAP/AC Serial Products

AC500( V1 ) , AC50( V1 ) , CAP300-Outdoor( V1 ) , CAP1750( V1 ) , CAP1200( V1 ) , CAP300( V1 )
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.
Load Balance is to avoid a single CAP to have too many clients while other CAPs are idle. In the topology below, we have CAP A and CAP B, because of the random distribution of wireless clients, there may be too many clients connected with one single CAP (like CAP A). At this time, we want to “Balance” and “Guide” newly-added client to connect to CAP B.
This document will introduce how to configure load balance function on TP-Link CAP/AC serial product with one configuration instance based on the topology above to achieve load balance between CAP A and CAP B.
Based on the topology above: we can see that
- A newly added client is within the wireless coverage area of CAP A and CAP B.
- CAP A is almost overloaded with 20 clients connected, while CAP B is idle with only 3 clients connected.
- At this time, we want this newly added client to connect to CAP B only.
Here are the configuration methods of Load Balance function on TP-Link AC serial product:
Explanations:
- Threshold means the “maximum number of clients for each CAP” before Load Balance function is triggered. In this instance, we set it as “20”, which means each CAP can have 20 clients at most before Load Balance function is triggered. Here CAP A already reaches this limitation (20 clients). In other words, CAP A already has too many clients so that Load Balance function may be effective to guide newly-added client to connect to other CAPs.
- Difference Threshold means the “minimum client number difference among adjacent CAPs” before Load Balance function is triggered. In this instance, we set it as “4”, and the client number difference between CAP A and CAP B is 17 which is larger than this difference threshold. In other words, CAP B has much fewer clients than CAP A, which means CAP B is idler than CAP A. In this situation, Load Balance function may be effective to guide newly-added client to connect to CAP B.
In a word, if Threshold and Difference Threshold are both satisfied, it means some CAP is almost overloaded while some other CAP is idle. At this time, Load Balance function will be effective, and guide newly-added clients to connect to idle CAPs with less clients.
Exceptions:
- If newly-added client failed to get connected with CAP B for 10 times (Maximum Fail Number), CAP A will accept this newly-added client’s connection request even though it already has many clients and Load Balance function is already effective.
- If newly-added client’s signal strength (RSSI) is less than “RSSI Threshold”, CAP A will not refuse this client’s connection request, which means Load Balance function is meaningless for client with signal strength less than “RSSI Threshold”.
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 .
Your Privacy Choices
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
SESSION, JSESSIONID, accepted_local_switcher, tp_privacy_banner, tp_privacy_base, tp_privacy_marketing, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
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
Zendesk
OptanonConsent, __cf_bm, __cfruid, _cfuvid, _help_center_session, _pendo___sg__.<container-id>, _pendo_meta.<container-id>, _pendo_visitorId.<container-id>, _zendesk_authenticated, _zendesk_cookie, _zendesk_session, _zendesk_shared_session, ajs_anonymous_id, cf_clearance
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