topic RE: XOS versus EOS configuration file in ExtremeSwitching (EOS)

XOS versus EOS configuration file

Eric_Jackson — Wed, 16 Mar 2016 02:36:00 GMT

Please forgive my ignorance, as I'm new to XOS, having used EOS for years. I'm trying to grasp the way XOS handles it config file and compare it to Enterasys (EOS) but I can't seem to grasp some concepts. Hopefully I can explain clearly enough so that someone can "translate" for me.

Coming from years of experience in the EOS world, when I enter a command in EOS (spanning-tree for example), I can run the command "show config spantree" to see the commands I've entered or "show config all spantree" to see what I've entered plus what the defaults are behind the scenes. When I do this for XOS, i don't think I'm getting the same results. Using the same commands with regards to spanning tree in XOS, I run the command "show configuration stp", this seems to mimic EOS and show me only what I've configured. However, lets say I then remove a command. The command seems to be removed, essentially setting it back to default because I don't see it when I run "show configuration stp". Yet, it is still there when I run "show configuration detail stp" but in the "reverse state" if that makes since. Shouldn't it be gone from both, since I set it back to defaults? For example, I entered the command in XOS "enable stpd s0 ports 1:1". This created a line in my config. When I remove it running "disable stpd "s0" ports 1:1", the command no longer appears when I run "show configuration stp" but is somehow still there when I run "show configuration stp detail". Since I set it back to the default, shouldn't that line be gone from both? I'm really confused by this.

RE: XOS versus EOS configuration file

davidj_cogliane — Wed, 16 Mar 2016 02:42:00 GMT

It is my understanding the show config detail shows the default config items as well.

Is that what you are seeing?

RE: XOS versus EOS configuration file

Henrique — Wed, 16 Mar 2016 02:43:00 GMT

Hi Eric,

show configuration stp shows non-default configuration
show configuration stp detail shows non-default + default configurations (all config)

RE: XOS versus EOS configuration file

EtherMAN — Wed, 16 Mar 2016 02:51:00 GMT

Can see where this would be very confusing and really had to get used to. Here is how we set up all our XOS switches to track who does what where. Enable cli logging on all of them. This will record every command any one makes via a cli session. Enable syslog and run a good syslog server. This gives the ability to go back and do searches for configuration changes and who did what when. Use netsight to manage your backup configurations. We upload these every night from all switches... 1600 takes about 15 or 20 minutes total.. keep configs for your comfort level and if you need to restore and replace a bad switch you have the config if you need to go back a few days and see if something got changed you can use your syslog or the archived config to look and see.

RE: XOS versus EOS configuration file

StephenW — Wed, 16 Mar 2016 02:51:00 GMT

en cli-config-logging

:)

RE: XOS versus EOS configuration file

Eric_Jackson — Wed, 16 Mar 2016 20:13:00 GMT

Thanks folks for your help. I was really pleasantly surprised to get a responses back so quickly.

To clarify a little more, I took a new switch out of the box and ran "show config stp" which obviously showed nothing. I then ran "show config stp detail" which shows me the defaults only. Then I decided to enter the command "enable stpd s0 port 1". When I run "show config stp" or "show config stp detail" I now see the command I entered, which is what I would expect.

The part that is troubling me is than when I run "disable stpd s0 port 1", shouldn't that put me back to the defaults? If so, why is it when I run a "show config stp detail" do I see the command "disable stpd s0 port 1"? Since I "undid" the previous command (which was never in the original "show config stp detail" to begin with) shouldn't that line be omitted from the output?

RE: XOS versus EOS configuration file

Drew_C — Wed, 16 Mar 2016 20:13:00 GMT

The only way to know exactly what changed is to take a look at the XML config. That's something I'll try to get to in the next few days to see if I can find out why your

code:

disable

shows up there. I'm betting a configuration for s0 doesn't actually exist at all until you

code:

enable

code:

