Changing banners with NetConfig

[raymond.lucas]

I am trying to create an IOS user template with NetConfig. I am importing the config from a file.

If the config contains a "banner exec", any job pushing this out fails with a "CLI Output - FAILURE" message.

Have others experienced this problem? Have others worked around this problem?

[steve.busby]

If you're creating a Template, ensure your command is as follows:

banner exec "Sample Text"

This works on a W2K/RME 3.5/IDU 9.0 system. I used the existing banner template, plus I created my own using the command above. Both worked flawlessly.

What OS, RME, IDU versions are you running?

[raymond.lucas]

I am just importing the configuration from a text file. The text file can be successfully tftp'ed to the running config of the device so the commands are right.

We are using SunOS 5.8/RME 3.5/IDU 11. I have tried it on earlier IDU's with the same result.

Using the banner template does work for me, but I can't save that to use later which is what I want.

Thanks for your time.

[pvanvuuren]

Hi there

I've had the exact same problem awhile ago. I also tried everything: installed newer IDU's , changed the banner format. No luck. Reading your message confirms that it might be a RME bug.

I will be watching this space for any news.

[steve.busby]

Raymond,

I'd be interested in seeing all the lines for a particular failed device, can you post those? Also, what type of device(s) are you trying to update?

Steve

[raymond.lucas]

The devices are a mix of 7200 on 12.1E, 3600 and 2600 on late 12.2T. IP Plus 3DES images.

Here is a (very simplified) example of the sort of config I'm trying to push (with the === bits :)

=======================

ntp server 1.1.1.1

banner exec "

----------

| Test |

----------

"

no ip http server

=======================

This is in a file on the CW server. I create a User Template (Type=IOS, mode=Config) and import from a file. Once saved, I create a job. Whenever displayed, the config looks correct. When the job finishes with Status: Failed, the only output is:

ntp server 1.1.1.1

test(config)#

PARTIALFAILURE

Via experiment, I know it is only the banner command that causes a problem. The transport is configured to use SSH, Telnet, TFTP. RCP is disabled. In this example telnet is actually used.

A tcpdump of the traffic shows the ntp command sent and responded to fine, the banner exec " part of the command is sent, the router responds as you would expect with:

Enter TEXT message. End with the character '"'.

The server then waits just over a minute and sends a logout command.

When you do a job using the provided Banner template bu contrast, the banner is sent as one long string. Which works fine.

So I guess it's different control characters being used to indicate the CR between the two methods that lets one work and the other not. Sigh.

And yes, I would open a TAC case, but we don't have cover for our Cisco software unfortunately.

Whew... that turned out quite long!