[rancid] Re: Rancid with Fortigate Devices?

john heasley heas at shrubbery.net
Mon Apr 20 16:25:09 UTC 2009


Mon, Apr 20, 2009 at 09:32:58AM -0400, Mina Eskander:
> 
> I ran the commanded and here is the output:
> 
> [rancid at pwcolocacti ~]$ nlogin -t 90 -c"get system status;get conf" pwcolofgt100c
> pwcolofgt100c
> spawn ssh -c 3des -x -l meskander pwcolofgt100c
> meskander at pwcolofgt100c's password:
> FGT100C3G0860259~ $
> Error: TIMEOUT reached
> 
> I think ive seen this before, it looks like rancid does not recognize the prompt, what do you think?

probably.  try it with the -d option

> -----Original Message-----
> From: john heasley [mailto:heas at shrubbery.net]
> Sent: Thursday, April 16, 2009 2:24 PM
> To: Mina Eskander
> Cc: rancid-discuss at shrubbery.net
> Subject: Re: [rancid] Re: Rancid with Fortigate Devices?
> 
> Thu, Apr 16, 2009 at 11:38:45AM -0400, Mina Eskander:
> > Has anybody made progress with this?
> > I set up a new rancid server and did a fnrancid with the following output.
> >
> > [rancid at pwcolocacti ~]$ bin/fnrancid -d pwcolofgt100c
> > executing nlogin -t 90 -c"get system status;get conf" pwcolofgt100c
> > pwcolofgt100c nlogin error: Error: TIMEOUT reached
> > pwcolofgt100c nlogin error: Error: TIMEOUT reached
> > pwcolofgt100c: missed cmd(s): get conf,get system status
> > pwcolofgt100c: missed cmd(s): get conf,get system status
> > 0: found end
> > pwcolofgt100c: End of run not found
> > pwcolofgt100c: End of run not found
> >
> > not really sure if it's because of a regex problem or the commands or what, I would appreciate any help with this.
> 
> first step should always be to make sure that the expect script is working.
> what does
> nlogin -t 90 -c"get system status;get conf" pwcolofgt100c
> o/p?
> 
> > Network Security | Disaster Recovery | Business Continuity | IT Projects | Application Development
> 
> what is 'business continuity'?


More information about the Rancid-discuss mailing list