How to configure XOS to use EOS default spanning tree configuration

[Eric_Jones]

I have worked with EOS for several years without any spanning tree problem, I would like to know how to mimic the default spanning tree setting in EOS on an XOS device(i.e. what commands would I need to use to have XOS stp work just like EOS stp?)

[Drew_C]

In many cases, ExtremeWare translates very well to EXOS without additional intervention or conversion.
If you're having trouble with specifics, I invite you to create a new topic here or to open a ticket with GTAC.

[Jimmy2]

What about converting Extremeware to XOS? Any plans.....?

[Stephane_Grosj1]

Hi,
yes, the STP section of the config could be pasted as a file and the tool would translate it. I've written a quick how-to for E2X, it should be posted soon.

By default, E2X adds the EOS default STP configuration to a generated EXOS file, so if you only have default configuration, that would be inserted automatically. E2X knows the different default config in both EOS and EXOS and adapts to it, unless specificaly told not to.

Now, if you use the following EOS config (stp.cfg):set port jumbo disable *.1.*
set spantree mstcfgid cfgname Showroom rev 1
set spantree msti sid 1 create
set spantree msti sid 2 create
set spantree mstmap 1,20,50,100 sid 1
set spantree mstmap 30,101,102,103 sid 2
set spantree priority 4096 1
set spantree priority 8192 2
E2X would translate that into EXOS like that:

C:\01 - EXOS\Features\E2X>e2x stp.cfg
NOTICE: Writing translated configuration to file "stp.xsf"
NOTICE: Mapping port "tg.1.49" to port "53"
NOTICE: Mapping port "tg.1.50" to port "54"
NOTICE: Port "49" of target switch is not used
NOTICE: Port "50" of target switch is not used
NOTICE: Port "51" of target switch is not used
NOTICE: Port "52" of target switch is not used
NOTICE: XOS always allows single port LAGs

C:\01 - EXOS\Features\E2X>type stp.xsf
configure mstp region Showroom
configure mstp revision 1
configure stpd s0 delete vlan Default ports all
disable stpd s0 auto-bind vlan Default
configure stpd s0 mode mstp cist
enable stpd s0
create stpd s1c
onfigure stpd s1 default-encapsulation dot1d
configure stpd s1 mode mstp msti 1
enable stpd s1 auto-bind vlan Default
configure stpd s1 priority 4096
enable stpd s1
create stpd s2
configure stpd s2 default-encapsulation dot1d
configure stpd s2 mode mstp msti 2
configure stpd s2 priority 8192
enable stpd s2

[Eric_Jones]

It sounds like an interesting tool, but considering that the spanning tree is preconfigured I don't know the commands that would need to be translated. Would I need to do a (:show config all command) in EOS then copy the stp section into the E2X translator?

[Stephane_Grosj1]

Hi, Do you know about E2X translate tool that we have made available on Github? That sounds like a good tool to help you. https://github.com/extremenetworks/E2X