I have a 5510 stack that has multiple L2 VLAN;s on it. It is constantly outputting a spanning tree topology change to our syslog server. The ports are very static, meaning no links are changing status. Any input on what triggers this and if it of concern?
Below are examples
2/27/2017 08:31 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: topologyChange
2/27/2017 08:31 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: topologyChange
2/27/2017 08:31 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: topologyChange
2/27/2017 08:31 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: topologyChange
2/27/2017 08:31 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: topologyChange
2/27/2017 08:31 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: newRoot
2/27/2017 08:31 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: topologyChange
2/27/2017 08:31 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: newRoot
2/27/2017 08:31 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: topologyChange
2/27/2017 04:25 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: topologyChange
2/27/2017 04:25 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: topologyChange
Below are examples
2/27/2017 08:31 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: topologyChange
2/27/2017 08:31 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: topologyChange
2/27/2017 08:31 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: topologyChange
2/27/2017 08:31 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: topologyChange
2/27/2017 08:31 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: topologyChange
2/27/2017 08:31 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: newRoot
2/27/2017 08:31 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: topologyChange
2/27/2017 08:31 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: newRoot
2/27/2017 08:31 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: topologyChange
2/27/2017 04:25 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: topologyChange
2/27/2017 04:25 AM dmz_5510_sw_stk1
192.168.223.250
:Trap: topologyChange