Header Only - DO NOT REMOVE - Extreme Networks

Problem with spaning tree on S Boning Switch Series


Dear all, i have problems chaning my topology every minutes i think i have some trouble with spaning tree can someone help me how to find spaning tree port

16 replies

Userlevel 6
What model switch is this? and what version is it running? If it is an EXOS switch can you run "show stp " and copy the output?
Userlevel 4
Assuming you meant an S series switch I would start withe the following:

Support-> show spantree stats

Support-> show spantree blockedports

Support-> show spantree debug port *.*.* active

Support-> show port operstatuscause
Userlevel 2
In EXOS, "show vlan" will help you to identify which ones have STP enabled on them - STP enabled vlans are denoted by the "T" flag.
You can then do "show vlan " and it will show you which ports are being blocked by STP - blocked ports will have a "b" next to them.
"Show port info detail" will then give you further information still about the state of the port and it's configuration.
Core_SW(su)->show spantree stats

Spanning tree status - enabled
Spanning tree instance - 0
Designated Root MacAddr - 02-00-0a-fe-63-0a
Designated Root Priority - 0
Designated Root Cost - 0
Designated Root Port - 0
Root Max Age - 20 sec
Root Hello Time - 2 sec
Root Forward Delay - 15 sec
Bridge ID MAC Address - 02-00-0a-fe-63-0a
Bridge ID Priority - 0
Bridge Max Age - 20 sec
Bridge Hello Time - 2 sec
Bridge Forward Delay - 15 sec
Topology Change Count - 16946
Time Since Top Change - 00 days 00:00:22
Max Hops - 20

Core_SW(su)->show spantree blockedports
Number of blocked ports in SID 0 : 0
Core_SW(su)->show spantree debug port *.*.* active

SID: 0, Bridge ID: 00-00-02-00-0a-fe-63-0a, Time Since TC: 00 days 00:00:46

Root Priority Vector
------------------------------------------------------------
Root ID - 00-00-02-00-0a-fe-63-0a
External Cost - 0
Regional Root ID - 00-00-02-00-0a-fe-63-0a
Internal Cost - 0
Designated Bridge ID - 00-00-02-00-0a-fe-63-0a
Designated Port - 0
Receive Port - 0 (none)

Alternate Ports Designated Bridge
------------------------------------------------------------
(none)

Ports with Received TC BPDUs Count
------------------------------------------------------------
--More-- next page, one line, quit
lag.0.4 112
lag.0.6 4
lag.0.8 2
lag.0.10 9326
lag.0.11 6
lag.0.13 54
lag.0.15 2
lag.0.19 6
lag.0.21 2
lag.0.22 2
lag.0.31 23078
lag.0.38 2
lag.0.46 6
ge.2.23 8
ge.2.24 354
ge.2.25 108
ge.2.27 6
ge.2.28 218
ge.2.32 176
--More-- next page, one line, quit
ge.2.40 18
ge.2.42 7

Ports with Message Age Expired Count
------------------------------------------------------------
(none)

Ports with Exceptional Condition Reason
------------------------------------------------------------
(none)

STP Diagnostic Common Counters
------------------------------------------------------------
Topology Change Count - 16952
Message Expiration Count - 0
Invalid BPDU Count - 0
Disputed BPDU Count - 32
STP BPDU Rx Count - 0
STP BPDU Tx Count - 0
--More-- next page, one line, quit
STP TCN BPDU Rx Count - 0
STP TCN BPDU Tx Count - 0
STP TC BPDU Rx Count - 0
STP TC BPDU Tx Count - 0
RST BPDU Rx Count - 33904
RST BPDU Tx Count - 450979516
RST TC BPDU Rx Count - 33490
RST TC BPDU Tx Count - 1076938
MST BPDU Rx Count - 8
MST BPDU Tx Count - 0
MST CIST TC BPDU Rx Count - 7
MST CIST TC BPDU Tx Count - 0
SPT BPDU Rx Count - 0
SPT BPDU Tx Count - 0
SPT TC BPDU Rx Count - 0
SPT TC BPDU Tx Count - 0

STP Diagnostic Root History Table for SID 0
Check lag.0.31 and the other lags that have high counters. Do you have spangaurd turned on on the edge ports with adminedge? What are your edge switches?
Userlevel 4
Jeremy Gibbs wrote:

Check lag.0.31 and the other lags that have high counters. Do you have spangaurd turned on on the edge ports with adminedge? What are your edge switches?

That looks like a good place to start.
I use s800 series edge switch, yes the spaning tree is activated on rstp mode

