Change output format with SED - cannot get rid of CR/LF
 

All,

I am trying to parse the output of a router command with script. It works most of the time as this is the output format:

If the first column is too wide the router adds some non-printable characters and spaces:

I tried with SED to replace the CR/LF/spaces sequence but was unsuccesful so far. Instead of the above I want this:

Any ideas on how to accomplish this?

Thanks,

Phil

Shouldn't be too hard - are you sure there isn't a newline in there as well ?. sed is a stream editor - newlines mess with it.

tr and sed to break lines and format output
 

Phil:


If you can give me the command that you are using, may be I can do better than what I have done to help you. I copied your command's output to a file:

and then did this:

So, I broke down all the input into single line containing of words/fields (see tr command above) and then broke them apart (see sed command above) to get the desired output as shown above.

Does that help you? (I am assuming that your lines with "Se". We can use the last field also that contains 10M/K etc.)

Cheers!

Well this is what I see when I show non-printable characters with cat:
When pasting the result in Notepad++ it shows a CR and and LF afterwards. I am not sure how to capture what it is exactly in a syntax that is suitable for sed.

The tr did not work; if I append that to my script (./myscript.sh 10.11.12.13 | tr '\n' ' ') then the output is empty...
Anyway, the lines can start with all sort of things (Se/Fe/GigE/...) and the last field can be any number or end with M or K as well... I guess it would be easier to replace the obsolete spaces in the output?
I am willing to share the script itself but it is a TCL script logging on to a router and issueing a command so not really necessary to show.

Thanks for the help so far!

Philip:

Try this:

My shift is over! I will check it later on. Can you share the router command you are using?

I would be checking your router command to as normally you can tell it to not split over lines.

@ devUnix:
This is the script:
I think that the main problem is that tr does not give a result, see the difference:



@grail: I am not aware of a Cisco router command like that but that would solve my issue ofcourse; if you can find it I am more than interested!

In the future it might be advisable to tell us you are using expect, telnet and then sending a cisco command (all of which may have some impact) and then finally that you are connecting
in a Windows interface, which of course use \n\r instead of just \n.

So maybe something like: