STP BPDU Drop

[cback85]

I am really new to STP on Extreme switches but I am seeing this error fill the logs. They are connected up to core Cisco switches I believe using PVST+ between the switches. 

01/27/2021 18:38:31.41 <Erro:STP.InBPDU.Drop> Port=10: No associated STP port for STP Domain tag 1 (Rate-limited)
01/27/2021 18:36:31.41 <Erro:STP.InBPDU.Drop> Previous message repeated 10 additional times in the last 108 second(s)
 

[Tomasz]

Hi Robert,

What’s the network topology?

Just food for thoughts: if the network doesn’t have any redundant connections that could be dealt using STP/LACP/MLAG/EAPS and you only aim to save access ports from loops I’d consider ELRP. Recently they’ve added some hardware assist to it so it can be even as low as 3ms of loop detection interval.

Hope that helps,

Tomasz

[RobertWilkinson]

Does anyone have any other thoughts on how to restrict BPDU’s from coming into the network other than disabling STP?

I understand how disabling STP will work and i understand the ELRP feature being used instead of STP however i have a customer who does not currently have ELRP configured on any of the switches (there are about 137 of them) and i don’t want to adopt something i have not tested myself.

I’ve seen old cases on here from around 7 years ago regarding applying an ACL on ingress to the port with a counter but was also wondering is that still a valid means (mainly because its not clear on a port that an ACL is applied so unless you go looking for it then you will never see it).

What about using the TCN Restrict feature within STP?

[cback85]

Unfortunately I can’t send you the config as it was for a customer but yes the issue is solved removing STP and using ELRP instead on the Extremes. Still got the BPDU error but like I said we just did a log filter. 

[DeoHeo]

Is the issue solved for you? If not can you send me the VLAN configuration of the EXOS switch? The VLAN 1 configuration is enough.