Mailing List Archive: Non-cisco gear?

Non-cisco gear?

Jun 14, 2005, 1:21 PM

Post #1 of 3 (450 views)

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?

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)

Non-cisco gear? [ In reply to ]

heas at shrubbery

Jun 14, 2005, 2:03 PM

Post #2 of 3 (450 views)

Permalink

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)
>

Non-cisco gear? [ In reply to ]

michael at halligan

Jun 14, 2005, 2:11 PM

Post #3 of 3 (450 views)

Permalink

2.3.2a seems to be somewhat broken in it's make process :

invalid command name "@INCLUDE"
while executing
"@INCLUDE login.top@"
(file "/home/rancid/bin/nlogin" line
34)

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