[rancid] login problem on cisco switch

N K Krishnan nkkrishnan at gmail.com
Fri Dec 7 13:48:57 UTC 2018

We ran into a similar problem recently with one (of over 200) 3850 stack.
Suggest you run each of the command that rancid runs after the clogin.

In our case, the "show version" command was taking too long and reported
that it could not figure out how long one of the switches in the stack was
up.  There were other log entries that pointed to a messed up control
plane.  A simple maintenance window switch reboot got "show version" to
work - rancid as well.

On Fri, Dec 7, 2018 at 2:25 AM Wayne Eisenberg <
Wayne.Eisenberg at carolinasit.com> wrote:

> Another similar issue - a cisco switch (SG350XG) that has no problem with
> clogin, but rancid-run always gets a timeout error ("san-switch01 clogin
> error: Error: TIMEOUT reached").
> What's the difference between the two programs? What is rancid-run
> doing/looking for that clogin is not providing?
> Thanks,
> Wayne
> _______________________________________________
> Rancid-discuss mailing list
> Rancid-discuss at shrubbery.net
> http://www.shrubbery.net/mailman/listinfo/rancid-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.shrubbery.net/pipermail/rancid-discuss/attachments/20181207/33fa7a7a/attachment.html>

More information about the Rancid-discuss mailing list