disable

it. It now exists in a defined state and can be seen in

code:

show config stp detail

. This tells us that something has changed, even if it's back to the expected default behavior.

RE: XOS versus EOS configuration file

Eric_Jackson — Wed, 16 Mar 2016 20:13:00 GMT

Drew I did as you suggested. I uploaded a new switches "primary.cfg" to a tftp server. I then entered "enable stpd s0 port 1". I saved the config. I then entered "disable stpd s0 port 1". I then saved the config and uploaded it. I compared the two configs and the only difference was on the 2nd config it had these extra lines:

configure sys-recovery-level switch resetconfigure vlan default delete ports all
configure vr VR-Default delete ports 1-54
configure vr VR-Default add ports 1-54
configure ports 49 auto off speed 10000 duplex full
configure ports 50 auto off speed 10000 duplex full
configure ports 51 auto off speed 10000 duplex full
configure ports 52 auto off speed 10000 duplex full
configure ports 53 auto off speed 10000 duplex full
configure ports 54 auto off speed 10000 duplex full
configure vlan Default add ports 1-54 untagged

None of this seems to relate to STP. However, when I run "show config stp detail" I see the line "disable stp s0 port 1".

RE: XOS versus EOS configuration file

Eric_Jackson — Wed, 16 Mar 2016 20:13:00 GMT

Actually, I just realized that wasn't the XML. I try again and let you know what I find.

RE: XOS versus EOS configuration file

Eric_Jackson — Wed, 16 Mar 2016 20:13:00 GMT

Ok, after running this experiment it appears as though quite a few things change behind the scenes. Specifically this is added:

1121
31
41
51
61
71
81
91
101
111
121
131
141
151
161
171
181
191
201
211
221
231
241
251
261
271
281
291
301
311
321
331
341
351
361
371
381
391
401
411
421
431
441
451
461
471
481
491
501
511
521
531
541

So I guess simply "undoing" something doesn't really undo it. However this could get frustrating if you ever want to go back to a "base" configuration.

RE: XOS versus EOS configuration file

Eric_Jackson — Wed, 16 Mar 2016 20:13:00 GMT

So does anyone know how to actually get back to defaults for spanning tree after entering those commands? As shown, if you enable stp, simply disabling it doesn't undo it. Here is my dilemma. I've enabled stp on port 1. Then, I decided that it would be better to simply use auto-bind. So to remove the line from my config and use auto-bind, i disabled stp. However, this seems to override the auto-bind on that port. Any help?

RE: XOS versus EOS configuration file

Eric_Jackson — Wed, 16 Mar 2016 20:13:00 GMT

Contacted GTAC and they were able to help me with this one particular issue. Basically, GTAC said I needed to remove the port from any vlans that have auto-bind enabled. Then add the port back. This worked. I now no longer have either the "enable stp s0 port 1:1" command or "disable stp s0 port 1:1" in the "show config detail stp"

However, the larger issue of simply "undoing" something will, I"m sure rear its ugly head again as I progress through learning XOS. Seems to me that if the default state of something is disabled, then you enable it, then decide to disable it again, you should be back at the default state.

RE: XOS versus EOS configuration file

Mike_D — Wed, 16 Mar 2016 23:16:00 GMT

Hello Eric,
I dont have a switch in front of me but i'd guess you've got a case for an engineering change request (a bug). Its unfortunate that that folks trying to learn are the ones who run into these sorts of things but if you're from the EOS side, consider how long its been since you've run 'show config xxx all' - unless looking for some obscure timer or such. Its when trying to make sense of a new environment these sorts of commands are most helpful - and it's the perfect place for a bug to hide.

Don't let it ruin the experience. I think you'll find there are some welcome features on the exos side once you break through the initial jolt of a new CLI.

Welcome to the hub. I can tell you there are several here ramping up on exos. Access to the community should help the transition go more quickly.

Best regards,
Mike