I used our LMS 3.0 system to push the command 'transport input telnet' to the line vty's on over 250 of our Cisco devices. I made a big mistake and typed 'transport input none' which effectively cut off remote access to these devices. The staffed locations have been corrected manually via correcting the command through the console port. Most of these are remote sites though and it will take a while before we can get our field ops guys out there. We cannot remotely support these devices due to my mistake.
Is there a way to correct this via our LMS system?
I'm not familiar with the snmpset command, but I thought we may be able to use LMS to perform this function?
Is there another section of LMS besides NetConfig that might be utilized?
Any help would be greatly appreciated.
LMS 2.5 came with at least one "snmpset" binary: /opt/CSCOpx/objects/jt/bin/snmpset, so chances are LMS 3.x still has it.
Then, assuming you have a recent copy of the startup config of the devices somewhere, make your modifications to "'transport input", haul that to a directory on the LMS server that its TFTP daemon is aware of, follow the "Copy the Startup-Configuration Located on the TFTP Server to the Device" directions to upload the startup config with /opt/CSCOpx/objects/jt/bin/snmpset
Once that's successful, follow the "How can I reload a router with use of SNMP?" directions to reboot the device, or reboot via the "smart"/managed powerstrips the devices are plugged into: