Rancid works with ACS 4.2 but not 5.3

[flyerhawk]

Hey folks,

We are in the process of upgrading from ACS 4.2 to 5.3.  Most things seem to be working but we are having some major issues with the Rancid configuration tool.   I can log into devices using CLI login with the credentials that Rancid uses but Rancid fails login.

This worked fine with our 4.2 implementation but not the 5.3.  Presumably I need to make a chance in the expect scripts because the new ACS server sends a different string but I have no idea what it is supposed to be.   I'm not an expert on Rancid so I apologize for my ignorance. 

[flyerhawk]

Actually I figured it out. 

The clogin expect script was expecting that the user prompt be Username, which is what ACS 4.2 provided.  ACS 5.3 provides 'username' which didn't match.  Adding that to the regex fixed the problem.

[jspringfield]

Had the same problem and your fix did the trick.  Thanks.

[Jason Cameron]

Hi

Di you mind sharing  the code you updated as I have this exact problem

Thanks

[flyerhawk]

In the clogin script look for the "Figure out prompts" sections and modify it to the following(specifically the bolded line)..

  # Figure out prompts

    set u_prompt [find userprompt $router]

    if { "$u_prompt" == "" } {

        set u_prompt "(Username|username|Login|login|user name|User):"

    } else {

        set u_prompt [join [lindex $u_prompt 0] ""]

    }