MS - Undocumented change about Spanning-Tree log behavior on switch stacks

[RaphaelL]

Hi ,

We recently upgraded from MS 14 to MS 17 and we encountered something special. Switches in a stack won't generate STP logs unless they are the active switch of a stack.

MS 14  :

MS 17 :

When I filter the Event Log with the switch name : 

When I don't filter the logs , the logs are present (RSTP) :

In all 3 screenshots , the only action taken was to port cycle a client on switch -2 which is not the active/master switch of the stack. The syslog also indicates that the log seen from screenshot #3 is SENT by the active switch but displayed by the switch -2 from the dashboard. That's why it disapears when filtering with the specific switch from dashboard.

.118 is switch #2

.159 is the active switch of the stack

The inital reply I got from engineering  :

this is an expected behavior on the MS switches since firmware release MS15. So, the STP logs will only be generated on the active stack member switch. So, consider this as expected behavior that the non-active switch stack members will not be reporting any STP logs

Please note that these logs are being reported on the primary switch stack member switch 5 and the filter should not be applied for switch-2. 

We love the extra confusion.

[cmr]

@RaphaelL it's a good job the dashboard clearly tells you which switch in a stack is the master 😉 

[RaphaelL]

Yes , it is a good thing that we have that visibility. 

However , it would be nice to see the RSTP logs with a switch filter even if the switch is not the master. That would clear some confusion.  

This would fall under a "wish/feedback request" which doesn't really make sense to me. 

[Gopinath_Pigili]

Thanks for sharing..! @RaphaelL