Strange RSTP logs

[VanDerTuch]

Hello guys,

i would like to ask for a advice. I have more sites, where are strange RSTP logs and behavior. Network logs showing that more ports are RSTP affected. In three different location. I am 100% sure, that all 3 location are loop free(without loop). One location is very simple. Only MX75 and two switches directy connected to LAN port of MX.(I know about MX does not participiate in STP, but only two switches, so it cannot be problem).

Next location si also without loop. but logs are there. Very often is showing RSTP logs to access port. IS this behavior normal?

What can generate this port RSTP logs??

I dont want to see logs if computer/TV going to sleep or some access port is flapping. If there is not BPDU with combination of MAC address it should not be logged as RSTP....am i wrong?

Thanks for your replies and advice.

[DarrenOC]

Hi @VanDerTuch , I’m afraid what you’re seeing is normal behaviour.  As you’ve already stated this will be PCs, phones etc going to sleep, waking etc

[VanDerTuch]

Maybe yes(I am not sure), because i know that some of this ports are connected to TVs.(not all). But i think, if there is not loop, it should be something like port state from down >> up(port status category). One line. Or more choices if i clik on it. This is very annoying for me to see in every network so many RSTP logs which are more perplexing then helpfull...

[DarrenOC]

Agree, it did take me by surprise many years ago when I started developing Meraki. It doesn’t make for a nice clean event log.

[DarrenOC]

If you run a search for the same issue you’ll see plenty of others with the same gripe.

[VanDerTuch]

Yes, I have seen another posts about it. But there were advice to check topology about loop. So now i am confused, but i think, taht this logs are related to port status, 4 lines about, port going from downt to up, then speed negot, then port designated, and tnen speed to 1 gig....for sure, this is not RSTP log, but port status.....for me is not important access port status....In bigger networks you can see slides of this logs.....

[GreenMan]

When a port with Spanning Tree enabled changes state (comes up / goes down), STP has to decide how to treat it - this is just reflecting that fact.   Maybe select  Port RSTP role change  as an Event type (to) ignore?

[VanDerTuch]

Yes, this is true, but not at full. If we are speaking about some uplink/downlink ports. Then logs are ok. But if we are speaking about Access port? Its normal behavior to have RSTP enabled on ports(by default). Yes, good practise is to have som security like BPDU guard an so on, but in general, i dont think, if switch know about link, that is access an from other site doesnt come BPDU packet, it shout be normal UP/Down state. No topology change/no Root change/ nothing, only state of port.I understand that on backround is some logic about rstp(stp), but from admin point of view is not important proces of STP on access port if there is no blocking state on port.(on access should not be blocking if everyting is ok). In this "standard" logs, in network you have full logs as on picture.

[ReganRunte]

Thank you so much for the suggestion, By the way, I am new here, can I ask a question?