10-10-2011 02:23 PM - edited 03-07-2019 02:43 AM
May be asking for the impossible here. We have a 1760 router that went out to one of our branches with telnet and ssh disabled (we usually disable telnet and enable ssh, unfortunately, this time ssh was not enabled). We are able to ping it remotely and from the 3550 switch that has the router connected to its port 24. Are there any other options aside from telnet or ssh that we can try? Or are we stuck sending a field tech with a console cable?
Thanks!
Solved! Go to Solution.
10-10-2011 04:00 PM
gshamlian wrote:
May be asking for the impossible here. We have a 1760 router that went out to one of our branches with telnet and ssh disabled (we usually disable telnet and enable ssh, unfortunately, this time ssh was not enabled). We are able to ping it remotely and from the 3550 switch that has the router connected to its port 24. Are there any other options aside from telnet or ssh that we can try? Or are we stuck sending a field tech with a console cable?
Thanks!
If you have an SNMP read/write community set on the device, you can do the following
1) Download the startup configuration via SNMP
2) Edit the startup configuration to enable SSH
3) Upload the edited configuration (again via SNMP) and have someone power off/on the router.
This document may help.
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_configuration_example09186a0080094aa6.shtml
or this one
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a008009463e.shtml
Cheers.
10-10-2011 02:35 PM
You can enable SSH remotely via SNMP.
10-10-2011 03:02 PM
Sorry, how do I go about doing that? I did try getting access using Cisco ASDM, but it was a no-go. I was looking on the switch to see what commands might help and saw "rcommand", doing some research on that now.
Thanks for responding.
10-10-2011 04:00 PM
gshamlian wrote:
May be asking for the impossible here. We have a 1760 router that went out to one of our branches with telnet and ssh disabled (we usually disable telnet and enable ssh, unfortunately, this time ssh was not enabled). We are able to ping it remotely and from the 3550 switch that has the router connected to its port 24. Are there any other options aside from telnet or ssh that we can try? Or are we stuck sending a field tech with a console cable?
Thanks!
If you have an SNMP read/write community set on the device, you can do the following
1) Download the startup configuration via SNMP
2) Edit the startup configuration to enable SSH
3) Upload the edited configuration (again via SNMP) and have someone power off/on the router.
This document may help.
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_configuration_example09186a0080094aa6.shtml
or this one
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a008009463e.shtml
Cheers.
10-10-2011 08:24 PM
If the remote router is configured with an SNMP read write string then changing the config to enable SSH using SNMP is certainly an option.
If the remote router is configured with either the ip http server or the secure server options then you might be able to access the remote router using a web browser and make changes to enable SSH.
Otherwise I believe that you may need to dispatch a tech carrying a console cable.
HTH
Rick
10-12-2011 06:49 PM
This worked beautifully. Downloaded the Cisco SNMP Tool (can be found on download.cnet.com). Grabbed the config. Changed the vty to allow all connections, so that we could get on via telnet. Enabled SSHv2, created the crypto keys, confirmed SSH connection, saved config, disabled telnet.
Thanks for all the answers!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide