Header Only - DO NOT REMOVE - Extreme Networks

i series rstp configuration


Userlevel 2
please help, we are very new to EOS and we need to configure the EOS switch using RSTP since we will use the switch in a ring network. can someone share sample configuration of RSTP in EOS? many thanks

8 replies

Userlevel 4
By default the I-Series (like the SecureStacks, D-Series, and G-Series) runs MSTP (Multiple Spanning Tree Protocol) which, when not specifically configured for MSTP behavior, functions as RSTP (Rapid Spanning Tree Protocol). Spanning Tree is enabled by default. No configuration is necessary.

Do you have any specific concerns, perhaps concerning existing behavior that is not as expected?
Paul Poyant wrote:

By default the I-Series (like the SecureStacks, D-Series, and G-Series) runs MSTP (Multiple Spanning Tree Protocol) which, when not specifically configured for MSTP behavior, functions as RSTP (Rapid Spanning Tree Protocol). Spanning Tree is enabled by default. No configuration is necessary.

Do you have any specific concerns, perhaps concerning existing behavior that is not as expected?

Try the following article for some basic commands including spanning tree
https://gtacknowledge.extremenetworks.com/articles/How_To/EOS-Basic-Switch-Layer-2-Configuration-Best-Practices/
Paul Poyant wrote:

By default the I-Series (like the SecureStacks, D-Series, and G-Series) runs MSTP (Multiple Spanning Tree Protocol) which, when not specifically configured for MSTP behavior, functions as RSTP (Rapid Spanning Tree Protocol). Spanning Tree is enabled by default. No configuration is necessary.

Do you have any specific concerns, perhaps concerning existing behavior that is not as expected?

Try the following article for some basic commands including spanning tree
https://gtacknowledge.extremenetworks.com/articles/How_To/EOS-Basic-Switch-Layer-2-Configuration-Bes...
Userlevel 2
Hi Paul,

thanks. we have a single VLAN that will map to MSTP. is this the command to to add the vlan in MSTP -set spantree mstmap fid [sid sid] ?

thanks
Userlevel 2
Hi Paul,

please see the network diagram, this is what we are trying to configure mstp but we have no knowledge in EOS configuration. we are only familiar with XOS. can you give us the configuration based on the network diagram below?

thanks

Userlevel 4
Hello Marlon,

If you only have one VLAN RSTP is all you need. Assuming these tree switches are all EOS, as Paul have said, no further configuration is necessary as spanning tree is enabled by default. I will also reinforce the suggestion posted by my colleague Luke French and advise you to review the best practice document we have published in our knowledge at https://gtacknowledge.extremenetworks.com/articles/How_To/EOS-Basic-Switch-Layer-2-Configuration-Best-Practices/.

I hope it helps.
Userlevel 2
In the network shown above, RSTP will always disable one of the links, and any redundancy will be lost. Spanning tree's job is to determine one path, and one path only, to any given destination. Any redundant path's will be turned off by STP.

What you CAN do in this situation, and if you wish to split your traffic into two or more VLANs, you can run MSTP, and create an instance for each VLAN. For instance, you could split your traffic up into two VLANs, name them VLAN 200 and VLAN 300, and assign them to seperate SIDs (SID 2 and SID 3 respectively). Your command set would look something like this (this is from memory, btw):

The command for setting up MSTP for each instance are as follows:

switch(su)->set spantree stpmode iee8021 <---not needed on C/D/G Series
switch(su)->set spantree version mstp
switch(su)->set spantree mstcfgid cfgname MSTCFG-1
switch(su)->set spantree msti sid 2 create
switch(su)->set spantree mstmap 200 sid 2
switch(su)->set spantree msti sid 3 create
switch(su)->set spantree mstmap 300 sid 3

In order for the stations in each of these VLANs to communicate with each other, they will need a routed interface, so you'll have to set that up as well. If you want link redudnancy, you'll also want to set up different switches to be the root bridge for each instance. And although there are other ways to skin this cat, this will ensure that all traffic won't be restricted to just one link, enable the redundant links to share the load, and to ensure that a path will exist should one of the links fail.

Otherwise, you can simply enable RSTP and be content with the fact that one of your links will not be in use unless another fails. And as always, don't be afraid to call GTAC. They know what they're doing, and they are always ready to assist.

Good luck.
Userlevel 2
hi all,

thanks for the support. as discussed above rstp is already configured in switches. We already setup the network with stp.

Reply