Wayne Eisenberg
2013-11-12 20:14:24 UTC
Hi all,
Here's another unusual (for me) problem: for one specific switch, when I run clogin, it doesn't respond after the login. In other words,
[***@host]$ bin/clogin switch.test.com
spawn ssh -c 3des -x -l user switch.test.com
******************************************************
* *
* WARNING *
* *
* This device is private property. *
* Unauthorized access is strictly prohibited. *
* If you are not authorized to access this device, *
* you MUST disconnect immediately. *
* All access to this device is logged. *
* *
******************************************************
Password:
MC_CORE_TOP#
[now I type:]
sh ver
[then after some seconds...]
Error: TIMEOUT reached
[***@host]$
It doesn't matter if I run clogin manually or if it happens as part of the normal rancid run, the same thing happens. The other cisco switches do not have this problem. If I run ssh manually from the prompt (ssh -c 3des -x -l user switch.test.com), it gets to the enable prompt and then responds to any command I give it without problem. So it's not the ssh program, (because the exact command line behaves as it should), or the configuration of the firewall that is between the rancid box and the switch (or nothing would work from behind there). The clogin script works for everything else, so it's not the script either, right?
Any ideas?
Wayne
________________________________
The information in this Internet e-mail (and any attachments) is confidential, may be legally privileged and is intended solely for the Addressee(s) named above. If you are not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, then any dissemination or copying of this e-mail (and any attachments) is prohibited and may be unlawful. If you received this e-mail in error, please immediately notify us by e-mail or telephone, then delete the message. Thank you.
Here's another unusual (for me) problem: for one specific switch, when I run clogin, it doesn't respond after the login. In other words,
[***@host]$ bin/clogin switch.test.com
spawn ssh -c 3des -x -l user switch.test.com
******************************************************
* *
* WARNING *
* *
* This device is private property. *
* Unauthorized access is strictly prohibited. *
* If you are not authorized to access this device, *
* you MUST disconnect immediately. *
* All access to this device is logged. *
* *
******************************************************
Password:
MC_CORE_TOP#
[now I type:]
sh ver
[then after some seconds...]
Error: TIMEOUT reached
[***@host]$
It doesn't matter if I run clogin manually or if it happens as part of the normal rancid run, the same thing happens. The other cisco switches do not have this problem. If I run ssh manually from the prompt (ssh -c 3des -x -l user switch.test.com), it gets to the enable prompt and then responds to any command I give it without problem. So it's not the ssh program, (because the exact command line behaves as it should), or the configuration of the firewall that is between the rancid box and the switch (or nothing would work from behind there). The clogin script works for everything else, so it's not the script either, right?
Any ideas?
Wayne
________________________________
The information in this Internet e-mail (and any attachments) is confidential, may be legally privileged and is intended solely for the Addressee(s) named above. If you are not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, then any dissemination or copying of this e-mail (and any attachments) is prohibited and may be unlawful. If you received this e-mail in error, please immediately notify us by e-mail or telephone, then delete the message. Thank you.