here is my logging server
2017-06-12 18:10:51 Local0 Notice 10.10.7.11 Jun 12 18:10:49 10.10.7.11 NOTICE: Topology changed (Instance:0, Port:51,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:51 Local0 Notice 10.10.7.45 Mar 17 03:40:22 10.10.7.45 NOTICE: Topology changed (Instance:0, Port:51,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:51 Local0 Notice 10.10.7.22 Jun 12 18:10:49 10.10.7.22 NOTICE: Topology changed (Instance:0, Port:51,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.61 Jun 21 21:00:20 10.10.7.61 NOTICE: Topology changed (Instance:0, Port:28,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.38 Jun 12 18:10:50 10.10.7.38 NOTICE: Topology changed (Instance:0, Port:51,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.24 Jun 12 18:10:50 10.10.7.24 NOTICE: Topology changed (Instance:0, Port:51,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.37 Jun 12 18:10:49 10.10.7.37 NOTICE: Topology changed (Instance:0, Port:24,MAC:20-B3-99-79-FA-E7) 2017-06-12 18:10:50 Local0 Notice 10.10.7.20 Jun 12 18:10:50 10.10.7.20 NOTICE: Topology changed (Instance:0, Port:51,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.10 Jun 12 18:10:50 10.10.7.10 NOTICE: Topology changed (Instance:0, Port:51,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.19 Jun 12 18:10:49 10.10.7.19 NOTICE: Topology changed (Instance:0, Port:24,MAC:20-B3-99-7A-15-9C) 2017-06-12 18:10:50 Local0 Notice 10.10.7.30 Jun 12 18:10:50 10.10.7.30 NOTICE: Topology changed (Instance:0, Port:51,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.42 Jun 12 18:10:49 10.10.7.42 NOTICE: Topology changed (Instance:0, Port:27,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.29 Jun 12 18:10:49 10.10.7.29 NOTICE: Topology changed (Instance:0, Port:51,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.17 Jun 12 18:10:49 10.10.7.17 NOTICE: Topology changed (Instance:0, Port:24,MAC:20-B3-99-7A-0B-E1) 2017-06-12 18:10:50 Local0 Notice 10.10.7.44 Jun 12 18:10:49 10.10.7.44 NOTICE: Topology changed (Instance:0, Port:27,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.21 Jun 12 18:10:50 10.10.7.21 NOTICE: Topology changed (Instance:0, Port:48,MAC:20-B3-99-7A-11-43) 2017-06-12 18:10:50 Local0 Notice 10.10.7.39 Jun 12 18:10:50 10.10.7.39 NOTICE: Topology changed (Instance:0, Port:24,MAC:20-B3-99-7A-0B-77) 2017-06-12 18:10:50 Local0 Notice 10.10.7.39 Jun 12 18:10:48 10.10.7.39 NOTICE: Topology changed (Instance:0, Port:24,MAC:20-B3-99-7A-0B-77) 2017-06-12 18:10:50 Local0 Notice 10.10.7.27 Jun 12 18:10:49 10.10.7.27 NOTICE: Topology changed (Instance:0, Port:51,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.27 Jun 12 18:10:47 10.10.7.27 NOTICE: Topology changed (Instance:0, Port:51,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.65 Jun 12 18:10:48 10.10.7.65 NOTICE: Topology changed (Instance:0, Port:28,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.33 Jun 12 18:10:50 10.10.7.33 NOTICE: Topology changed (Instance:0, Port:27,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.33 Jun 12 18:10:48 10.10.7.33 NOTICE: Topology changed (Instance:0, Port:27,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.23 Jun 12 18:10:49 10.10.7.23 NOTICE: Topology changed (Instance:0, Port:24,MAC:20-B3-99-7A-13-55) 2017-06-12 18:10:50 Local0 Notice 10.10.7.23 Jun 12 18:10:48 10.10.7.23 NOTICE: Topology changed (Instance:0, Port:24,MAC:20-B3-99-7A-13-55) 2017-06-12 18:10:50 Local0 Notice 10.10.7.13 Jun 12 18:10:49 10.10.7.13 NOTICE: Topology changed (Instance:0, Port:51,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.13 Jun 12 18:10:47 10.10.7.13 NOTICE: Topology changed (Instance:0, Port:51,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.15 Jun 12 18:10:50 10.10.7.15 NOTICE: Topology changed (Instance:0, Port:51,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.15 Jun 12 18:10:48 10.10.7.15 NOTICE: Topology changed (Instance:0, Port:51,MAC:02-00-0A-FE-63-0A) 2017-06-12 18:10:50 Local0 Notice 10.10.7.12 Jun 12 18:10:47 10.10.7.12 NOTICE: Topology changed (Instance:0, Port:48,MAC:20-B3-99-75-2B-81) 2017-06-12 18:10:50 Local0 Notice 10.10.7.41 Jun 12 18:10:49 10.10.7.41 NOTICE: Topology changed (Instance:0, Port:24,MAC:20-B3-99-7A-0A-39) 2017-06-12 18:10:50 Local0 Notice 10.10.7.41 Jun 12 18:10:48 10.10.7.41 NOTICE: Topology changed (Instance:0, Port:24,MAC:20-B3-99-7A-0A-39)

every minutues my topology changes i dont know what heppen
I use s800 series edge switch, yes the spaning tree is activated on rstp mode
Hmm..

Run these commands on EDGE ports ONLY:
set spantree adminedge ge.1.1-48

Then

set spantree spangaurd enable

set linkflap globalstate enable
set linkflap action ge.1.1-48 gensyslogEntry
set linkflap portstate enable ge.1.1-48
By edge ports, I mean on the 800 series.
Yes but this commands is not working on my switch
set spantree adminedge ge.1.1-48

Then

set spantree spangaurd enable

set linkflap globalstate enable
set linkflap action ge.1.1-48 gensyslogEntry
set linkflap portstate enable ge.1.1-48
Userlevel 4
The cli on the 800 is a bit different

800-Series
enable stp
config stp version rstp
config stp ports 1-23 edge true (User port)
config stp ports 24 edge false (Uplink Port)
Daniel Coughlin wrote:

The cli on the 800 is a bit different

800-Series
enable stp
config stp version rstp
config stp ports 1-23 edge true (User port)
config stp ports 24 edge false (Uplink Port)

Ahh, thanks for pointing that out!
Userlevel 4
Daniel Coughlin wrote:

The cli on the 800 is a bit different

800-Series
enable stp
config stp version rstp
config stp ports 1-23 edge true (User port)
config stp ports 24 edge false (Uplink Port)

no worries just trying to help.
Thanks all for your reply, i have found the loop on edge switch, the command that i use is:

first to clear all stp stats
debug stp clear counter ports all

then to show stp stats
debug stp show counter ports all

and i got on port 23
TCN BPDU : 12554

thanks so much from all 😃
Glad you figured it out.
Userlevel 4
Glad you were able to get to the bottom of this.

Reply