Success with 2.3.1 (Re: Non-cisco gear?)
Michael T. Halligan
michael at halligan.org
Tue Jun 14 23:00:31 UTC 2005
John,
I've got it all working now with 2.3.1 after fixing nrancid.in, and
using Joshua's change to nlogin. Here's
my patch for nrancid.in
*** rancid-2.3.1/bin/nrancid.in.orig 2005-06-14 15:28:19.000000000 -0700
--- rancid-2.3.1/bin/nrancid.in.new 2005-06-14 15:29:02.000000000 -0700
***************
*** 198,203 ****
--- 198,204 ----
"!set admin user $1 password <removed> privilege $3\n");
next;
ProcessHistory("","","","$_");
+ }
}
$found_end=1;
return(1);
john heasley wrote:
>Tue, Jun 14, 2005 at 02:21:08PM -0700, Michael T. Halligan:
>
>
>>I'm trying to use Rancid on some netscreens and am running into some
>>problems. None of the documentation I've seen really addresses
>>configuration for non-cisco
>>devices. For example, do all add password statements go into .cloginrc,
>>or would something for a netscreen go into .nloginrc?
>>
>>
>
>All passwords go in ~/.cloginrc. Please try rancid-2.3.2a.tar.gz, with the
>replacement nlogin rancid-2.3.2a.nlogin.in. I think the netscreen handling
>has been fixed.
>
>
>
>>The error I'm seeing is:
>>
>>gate-1(B)-> can't read "enable": no such variable
>> while executing
>>"if { $enable } {
>> if {[do_enable $enauser $enapasswd]} {
>> if { $do_command || $do_script } {
>> close; wait
>> continue
>> }
>> }
>> }"
>> ("foreach" body line 66)
>> invoked from within
>>"foreach firewall [lrange $argv $i end] {
>> set firewall [string tolower $firewall]
>> send_user "$firewall\n"
>>
>> set prompt ">"
>>
>> # Figure out..."
>> (file "/home/rancid/bin/nlogin" line 423)
>>
>>
>>
--
-------------------
BitPusher, LLC
http://www.bitpusher.com/
1.888.9PUSHER
(415) 724.7998 - Mobile
More information about the Rancid-discuss
mailing list