OID to enable transport input telnet

[shanemoss]

Hi Folks,

SSH access has ceased to work on one of my remote routers due to human error (my own!) meaning that I cannot access the CLI anymore.  I have RW SNMP communities configured - is there a way to enable transport input telnet via an OID? This would allow me to get access to the CLI and fix my mistake.

Any help appreciated.

Thanks in advance. S.

[shanemoss]

Hi Folks,

I was able to enable telnet using procedures outlined on other discussions here;

http://www.cisco.com/en/US/tech/tk648/tk362/technologies_configuration_example09186a0080094aa6.shtml

Basically I copied the running config of the router to TFTP using;

snmpset -v 1 -c RW-Community Router-IP-Address .1.3.6.1.4.1.9.9.96.1.1.1.1.2.700 i 1 .1.3.6.1.4.1.9.9.96.1.1.1.1.3.700 i 4 .1.3.6.1.4.1.9.9.96.1.1.1.1.4.700 i 1 .1.3.6.1.4.1.9.9.96.1.1.1.1.5.700 a TFTP-Server-IP.1.3.6.1.4.1.9.9.96.1.1.1.1.6.700 s "filename" .1.3.6.1.4.1.9.9.96.1.1.1.1.14.700 i 4

Then modified the config file (changed the transport input from ssh to telnet) and copied it back to the router;

snmpset -v 1 -c RW-Community Router-IP-Address .1.3.6.1.4.1.9.9.96.1.1.1.1.2.701 i 1 .1.3.6.1.4.1.9.9.96.1.1.1.1.3.701 i 1 .1.3.6.1.4.1.9.9.96.1.1.1.1.4.701 i 4 .1.3.6.1.4.1.9.9.96.1.1.1.1.5.701 a TFTP-Server-IP .1.3.6.1.4.1.9.9.96.1.1.1.1.6.701 s "modified-file" .1.3.6.1.4.1.9.9.96.1.1.1.1.14.701 i 4

The best thing about this method is that there was no interuption to service of the router.  The 700 and 701 above are random numbers but must be unique for each snmpset. This session id times out after five minutes, if you try a second snmpset within five minutes of a previous snmpset using the same session id it will not work.

[lmediavilla]

shanemoss in 2017 you've saved my life. Thank you for your answer.