From ted at cw.net Sun Jun 1 00:22:59 2003 From: ted at cw.net (Ted Bedwell) Date: Sat, 31 May 2003 20:22:59 -0400 Subject: False unreachable? Message-ID: <00cc01c327d3$f4cc0560$6601a8c0@mozart> Hi all, I've have rancid running on 300+ devices. I have a few however claim that they are unreachable. I get the: "The following routers have not been successfully contacted for more than 4 hours" email on every polling cycle. The logs state: "my.device clogin error: Error: Connection Refused (telnet)" However, I can clogin just fine from the command line. Any ideas where I can being investigating this further? Thanks, ~~ted From jlewis at lewis.org Sun Jun 1 02:07:12 2003 From: jlewis at lewis.org (jlewis at lewis.org) Date: Sat, 31 May 2003 22:07:12 -0400 (EDT) Subject: False unreachable? In-Reply-To: <00cc01c327d3$f4cc0560$6601a8c0@mozart> Message-ID: On Sat, 31 May 2003, Ted Bedwell wrote: > Hi all, > I've have rancid running on 300+ devices. I have a few however claim that they are unreachable. I get the: > > "The following routers have not been successfully contacted for more > than 4 hours" > > email on every polling cycle. The logs state: > > "my.device clogin error: Error: Connection Refused (telnet)" Is it possible at the instant rancid failed, the device was out of vty interfaces? ---------------------------------------------------------------------- Jon Lewis *jlewis at lewis.org*| I route System Administrator | therefore you are Atlantic Net | _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________ From georg.naggies at rizit.at Mon Jun 2 13:46:44 2003 From: georg.naggies at rizit.at (georg.naggies at rizit.at) Date: Mon, 2 Jun 2003 15:46:44 +0200 Subject: how to make rancid ignore password string changes Message-ID: Hello! Thanks for the suggestions. As a quick fix in the meantime, I have mucked with the code of "rancid", in a very crude manner. As an excuse I might cite that I don't know any perl. Don't look if you are of sensitive dispostion, might make you cringe: (Have commented out the " /^ clockrate / && next;" statement, and set the filter_pwds condition to 0, in "if (/^(ntp authentication-key \d+ md5) / && filter_pwds >= 1)" just for the moment. ) Will now look into the cleaner options you suggested. Thanks, Mag. Georg Naggies Raiffeisen Informatik Zentrum GmbH NOC A-1020 Wien, Lilienbrunngasse 7-9, Zimmer 06F Tel: +43-(1)-99398 - 9354 Fax: +43-(1)-99398 - 5501 georg.naggies at rizit.at http://www.rizit.at heas at shrubbery.net Gesendet von: An: georg.naggies at rizit.at owner-rancid-discuss at shrubbery.n Kopie: rancid-discuss at shrubbery.net et Blindkopie: Thema: Re: how to make rancid ignore password string changes 30.05.2003 18:01 Fri, May 30, 2003 at 08:34:41AM +0200, georg.naggies at rizit.at: > Hello! > > I'm quite new to Rancid and love it of course, because for example > CiscoWorks just can't compare in speed and reliability. > > Now I would like to tweak it to its best. > > Therefore one question, ... how to make rancid ignore password string > changes? > > For example the "ntp authentication-key" changes all the time, and this > makes cvs create a new version all the time. I would still like to have the > passwords in the archive. (FILTER_PWDS=NO; export FILTER_PWDS) well, this would require post-cvs diff filtering. one could 1) run a second instance of rancid or the particular group 2) use a filter as the destination of the diff email which filtered things in which you were not interested 3) let users filter what they want via procmail (preferred). eg: someone balked about nvram diffs. .... # /dev/null rancid msgs with no diffs other than nvram: :0 HWi b * Subject: router config diffs$ | awk 'BEGIN{n=0;}{if(/...Flash: nvram:/)next; if(/^[-+]/){n++;}next;}END{exit n;}' From ted at cw.net Mon Jun 2 16:05:49 2003 From: ted at cw.net (Ted Bedwell) Date: Mon, 2 Jun 2003 12:05:49 -0400 Subject: False unreachable? References: Message-ID: <00d401c32920$e7994620$0b01a8c0@tchikovsky> I'm fairly sure this is not the problem. It happens at every polling interval (2 hours) without exception, and always works from the CLI. If it were a vty issue, you would expect it to occasionally go through. Any other ideas? Thanks, ~~ted ----- Original Message ----- From: To: "Ted Bedwell" Cc: Sent: Saturday, May 31, 2003 10:07 PM Subject: Re: False unreachable? > On Sat, 31 May 2003, Ted Bedwell wrote: > > > Hi all, > > I've have rancid running on 300+ devices. I have a few however claim that they are unreachable. I get the: > > > > "The following routers have not been successfully contacted for more > > than 4 hours" > > > > email on every polling cycle. The logs state: > > > > "my.device clogin error: Error: Connection Refused (telnet)" > > Is it possible at the instant rancid failed, the device was out of vty > interfaces? > > ---------------------------------------------------------------------- > Jon Lewis *jlewis at lewis.org*| I route > System Administrator | therefore you are > Atlantic Net | > _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________ > From afort at choqolat.org Tue Jun 3 00:29:02 2003 From: afort at choqolat.org (Andrew Fort) Date: Tue, 3 Jun 2003 10:29:02 +1000 Subject: False unreachable? Message-ID: <20030603002904.112E64ED58@koro.off.connect.com.au> Hi Ted, Can you replicate with, or show us the contents of... export NOPIPE=1 rancid -d my.device You'll have a file called 'my.device.new' in the cwd afterwards, which may shed some more light. -afort >Subject: Re: False unreachable? > From: "Ted Bedwell" > Date: Mon, 2 Jun 2003 12:05:49 -0400 > To: > >I'm fairly sure this is not the problem. It happens at every polling >interval (2 hours) without exception, and always works from the CLI. If it >were a vty issue, you would expect it to occasionally go through. Any other >ideas? > >Thanks, >~~ted > > >----- Original Message ----- >From: >To: "Ted Bedwell" >Cc: >Sent: Saturday, May 31, 2003 10:07 PM >Subject: Re: False unreachable? > > >> On Sat, 31 May 2003, Ted Bedwell wrote: >> >> > Hi all, >> > I've have rancid running on 300+ devices. I have a few however claim >that they are unreachable. I get the: >> > >> > "The following routers have not been successfully contacted for more >> > than 4 hours" >> > >> > email on every polling cycle. The logs state: >> > >> > "my.device clogin error: Error: Connection Refused (telnet)" >> >> Is it possible at the instant rancid failed, the device was out of vty >> interfaces? >> >> ---------------------------------------------------------------------- >> Jon Lewis *jlewis at lewis.org*| I route >> System Administrator | therefore you are >> Atlantic Net | >> _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________ >> From ted at cw.net Tue Jun 3 20:01:13 2003 From: ted at cw.net (Ted Bedwell) Date: Tue, 3 Jun 2003 16:01:13 -0400 Subject: False unreachable? References: <20030603002904.112E64ED58@koro.off.connect.com.au> Message-ID: <012501c32a0a$e2a2b760$3301a8c0@chopin> That worked beautifully. my.devce.new has the config in it. However, it still is not working when the do-diffs runs. ~~ted ----- Original Message ----- From: "Andrew Fort" To: ; Sent: Monday, June 02, 2003 8:29 PM Subject: Re: False unreachable? > Hi Ted, > > Can you replicate with, or show us the contents of... > > export NOPIPE=1 > rancid -d my.device > > You'll have a file called 'my.device.new' in the cwd afterwards, which may shed some more light. > > -afort > > >Subject: Re: False unreachable? > > From: "Ted Bedwell" > > Date: Mon, 2 Jun 2003 12:05:49 -0400 > > To: > > > >I'm fairly sure this is not the problem. It happens at every polling > >interval (2 hours) without exception, and always works from the CLI. If it > >were a vty issue, you would expect it to occasionally go through. Any other > >ideas? > > > >Thanks, > >~~ted > > > > > >----- Original Message ----- > >From: > >To: "Ted Bedwell" > >Cc: > >Sent: Saturday, May 31, 2003 10:07 PM > >Subject: Re: False unreachable? > > > > > >> On Sat, 31 May 2003, Ted Bedwell wrote: > >> > >> > Hi all, > >> > I've have rancid running on 300+ devices. I have a few however claim > >that they are unreachable. I get the: > >> > > >> > "The following routers have not been successfully contacted for more > >> > than 4 hours" > >> > > >> > email on every polling cycle. The logs state: > >> > > >> > "my.device clogin error: Error: Connection Refused (telnet)" > >> > >> Is it possible at the instant rancid failed, the device was out of vty > >> interfaces? > >> > >> ---------------------------------------------------------------------- > >> Jon Lewis *jlewis at lewis.org*| I route > >> System Administrator | therefore you are > >> Atlantic Net | > >> _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________ > >> > From heas at shrubbery.net Tue Jun 3 20:43:53 2003 From: heas at shrubbery.net (john heasley) Date: Tue, 3 Jun 2003 20:43:53 +0000 Subject: False unreachable? In-Reply-To: <012501c32a0a$e2a2b760$3301a8c0@chopin> References: <20030603002904.112E64ED58@koro.off.connect.com.au> <012501c32a0a$e2a2b760$3301a8c0@chopin> Message-ID: <20030603204352.GA19307@shrubbery.net> doesnt make sense. just to review the obvious... - you tried it manually as the user who runs rancid - your manual attempt used telnet and not ssh - your path and/or environment matches that of the rancid user (no goofy telnet executable or kerberos ...) otherwise, i would disable the do-diffs cron job, edit bin/rancid-fe and place -d after the device's rancid script, eg: < elsif ($vendor =~ /^cisco$/i) { exec('rancid', $router); } > elsif ($vendor =~ /^cisco$/i) { exec('rancid', '-d', $router); } and set NOPIPE=YES in bin/env, then run bin/do-diffs this way, the .raw file will remain behind and can be further examined. warning: this will cause zero-ing/truncation of any configs that fail to be collected. of course, it will be corrected on the next successful run. Tue, Jun 03, 2003 at 04:01:13PM -0400, Ted Bedwell: > That worked beautifully. my.devce.new has the config in it. However, it > still is not working when the do-diffs runs. > > ~~ted From nicolas.strina at smart-telecom.ch Thu Jun 5 07:40:15 2003 From: nicolas.strina at smart-telecom.ch (Strina Nicolas) Date: Thu, 5 Jun 2003 09:40:15 +0200 Subject: Problems In-Reply-To: <20030603204352.GA19307@shrubbery.net> Message-ID: Hello, After a while and doing what is on the FAQ i still have the same problems After removing some nodes here is what i have: starting: Thu Jun 5 09:36:46 CEST 2003 cvs remove: nothing known about `ir00.int.stg.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `ir00.int.stg.lb0.ch.vtxnet.net' cvs [commit aborted]: correct above errors first! Deleted ir00.int.stg.lb0.ch.vtxnet.net cvs remove: nothing known about `ir00.sev.stg.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `ir00.sev.stg.lb0.ch.vtxnet.net' cvs [commit aborted]: correct above errors first! Deleted ir00.sev.stg.lb0.ch.vtxnet.net cvs remove: nothing known about `ir00.unk.arb.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `ir00.unk.arb.lb0.ch.vtxnet.net' cvs [commit aborted]: correct above errors first! Deleted ir00.unk.arb.lb0.ch.vtxnet.net cvs remove: nothing known about `ir00.unk.kre.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `ir00.unk.kre.lb0.ch.vtxnet.net' cvs [commit aborted]: correct above errors first! Deleted ir00.unk.kre.lb0.ch.vtxnet.net cvs remove: nothing known about `ir01.int.stg.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `ir01.int.stg.lb0.ch.vtxnet.net' cvs [commit aborted]: correct above errors first! Deleted ir01.int.stg.lb0.ch.vtxnet.net cvs remove: nothing known about `ir02.int.stg.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `ir02.int.stg.lb0.ch.vtxnet.net' cvs [commit aborted]: correct above errors first! Deleted ir02.int.stg.lb0.ch.vtxnet.net Trying to get all of the configs. All routers sucessfully completed. cvs diff: Diffing . cvs diff: Diffing configs cvs commit: Examining . cvs commit: Examining configs cvs commit: Up-to-date check failed for `configs/br00.cix.gva.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/br00.tix.zur.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/cr00.cix.gva.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ghi.customer.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.air.gva.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.arc.neu.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.bcs.lsm.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.ber.gva.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.boi.lsn.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.bor.mon.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.cbc.lcd.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.cvc.lso.e0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.dix.loc.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.gsx.gva.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.ico.bas.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.idi.lcd.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.inp.por.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.lon.gva.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.mon.gva.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.ome.mar.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.pra.gva.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.pre.lsn.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.pul.lsn.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.sal.lsn.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.sis.bie.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.sis.del.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.sis.loc.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.tek.zur.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.tix.zur.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.unk.bie.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.unk.mor.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.unk.mty.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.unk.nyo.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.unk.sio.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir00.unk.yve.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir01.air.gva.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir01.cbc.lcd.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir01.mon.gva.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir01.ome.mar.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir01.sis.del.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/ir01.unk.nyo.lb0.ch.vtxnet.net' cvs commit: Up-to-date check failed for `configs/lcite.customer.vtxnet.net' cvs commit: Up-to-date check failed for `configs/secheron.customer.vtxnet.net' cvs commit: Up-to-date check failed for `configs/valtronic.customer.vtxnet.net' cvs [commit aborted]: correct above errors first! ending: Thu Jun 5 09:37:57 CEST 2003 "network.20030605.093646" 82L, 5210C ---------------------------------------- STRINA Nicolas IP Network Engineer VTX Services - Internet Service Provider Av. de Lavaux, 101 CH-1009 Pully nicolas.strina at smart-telecom.ch http://www.vtx.ch ---------------------------------------- From heas at shrubbery.net Thu Jun 5 08:12:45 2003 From: heas at shrubbery.net (john heasley) Date: Thu, 5 Jun 2003 08:12:45 +0000 Subject: Problems In-Reply-To: References: <20030603204352.GA19307@shrubbery.net> Message-ID: <20030605081245.GE20163@shrubbery.net> Thu, Jun 05, 2003 at 09:40:15AM +0200, Strina Nicolas: > Hello, > > After a while and doing what is on the FAQ i still have the same problems > > After removing some nodes here is what i have: > > starting: Thu Jun 5 09:36:46 CEST 2003 > > > > cvs remove: nothing known about `ir00.int.stg.lb0.ch.vtxnet.net' > cvs commit: Up-to-date check failed for `ir00.int.stg.lb0.ch.vtxnet.net' > cvs [commit aborted]: correct above errors first! > Deleted ir00.int.stg.lb0.ch.vtxnet.net this means that the files has not been 'cvs add'-ed to the repository. this is done by control_rancid when a device is added. it can fail for in three cases, 1) the group was not properly added use bin/create_cvs 2) the device was not added properly 3) someone has been mucking with the versions in the cvs repository fir the last two cases; remove the device from the router.db file, run bin/do-diffs, replaced the devices in router.db and it should work as expected upon the next run. From ted at cw.net Thu Jun 5 14:08:04 2003 From: ted at cw.net (Ted Bedwell) Date: Thu, 5 Jun 2003 10:08:04 -0400 Subject: False unreachable? References: <20030603002904.112E64ED58@koro.off.connect.com.au> <012501c32a0a$e2a2b760$3301a8c0@chopin> <20030603204352.GA19307@shrubbery.net> Message-ID: <01a801c32b6b$e1dabe10$0b01a8c0@tchikovsky> That did it. One KEY piece of info I neglected to include in all these discussions is that I am running v 2.1. I apologize for not providing this info. I will endeavor to upgrade in the near future. For the time being, running in debug mode will have to suffice. I'll post a follow-up if the upgrade fixes the problem. Thanks again to everyone who contributed. ~~ted ----- Original Message ----- From: "john heasley" To: "Ted Bedwell" Cc: Sent: Tuesday, June 03, 2003 4:43 PM Subject: Re: False unreachable? > doesnt make sense. just to review the obvious... > - you tried it manually as the user who runs rancid > - your manual attempt used telnet and not ssh > - your path and/or environment matches that of the rancid user > (no goofy telnet executable or kerberos ...) > > otherwise, i would disable the do-diffs cron job, edit bin/rancid-fe > and place -d after the device's rancid script, eg: > > < elsif ($vendor =~ /^cisco$/i) { exec('rancid', $router); } > > elsif ($vendor =~ /^cisco$/i) { exec('rancid', '-d', $router); } > > and set NOPIPE=YES in bin/env, then run bin/do-diffs > > this way, the .raw file will remain behind and can be further examined. > > warning: this will cause zero-ing/truncation of any configs that fail to > be collected. of course, it will be corrected on the next successful run. > > Tue, Jun 03, 2003 at 04:01:13PM -0400, Ted Bedwell: > > That worked beautifully. my.devce.new has the config in it. However, it > > still is not working when the do-diffs runs. > > > > ~~ted > From stefmit at comcast.net Thu Jun 5 20:48:53 2003 From: stefmit at comcast.net (stefmit) Date: Thu, 5 Jun 2003 15:48:53 -0500 Subject: Nortel/bay routers and rancid Message-ID: <200306051548.53345.stefmit@comcast.net> Has anybody been able to use rancid with Nortel routers? I have a BCN and I have tweaked the configs in all possible ways, but blogin won't go beyond the login (first level) ... i.e. never kicking in bcc. And - besides that - when doing blogin, vs. a regular telnet, I cannot log out - I have to CTRL/C the process. TIA, Stef From stefmit at comcast.net Fri Jun 6 11:43:17 2003 From: stefmit at comcast.net (stefmit) Date: Fri, 6 Jun 2003 06:43:17 -0500 Subject: Nortel/bay routers and rancid In-Reply-To: <20030606033834.GX20163@shrubbery.net> References: <200306051548.53345.stefmit@comcast.net> <20030606033834.GX20163@shrubbery.net> Message-ID: <200306060643.17832.stefmit@comcast.net> Thank you for your answer. To clarify a little bit: bcc is [a sort of] enable. After one gets the "regular" prompt, certain things can be carried out from there on, but this level of CLI is very limited, so additional steps have to be pursued for full access to configuration, i.e. moving into bcc. Here is how it usually works: telnet Login: Password: $ bcc bcc> configure bcc# --> this is (in my opinion) the equivalent of Cisco's enable ... but I may be wrong. I was hoping someone has a Bay/Nortel router (really, really nobody out there?!?), and can confirm my supposition in regards to how far blogin or do-diff should get into. I guess the only alternative I have is to look into rancid's code, to see if the "bcc" assumption is correct, or what else I can do. Thx again, Stef On Thursday 05 June 2003 10:38 pm, you wrote: > Thu, Jun 05, 2003 at 03:48:53PM -0500, stefmit: > > Has anybody been able to use rancid with Nortel routers? I have a BCN and > > I have tweaked the configs in all possible ways, but blogin won't go > > beyond the login (first level) ... i.e. never kicking in bcc. And - > > besides that - when doing blogin, vs. a regular telnet, I cannot log out > > - I have to CTRL/C the process. > > i do not have one myself and i dont know what "bcc" is. but, if you get > logged-in, followed by a prompt and then can not do anything, i would > suspect that your .cloginrc is misconfigured if the bcn has a concept > of "enable" (or entering privledged mode). > > see the autoenable .cloginrc knob. From heas at shrubbery.net Fri Jun 6 16:35:08 2003 From: heas at shrubbery.net (john heasley) Date: Fri, 6 Jun 2003 16:35:08 +0000 Subject: Nortel/bay routers and rancid In-Reply-To: <200306060643.17832.stefmit@comcast.net> References: <200306051548.53345.stefmit@comcast.net> <20030606033834.GX20163@shrubbery.net> <200306060643.17832.stefmit@comcast.net> Message-ID: <20030606163508.GF20163@shrubbery.net> Fri, Jun 06, 2003 at 06:43:17AM -0500, stefmit: > Thank you for your answer. > > To clarify a little bit: bcc is [a sort of] enable. After one gets the > "regular" prompt, certain things can be carried out from there on, but this > level of CLI is very limited, so additional steps have to be pursued for full > access to configuration, i.e. moving into bcc. Here is how it usually works: > > telnet > Login: > Password: > $ bcc > bcc> configure > bcc# --> this is (in my opinion) the equivalent of Cisco's enable ... but I > may be wrong. I was hoping someone has a Bay/Nortel router (really, really > nobody out there?!?), and can confirm my supposition in regards to how far > blogin or do-diff should get into. > > I guess the only alternative I have is to look into rancid's code, to see if > the "bcc" assumption is correct, or what else I can do. a quick look at the code; blogin doesn't use anything. # blogin - Bay Networks(Nortel) login # # Unlike the Cisco's, there is no enable function on the Bay's. # Instead there are seperate User and Manager accounts. A 'system' command # exists, which i am told does nothing. (i didnt write blogin). but it does call the enable() function which uses 'enable' to get elevated privs and expects the prompt to change from > to #. so, this seems kind of buggered. i dont have a bay/nortel (thankfully); someone who does will have to contribute. > Thx again, > Stef > > On Thursday 05 June 2003 10:38 pm, you wrote: > > Thu, Jun 05, 2003 at 03:48:53PM -0500, stefmit: > > > Has anybody been able to use rancid with Nortel routers? I have a BCN and > > > I have tweaked the configs in all possible ways, but blogin won't go > > > beyond the login (first level) ... i.e. never kicking in bcc. And - > > > besides that - when doing blogin, vs. a regular telnet, I cannot log out > > > - I have to CTRL/C the process. > > > > i do not have one myself and i dont know what "bcc" is. but, if you get > > logged-in, followed by a prompt and then can not do anything, i would > > suspect that your .cloginrc is misconfigured if the bcn has a concept > > of "enable" (or entering privledged mode). > > > > see the autoenable .cloginrc knob. From stefmit at comcast.net Fri Jun 6 18:57:22 2003 From: stefmit at comcast.net (stefmit) Date: Fri, 6 Jun 2003 13:57:22 -0500 Subject: Nortel/bay routers and rancid In-Reply-To: <3EE08301.1090308@blueyonder.co.uk> References: <200306051548.53345.stefmit@comcast.net> <200306060643.17832.stefmit@comcast.net> <3EE08301.1090308@blueyonder.co.uk> Message-ID: <200306061357.22737.stefmit@comcast.net> Here is what I have: .cloginrc: add password router password (tried also {password} add user router user (tried alternatively with the above, {user}) add userprompt {Login:} # the above is the only one getting me to the $ prompt, all other options # (e.g. {"Login:"}) leaving me at the Login: prompt! add autoenable router 1 add userpwassword password # lqast two lines tried without, with one at a time, with both, etc. With all five lines above, in the form I have them now, get me as far as the $ prompt, which is one step before the bcc. When running the suggested: blogin -c "help" router I still stop at the $ prompt - no "help" and no logout. Any ideas of what could be wrong at this level? Thx, Stefan On Friday 06 June 2003 07:03 am, Mark Cooper wrote: > I did the original port to the Nortel/Bay platform, and brancid will run > bcc to get the configs. blogin does *not* do a bcc unless told to by > brancid or a 'blogin -c etc etc' > > Can you confirm that blogin can successfully login and run commands? You > should be able to do something like:- > > blogin -c "help" > > and it should login to the device, run the help command, and then exit > without any errors. If it doesn't do this, brancid will not work either :) > > I don't have access to any Nortel/Bay devices anymore so i'm a bit > limited in the support I can provide. > > stefmit wrote: > > Thank you for your answer. > > > > To clarify a little bit: bcc is [a sort of] enable. After one gets the > > "regular" prompt, certain things can be carried out from there on, but > > this level of CLI is very limited, so additional steps have to be pursued > > for full access to configuration, i.e. moving into bcc. Here is how it > > usually works: > > > > telnet > > Login: > > Password: > > $ bcc > > bcc> configure > > bcc# --> this is (in my opinion) the equivalent of Cisco's enable ... but > > I may be wrong. I was hoping someone has a Bay/Nortel router (really, > > really nobody out there?!?), and can confirm my supposition in regards to > > how far blogin or do-diff should get into. > > > > I guess the only alternative I have is to look into rancid's code, to see > > if the "bcc" assumption is correct, or what else I can do. > > > > Thx again, > > Stef > > > > On Thursday 05 June 2003 10:38 pm, you wrote: > >>Thu, Jun 05, 2003 at 03:48:53PM -0500, stefmit: > >>>Has anybody been able to use rancid with Nortel routers? I have a BCN > >>> and I have tweaked the configs in all possible ways, but blogin won't > >>> go beyond the login (first level) ... i.e. never kicking in bcc. And - > >>> besides that - when doing blogin, vs. a regular telnet, I cannot log > >>> out - I have to CTRL/C the process. > >> > >>i do not have one myself and i dont know what "bcc" is. but, if you get > >>logged-in, followed by a prompt and then can not do anything, i would > >>suspect that your .cloginrc is misconfigured if the bcn has a concept > >>of "enable" (or entering privledged mode). > >> > >>see the autoenable .cloginrc knob. From mcooper at blueyonder.co.uk Fri Jun 6 20:42:02 2003 From: mcooper at blueyonder.co.uk (Mark Cooper) Date: Fri, 06 Jun 2003 21:42:02 +0100 Subject: Nortel/bay routers and rancid In-Reply-To: <200306061357.22737.stefmit@comcast.net> References: <200306051548.53345.stefmit@comcast.net> <200306060643.17832.stefmit@comcast.net> <3EE08301.1090308@blueyonder.co.uk> <200306061357.22737.stefmit@comcast.net> Message-ID: <3EE0FC9A.7070705@blueyonder.co.uk> The "$" prompt ? The bay's I've come across usually have a prompt of ">" which is probably the cause of your problem. Try the following patch.. --- blogin.ORIG Fri Jun 6 21:12:57 2003 +++ blogin Fri Jun 6 21:13:22 2003 @@ -483,7 +483,7 @@ set prompt "#" } else { set autoenable 0 - set prompt ">" + set prompt "$" } } stefmit wrote: > Here is what I have: > > .cloginrc: > > add password router password (tried also {password} > add user router user (tried alternatively with the above, {user}) > add userprompt {Login:} > # the above is the only one getting me to the $ prompt, all other options > # (e.g. {"Login:"}) leaving me at the Login: prompt! > add autoenable router 1 > add userpwassword password > # lqast two lines tried without, with one at a time, with both, etc. > > With all five lines above, in the form I have them now, get me as far as the $ > prompt, which is one step before the bcc. > > When running the suggested: > > blogin -c "help" router > > I still stop at the $ prompt - no "help" and no logout. > > Any ideas of what could be wrong at this level? > > Thx, > Stefan > > On Friday 06 June 2003 07:03 am, Mark Cooper wrote: > >>I did the original port to the Nortel/Bay platform, and brancid will run >>bcc to get the configs. blogin does *not* do a bcc unless told to by >>brancid or a 'blogin -c etc etc' >> >>Can you confirm that blogin can successfully login and run commands? You >>should be able to do something like:- >> >> blogin -c "help" >> >>and it should login to the device, run the help command, and then exit >>without any errors. If it doesn't do this, brancid will not work either :) >> >>I don't have access to any Nortel/Bay devices anymore so i'm a bit >>limited in the support I can provide. >> >>stefmit wrote: >> >>>Thank you for your answer. >>> >>>To clarify a little bit: bcc is [a sort of] enable. After one gets the >>>"regular" prompt, certain things can be carried out from there on, but >>>this level of CLI is very limited, so additional steps have to be pursued >>>for full access to configuration, i.e. moving into bcc. Here is how it >>>usually works: >>> >>>telnet >>>Login: >>>Password: >>>$ bcc >>>bcc> configure >>>bcc# --> this is (in my opinion) the equivalent of Cisco's enable ... but >>>I may be wrong. I was hoping someone has a Bay/Nortel router (really, >>>really nobody out there?!?), and can confirm my supposition in regards to >>>how far blogin or do-diff should get into. >>> >>>I guess the only alternative I have is to look into rancid's code, to see >>>if the "bcc" assumption is correct, or what else I can do. >>> >>>Thx again, >>>Stef >>> >>>On Thursday 05 June 2003 10:38 pm, you wrote: >>> >>>>Thu, Jun 05, 2003 at 03:48:53PM -0500, stefmit: >>>> >>>>>Has anybody been able to use rancid with Nortel routers? I have a BCN >>>>>and I have tweaked the configs in all possible ways, but blogin won't >>>>>go beyond the login (first level) ... i.e. never kicking in bcc. And - >>>>>besides that - when doing blogin, vs. a regular telnet, I cannot log >>>>>out - I have to CTRL/C the process. >>>> >>>>i do not have one myself and i dont know what "bcc" is. but, if you get >>>>logged-in, followed by a prompt and then can not do anything, i would >>>>suspect that your .cloginrc is misconfigured if the bcn has a concept >>>>of "enable" (or entering privledged mode). >>>> >>>>see the autoenable .cloginrc knob. > > -- Mark Cooper http://netmangler.sourceforge.net - Network Management with Attitude http://pvrhw.goldfish.org - Open Source PVR Hardware Database From stefmit at comcast.net Sat Jun 7 10:48:38 2003 From: stefmit at comcast.net (stefmit) Date: Sat, 07 Jun 2003 05:48:38 -0500 Subject: Nortel/bay routers and rancid Message-ID: <200306070548.38573.stefmit@comcast.net> Thank you ... didn't work, yet, but you pointed me to the right place, and I started to play around with it. I need to figure out where you have the "bcc" part, to see if I can figure it out in conjunction with the "enable" and prompt sequence. FYI: the sequence of events (including prompt "history" during the login and enable processing) is as I explained it in the original message, i.e.: telnet prompt is Login: --> prompt is Password: --> prompt is $ --> bcc prompt is bcc> --> config prompt is bcc# --> this is what I could probably call "enable" mode, if I were to compare it - somehow - with Cisco So - after logging in succesfully, the sequence of prompts is $, >, then #. Thanks again for all the help, Stef On Friday 06 June 2003 03:42 pm, Mark Cooper wrote: > The "$" prompt ? The bay's I've come across usually have a prompt of ">" > which is probably the cause of your problem. > > Try the following patch.. > > > --- blogin.ORIG Fri Jun 6 21:12:57 2003 > +++ blogin Fri Jun 6 21:13:22 2003 > @@ -483,7 +483,7 @@ > set prompt "#" > } else { > set autoenable 0 > - set prompt ">" > + set prompt "$" > } > } > > stefmit wrote: > > Here is what I have: > > > > .cloginrc: > > > > add password router password (tried also {password} > > add user router user (tried alternatively with the above, {user}) > > add userprompt {Login:} > > # the above is the only one getting me to the $ prompt, all other options > > # (e.g. {"Login:"}) leaving me at the Login: prompt! > > add autoenable router 1 > > add userpwassword password > > # last two lines tried without, with one at a time, with both, etc. > > > > With all five lines above, in the form I have them now, get me as far as > > the $ prompt, which is one step before the bcc. > > > > When running the suggested: > > > > blogin -c "help" router > > > > I still stop at the $ prompt - no "help" and no logout. > > > > Any ideas of what could be wrong at this level? > > > > Thx, > > Stefan From stefmit at comcast.net Sat Jun 7 11:05:04 2003 From: stefmit at comcast.net (stefmit) Date: Sat, 07 Jun 2003 06:05:04 -0500 Subject: Nortel/bay routers and rancid In-Reply-To: <200306070548.38573.stefmit@comcast.net> References: <200306070548.38573.stefmit@comcast.net> Message-ID: <200306070605.04780.stefmit@comcast.net> Minor correction, more for completeness (though irrelevant, as long as the *prompt* is to be analyzing only the last character): - after issuing the *config* command, under the *bcc>* prompt, the prompt changes to *box#*, not *bcc#* ... sorry. On Saturday 07 June 2003 05:48 am, stefmit wrote: > Thank you ... didn't work, yet, but you pointed me to the right place, and > I started to play around with it. I need to figure out where you have the > "bcc" part, to see if I can figure it out in conjunction with the "enable" > and prompt sequence. > > FYI: the sequence of events (including prompt "history" during the login > and enable processing) is as I explained it in the original message, i.e.: > > telnet > prompt is Login: --> > prompt is Password: --> > prompt is $ --> bcc > prompt is bcc> --> config > prompt is bcc# --> this is what I could probably call "enable" mode, if I > were to compare it - somehow - with Cisco > > So - after logging in succesfully, the sequence of prompts is $, >, then #. > > Thanks again for all the help, > Stef > > On Friday 06 June 2003 03:42 pm, Mark Cooper wrote: > > The "$" prompt ? The bay's I've come across usually have a prompt of ">" > > which is probably the cause of your problem. > > > > Try the following patch.. > > > > > > --- blogin.ORIG Fri Jun 6 21:12:57 2003 > > +++ blogin Fri Jun 6 21:13:22 2003 > > @@ -483,7 +483,7 @@ > > set prompt "#" > > } else { > > set autoenable 0 > > - set prompt ">" > > + set prompt "$" > > } > > } > > > > stefmit wrote: > > > Here is what I have: > > > > > > .cloginrc: > > > > > > add password router password (tried also {password} > > > add user router user (tried alternatively with the above, {user}) > > > add userprompt {Login:} > > > # the above is the only one getting me to the $ prompt, all other > > > options # (e.g. {"Login:"}) leaving me at the Login: prompt! > > > add autoenable router 1 > > > add userpwassword password > > > # last two lines tried without, with one at a time, with both, etc. > > > > > > With all five lines above, in the form I have them now, get me as far > > > as the $ prompt, which is one step before the bcc. > > > > > > When running the suggested: > > > > > > blogin -c "help" router > > > > > > I still stop at the $ prompt - no "help" and no logout. > > > > > > Any ideas of what could be wrong at this level? > > > > > > Thx, > > > Stefan > > From randy at psg.com Sat Jun 14 16:45:42 2003 From: randy at psg.com (Randy Bush) Date: Sat, 14 Jun 2003 09:45:42 -0700 Subject: hp config goes to null Message-ID: for weeks, rancid fetched a good config from my procurve 2524. then, one otherwise calm day, i got the following diff. and i no longer get the config. any clues? randy --- =================================================================== RCS file: /usr/home/randy/rancid/CVS/psgnet/configs//myswitch.bellhead.com,v retrieving revision 1.2 retrieving revision 1.3 diff -u -p -r1.2 -r1.3 --- myswitch.bellhead.com 2003/06/11 07:15:14 1.2 +++ myswitch.bellhead.com 2003/06/14 04:15:13 1.3 @@ -1,111 +1,8 @@ ;RANCID-CONTENT-TYPE: hp-procurve ; -;Chassis type: J4813A -;Serial Number: tw04104285 ; -;Memory: 11,337,704 ; -;Image: Firmware F.02.02 -;Image: stamp: /sw/code/build/info(f00) -;Image: Jan 16 2001 09:36:32 -;Image: F.02.02 -;Image: 887 -;Image: ROM F.01.01 -; -; -; -; Stacking Status -; Stack State : Candidate -; Transmission Interval : 60 -; Auto Join : Yes -; -; -time daylight-time-rule None -hostname "RGnet Westin" -snmp-server contact "Randy Bush +1 206 356 8341" -max-vlans 1 -interface 1 - speed-duplex 100-full - exit -interface 2 - speed-duplex 100-full - exit -interface 3 - speed-duplex 100-full - exit -interface 4 - speed-duplex 100-full - exit -interface 5 - speed-duplex 100-full - exit -interface 6 - speed-duplex 100-full - exit -interface 7 - speed-duplex 100-full - exit -interface 8 - speed-duplex 100-full - exit -interface 9 - speed-duplex 100-full - exit -interface 10 - speed-duplex 100-full - exit -interface 11 - speed-duplex 100-full - exit -interface 12 - speed-duplex 100-full - exit -interface 13 - speed-duplex 100-full - exit -interface 14 - speed-duplex 100-full - exit -interface 15 - speed-duplex 100-full - exit -interface 16 - speed-duplex 10-half - exit -interface 17 - speed-duplex 100-full - exit -interface 18 - speed-duplex 100-full - exit -interface 19 - speed-duplex 100-full - exit -interface 20 - speed-duplex 100-full - exit -interface 21 - speed-duplex 100-full - exit -interface 22 - speed-duplex 100-full - exit -interface 23 - speed-duplex 100-full - exit -interface 24 - speed-duplex 100-full - exit -ip default-gateway -sntp server -ip timep dhcp -snmp-server community "" Manager -vlan 1 - name "DEFAULT_VLAN" - untagged 1-26 - ip address 255.255.255.0 - exit -ip authorized-managers -ip authorized-managers mask 255.255.255.0 +; +; +; +; From babydr at baby-dragons.com Sat Jun 14 17:10:33 2003 From: babydr at baby-dragons.com (Mr. James W. Laferriere) Date: Sat, 14 Jun 2003 13:10:33 -0400 (EDT) Subject: hp config goes to null In-Reply-To: References: Message-ID: Hello Randy , Is the system still contactable ? I suspect you've already check that ? Does the present config show the same as the last update ? If I were to recieve a config change like that basically showing the the config had been erased ... Any code updates ? , ??? Sorry for just the ?'s . JimL On Sat, 14 Jun 2003, Randy Bush wrote: > for weeks, rancid fetched a good config from my procurve 2524. > then, one otherwise calm day, i got the following diff. > > and i no longer get the config. > > any clues? > > randy > --- ...snip... > -ip authorized-managers > -ip authorized-managers mask 255.255.255.0 > +; > +; > +; > +; > -- +------------------------------------------------------------------+ | James W. Laferriere | System Techniques | Give me VMS | | Network Engineer | P.O. Box 854 | Give me Linux | | babydr at baby-dragons.com | Coudersport PA 16915 | only on AXP | +------------------------------------------------------------------+ From randy at psg.com Sat Jun 14 17:14:11 2003 From: randy at psg.com (Randy Bush) Date: Sat, 14 Jun 2003 10:14:11 -0700 Subject: hp config goes to null References: Message-ID: > Hello Randy , Is the system still contactable ? I suspect > you've already check that ? Does the present config show the > same as the last update ? If I were to recieve a config change > like that basically showing the the config had been erased ... > Any code updates ? , ??? Sorry for just the ?'s . JimL system contactable, snmp-able, same old config when logging in, blah blah. no code load (should i?). randy From babydr at baby-dragons.com Sat Jun 14 17:25:08 2003 From: babydr at baby-dragons.com (Mr. James W. Laferriere) Date: Sat, 14 Jun 2003 13:25:08 -0400 (EDT) Subject: hp config goes to null In-Reply-To: References: Message-ID: Hello Randy , On Sat, 14 Jun 2003, Randy Bush wrote: > > Hello Randy , Is the system still contactable ? I suspect > > you've already check that ? Does the present config show the > > same as the last update ? If I were to recieve a config change > > like that basically showing the the config had been erased ... > > Any code updates ? , ??? Sorry for just the ?'s . JimL > system contactable, snmp-able, same old config when logging in, > blah blah. no code load (should i?). Can you using snmpget acquire the config ? I am going to assume that you will not get a valid config back from the request . I don't recommend (yet) to upgrade the code base . Uptime of the switch ? Just off chance have you tried rebooting the unit ? If you have not , I am getting a bad feeling that something in the unit may be getting corrupted . Not a certainty just a bad feeling . So rebooting could be a bad thing . Can you check the or even do you have a CRC/MD5 of the codebase ? One thing for certain 'something' has changed . -- +------------------------------------------------------------------+ | James W. Laferriere | System Techniques | Give me VMS | | Network Engineer | P.O. Box 854 | Give me Linux | | babydr at baby-dragons.com | Coudersport PA 16915 | only on AXP | +------------------------------------------------------------------+ From randy at psg.com Sat Jun 14 18:03:07 2003 From: randy at psg.com (Randy Bush) Date: Sat, 14 Jun 2003 11:03:07 -0700 Subject: hp config goes to null References: Message-ID: > Can you using snmpget acquire the config ? hmmm % snmpget -v1 -Cf -c "" system.sysDescr.0 SNMPv2-MIB::sysDescr.0 = STRING: HP J4813A ProCurve Switch 2524, revision F.02.02, ROM F.01.01 (/sw/code/build/info(f00)) do you happen to know how to do a get for the whole config? > Uptime of the switch ? % snmpget -v1 -Cf -c "" system.sysUpTime.0 SNMPv2-MIB::sysUpTime.0 = Timeticks: (356102402) 41 days, 5:10:24.02 > Just off chance have you tried rebooting the unit ? too scared randy From heas at shrubbery.net Sat Jun 14 18:29:54 2003 From: heas at shrubbery.net (john heasley) Date: Sat, 14 Jun 2003 11:29:54 -0700 Subject: hp config goes to null In-Reply-To: References: Message-ID: <20030614182954.GY18898@shrubbery.net> Sat, Jun 14, 2003 at 09:45:42AM -0700, Randy Bush: > for weeks, rancid fetched a good config from my procurve 2524. > then, one otherwise calm day, i got the following diff. > > and i no longer get the config. > > any clues? are there any error msgs in ~randy/rancid/logs/psgnet.* wrt this switch? rancid should not "delete" the saved config if it has trouble collecting any of the data, but there is always the chance that we have missed some corner case. a quick check is, as the user who runs rancid, % cd ~randy/rancid/bin % hrancid -c "show version;show flash;show system-information;show module;show stack;write term" myswitch.bellhead.com From randy at psg.com Sat Jun 14 18:40:05 2003 From: randy at psg.com (Randy Bush) Date: Sat, 14 Jun 2003 11:40:05 -0700 Subject: hp config goes to null References: <20030614182954.GY18898@shrubbery.net> Message-ID: > are there any error msgs in ~randy/rancid/logs/psgnet.* wrt this switch? Checking in configs/switch0.psg.com; /usr/home/randy/rancid/CVS/psgnet/configs/switch0.psg.com,v <-- switch0.psg.com new revision: 1.2; previous revision: 1.1 done Checking in configs/switch0.psg.com; /usr/home/randy/rancid/CVS/psgnet/configs/switch0.psg.com,v <-- switch0.psg.com new revision: 1.3; previous revision: 1.2 done that's it randy From hank at rem.com Sat Jun 14 19:15:57 2003 From: hank at rem.com (Henry Kilmer) Date: Sat, 14 Jun 2003 15:15:57 -0400 Subject: hp config goes to null In-Reply-To: References: <20030614182954.GY18898@shrubbery.net> Message-ID: <16107.29805.553147.142566@durmstrang.padfoot.com> Randy Bush writes: >> are there any error msgs in ~randy/rancid/logs/psgnet.* wrt this switch? > >Checking in configs/switch0.psg.com; >/usr/home/randy/rancid/CVS/psgnet/configs/switch0.psg.com,v <-- switch0.psg.com >new revision: 1.2; previous revision: 1.1 >done > >Checking in configs/switch0.psg.com; >/usr/home/randy/rancid/CVS/psgnet/configs/switch0.psg.com,v <-- switch0.psg.com >new revision: 1.3; previous revision: 1.2 >done > > >that's it Then rancid seems to think it got the config fine or we missed a corner case. It would be interesting to see what rancid is doing as Heas suggested: % hrancid -c "show version;show flash;show system-information;show module;show stack;write term" myswitch.bellhead.com -Hank From randy at psg.com Sat Jun 14 19:18:45 2003 From: randy at psg.com (Randy Bush) Date: Sat, 14 Jun 2003 12:18:45 -0700 Subject: hp config goes to null References: <20030614182954.GY18898@shrubbery.net> <16107.29805.553147.142566@durmstrang.padfoot.com> Message-ID: hosed switch > RGnet Westin# reboot > RGnet Westin# > RGnet Westin# > RGnet Westin# > RGnet Westin# randy From Mark.Duling at biola.edu Sat Jun 14 22:27:45 2003 From: Mark.Duling at biola.edu (Mark Duling) Date: Sat, 14 Jun 2003 15:27:45 -0700 Subject: RANCID on Mac OS X (Darwin) Message-ID: Hello All, Just thought I mention that I got RANCID running on OS X 10.2.4. I am not very UNIX literate so I was tripped up by a Unix issue I wasn't familiar with (step 4 below). I thought I'd post this and get it in the archives so other OS X users would be aware. The basic steps I performed were: 1) Install the "batteries included" distribution of tcl/tk Aqua 8.4.2 which included expect 5.38. It is a binary image so it is a one click install familiar to OS X users. 2) Modify the perl path in the install script to be correct for OS X. 3) Install RANCID as described in the instructions and add the path to RANCID to your environment path. 4) Modify the clogin (for Cisco) expect script's 1st line to be #!/usr/local/bin/expect (Not doing that was what caused my trouble, I added the path to my shell. I know, Unix newbies :) 5) Now you can follow the instructions on the RANCID site or follow the link to Chris Boyd's helpful instructions for BSD. Thanks to those who have made this very useful utility. Mark From randy at psg.com Sat Jun 14 23:04:09 2003 From: randy at psg.com (Randy Bush) Date: Sat, 14 Jun 2003 16:04:09 -0700 Subject: hp config goes to null References: <20030614182954.GY18898@shrubbery.net> <16107.29805.553147.142566@durmstrang.padfoot.com> Message-ID: > RGnet Westin# reboot > RGnet Westin# > RGnet Westin# > RGnet Westin# > RGnet Westin# interestingly, i could run the menu system and use it to reboot the switch. switch acting 'normally' now. time to find out how to get later code into the puppy. randy From heas at shrubbery.net Sun Jun 15 03:39:56 2003 From: heas at shrubbery.net (john heasley) Date: Sun, 15 Jun 2003 03:39:56 +0000 Subject: hp config goes to null In-Reply-To: <16107.29805.553147.142566@durmstrang.padfoot.com> References: <20030614182954.GY18898@shrubbery.net> <16107.29805.553147.142566@durmstrang.padfoot.com> Message-ID: <20030615033956.GB8176@shrubbery.net> Sat, Jun 14, 2003 at 03:15:57PM -0400, Henry Kilmer: > > Randy Bush writes: > >> are there any error msgs in ~randy/rancid/logs/psgnet.* wrt this switch? > > > >Checking in configs/switch0.psg.com; > >/usr/home/randy/rancid/CVS/psgnet/configs/switch0.psg.com,v <-- switch0.psg.com > >new revision: 1.2; previous revision: 1.1 > >done > > > >Checking in configs/switch0.psg.com; > >/usr/home/randy/rancid/CVS/psgnet/configs/switch0.psg.com,v <-- switch0.psg.com > >new revision: 1.3; previous revision: 1.2 > >done > > > > > >that's it > > Then rancid seems to think it got the config fine or we missed a > corner case. It would be interesting to see what rancid is doing as we should count lines; eg: a zero-length 'show version' or 'show config' should be a red flag. From heas at shrubbery.net Sun Jun 15 03:47:50 2003 From: heas at shrubbery.net (john heasley) Date: Sun, 15 Jun 2003 03:47:50 +0000 Subject: RANCID on Mac OS X (Darwin) In-Reply-To: References: Message-ID: <20030615034750.GD8176@shrubbery.net> Sat, Jun 14, 2003 at 03:27:45PM -0700, Mark Duling: > Hello All, > > Just thought I mention that I got RANCID running on OS X 10.2.4. I am not > very UNIX literate so I was tripped up by a Unix issue I wasn't familiar > with (step 4 below). I thought I'd post this and get it in the archives > so other OS X users would be aware. The basic steps I performed were: > i dont understand why 2 or 4 were necessary. the configure script should have taken care of these steps. > 1) Install the "batteries included" distribution of tcl/tk Aqua 8.4.2 > which included expect 5.38. It is a binary image so it is a one click > install familiar to OS X users. > > 2) Modify the perl path in the install script to be correct for OS X. > > 3) Install RANCID as described in the instructions and add the path to > RANCID to your environment path. > > 4) Modify the clogin (for Cisco) expect script's 1st line to be > #!/usr/local/bin/expect > (Not doing that was what caused my trouble, I added the path to my > shell. I know, Unix newbies :) > > 5) Now you can follow the instructions on the RANCID site or follow the > link to Chris Boyd's helpful instructions for BSD. > > > Thanks to those who have made this very useful utility. > > Mark From heas at shrubbery.net Mon Jun 16 20:53:45 2003 From: heas at shrubbery.net (john heasley) Date: Mon, 16 Jun 2003 13:53:45 -0700 Subject: Nortel/bay routers and rancid In-Reply-To: <200306061357.22737.stefmit@comcast.net> References: <200306051548.53345.stefmit@comcast.net> <200306060643.17832.stefmit@comcast.net> <3EE08301.1090308@blueyonder.co.uk> <200306061357.22737.stefmit@comcast.net> Message-ID: <20030616205345.GQ11687@shrubbery.net> Fri, Jun 06, 2003 at 01:57:22PM -0500, stefmit: > Here is what I have: > > .cloginrc: > > add password router password (tried also {password} > add user router user (tried alternatively with the above, {user}) > add userprompt {Login:} > # the above is the only one getting me to the $ prompt, all other options > # (e.g. {"Login:"}) leaving me at the Login: prompt! > add autoenable router 1 > add userpwassword password > # lqast two lines tried without, with one at a time, with both, etc. > > With all five lines above, in the form I have them now, get me as far as the $ > prompt, which is one step before the bcc. each of these is supposed to have a "target", routername for example. add password router password (tried also {password} add user router user (tried alternatively with the above, {user}) add userprompt {Login:} # the above is the only one getting me to the $ prompt, all other options # (e.g. {"Login:"}) leaving me at the Login: prompt! add autoenable router 1 add userpwassword password # lqast two lines tried without, with one at a time, with both, etc. > When running the suggested: > > blogin -c "help" router > > I still stop at the $ prompt - no "help" and no logout. > > Any ideas of what could be wrong at this level? it's probably waiting to try to match the prompt, which it expects to be '#'. It should timeout after 45 seconds. but, as the other guy mentioned, '$' is a strange prompt and of course is not '#'. again, I dont know much about bay routers. i'd investigate what the prompt should be by default, according to documentation. afaik, its supposed to be '#'. > Thx, > Stefan > > On Friday 06 June 2003 07:03 am, Mark Cooper wrote: > > I did the original port to the Nortel/Bay platform, and brancid will run > > bcc to get the configs. blogin does *not* do a bcc unless told to by > > brancid or a 'blogin -c etc etc' > > > > Can you confirm that blogin can successfully login and run commands? You > > should be able to do something like:- > > > > blogin -c "help" > > > > and it should login to the device, run the help command, and then exit > > without any errors. If it doesn't do this, brancid will not work either :) > > > > I don't have access to any Nortel/Bay devices anymore so i'm a bit > > limited in the support I can provide. > > > > stefmit wrote: > > > Thank you for your answer. > > > > > > To clarify a little bit: bcc is [a sort of] enable. After one gets the > > > "regular" prompt, certain things can be carried out from there on, but > > > this level of CLI is very limited, so additional steps have to be pursued > > > for full access to configuration, i.e. moving into bcc. Here is how it > > > usually works: > > > > > > telnet > > > Login: > > > Password: > > > $ bcc > > > bcc> configure > > > bcc# --> this is (in my opinion) the equivalent of Cisco's enable ... but > > > I may be wrong. I was hoping someone has a Bay/Nortel router (really, > > > really nobody out there?!?), and can confirm my supposition in regards to > > > how far blogin or do-diff should get into. > > > > > > I guess the only alternative I have is to look into rancid's code, to see > > > if the "bcc" assumption is correct, or what else I can do. > > > > > > Thx again, > > > Stef > > > > > > On Thursday 05 June 2003 10:38 pm, you wrote: > > >>Thu, Jun 05, 2003 at 03:48:53PM -0500, stefmit: > > >>>Has anybody been able to use rancid with Nortel routers? I have a BCN > > >>> and I have tweaked the configs in all possible ways, but blogin won't > > >>> go beyond the login (first level) ... i.e. never kicking in bcc. And - > > >>> besides that - when doing blogin, vs. a regular telnet, I cannot log > > >>> out - I have to CTRL/C the process. > > >> > > >>i do not have one myself and i dont know what "bcc" is. but, if you get > > >>logged-in, followed by a prompt and then can not do anything, i would > > >>suspect that your .cloginrc is misconfigured if the bcn has a concept > > >>of "enable" (or entering privledged mode). > > >> > > >>see the autoenable .cloginrc knob.