From afort at choqolat.org Tue Jan 4 20:41:33 2005 From: afort at choqolat.org (Andrew Fort) Date: Wed, 05 Jan 2005 07:41:33 +1100 Subject: Rancid and Netscalers In-Reply-To: <6E494551E68B574688EB0D7E9B7169C98D808A@ex2000-c.vistocorp.com> References: <6E494551E68B574688EB0D7E9B7169C98D808A@ex2000-c.vistocorp.com> Message-ID: <41DAFF7D.6020009@choqolat.org> Andy Litzinger wrote: > Hi, > I'm having trouble using the netscaler code for rancid. Has anyone had > any success with it, especially with some of the newer nescaler code? I > have my .cloginrc line set up similar to: > > add user netscaler.foo.com nsroot > #note that I only supplied a vty password because netscaler is FreeBSD > based and does not use enable > add password netscaler.foo.com password > add method netscaler.foo.com ssh > > router.db > netscaler.foo.com:netscaler:up > > When I test with nslogin netscaler.foo.com it connects to the netscaler > and logs in(you get the login message and prompt >), but then you can't > enter any commands and eventually the expect script times out and > disconnects. I'm not sure what the expect script is trying to do at > this point. Wild-ass-guess: sounds like it's not recognizing the prompt, so the logic doesn't continue (to recognize command output if you type it in, or type commands in for you if you're '-c' ing). > I believe some of the netscaler commands may have changed in recent > versions and I'm not sure when the nslogin/nsrancid scripts were last > tested. FYI I am running NS5.2 Build 50.17. Did this 'use to' work? Has the prompt (format) changed (in recent software releases)? I don't have a netscaler so I can't help much more than that, sorry. -andrew From iggy at merit.edu Wed Jan 26 21:10:39 2005 From: iggy at merit.edu (Glenn Wiltse) Date: Wed, 26 Jan 2005 16:10:39 -0500 (EST) Subject: Problems Collecting Extreme configs. Message-ID: I've recently started trying to collect configurations from a Extreme switch. I've ran into problems, sorted some out, but still have questions... First off I'm currently runing 2.8b version of rancid. For this Extreme switch, I'm using telnet, adding autoenable, getting loged in alright... but I keep getting hung up on the clipaging that we like to keep enabled on these switches. If I disable clipaging, all goes well, but I really hate to have to leave clipaging off permenently. I was asked/told that if I just issue a the command 'diable clipaging session' before I issued the other commands, it should work. Well not knowing rancid and/or expect well enough to figure out how to make this hapen on my own. I decided to come and ask, if this issue has been delt with already in a more recent revsion of rancid... and/or if somone can point me in the right direction for dealing with the paging issue on a session basis. We really don't want to permenetly disable paging on our Extreme switches unless that is really our only option. Please advise... Thanks Glenn S. Wiltse From heas at shrubbery.net Thu Jan 27 05:42:52 2005 From: heas at shrubbery.net (john heasley) Date: Wed, 26 Jan 2005 21:42:52 -0800 Subject: Problems Collecting Extreme configs. In-Reply-To: References: Message-ID: <20050127054252.GO5245@shrubbery.net> Wed, Jan 26, 2005 at 04:10:39PM -0500, Glenn Wiltse: > > I've recently started trying to collect configurations from > a Extreme switch. I've ran into problems, sorted some out, but > still have questions... > > First off I'm currently runing 2.8b version of rancid. we have not reached 2.8 yet and all b ("beta") images have been yanked. perhaps this is 2.3b? I'd prefer that you had 2.3.1 + p1. > For this Extreme switch, I'm using telnet, adding autoenable, getting > loged in alright... but I keep getting hung up on the clipaging that we > like to keep enabled on these switches. If I disable clipaging, all goes > well, but I really hate to have to leave clipaging off permenently. > > I was asked/told that if I just issue a the command 'diable clipaging > session' before I issued the other commands, it should work. Well not > knowing rancid and/or expect well enough to figure out how to make this > hapen on my own. I decided to come and ask, if this issue has been > delt with already in a more recent revsion of rancid... and/or if somone > can point me in the right direction for dealing with the paging issue > on a session basis. > > We really don't want to permenetly disable paging on our Extreme switches > unless that is really our only option. The pager can normally be dealt with in the run_commands loop. ISTR there was a reason why we could not do this for the extreme, but I can't remember. I think it used terminal control codes to manipulate the lines, so weird spacing would show-up. but, you can certainly upgrade and try it. sorry - extreme is a bit of a bastard child for us. From iggy at merit.edu Thu Jan 27 13:42:19 2005 From: iggy at merit.edu (Glenn Wiltse) Date: Thu, 27 Jan 2005 08:42:19 -0500 (EST) Subject: Problems Collecting Extreme configs. In-Reply-To: <20050127054252.GO5245@shrubbery.net> References: <20050127054252.GO5245@shrubbery.net> Message-ID: Ah, sorry... it's 2.2b8 that we are running. I've asked to have it updated so we'll see what happens afterwords. I'll let you all know if it helps any... and/or if I find another solution. Thanks, Glenn On Wed, 26 Jan 2005, john heasley wrote: > Wed, Jan 26, 2005 at 04:10:39PM -0500, Glenn Wiltse: > > > > I've recently started trying to collect configurations from > > a Extreme switch. I've ran into problems, sorted some out, but > > still have questions... > > > > First off I'm currently runing 2.8b version of rancid. > > we have not reached 2.8 yet and all b ("beta") images have been yanked. > perhaps this is 2.3b? I'd prefer that you had 2.3.1 + p1. > > > For this Extreme switch, I'm using telnet, adding autoenable, getting > > loged in alright... but I keep getting hung up on the clipaging that we > > like to keep enabled on these switches. If I disable clipaging, all goes > > well, but I really hate to have to leave clipaging off permenently. > > > > I was asked/told that if I just issue a the command 'diable clipaging > > session' before I issued the other commands, it should work. Well not > > knowing rancid and/or expect well enough to figure out how to make this > > hapen on my own. I decided to come and ask, if this issue has been > > delt with already in a more recent revsion of rancid... and/or if somone > > can point me in the right direction for dealing with the paging issue > > on a session basis. > > > > We really don't want to permenetly disable paging on our Extreme switches > > unless that is really our only option. > > The pager can normally be dealt with in the run_commands loop. ISTR there > was a reason why we could not do this for the extreme, but I can't remember. > I think it used terminal control codes to manipulate the lines, so weird > spacing would show-up. > > but, you can certainly upgrade and try it. sorry - extreme is a bit of a > bastard child for us. > > !DSPAM:41f87f6a2219362611576! > > > From afort at choqolat.org Thu Jan 27 21:16:27 2005 From: afort at choqolat.org (Andrew Fort) Date: Fri, 28 Jan 2005 08:16:27 +1100 Subject: Rancid and Netscalers In-Reply-To: <6E494551E68B574688EB0D7E9B7169C98D80BC@ex2000-c.vistocorp.com> References: <6E494551E68B574688EB0D7E9B7169C98D80BC@ex2000-c.vistocorp.com> Message-ID: On 28/01/2005, at 6:23 AM, Andy Litzinger wrote: > > I did get a reply from Anshuman Karwar, who wrote hacked the clogin to > create the nslogin script. He is running almost the same netscaler > code revision as me and it works for him. Since he wrote the nslogin > code, I don't know if he is using a new/different version than what is > included in the Rancid build. > > anyway, I agree that it seems like nslogin is having trouble > recognizing the prompt. Is there anyway to have rancid/ the login > scrips dump out any more verbose info about where it is dying or > having trouble? > > -andy yes, this can be done: $ export NOPIPE=1 $ nsrancid -d -l hostname the output to the terminal, along with the output written into file hostname.raw should get things started. cheers, -andrew