Mailing List Archive

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@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@shrubbery.net
> http://www.shrubbery.net/mailman/listinfo/rancid-discuss
>

Fri, Dec 07, 2018 at 05:48:57AM -0800, N K Krishnan:
> 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.

just a pointer to help with this; rancid -t <type> -C hostname

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

> 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.

I see the same issue here as with the other one. It doesn't like the 'terminal length 0' command. What to do?

$ bin/clogin -c'show version' san-switch01

User Name: ****
Password:****************

San-Switch01#
San-Switch01#terminal length 0
% Unrecognized command
_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@shrubbery.net
http://www.shrubbery.net/mailman/listinfo/rancid-discuss

Do you have "terminal length 0" disabled either by your AAA server, or by the priviledge level defined, or by the... I forget from the other day, there was a 3rd way to define role-based access control, but do you have this command either (a) not specifically allowed or (b) specifically disabled by whatever AAA mechanism you're using?




?On 12/11/18, 2:07 AM, "Wayne Eisenberg" <Wayne.Eisenberg@CarolinasIT.com> wrote:

> 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.

I see the same issue here as with the other one. It doesn't like the 'terminal length 0' command. What to do?

$ bin/clogin -c'show version' san-switch01

User Name: ****
Password:****************

San-Switch01#
San-Switch01#terminal length 0
% Unrecognized command


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