× NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Orbi WiFi 7 RBE973
Reply

many of these in log "Spanning Tree Topology Change Received"

robfantini
Aspirant

many of these in log "Spanning Tree Topology Change Received"

Hello

 

at Monitoring > lags ,  lag 11    has had some "Packets received with Errors" . now there are about 20.   last week 8 .

 

so I set up logging to go to a rsyslog server .  just lag 11 has entries [ besides login/logout ] . the

here are some:

Jul 11 10:23:22 169.254.100.100-1 TRAPMGR[51016628]: traputil.c(658) 1710 %% Spanning Tree Topology Change: 0, Unit: 1
Jul 11 10:23:21 169.254.100.100-1 TRAPMGR[155922352]: traputil.c(658) 26719 %% Spanning Tree Topology Change Received: MSTID: 0 lag 11   
Jul 11 10:23:21 169.254.100.100-1 TRAPMGR[155922352]: traputil.c(658) 26720 %% Spanning Tree Topology Change: 0, Unit: 1
Jul 11 10:23:23 169.254.100.100-1 TRAPMGR[155922352]: traputil.c(658) 26721 %% Spanning Tree Topology Change Received: MSTID: 0 lag 11   
Jul 11 10:23:53 169.254.100.100-1 TRAPMGR[155922352]: traputil.c(658) 26722 %% Spanning Tree Topology Change Received: MSTID: 0 lag 11   
Jul 11 10:23:53 169.254.100.100-1 TRAPMGR[155922352]: traputil.c(658) 26723 %% Spanning Tree Topology Change: 0, Unit: 1
Jul 11 10:23:55 169.254.100.100-1 TRAPMGR[155922352]: traputil.c(658) 26724 %% Spanning Tree Topology Change Received: MSTID: 0 lag 11 

the lag target is a M4100-50G-POE+ .  lag hash mode = 6 .    

 

Question -   could I have suggestions on how to fix that?    

 

 

Model: GSM7352Sv2|ProSAFE 48-port Managed L3 Gigabit Stackable Switch
Message 1 of 8

Accepted Solutions
Retired_Member
Not applicable

Re: many of these in log "Spanning Tree Topology Change Received"

@robfantini

 

Yes, we have got the detailed info. Thanks for your immediately response.

 

1. According to the memory log, we found that port 1/0/29 and 2/0/29 is flapping. Could you please double check these two port status?

port flapping.jpg

 

2. According to spanning tree log, there is loop topo change. Could you please provide the network topo to us for further analysis?

 

3. I am afraid the traffic wasn't interrupted by these spanning tree log, right? As I think these log is normal, just dut to STP protocol detect topo tree changing, and adjust forwarding path.

View solution in original post

Message 6 of 8

All Replies
Retired_Member
Not applicable

Re: many of these in log "Spanning Tree Topology Change Received"

Hi @robfantini,

 

Welcome to the community!

These spanning tree log is due to topo change, please check whether there is port flapping or not in the switch?


Hope it helps!

Regards,

EricZ
NETGEAR employee

Message 2 of 8
robfantini
Aspirant

Re: many of these in log "Spanning Tree Topology Change Received"

Hello

 

Could you please advise on were to check for 'port flapping or not in the switch '   

Message 3 of 8
Retired_Member
Not applicable

Re: many of these in log "Spanning Tree Topology Change Received"

@robfantini

 

 

Ok, please send the tech-support file to us. As this file contain more detailed info.

 

How do I send tech-support files from my Managed Switch to NETGEAR community moderators?

http://kb.netgear.com/app/answers/detail/a_id/31439

Message 4 of 8
robfantini
Aspirant

Re: many of these in log "Spanning Tree Topology Change Received"

OK I just sent what I could  AND

Note on my switch there are not options for  ' full memory dump '  and ' crash logs '  .  In case you have a suggestion for those.

 

thank you for the help so far!

Message 5 of 8
Retired_Member
Not applicable

Re: many of these in log "Spanning Tree Topology Change Received"

@robfantini

 

Yes, we have got the detailed info. Thanks for your immediately response.

 

1. According to the memory log, we found that port 1/0/29 and 2/0/29 is flapping. Could you please double check these two port status?

port flapping.jpg

 

2. According to spanning tree log, there is loop topo change. Could you please provide the network topo to us for further analysis?

 

3. I am afraid the traffic wasn't interrupted by these spanning tree log, right? As I think these log is normal, just dut to STP protocol detect topo tree changing, and adjust forwarding path.

Message 6 of 8
robfantini
Aspirant

Re: many of these in log "Spanning Tree Topology Change Received"

The proxmox system attached to that lag  was  having cluster communication issue.     

 

I rebooted it and it has been OK for now as far as cluster.   But we have been having off and on issues with that cluster.   It occurs often when I was testing  our 3  port lags [ see other thread ].   When I'd plug patch cable in to  3/0/1 ,  this cluster and some vm's would have  time and network connect issues.

 

Per another thread it looks like we should use  lag has mode 3 instead of 6 .

 

AND

 

could you teach me how to find the log that shows  port flapping?    I want to monitor that after changing the hash mode.

Message 7 of 8
robfantini
Aspirant

Re: many of these in log "Spanning Tree Topology Change Received"

I figured out how to see the logs -  create and download tech support file.

 

Will use the file to check and correct flapping.     I'll report back in a few days or so.

Message 8 of 8
Top Contributors
Discussion stats
  • 7 replies
  • 13244 views
  • 0 kudos
  • 2 in conversation
Announcements