This doesn't seem to fix the problem for me, I've tried putting the "^" in several places and it still double spaces the banner. Anyone find a solution for this?
I also had to deploy an extremely long banner and I was having the same issue. I was able to fix the issue by using Command Script Variables. If you insert a carriage return variable instead of using separate lines in the script it should deliver the banner properly. So in your example you can use the following instead:
THIS IS A DOD COMPUTER SYSTEM. BEFORE PROCESSING CLASSIFIED${CRLF}INFORMATION, CHECK THE SECURITY ACCREDITATION LEVEL OF THIS SYSTEM.
The result of which will be the string of text on two separate lines without the double spacing.
Something similar happened to me quite a while back while pushing configuration changes with a terminal emulator. The fix for me was choosing a different emulation (vt52 in this case). If your sending and receiving emulations aren't the same, you could be sending something to your switch that it is interpreting as 2 line feeds instead of a carriage return and a line feed.
I can't even get a login banner to work through NCM.
Okay I take that back... it only takes about 30 seconds per line... so 150 devices... awesome!
EDIT: Okay, changing the Telnet/SSH Prompt Timeout to 5 seconds made each line appear after 5 seconds. Why does it do this? It's a simple paste...
Can you please open a support ticket on this one and reference reproduction steps in your post? We'll need to try to reproduce in house to figure out what's going on.
Hi Chris,
I'm seeing a similar issue while trying to upload a long banner. Even when using Command script variables such as ${CR} and ${CRLF} I still can't get more than a few words per line.
I ran Wire shark to see if I could spot anything with the transmission of the data but nothing obvious popped up. The only thing I saw which may or may not be contributing to the issue is that all the commands are echoed by the device being uploaded to. This is what I would expect to see if I was typing in the commands through a terminal window, but it might not be needed for the way that NCM uploads the data.
To be honest I'm clutching at straws here because I don't really know what's happening. Will I go ahead and raise a ticket as well?
I also had to deploy an extremely long banner and I was having the same issue. I was able to fix the issue by using Command Script Variables. If you insert a carriage return variable instead of using separate lines in the script it should deliver the banner properly. So in your example you can use the following instead:THIS IS A DOD COMPUTER SYSTEM. BEFORE PROCESSING CLASSIFIED${CRLF}INFORMATION, CHECK THE SECURITY ACCREDITATION LEVEL OF THIS SYSTEM.The result of which will be the string of text on two separate lines without the double spacing.
Heh... why was this suggested as an answer? It doesn't even mention the source of the problem, let alone a resolution :P
While this does not pertain to your scripting issue, I found that if you use putty rather than that pile of shite known as hyperterminal via serial, it does not exhibit the duplicated line feeds issue.
Both hyperterminal and realterm borked it badly. Don't know why this happens. I suppose it could be an IOS issue, as I tried change cr/lfs to lf's, cr's, etc all to no avail.
