[rancid] Problem with Rancid and Nexus 7000

[Matt L]

So I have Rancid working fine with all my other gear, ASA 5510's, Catalyst
3560's, etc. We recently installed a Nexus 7000 and I have been trying to
get it going with Rancid.

I created a new TACACS user for this purpose (due to the way logins work for
NX-OS), defined it in cloginrc with autoenable as '1'.

This is what happens if I just run clogin to the box with no extra flags:

[***@linuxhost ~]$ clogin nexus
nexus
spawn ssh -c 3des -x -l rancidnx nexus
#User Access Verification#
Password:


It just sits there and does nothing at this point. I can enter the password
manually and it will login successfully.

If I remove the autoenable from cloginrc, it will successfully login, but
then hang there (I assume waiting for enable prompt which will never
appear).

Rancid version is 2.3.3 (I have tried with 2.3.6 clogin separately as well).

NX-OS version is 5.1(2).

Obviously until I can get past the initial login, I can't test with nxrancid
or any type of automation.

Any ideas? Am I missing something stupid?

Thanks,

Matt

[john heasley]

Post by Matt L
So I have Rancid working fine with all my other gear, ASA 5510's, Catalyst
3560's, etc. We recently installed a Nexus 7000 and I have been trying to
get it going with Rancid.
I created a new TACACS user for this purpose (due to the way logins work for
NX-OS), defined it in cloginrc with autoenable as '1'.
nexus
spawn ssh -c 3des -x -l rancidnx nexus
#User Access Verification#

where are the #'s coming from? from your tacacs, i suspect. that looks
like a cli prompt to clogin.

Post by Matt L
It just sits there and does nothing at this point. I can enter the password
manually and it will login successfully.
If I remove the autoenable from cloginrc, it will successfully login, but
then hang there (I assume waiting for enable prompt which will never
appear).
Rancid version is 2.3.3 (I have tried with 2.3.6 clogin separately as well).
NX-OS version is 5.1(2).
Obviously until I can get past the initial login, I can't test with nxrancid
or any type of automation.
Any ideas? Am I missing something stupid?
Thanks,
Matt
_______________________________________________
Rancid-discuss mailing list
http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss

[Matt L]

Default login banner. Someone mentioned to me privately to change it to
remove any #'s, and that actually did the trick. So everything looks good
now.

Thanks for the responses everyone!

Post by Matt L

Post by Matt L
So I have Rancid working fine with all my other gear, ASA 5510's,

Catalyst

Post by Matt L
3560's, etc. We recently installed a Nexus 7000 and I have been trying

to

Post by Matt L
get it going with Rancid.
I created a new TACACS user for this purpose (due to the way logins work

for

Post by Matt L
NX-OS), defined it in cloginrc with autoenable as '1'.
nexus
spawn ssh -c 3des -x -l rancidnx nexus
#User Access Verification#

where are the #'s coming from? from your tacacs, i suspect. that looks
like a cli prompt to clogin.

Post by Matt L
It just sits there and does nothing at this point. I can enter the

password

Post by Matt L
manually and it will login successfully.
If I remove the autoenable from cloginrc, it will successfully login, but
then hang there (I assume waiting for enable prompt which will never
appear).
Rancid version is 2.3.3 (I have tried with 2.3.6 clogin separately as

well).

Post by Matt L
NX-OS version is 5.1(2).
Obviously until I can get past the initial login, I can't test with

nxrancid

Post by Matt L
or any type of automation.
Any ideas? Am I missing something stupid?
Thanks,
Matt
_______________________________________________
Rancid-discuss mailing list
http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss

[Chris Moody]

This post might be inappropriate. Click to display it.

[Routt, Brian]

How did you remove the #? I removed my banner and used different delimiters (}) but the running config still displays #.
To illustrate, I typed this
banner motd }
******************************************************
Message text
******************************************************
}

But the config still displays this

banner motd #
******************************************************
Message text
******************************************************
#

Thanks
-Brian Routt

From: rancid-discuss-***@shrubbery.net [mailto:rancid-discuss-***@shrubbery.net] On Behalf Of Matt L
Sent: Wednesday, February 09, 2011 1:23 PM
To: john heasley
Cc: rancid-***@shrubbery.net
Subject: Re: [rancid] Problem with Rancid and Nexus 7000

Default login banner. Someone mentioned to me privately to change it to remove any #'s, and that actually did the trick. So everything looks good now.

Thanks for the responses everyone!

Post by Matt L
So I have Rancid working fine with all my other gear, ASA 5510's, Catalyst
3560's, etc. We recently installed a Nexus 7000 and I have been trying to
get it going with Rancid.
I created a new TACACS user for this purpose (due to the way logins work for
NX-OS), defined it in cloginrc with autoenable as '1'.
nexus
spawn ssh -c 3des -x -l rancidnx nexus
#User Access Verification#

where are the #'s coming from? from your tacacs, i suspect. that looks
like a cli prompt to clogin.

Post by Matt L
It just sits there and does nothing at this point. I can enter the password
manually and it will login successfully.
If I remove the autoenable from cloginrc, it will successfully login, but
then hang there (I assume waiting for enable prompt which will never
appear).
Rancid version is 2.3.3 (I have tried with 2.3.6 clogin separately as well).
NX-OS version is 5.1(2).
Obviously until I can get past the initial login, I can't test with nxrancid
or any type of automation.
Any ideas? Am I missing something stupid?
Thanks,
Matt
_______________________________________________
Rancid-discuss mailing list
http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss

[john heasley]

Post by Routt, Brian
How did you remove the #? I removed my banner and used different delimiters (}) but the running config still displays #.

are you sure thats the problem? assuming that your problem still lies

Post by Routt, Brian

Post by Matt L
nexus
spawn ssh -c 3des -x -l rancidnx nexus
#User Access Verification#

where are the #'s coming from? from your tacacs, i suspect. that looks
like a cli prompt to clogin.

thats not the banner in the configuration. clogin should, after the
_displayed_ banner and successful login, acquire a more specific match
of the prompt and avoid matching the #s in the configuration.