Stp topology change not showing in syslog

  • 0
  • 1
  • Question
  • Updated 1 year ago
  • Answered
Hi,

i have my switches configured with the following:

configure log filter LabFilter add events STP.SendClntTopoChgMsg
configure log filter LabFilter add events STP.State.Topology

configure syslog add 10.96.32.32:514 vr VR-Default local0
enable log target syslog 10.96.32.32:514 vr VR-Default local0
configure log target syslog 10.96.32.32:514 vr VR-Default local0 filter LabFilter severity Info
configure log target syslog 10.96.32.32:514 vr VR-Default local0 match Any
configure log target syslog 10.96.32.32:514 vr VR-Default local0 format timestamp seconds date Mmm-dd event-name none process-slot priority host-name tag-name

Im playing around by changing the stpd bridge priority and i dont see any STP.State.Topology log on my syslog.

Is there any extra configuration that i need to add?

thanks
Photo of GONÇALO NUNO CONTENTE PIMENTEL DA SILVA REIS

Posted 1 year ago

  • 0
  • 1
Photo of Nick Yakimenko

Nick Yakimenko

  • 2,518 Points 2k badge 2x thumb
why did you filtered-out the  severity Info ?
I' ve tried also with severity debug-data and i dont receive any notificacion. When i issue the command "enable log debug-mode" i receive the notifications, but i cannot have this enable on a production environment. I need to figure out how can i enable Spanning-tree debug-data notificacions without the "debug-mode enable". 
I was able to find the unswer searching through Extreme documentation.

"Any EMS (Event Management System) events with severity debug-summary, debug-verbose, or debug-data will not be logged unless debug mode is enabled. See the command enable log debug-mode."