Hi,
We have a recurring issue with Spanning Tree on our network that we desperately need to address. We Run a Layer2 Service Provider network and we continually have issues with Spanning Tree when connecting to customers at the Edge and also running on the network. We would like to filter out spanning tree TOTALLY from our environment if possible.
We run a mix of RouterOS v7 and v6 devices and need to know the best way to do this. As a note, most of our customers run Cisco Layer3 switches on the Edge to connect to us, but as I indicated earlier we would just like to get rid of STP as a whole running on our network. What would be the best way to achieve this?
Cheers!
Give us some clues! What’s not working about the usual ways? Is this actually about STP or is your problem with PVST running across your domain?
Essentially we are attempting to deploy a new connection to a client, when we attempt this we see no traffic. After taking a packet capture we see a great deal of STP traffic between our network and their CISCO device. In the past when we have seen this we request the client kill STP at their end and this normally sorts it out, but this time it hasn’t…
And you are correct, when we say STP we mean STP, PVST and all other STP variants… What I can say is that the capture did not show the traffic as PVST but as plain STP…
By “lots of traffic” I assume you mean that your devices answer. With edge=yes and not enabling forward-restricted, your side shouldn’t send bpdus.
Pvst doesn’t use ieee restricted addressing (on purpose,) so blocking it has to happen separately.
Thanks 
we will try that after operating hours and let you know what we see. I will execute it on our network edge device which is directly connecting to the customer and see what happens…
Cheers!
maybe also you may want to drop incoming STP from client
Drop received BPDUs
Literally the preceding sentence:
Setting a bridge port as an edge port will restrict it from sending BPDUs and will ignore any received BPDUs: