ExtremeSwitching (EOS)

Expand all | Collapse all

Problem with spaning tree on S Boning Switch Series

Daniel Coughlin

Daniel Coughlin06-12-2017 14:01

Jeremy Gibbs

Jeremy Gibbs06-12-2017 14:19

Jeremy Gibbs

Jeremy Gibbs06-12-2017 14:52

Daniel Coughlin

Daniel Coughlin06-12-2017 14:52

Jeremy Gibbs

Jeremy Gibbs06-16-2017 12:29

  • 1.  Problem with spaning tree on S Boning Switch Series

    Posted 06-12-2017 13:42
    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


  • 2.  RE: Problem with spaning tree on S Boning Switch Series

    Posted 06-12-2017 13:45
    What model switch is this? and what version is it running? If it is an EXOS switch can you run "show stp


  • 3.  RE: Problem with spaning tree on S Boning Switch Series

    Posted 06-12-2017 13:46
    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


  • 4.  RE: Problem with spaning tree on S Boning Switch Series

    Posted 06-12-2017 13:52
    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


  • 5.  RE: Problem with spaning tree on S Boning Switch Series

    Posted 06-12-2017 13:57
    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--


  • 6.  RE: Problem with spaning tree on S Boning Switch Series

    Posted 06-12-2017 14:01
    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?


  • 7.  RE: Problem with spaning tree on S Boning Switch Series

    Posted 06-12-2017 14:09
    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


  • 8.  RE: Problem with spaning tree on S Boning Switch Series

    Posted 06-12-2017 14:18
    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



  • 9.  RE: Problem with spaning tree on S Boning Switch Series

    Posted 06-12-2017 14:19
    By edge ports, I mean on the 800 series.


  • 10.  RE: Problem with spaning tree on S Boning Switch Series

    Posted 06-12-2017 14:47
    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



  • 11.  RE: Problem with spaning tree on S Boning Switch Series

    Posted 06-12-2017 14:52
    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)


  • 12.  RE: Problem with spaning tree on S Boning Switch Series

    Posted 06-16-2017 07:47
    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 😃


  • 13.  RE: Problem with spaning tree on S Boning Switch Series

    Posted 06-16-2017 12:29
    Glad you figured it out.


  • 14.  RE: Problem with spaning tree on S Boning Switch Series

    Posted 06-16-2017 13:04
    Glad you were able to get to the bottom of this.


  • 15.  RE: Problem with spaning tree on S Boning Switch Series

    Posted 06-12-2017 14:01
    That looks like a good place to start.


  • 16.  RE: Problem with spaning tree on S Boning Switch Series

    Posted 06-12-2017 14:52
    Ahh, thanks for pointing that out!


  • 17.  RE: Problem with spaning tree on S Boning Switch Series

    Posted 06-12-2017 14:52
    no worries just trying to help.