[rancid] Re: Nortel Alteons (UNCLASSIFIED)

[Roeun, Don T Mr CTR USA HRC]

Classification:  UNCLASSIFIED 
Caveats: NONE

Thanks for chiming in John.  You're right, I'm using 2.3.2 + expect
5.40.  Should I upgrade rancid in addition to the expect patch? I
checked this morning and everything went through, although I didn't make
any changes.  Thanks for the help from everyone.



-----Original Message-----
From: john heasley [mailto:heas at shrubbery.net] 
Sent: Thursday, July 23, 2009 1:42 PM
To: Ryan West
Cc: Roeun, Don T Mr CTR USA HRC; rancid-discuss at shrubbery.net
Subject: Re: [rancid] Re: Nortel Alteons (UNCLASSIFIED)

Thu, Jul 23, 2009 at 12:11:16PM -0400, Ryan West:
> Hey Don.  Long time, how is everything?
> 
> Does it work every time if it's called from 'rancid-run -r <devname>'.
I have the same issue going on with an F5.  Is the config substantially
larger on those two Alteon boxes?

you must be using rancid 2.3.2.

if you have solaris or linux and are using expect 5.40 or newer, you
must use the expect patch/hack from
http://www.shrubbery.net/rancid/#osystems.
if you have inconsistent behavior, dollars to donuts this is your
problem.

after that/those issues; if you still have failures, then look at the
log file for the group(s) with problems and resolve any errors that
appear there and see the FAQ for typical errors, fixes and tests.

if you still have failures, post here and include the log msgs for the
group, output of your *login test as described in section 3 of the faq,
and any other useful o/p you have from testing.

.cloginrc is used by all of the scripts.  see clogin(1) and cloginrc(5).

rancid-run -r won't produce output unless there is an error in the
script itself.  otherwise, its just like running rancid-run, it just
processes the single device specified in -r's argument, diffs are sent
and a log file is created.

> -ryan
> 
> From: rancid-discuss-bounces at shrubbery.net 
> [mailto:rancid-discuss-bounces at shrubbery.net] On Behalf Of Roeun, Don 
> T Mr CTR USA HRC
> Sent: Thursday, July 23, 2009 10:07 AM
> To: rancid-discuss at shrubbery.net
> Subject: [rancid] Nortel Alteons (UNCLASSIFIED)
> 
> 
> Classification:  UNCLASSIFIED
> Caveats: NONE
> 
> 
> We have a total of 14 Nortel Alteons, and clogin fails on a couple of
them.  I tried testing with bin/clogin 5x in a row and it is hit or
miss, sometimes it works and sometimes it doesn't.  I can see the
username get filled in but not the password.  When it fails with clogin,
I can always connect straight to the device from the rancid box outside
of clogin using the same credentials.  I tested it 5 times on a single
device & it worked once or twice.  This is only happening on 2 of the 14
Alteons that we have.  Any thoughts?
> 
> cloginrc:
> 
> #Alteons#
> 
> add user a184-* {password}
> 
> add userprompt a184-* {"Enter radius username"}
> 
> add userpassword a184-* {password}
> 
> add passprompt a184-* {"Enter radius password"}
> 
> log:
> 
> a184-dmz13: missed cmd(s): /info/sys,/cfg/dump
> 
> > a184-dmz13: End of run not found
> 
> > /*
> 
> > a184-dmz14: missed cmd(s): /info/sys,/cfg/dump
> 
> > a184-dmz14: End of run not found
> 
> 
> 
> Classification:  UNCLASSIFIED
> Caveats: NONE

> _______________________________________________
> Rancid-discuss mailing list
> Rancid-discuss at shrubbery.net
> http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss
Classification:  UNCLASSIFIED 
Caveats: NONE