cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1992
Views
0
Helpful
8
Replies

%SPANTREE-5-ROOTCHANGE Root Changed for vlan 123

ioannisv
Level 1
Level 1

Recently we have added a switch as secondary root bridge and we are getting :

013296: Jan 6 2022 20:05:38.128 Cyprus: %SPANTREE-5-TOPOTRAP: Topology Change Trap for vlan ZZZ
013297: Jan 6 2022 20:05:38.128 Cyprus: %SPANTREE-5-ROOTCHANGE: Root Changed for vlan 113: New Root Port is GigabitEthernet1/0/24. New Root Mac Address is xxxx.xxxx.xxxx

 

There is no evidence of link up/down or error on connectivity with the uplink between switches.

What could be causing the above behavior?

 

8 Replies 8

balaji.bandi
Hall of Fame
Hall of Fame

if you do not set up the spanning-tree root priority spanning root election kicks in

 

as explained below :

 

https://www.certificationkits.com/cisco-certification/ccna-articles/cisco-ccna-switching/cisco-ccna-spanning-tree-protocolroot-bridge-rootdesignatedblocked-ports/

 

Recently we have added a switch as secondary root bridge and we are getting :

explain more will helpfull here.

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

ioannisv
Level 1
Level 1

The designated switch is configured with priority "4096" and the secondary with "24576"

 

As for the logs received every minute or so (on the secondary) :

026228: Jan 7 2022 07:43:19.938 Cyprus: %SPANTREE-5-ROOTCHANGE: Root Changed for vlan 64: New Root Port is GigabitEthernet1/0/24. New Root Mac Address is xxxx.xxxx.xxxx
026229: Jan 7 2022 07:43:43.965 Cyprus: %SPANTREE-5-TOPOTRAP: Topology Change Trap for vlan 31

 

to come to understand we need your network topo and full config to understand, along with show spanning tree information

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Hello
GigabitEthernet1/0/24 has become the root port due to a stp topology change being initiated in the switching estate, if you have made any changes, adding additional trunk ports or new switches this could be the reason.


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

ioannisv
Level 1
Level 1

unfortunately none of the above occurred and that's worries me a lot.

Since the link between the root and the secondary is not direct , that could be causing the issue?

 

 

Hello,

 

I remotely remember a similar case, the solution was to delete and then re-add the Vlan altogether. Which obviously can cause a disruption to your connectivity, so you might want to do this after hours.

Hello
So you have had no link/port failures, added/removed no switch's/trunks etc. Manually pruned any vlans off trunks, create vlans that trunks are been pruned from?
Are you running vtp and if so are all your switches running the same version ?


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

ioannisv
Level 1
Level 1

Vlan delete and create did not help.

As for the VTP version , all switches are on the same v2 with pruning enabled.

How do i manually enforce vtp pruning?

Review Cisco Networking products for a $25 gift card