[rancid] problems with PowerConnect switches

[Wayne Eisenberg]

> Tue, Dec 11, 2018 at 09:12:00PM +0000, Wayne Eisenberg:
> > > -----Original Message-----
> > > From: 'heasley' [mailto:heas at shrubbery.net]
> > > Sent: Tuesday, December 11, 2018 1:13 PM
> > > To: Wayne Eisenberg <Wayne.Eisenberg at CarolinasIT.com>
> > > Cc: 'heasley' <heas at shrubbery.net>; 'rancid-discuss at shrubbery.net'
> > > <rancid-discuss at shrubbery.net>
> > > Subject: Re: [rancid] problems with PowerConnect switches
> > >
> > > Tue, Dec 11, 2018 at 06:51:01AM +0000, Wayne Eisenberg:
> > > > > -----Original Message-----
> > > > > From: heasley [mailto:heas at shrubbery.net]
> > > > > Sent: Friday, December 07, 2018 3:06 PM
> > > > > To: Wayne Eisenberg <Wayne.Eisenberg at CarolinasIT.com>
> > > > > Cc: 'rancid-discuss at shrubbery.net'
> > > > > <rancid-discuss at shrubbery.net>
> > > > > Subject: Re: [rancid] problems with PowerConnect switches
> > > > >
> > > > > Fri, Dec 07, 2018 at 10:18:54AM +0000, Wayne Eisenberg:
> > > > > > Hi,
> > > > > >
> > > > > > I have a PowerConnect 5448 that I am having trouble with. If I
> > > > > > run the steps
> > > > > manually it's fine, but using rancid-run always fails.
> > > > > >
> > > > > > The router.db file is:
> > > > > > pc5448;powerconnect;up
> > > > > >
> > > > > > The etc/rancid.types.conf section is:
> > > > > >
> > > > > > powerconnect;script;rancid -t powerconnect
> > > > > > powerconnect;login;clogin powerconnect;module;dell
> > > > > > powerconnect;inloop;dell::inloop
> > > > > > powerconnect;command;dell::GetSystem;show system
> > > > > > powerconnect;command;dell::GetConf;show running-config
> > > > > >
> > > > > > and all the info in .clogin is fine.
> > > > > >
> > > > > > If I manually run clogin for that switch, it has no problems.
> > > > > > Then running
> > > > > 'show system' and 'show running-config' gives no problems.
> > > >
> > > > >
> > > > > meaning that
> > > > > clogin -c 'show system;show running-config' hostname completes
> > > > > w/o a timeout?  if so, that implies to me that either a pager is
> > > > > involving itself in an unrecognized manner or there is other
> > > > > unrecognized input preventing it from finding the prompt
> > > > > reliably, possibly due to TERM settings (and poor defaults).
> > > > > that could be tested, or it might debugging to, run that clogin
> > > > > from cron to see how it acts w/o a
> > > terminal.
> > > > >
> > > >
> > > > That results in:
> > > >
> > > > User Name:admin
> > > > Password:************
> > > >
> > > > console#
> > > > console# terminal length 0
> > > > % Unrecognized command
> > > >
> > > > What is issuing the 'terminal length 0' command?
> > >
> > > clogin.  how is the pager disabled on that device?
> >
> > 'terminal datadump' for both devices
> 
> you need a login script that sends that command.
> 
> > Interestingly enough, the 'show system' and 'show version' outputs of both
> switches look amazingly similar to each other. I don't know who copied who,
> but the command sets look very similar.
> 

Thanks. That got me pointed in the right direction. The built-in cisco-sb type and csblogin script seems to do the job.