[rancid] Rancid

[Heasley]

> Am 22.04.2017 um 16:57 schrieb Graham Mitchell <mitchell at ceicmh.org>:
> 
> I’ve just been having an issue with 3.4.1 for a couple of weeks which was driving me mad. I didn’t have much chance to look at it till today - and I did an upgrade to 3.6.2, and the issue was still there.
> 
> I had been having an issue with one of our Cisco 3945E routers. All the others were fine, and 4 new ones I set up a couple of weeks ago were working well too. In the interim, we’ve also updated the IOS code on the router from c3900e-universalk9-mz.SPA.155-3.M1.bin to c3900e-universalk9-mz.SPA.155-3.M5.bin with no resolution of the problem.
> 
> After poking around for a couple of hours (I’m not at all familiar with the RANCID internals), I tracked the issue down to the
> 
>        more system:running-config;write term
> 
> command that was being run. I did a clogin test
> 
>        ./clogin -t 90 -c "more system:running-config;write term" c1-r00-3945e-a
> 
> Which eventually timed out. Manually running the command on the router seemed to work as expected, and running on the new ones worked as expected too. However, after paying closer attention, the router giving me the issue was prompting me with the file name before doing the more, whereas the others were not.
> 
> Checking through the configuration, the router giving me the issue had
> 
>        file prompt noisy
> 
> set. The others did not.

Could you show us what that looked like, prompt to prompt?

> I’m not 100% sure why this was set on the one router (I need to check something on Monday), but setting it either ‘alert’ or ‘quiet’ fixes the issue for the moment.
> 
> I’m certainly in no position to offer a patch to the RANCID code to make it work when it’s set to noisy, but just want to bring it to the maintainers attention.
> 
> Graham Mitchell|None
> Senior Systems Engineer
> Community Mental Health Authority of Clinton, Eaton, Ingham Counties
> 
> telephone: 517 346 9523
> fax:
> email: mitchell at ceicmh.org
> website: www.ceicmh.org
> 
> 
> 
> 
> 
> 
> 
> This email might contain confidential patient or other information that is protected by federal and state law. If you believe that this email reached you accidentally please reply back to notify me about the error, and please do not share this email with anybody else. If you are not the intended recipient do not review, distribute or duplicate any portion of this email.
>