Larry,
I'm running Rancid against 2950's with SSH no problem. Can you send over parts of your config for me to cross check. I would paste mine but the switch I'm thinking about is off right now because it's getting installed tomorrow :)
Cheers,
Christopher DeRemer, CCENT
Network Administrator
Phoebe Services
484.619.2168 (Single # Reach)
From: rancid-discuss-***@shrubbery.net [mailto:rancid-discuss-***@shrubbery.net] On Behalf Of Kemp, Larry
Sent: Thursday, February 11, 2010 1:04 PM
To: 'Jose Madrid'
Cc: rancid
Subject: [rancid] Re: Increasing Timeout For RANCID
Jose - Thanks to you and all. My company took over a smaller company and the admin duties for some smaller older Cisco devices. I increased the timeout from a value of 45 to 100 and it still did not work via ssh. I zeroized my keys and generated new ones on the Cisco gear, I also checked that "transport input ssh" was there in my vty lines; still no dice. Rancid is backing up these devices fine via telnet but errors out when switched to ssh. I think it is most likely a software revision issue on these smaller older Cisco devices. Thanks again!
LK
From: Jose Madrid [mailto:***@gmail.com]
Sent: Thursday, February 11, 2010 12:06 PM
To: Kemp, Larry
Cc: Brian Lam; rancid
Subject: Re: [rancid] Re: Increasing Timeout For RANCID
Larry,
Take a look at bin/clogin on line 80. Mine sets the timeout to 45 seconds. Maybe you want to extend this??
# Sometimes routers take awhile to answer (the default is 10 sec)
set timeout 45
2010/2/10 Kemp, Larry <***@usmetrotel.com<mailto:***@usmetrotel.com>>
I appreciate your help very much. I found something that sounds familiar here in the archives: http://www.shrubbery.net/pipermail/rancid-discuss/2007-October/002540.html
I am in a bit over my head if I have to "pass a parameter" as you say, or as this link above discusses "modify clogin". Not sure exactly how I would do either; could you please be more specific in what I need to do. Thanks again.
LK
From: Brian Lam [mailto:***@rockyou.com<mailto:***@rockyou.com>]
Sent: Tuesday, February 09, 2010 9:03 PM
To: Kemp, Larry
Cc: rancid
Subject: Re: [rancid] Increasing Timeout For RANCID
looks like you should pass it as a parameter instead of modifying clogin...
2010/2/9 Kemp, Larry <***@usmetrotel.com<mailto:***@usmetrotel.com>>
I have some Cisco 2950's that I need RANCID to reach via SSH. Each time rancid-run executes (either manually by me or via the cron) I see in the log that there is a clogin error for these devices. I am able to manually login by entering: "ssh ***@172.20.30.1<mailto:***@172.20.30.1>" as user rancid. I am able to login to these devices and then enter my enable password and run privledged commands, however to reach a password prompt takes a good 7 seconds because of how me have to route to these devices. The devices are also small and contain little memory.
I read here: http://www.shrubbery.net/rancid/man/clogin.1.html about the -t option to increase the time that Rancid waits before erroring out waiting for a login prompt. I also looked in the /usr/local/rancid/bin/clogin file to see if there was a place for me to increase this timeout limit. I am not sure if this is where I need to edit. Can anyone that has done this before point me in the right direction to increase the login timeout.
[cid:***@01CAAB53.C05399A0]
_______________________________________________
Rancid-discuss mailing list
Rancid-***@shrubbery.net<mailto:Rancid-***@shrubbery.net>
http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss
_______________________________________________
Rancid-discuss mailing list
Rancid-***@shrubbery.net<mailto:Rancid-***@shrubbery.net>
http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss
--
It has to start somewhere, it has to start sometime. What better place than here? What better time than now?
________________________________
NOTICE: This confidential message/attachment contains information intended for a specific individual(s). Any inappropriate use, distribution or duplication is strictly prohibited. If received in error, notify the sender and immediately delete this transmission.