TP-Link Spanning Tree (RSTP) config

TP-Link Spanning Tree (RSTP) config

TP-Link Spanning Tree (RSTP) config
TP-Link Spanning Tree (RSTP) config
2025-08-01 21:46:49 - last edited 2025-08-05 03:38:30
Model: TL-SG3428  
Hardware Version:
Firmware Version:

Hi!

I have four SG3428 TP-Link switches. I am configuring the RSTP protocol on these devices.

I found that the “STP” option can be enabled globally and also on a per-port basis.

Could you please tell me what the “STP: Enable/Disable” option for each port configured as “EDGE” is for?

Does this option have any real impact on the functions of the switch?

 

  0      
  0      
#1
Options
1 Accepted Solution
Re:TP-Link Spanning Tree (RSTP) config-Solution
2025-08-05 03:37:48 - last edited 2025-08-05 03:38:51

  @gawkla 

gawkla wrote

I have run some tests and it appears that both options are working well. Even if the STP tree was changed, the two devices can continuously ping each other without loosing even one ping. Therefore, Edge=Enabled (portfast) seems to be sufficient for configuring an edge port. Isn't it?

STP enabled, and Edge enabled, should be the proper syntax we look for if you ask me about it. 

You can also try the commands to output the STP status. 

STP enabled is a global setting. We usually require a port-level config to enable/disable a function per port.

So, I think it is necessary. 

Recommended Solution
  2  
  2  
#11
Options
10 Reply
Re:TP-Link Spanning Tree (RSTP) config
2025-08-02 08:22:38 - last edited 2025-08-02 08:24:25

  @gawkla 

 

The following link may answer your questions and give you some guidance.

 

1x ER706W 1x OC300 4x SG2008 1x EAP610 2x EAP650
  0  
  0  
#2
Options
Re:TP-Link Spanning Tree (RSTP) config
2025-08-02 13:27:03

I read this article, but I couldn't find the answer to my question.

  0  
  0  
#3
Options
Re:TP-Link Spanning Tree (RSTP) config
2025-08-02 15:20:46

  @gawkla 

 

I found another article on the subject but it too will probably not answer your question.

 

In taking another look at your initial post, it appears that the switch is standalone mode as that screen is not available when using a controller.  In that case, if there is a global STP setting, it probably enables STP on the switch.  Then each port can have STP enabled or disabled, depending on whether it is being used as an access port or trunk port.  Otherwise, the switch has no way of knowing what the port is used for.  The fifth paragraph in the article gives some info on the reasons for enabling/disabling.

 

Perhaps someone from Tp-LInk can share some more information on this.

 

 

1x ER706W 1x OC300 4x SG2008 1x EAP610 2x EAP650
  0  
  0  
#4
Options
Re:TP-Link Spanning Tree (RSTP) config
2025-08-02 15:44:02
In my opinion, the 'function' of the port is defined by 'edge: disable/enable [portfast]' and 'P2Link' (closed/open/auto). I am trying to understand what the additional STP enable/disable per port is used for.
  0  
  0  
#5
Options
Re:TP-Link Spanning Tree (RSTP) config
2025-08-04 01:39:01

  @gawkla 

gawkla wrote

In my opinion, the 'function' of the port is defined by 'edge: disable/enable [portfast]' and 'P2Link' (closed/open/auto). I am trying to understand what the additional STP enable/disable per port is used for.

In your original post, I see you are looking for the explanation of the "edge". 

So, are you trying to understand the whole concept of the STP?

Or you want to figure out the single term "edge"?

 

For both, you can refer to the general Wikipedia for help and explanation. These are industrial standards and terminology. 

  1  
  1  
#6
Options
Re:TP-Link Spanning Tree (RSTP) config
2025-08-04 15:10:13

  @gawkla

 

 

Edge port is the TP-Link equivalent of Cisco’s spanning-tree portfast.
It tells the switch that the port is connected to a non-switching device (like a PC or printer), allowing it to immediately enter the forwarding state by skipping the usual STP listening and learning phases.

 

BPDU Guard should be enabled alongside Edge Port as a best practice to protect the network by shutting down the port if any BPDU packets are received, preventing potential loops caused by unauthorized switches.

With  the  BPDU  protect  function  enabled,  the  port  will  set itself  automatically  as  ERROR-PORT when  it  receives BPDU  packets,  and the port  willdisable  the  forwarding function  for  a  while. 

  0  
  0  
#7
Options
Re:TP-Link Spanning Tree (RSTP) config
2025-08-04 19:23:11

  @gawkla 

 

I understand what an edge port is. My question was about enabling/disabling STP for each edge port at the port level.

Perhaps I should ask my question differently. Please see the attached pictures. Option 1 and Option 2. Which one is correct? What will happen if I set the port as 'Edge=Enabled' but 'Disable' STP Status?

 

 

 

 

 

 

  1  
  1  
#8
Options
Re:TP-Link Spanning Tree (RSTP) config
2025-08-04 19:32:38
For option 1) command is accepted and applied, but it has no functional effect, because STP isn't running in the first place Option 2) works fine you can easily test with pc and wireshark both options
  1  
  1  
#9
Options
Re:TP-Link Spanning Tree (RSTP) config
2025-08-04 19:45:26
I have run some tests and it appears that both options are working well. Even if the STP tree was changed, the two devices can continuously ping each other without loosing even one ping. Therefore, Edge=Enabled (portfast) seems to be sufficient for configuring an edge port. Isn't it?
  1  
  1  
#10
Options
Re:TP-Link Spanning Tree (RSTP) config-Solution
2025-08-05 03:37:48 - last edited 2025-08-05 03:38:51

  @gawkla 

gawkla wrote

I have run some tests and it appears that both options are working well. Even if the STP tree was changed, the two devices can continuously ping each other without loosing even one ping. Therefore, Edge=Enabled (portfast) seems to be sufficient for configuring an edge port. Isn't it?

STP enabled, and Edge enabled, should be the proper syntax we look for if you ask me about it. 

You can also try the commands to output the STP status. 

STP enabled is a global setting. We usually require a port-level config to enable/disable a function per port.

So, I think it is necessary. 

Recommended Solution
  2  
  2  
#11
Options