[rancid] Wildcards in banner potentially causing issue

[Shapery, Steve]

So I have rancid running, trying to collect configs from Cisco routers,
and it works dandy if I do a command-line clogin with the full commands.



clogin -t 90 -c "show run" router1



however, if I run it through the rancid-run script, I get odd errors and
it doesn't seem to work.



The only thing I can think of is that the login banners have & * ' and &
in them.



Does anyone know if I have to somehow escape those out, or do something
to force the rancid script to ignore the special characters?





Thanks.










_________________________________________________

This message is for the designated recipient only and may contain privileged, proprietary
or otherwise private information. If you have received it in error, please notify the sender
immediately and delete the original. Any other use of the email by you is prohibited.

Dansk - Deutsch - Espanol - Francais - Italiano - Japanese - Nederlands - Norsk - Portuguese
Svenska: www.cardinalhealth.com/legal/email

[Ed Ravin]

Post by Shapery, Steve
So I have rancid running, trying to collect configs from Cisco routers,
and it works dandy if I do a command-line clogin with the full commands.
clogin -t 90 -c "show run" router1
however, if I run it through the rancid-run script, I get odd errors
and it doesn't seem to work.
The only thing I can think of is that the login banners have & * ` and
& in them.
Does anyone know if I have to somehow escape those out, or do something
to force the rancid script to ignore the special characters?

The RANCID FAQ ( http://www.shrubbery.net/rancid/FAQ ) says:

Q. Are there any characters in the banner that rancid has problems with OR
I changed the device's command prompt and now collection is failing?

A. The trickiest part about clogin (et al) is recognizing the prompt
correctly. clogin looks for '>' and '#' to figure out if it is logged
in or in enable mode. So if you have a '>' or '#' in your login banner
(or other motd), then clogin gets all confused and will not be able to log
in correctly, and thus rancid will fail.

Don't use '>' or '#' in your prompt or in your banner or other motd.

Suggest you go through the FAQ and see if that warning or any
other section in there applies to you. If you can't fix it, come back
here and post the exact text of the "odd errors" that you're getting.

[Shapery, Steve]

The devices were responding properly to a clogin -c 'command' but not to
the rancid-run script.

After digging and digging, it turned out that if I removed the 'show
version' section of the rancid script, that it successfully ran.

The devices are standard 3845's, with no unusual mods... so I have no
idea.

Oh well, at least it works now.

-S



-----Original Message-----
From: Ed Ravin [mailto:***@panix.com]
Sent: Saturday, February 23, 2008 5:25 PM
To: Shapery, Steve
Cc: rancid-***@shrubbery.net
Subject: Re: [rancid] Wildcards in banner potentially causing issue

Post by Shapery, Steve
So I have rancid running, trying to collect configs from Cisco routers,
and it works dandy if I do a command-line clogin with the full commands.
clogin -t 90 -c "show run" router1
however, if I run it through the rancid-run script, I get odd errors
and it doesn't seem to work.
The only thing I can think of is that the login banners have & * ` and
& in them.
Does anyone know if I have to somehow escape those out, or do something
to force the rancid script to ignore the special characters?

The RANCID FAQ ( http://www.shrubbery.net/rancid/FAQ ) says:

Q. Are there any characters in the banner that rancid has problems with
OR
I changed the device's command prompt and now collection is failing?

A. The trickiest part about clogin (et al) is recognizing the prompt
correctly. clogin looks for '>' and '#' to figure out if it is
logged
in or in enable mode. So if you have a '>' or '#' in your login
banner
(or other motd), then clogin gets all confused and will not be able
to log
in correctly, and thus rancid will fail.

Don't use '>' or '#' in your prompt or in your banner or other motd.

Suggest you go through the FAQ and see if that warning or any
other section in there applies to you. If you can't fix it, come back
here and post the exact text of the "odd errors" that you're getting.



_________________________________________________

This message is for the designated recipient only and may contain privileged, proprietary
or otherwise private information. If you have received it in error, please notify the sender
immediately and delete the original. Any other use of the email by you is prohibited.

Dansk - Deutsch - Espanol - Francais - Italiano - Japanese - Nederlands - Norsk - Portuguese
Svenska: www.cardinalhealth.com/legal/email