cancel
Showing results for 
Search instead for 
Did you mean: 

XOS Spanning Tree Config

XOS Spanning Tree Config

EtherNation_Use
Contributor II
Create Date: Apr 29 2013 9:48AM

Hi All,

I'm still a relative newbie with Extreme Networks, having previously been a Cisco and 3Com guy, and there are a few things I'm getting used to still.

I recently discovered that Spanning Tree is disabled by default and I wanted to just ensure that what I have done is correct, and if there are any tips. I have combined STP with ELRP, but I am only using ELRP as a checking & notification mechanism.

So in this example the switch is an edge unit and I am using RSTP. I have found that if I do not add the voice vlan to STPD s0, my phones do not work.

My STP config is as follows...

configure stpd s0 mode dot1w
conf stpd "s0" add vlan "Default" ports all
conf stpd "s0" add vlan "Voice" ports all


Then on the edge ports I have:

configure stpd s0 ports link-type edge
configure stpd s0 ports edge-safeguard enable


I've created loops on edge ports on purpose and after 2 seconds or so the port is blocked and I see the ELRP messages.

One thing I have noticed is that even though I have set STPD s0 to dot1w mode, I still see the ports as dot1d - do I need to manually set this on all ports?

3Coms have MSTP enabled by default (I literally don't have to do anything and STP is running and ports are protected). However MSTP config on XOS seems tricky, so any tips on that front would be appreciated.

Thanks  (from networkguy)
3 REPLIES 3

EtherNation_Use
Contributor II
Create Date: May 4 2013 6:26AM

ELRP here too.piece of cake to setup, we have pretty much the same config on all our edge switches so it was really a cut and paste jobbie. definitely works really nicely.we are a school so we have it set to auto disable the port for a period of time and then attempt to re-enable it. traps are sent to ridgeline. we didn't wan't permanently disabling because it would give disruptive students an angle to exploit. (from conrad_jones)

EtherNation_Use
Contributor II
Create Date: May 3 2013 7:26PM

If you're just looking to protect against loops, ELRP is the way to go. It's quite efficient. I've been using it for years in a campus-type environment where clients do lots of rewiring and make loops frequently. STP and its variants tend to let things get out of hand - we've seen it block loops properly (and silently), but then if something else changes in the topology the problem ends up being bigger as there are multiple loops present, as well as possible bridge links between networks.

All told, in our environment a combination of ELRP and dhcp-snooping have cut client rewiring-based network failure down to almost nil. (from Ansley_Barnes)

EtherNation_Use
Contributor II
Create Date: May 1 2013 9:37AM

You have to enable rstp.

enable stpd "stpdomain-name" rapid-root-failover

(from LNU)
GTM-P2G8KFN