[rancid] Re: Issues getting Rancid to Back up the JuniperMX960.

[Elliott, Andrew]

> > > -----Original Message-----
> > > From: john heasley [mailto:heas at shrubbery.net]
> > > Sent: Monday, June 01, 2009 1:06 PM
> > > To: Elliott, Andrew
> > > Cc: Rowe, William; rancid-discuss at shrubbery.net
> > > Subject: Re: [rancid] Re: Issues getting Rancid to Back up the
> > > JuniperMX960.
> > >
> > > Mon, Jun 01, 2009 at 12:39:16PM -0400, Elliott, Andrew:
> > > > I think we were able to find the problem.
> > > >
> > > >
> > > >
> > > > The routers have very large configurations and when I ran jlogin
> > > > manually, I saw that it was timing out about 90% of the way
> through
> > > the
> > > > configuration output.  The point at which it timed out varied
> > > slightly
> > > > every time I ran it.
> > > >
> > >
> > > I think you have some other problem and this fix is going to fail
> in
> > > the
> > > future/randomly.
> > >
> > > What do you mean by 'timed out'?  did it hang?  did jlogin/expect
> exit
> > > with a
> > > timeout error?  if you run the command manually,
> > > 	NOPIPE=YES; export NOPIPE
> > > 	jlogin -c 'show version;...' host
> > > what is at the end of the host.raw file?
> > >
> >
> > Jlogin just hangs until it times out.
> >
> > The log shows the following for each of the routers that are
> failing(I
> > changed the router name):
> 
> Are you using Linux or Solaris and haven't applied the expect patch
> available on the rancid website?
> 
> Have you tried the cmdline?
> NOPIPE=YES; export NOPIPE
> jlogin -c 'show chassis clocks;show chassis environment;show chassis
> firmware;show chassis fpc detail;show chassis hardware detail;show
> chassis routing-engine;show chassis scb;show chassis sfm detail;show
> chassis ssb;show chassis feb detail;show chassis feb;show chassis
> cfeb;show chassis alarms;show system license;show system boot-
> messages;show system core-dumps;show version detail;show
configuration'
> host
> 
> and if that fails jlogin -d -c ....
> 

Yes, I have been running it from the command line.

The -d switch is failing for me:

stlrvrpol0> ./jlogin -d -c 'show chassis clocks;show chassis
environment;show chassis firmware;show chassis fpc detail;show chassis
hardware detail;show chassis routing-engine;show chassis scb;show
chassis sfm detail;show chassis ssb;show chassis feb;show chassis
cfeb;show chassis alarms;show system boot-messages;show version
detail;show configuration' rtr1.city-st


Error: Unknown argument! -d
Usage: ./jlogin [-c command] [-Evar=x] [-f cloginrc-file]  [-p
user-password] [-r passphrase] [-s script-file]  [-u username] [-t
timeout] [-x command-file] [-y ssh_cypher_type]  router [router...]
stlrvrpol0>


stlrvrpol0> uname -a
SunOS stlrvrpol0 5.8 Generic_117350-43 sun4u sparc SUNW,Ultra-Enterprise
stlrvrpol0> expect -v
expect version 5.31.5
stlrvrpol0> ssh -V
OpenSSH_4.7p1, OpenSSL 0.9.8e 23 Feb 2007
stlrvrpol0>

Due to specific restrictions within the organization, I will have an
extremely difficult time getting approval for the patched version of
expect to be compiled.  Is the issue still present in 5.43?  I would
have a much easier time getting the expect upgraded to the latest
official version than getting a patched one installed.


> > cp: cannot access rtr1.city-st.raw
> > rtr1.city-st jlogin error: Error: TIMEOUT reached
> > rtr1.city-st: End of run not found
> >
> >
> > > >
> > > > To correct the issue, I added compression to ssh to get the
> > data-rate
> > > to
> > > > slow down a bit:
> > > >
> > > >
> > > >
> > > > stlrvrpol0> grep "\-C" jlogin
> > > >
> > > >         -C* {
> > > >
> > > >                 if [ catch {spawn $sshcmd -C -c $cyphertype -x
-l
> > > $user
> > > > -i $identfile $router} reason ] {
> > > >
> > > >                 if [ catch {spawn $sshcmd -C -c $cyphertype -x
-l
> > > $user
> > > > $router} reason ] {
> > > >
> > > > stlrvrpol0>
> > > >
> > > >
> > > >
> > > > -andrew
> > > >
> > > >
> > > >
> > > > From: rancid-discuss-bounces at shrubbery.net
> > > > [mailto:rancid-discuss-bounces at shrubbery.net] On Behalf Of Rowe,
> > > William
> > > > Sent: Monday, June 01, 2009 10:37 AM
> > > > To: rancid-discuss at shrubbery.net
> > > > Subject: [rancid] Issues getting Rancid to Back up the Juniper
> > MX960.
> > > >
> > > >
> > > >
> > > > Has anyone else encountered issues backing up the Juniper MX960
> with
> > > > Rancid.
> > > >
> > > > Any insight is appreciated.
> > > >
> > > >
> > > >
> > > > Bill
> > > >
> > >
> > > > _______________________________________________
> > > > Rancid-discuss mailing list
> > > > Rancid-discuss at shrubbery.net
> > > > http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss
> >