• September 22, 2020, 12:02:02 AM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: White spaces and command line  (Read 2030 times)

0 Members and 1 Guest are viewing this topic.

Offline bhusebye

  • Rookie
  • **
  • Posts: 12
White spaces and command line
« on: December 22, 2014, 11:58:22 AM »
Can white spaces be introduced with cut and paste at command line and will it cause corruption of .cfg file on a switch?  I have noticed a high amount of corruption lately and I see NBSP added via cut and paste into some of the corrupt .ascii files.


Thanks for your help


Offline bhusebye

  • Rookie
  • **
  • Posts: 12
Re: White spaces and command line
« Reply #1 on: December 23, 2014, 12:28:51 AM »
Guess I will  dirty a clean config and let everyone know the outcomes.  My theory is this.  Someone has been working in the ascii file and saving it corrupted with say 4 lines with spaces.  At that point the config tells the person trying to load it is corrupt and won't push.  Then that same person then gets frustrated and shoves those added lines into the switch with config with the spaces attached.

Just a theory, we will see how Good it is tomorrow



Offline bhusebye

  • Rookie
  • **
  • Posts: 12
Re: White spaces and command line
« Reply #2 on: December 31, 2014, 05:54:56 PM »
The 470s are adding the spaces into the ends of certain lines themselves, vlans in particular.  At command line a space at the end of a line is a registered character.  I  know someone rebuilt the switch stack in question from the corrupted ascii file by pasting line by line.  I did a download of an ascii on a fresh config I built by hand, then used notepad++ to trim leading and trailing white spaces, did a save as version 2.  Then used notepad++ to compare and they show up.  Someone mentioned exam diff at work, doubted me, exam diff doesn't show white space leading or trailing.

Once again I had to prove myself.   Crime scene photos, fingerprints, secret recorded conversations and evil trailing white spaces.  If you select a whole line in ascii to load via command line your potentially  adding white spaces to lines that already have them.   And that switch that was rebuilt from the corrupted ascii, the login prompt is screwed up because of these spaces I mention.  Copy and paste from first character to last only.

Case closed

Offline bhusebye

  • Rookie
  • **
  • Posts: 12
Re: White spaces and command line
« Reply #3 on: January 06, 2015, 01:46:45 PM »
More testing done today.  The spaces from Ascii do not move nor will they propagate when added back in by cutting and pasting an entire line.  They can be ignored, so its a non issue.  No one could tell me why they are there or added.