Discussion:
[rancid] Rancid-discuss Digest, Vol 55, Issue 13
alq16
2015-05-17 07:26:50 UTC
Permalink
Hi All,

I have some questions with today's topic 1.System Up Time & Dell (JC)

For Dell devices & F5,cloginrc is ok but failed to get the config.

Shall I edit the file rancid.types.conf?

And also,where can I find the website for all past topics,especially for Huawei switches?

Also Rancid log is missing in my system,(although previously existing),is it forwarded to somewhere else?
rancid-3.1-2.el6.x86_64
sh -x path-to/rancid-run
+ for GROUP in '$LIST_OF_GROUPS'
+ LOCKFILE=/tmp/.ES19F.run.lock
++ date +%Y%m%d.%H%M%S
+ for GROUP in '$LIST_OF_GROUPS'
+ LOCKFILE=/tmp/.ES21F.run.lock
++ date +%Y%m%d.%H%M%S
+ for GROUP in '$LIST_OF_GROUPS'
+ LOCKFILE=/tmp/.MI31F.run.lock
++ date +%Y%m%d.%H%M%S
+ for GROUP in '$LIST_OF_GROUPS'
+ LOCKFILE=/tmp/.MI32F.run.lock
++ date +%Y%m%d.%H%M%S
+ for GROUP in '$LIST_OF_GROUPS'
+ LOCKFILE=/tmp/.HKDR-site.run.lock
++ date +%Y%m%d.%H%M%S
+ for GROUP in '$LIST_OF_GROUPS'
+ LOCKFILE=/tmp/.Remote-site.run.lock
++ date +%Y%m%d.%H%M%S
2015-05-17



alq16



发件人rancid-discuss-***@shrubbery.net
发送时闎2015-05-17 04:00
䞻题Rancid-discuss Digest, Vol 55, Issue 13
收件人"rancid-discuss"<rancid-***@shrubbery.net>
抄送

Send Rancid-discuss mailing list submissions to
rancid-***@shrubbery.net

To subscribe or unsubscribe via the World Wide Web, visit
http://www.shrubbery.net/mailman/listinfo/rancid-discuss
or, via email, send a message with subject or body 'help' to
rancid-discuss-***@shrubbery.net

You can reach the person managing the list at
rancid-discuss-***@shrubbery.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Rancid-discuss digest..."


Today's Topics:

1. Re: System Up Time & Dell (JC)
2. Re: As one door closes, another opens... ssh failing with
(some) Cisco devices after OS upgrade? (Howard Jones)
3. Re: xlogin possible unbalanced brace in comment (martyMusto)


----------------------------------------------------------------------

Message: 1
Date: Sat, 16 May 2015 02:26:32 +0000 (UTC)
From: JC <***@yahoo.com>
To: "rancid-***@shrubbery.net" <rancid-***@shrubbery.net>
Subject: Re: [rancid] System Up Time & Dell
Message-ID:
<***@mail.yahoo.com>
Content-Type: text/plain; charset=UTF-8

I've gotten a little further in my hopes of getting these Dell powerconnect switches backed up w/o the up time creating diffs each run.

I added the rancid.types.conf with what's below.
test;login;dlogin
test;module;drancid
test;inloop;ios::inloop
test;command;ShowVersion;show version

When I run the command below it generates the following errors.
[***@ALVMANL01 etc]$ /usr/local/rancid/bin/rancid -d -t test ukbswid05
loadtype: device type test
loadtype: found device type test in /usr/local/rancid/etc/rancid.types.conf
ukbswid05: missed cmd(s): show system,show vlan,show version,show running-config
found_end = 0, clean_run = 0
ukbswid05: End of run not found
!
write(spawn_id=1): broken pipe
while executing
"send_user "$router\n""
("foreach" body line 3)
invoked from within
"foreach router [lrange $argv $i end] {
set router [string tolower $router]
send_user "$router\n"

# device timeout
set timeout [find t..."
(file "/usr/local/rancid/bin/dlogin" line 509)
ukbswid05: missed cmd(s): all commands
ukbswid05: End of run not found

Am I on the right path or even more screwed up than before?

Thanks for the look.

-John


------------------------------

Message: 2
Date: Sat, 16 May 2015 11:08:08 +0100
From: Howard Jones <***@thingy.com>
To: rancid-***@shrubbery.net
Subject: Re: [rancid] As one door closes, another opens... ssh failing
with (some) Cisco devices after OS upgrade?
Message-ID: <***@thingy.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
This seems to be to do with a new lower key size restriction in newer
openssh version - does anyone know a way around it? Ideally without
regenerating the keys on the routers? In fact, I just tried
regenerating a 2048-bit key on one of the affected routers, and it
makes no difference anyway.
I "resolved" my issue for now by installing a copy of openssh 4.9 in
/opt and using sshcmd for the affected devices - a selection of ASRs and
ISRs, but not all. I'd still be interested in what the real fix is
though! Evidently those specific devices don't meet some minimum
standard that the openssh folks enforce.

Cheers,

Howard


------------------------------

Message: 3
Date: Thu, 14 May 2015 10:03:51 -0600
From: martyMusto <***@gmail.com>
To: Rancid-***@shrubbery.net
Cc: ***@shrubbery.net
Subject: Re: [rancid] xlogin possible unbalanced brace in comment
Message-ID:
<CAJwGz88V3zsSWBVPV5puqm+VOHeU1RVK99ErdLeoiGgbvMgT=***@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Just wanted to update the list before my mind melts from getting this
working...

If the password of your device in cloginrc contains curly braces, the curly
brace password escaping mechanism will break causing clogin and or nlogin
to fail with the aforementioned expect error.

-Marty
Hello All,
I am receiving an error on both new(v3.2) and old(v2.3) unmodified RANCID
nlogin and clogin.
"Error: missing close-brace: possible unbalanced brace in comment"
I am running expect 5.45 and Tcl 8.6.
I haven't had a chance to test but I believe I need expect 5.43 and Tcl
8.4 (per shrubbery FTP) to get these scripts running without error.
I didn't see anything of the forums or site about avoiding expect 5.45.
The site only mentions you must use expect >=5.40 with latest RANCID 3.2.
Going to try the shrubbery patched expect+Tcl tomorrow.
Figured it would be worth it to post this.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.shrubbery.net/pipermail/rancid-discuss/attachments/20150514/b6425dd1/attachment-0001.html>

------------------------------

Subject: Digest Footer

_______________________________________________
Rancid-discuss mailing list
Rancid-***@shrubbery.net
http://www.shrubbery.net/mailman/listinfo/rancid-discuss

------------------------------

End of Rancid-discuss Digest, Vol 55, Issue 13
**********************************************

Loading...