conf_diff.py: explanation of returning output

  • 0
  • 1
  • Problem
  • Updated 2 months ago
  • Solved
Hi,

i am playing around with "conf_diff.py" and i have some problems to understand the output.

Switch X450G2-48p-G4 - EXOS: 22.4.1.4

SW-TEST.21 # run script conf_diff.py
Comparing configurations, please wait...

error-correction off
disable mac-lockdown-timeout ports 49
configure mac-lockdown-timeout ports 49 aging-time 15
configure ports 49 far-end-fault-indication off
disable vman cep egress filtering ports 49
configure port 49 dot1p 0
disable snmp traps port-up-down port 50
enable diffserv examination port 50
configure port 50 reflective-relay off
configure port 50 isolation off
disable flow-control tx-pause port 50
disable flow-control rx-pause port 50
configure ports 50 forward-error-correction off
disable mac-lockdown-timeout ports 50
configure mac-lockdown-timeout ports 50 aging-time 15
configure ports 50 far-end-fault-indication off
disable vman cep egress filtering ports 50
configure port 50 dot1p 0

If line starts with '+', the command has been added since last save.
If line starts with '-', the command was present in the last save, and has been deleted.

Config changes:
- configure ports 27 display-string Auth-TEST-MN
+ configure ports 27 display-string Auth-TEST-MN2
Note that this script has cleared the CLI dirty bit. The configuration has not been saved.
SW-TEST.22 #
What does mean the block of commands between "please wait ..." and "if line starts ...". 
At GitHub example there is no output seen.

Is there a special meaning or is this maybe a result of EXOS 22.4 and some upcoming incompatibility with python script (because it seem to be programmed for an older EXOS version)

Regards
Photo of M.Nees

M.Nees, Embassador

  • 8,874 Points 5k badge 2x thumb

Posted 3 months ago

  • 0
  • 1
Photo of Brandon Clay

Brandon Clay, Escalation Support Engineer

  • 13,086 Points 10k badge 2x thumb
That looks like a bug of some sort. There shouldn't be any output between the "please wait..." and "If line starts...".

Some of the underlying commands that this script relies on my have changed in EXOS 22.4. I'll do some research/testing and see what I can find.

Out of curiosity, did you test this with older EXOS versions, like 22.3 or 21.x? 

I've also opened up an issue for tracking this on the ExtremeScripting GitHub repo. https://github.com/extremenetworks/ExtremeScripting/issues/36
Photo of Brandon Clay

Brandon Clay, Escalation Support Engineer

  • 13,086 Points 10k badge 2x thumb
With a basic config on one of my lab switches, I haven't see this happen. Would you mind posting the full config from this switch?

Let me know if you'd rather not post it publicly, and I can shoot you an email to get it.
Photo of M.Nees

M.Nees, Embassador

  • 8,874 Points 5k badge 2x thumb
Please send me a short e-mail!
Photo of Brandon Clay

Brandon Clay, Escalation Support Engineer

  • 13,086 Points 10k badge 2x thumb
Just sent you one!
Photo of Brandon Clay

Brandon Clay, Escalation Support Engineer

  • 13,086 Points 10k badge 2x thumb
It looks like this is an issue on the EXOS side of things.

When the Python script calls 'clicmd("debug cfgmgr show configuration file {0}".format(selected_config), True)', part of the output of the EXOS command is written to the current session incorrectly, with certain config files.

I'm going to bring this issue to out EXOS development team, and I'll follow up back here once I have an update.
Photo of M.Nees

M.Nees, Embassador

  • 8,874 Points 5k badge 2x thumb
Some progress here ?
Photo of Drew C.

Drew C., Community Manager

  • 36,956 Points 20k badge 2x thumb
Photo of Brandon Clay

Brandon Clay, Escalation Support Engineer

  • 13,086 Points 10k badge 2x thumb
FYI, I just confirmed this is fixed in a pre-GA build of 22.5. Once 22.5 goes GA, the fix will be available there.