How to configure MSTP on L2 Managed switches using the new GUI

T1600G-18TS( V2 ) , T1500G-10PS( V2 ) , T1600G-28TS( V3 ) , T2600G-52TS( V3 ) , T1500-28PCT( V3 ) , T2600G-28TS( V3 ) , T1600G-28PS( V3 ) , T2500G-10TS( V2 ) , T2600G-28MPS , T1500G-10MPS( V3 ) , T1600G-52PS( V3 ) , T1500G-8T( V2 ) , T1600G-52TS( 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.
MSTP (Multiple Spanning Tree Protocol) is the extension of STP and RSTP. In STP and RSTP, once a link is blocked, all traffic are not allowed to transmit through this link. This will cause load imbalance, because other links have to take on more traffic. To solve this problem, MSTP appears.
MSTP blocks ports based on VLAN. For example, port 1 belongs to VLAN 1 and VLAN 2. MSTP may block port 1 in VLAN 1, but still keep port 1 up in VLAN 2. Thus, port 1 is not completely blocked and still can forward the packets from VLAN 2.
Here is an example for MSTP. As the figure shows below, the network consists of three switches. Traffic in VLAN 101-VLAN 106 is transmitted in this network. The link speed between the switches is 100Mb/s (this means the default path cost of the port is 200000). It is required that traffic in VLAN 101-VLAN 103 and traffic in VLAN 104-VLAN 106 should be transmitted along different paths.
Configuration Scheme:
We can configure MSTP to meet the requirement. By configuring MSTP, you can manually design two different links for VLAN 101-VLAN 103 and VLAN 104-VLAN 106. To achieve this goal, we need to create two instances and map them to VLAN 101-VLAN 103 and VLAN 104-VLAN 106 respectively. Then in each instance, manually designate the root switch and specify the path cost for each port so that we can decide which port would be blocked.
The figure below shows the paths we design for the VLANs. We create instance 1 and instance 2, and map them to VLAN101-VLAN103 and VLAN 104-VLAN 106 respectively. In instance 1, we will block port 1/0/2 on switch A; in instance 2, we will block port 1/0/1 on switch B. Thus the traffic in VLAN 101-VLAN 103 and VLAN 104-VLAN 106 will be transmitted through different paths.
The overview of configuration is as follows:
- Enable MSTP globally on each switch. Enable spanning tree on the corresponding ports.
- Configure Switch A, Switch B and Switch C in the same region. Configure the region name as 1, and the revision level as 100. Map VLAN 101-VLAN 103 to instance 1 and VLAN 104-VLAN 106 to instance 2.
- Configure the priority of Switch B as 4096 to set it as the root bridge in instance 1; configure the priority of Switch C as 4096 to set it as the root bridge in instance 2.
- Configure the path cost to block the specified ports. For instance 1, set the path cost of port 1/0/1 of Switch A to be greater than the default path cost (200000); for instance 2, set the path cost of port 1/0/2 of Switch B to be greater than the default path cost (200000). After this configuration, port 1/0/2 of Switch A in instance 1 and port 1/0/1 of Switch B in instance 2 will be blocked for they cannot be neither root port nor designated port.
Note:
Please configure MSTP for each switch first and then connect them together to avoid broadcast storm.
Configuring Switch A:
- Go to L2 FEATURES > Spanning Tree > STP Config > STP Config page. Enable MSTP function globally. Here we leave the other global parameters as default settings.
- Go to L2 FEATURES > Spanning Tree > STP Config > Port Config page. Enable spanning tree function on port 1/0/1 and port 1/0/2. Leave the other parameters as default settings.
- Go to L2 FEATURES > Spanning Tree > MSTP Instance > Region Config page. Set the region name as 1 and the revision level as 100.
- Go to L2 FEATURES > Spanning Tree > MSTP Instance > Instance Config page. Map VLAN101-VLAN103 to instance 1 and set the priority as 32768; map VLAN104-VLAN106 to instance 2 and set the priority as 32768.
5. Go to L2 FEATURES > Spanning Tree > MSTP Instance > Instance Port Config page. Set the path cost of port 1/0/1 in instance 1 as 300000 so that port 1/0/1 of switch C can be selected as the designated port.
Configuring Switch B:
- Go to L2 FEATURES > Spanning Tree > STP Config > STP Config page. Enable MSTP function globally. Leave the other global parameters as default settings.
- Go to L2 FEATURES > Spanning Tree > STP Config > Port Config page. Enable spanning tree function on port 1/0/1 and port 1/0/2. Leave the other parameters as default settings.
- Go to L2 FEATURES > Spanning Tree > MSTP Instance > Region Config page. Set the region name as 1 and the revision level as 100.
- Go to L2 FEATURES > Spanning Tree > MSTP Instance > Instance Config page. Map VLAN101-VLAN103 to instance 1 and set the priority as 4096; map VLAN104-VLAN106 to instance 2 and set the priority as 32768.
- Go to L2 FEATURES > Spanning Tree > MSTP Instance > Instance Port Config page. Set the path cost of port 1/0/2 in instance 2 as 300000 so that port 1/0/1 of switch A can be selected as the designated port.
Configuring Switch C:
- Go to L2 FEATURES > Spanning Tree > STP Config > STP Config page. Enable MSTP function globally. Leave the other global parameters as default settings.
- Go to L2 FEATURES > Spanning Tree > STP Config > Port Config page. Enable spanning tree function on port 1/0/1 and port 1/0/2. Leave the other parameters as default settings.
- Go to L2 FEATURES > Spanning Tree > MSTP Instance > Region Config page. Set the region name as 1 and the revision level as 100.
- Go to L2 FEATURES > Spanning Tree > MSTP Instance > Instance Config page. Map VLAN101-VLAN103 to instance 1 and set the priority as 32768; map VLAN104-VLAN106 to instance 2 and set the priority as 4096.
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.
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
Standaard Cookies
Deze cookies zijn noodzakelijk voor de werking van de website en kunnen niet worden uitgeschakeld.
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
Live-Chat
__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
Analyse en Marketing Cookies
Cookies voor analyse geven ons de mogelijkheid uw activiteiten op onze website te volgen en zo de functionaliteit van de website aan te passen en te verbeteren.
Marketing cookies kunnen op onze website worden geplaatst door externe adverteerders waar wij mee samenwerken om een profiel te creëren met uw interesses en u zo van relevante advertenties te kunnen voorzien op andere 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