[rancid] Re: Timeouts on Cisco ASA

[john heasley]

Tue, Apr 21, 2009 at 09:39:16AM -0400, marcus gaysek:
> I have quite a few ASAs in my environment and do not have that issue.
> What version of rancid are you both running?
> Is it possible something else in your .cloginrc config is taking precedence?
> What happens if you run:  ./clogin -u user-name -p user-password -e
> enable-password 10.1.2.1

and -noenable
and -d

> 
> On Tue, Apr 21, 2009 at 8:15 AM, Carlo Finotti <carlo.finotti at gmail.com>wrote:
> 
> > Yep that is basically the same thing that is happening to me.  It
> > seems like the package works great for routers and switches but is a
> > bit buggy for an ASA especially in multiple context mode.  Hopefully
> > someone has this setup and working and can shed some light on our
> > dilemma.
> >
> >
> > On Tue, Apr 21, 2009 at 5:22 AM, JP Viljoen <froztbyte at froztbyte.net>
> > wrote:
> > > I've got a few Cisco devices that I'm monitoring configs and changes to
> > the
> > > configs with using RANCID, and among them is an ASA. The problem I have
> > is that
> > > logging into the ASA with clogin seems to just stall. It gets as far the
> > > prompt immediately after login, and from there's it's just dead.
> > >
> > > rancid at mon:~/rancid/bin$ ./clogin 10.1.2.1
> > > 10.1.2.1
> > > spawn ssh -c 3des -x -l user 10.1.2.1
> > > user at 10.1.2.1's password:
> > > Type help or '?' for a list of available commands.
> > > ciscoasa>
> > > {TIMEOUT here}
> > >
> > > Entering commands at this point is unsuccessful, as is giving commands
> > with
> > > the -c parameter. Logging into the device with ssh on its own works
> > perfectly
> > > though:
> > >
> > > rancid at mon:~/rancid/bin$ ssh user at 10.1.2.1
> > > user at 10.1.2.1's password:
> > > Type help or '?' for a list of available commands.
> > > ciscoasa> ?
> > >
> > >  clear       Reset functions
> > >  enable      Turn on privileged commands
> > > <snip>
> > >
> > > My .cloginrc for the specific device is as follows:
> > >
> > > add user 10.1.2.1               {user}
> > > add password 10.1.2.1           {loginpass} {enablepass}
> > > add method 10.1.2.1             ssh
> > >
> > > Initially the configuration was with Telnet, using which I experienced
> > the same
> > > timeout issue. After some reading through the archives I established that
> > it
> > > might be worth attempting to use SSH and have now run into the same
> > issue. If
> > > anyone else has perhaps solved this issue, or have a pointer on what I
> > could
> > > look at?
> > > _______________________________________________
> > > Rancid-discuss mailing list
> > > Rancid-discuss at shrubbery.net
> > > http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss
> > >
> > _______________________________________________
> > Rancid-discuss mailing list
> > Rancid-discuss at shrubbery.net
> > http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss
> >

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