[rancid] Rancid submits random characters after logon - causes config read failure

[Jon Lewis]

With bash being my shell, I've just been doing TERM="" before using clogin 
on aristas.  After seeing heasley's response, I did a little testing, and 
vt100 seems to work as well.  My native TERM was "screen" since I like to 
use screen, it results in display similar to what you posted and an "n" 
spit out as if typed.

On Fri, 12 Sep 2014, Neil Arnold wrote:

> Hi Jethro, I've tried the hlogon too. No luck I'm afraid.
>
> John, this sounds like it could be the solution as the characters do look
> like terminal output. Can you explain how I would go about clearing the
> TERM environment and if this works, I'm assuming I would have to make a
> seperate cron job running clogin with these new parameters just for these
> problem switches?
>
> Thanks again for you help with this.
>
>
> On 12 September 2014 13:03, Jon Lewis <jlewis at lewis.org> wrote:
>
>> On Fri, 12 Sep 2014, Neil Arnold wrote:
>>
>>  Hi,
>>>
>>> I've got an issue with 3 HP Procurve switches. All are running a recent
>>> firmware version. The problem is that no config is being pulled from 3 HP
>>> switches. in my network, the others give up their config just fine. I've
>>> discovered the reason but I'm unsure of how to fix it.
>>> The issue is caused because rancid is issuing the following command to the
>>> switch after it logs on: ^[[46;148R
>>>
>>> I can see this by running /bin/clogin 10.100.20.149 and seeing that I get
>>> dropped to the following:
>>>
>>> HP_SWITCH_1# ^[[46;148R
>>> HP_SWITCH_1#
>>>
>>> So Rancid is issuing the manager username and password and then issuing
>>> ^[[46;148R which the switch doesn't understand, Rancid, having not
>>> received
>>>
>>
>> I have similar problems with clogin and arista gear.  In this case, it's
>> solved by clearing the TERM environment variable before running clogin.
>>
>> ----------------------------------------------------------------------
>>  Jon Lewis, MCP :)           |  I route
>>                              |  therefore you are
>> _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
>>
>

----------------------------------------------------------------------
  Jon Lewis, MCP :)           |  I route
                              |  therefore you are
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________