08-13-2010 05:10 AM
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.
Thanks,
Solved! Go to Solution.
08-13-2010 03:12 PM
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
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_configuration_example09186a0080094aa6.shtml
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:
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_q_and_a_item09186a00800c263d.shtml#qa4
08-13-2010 03:12 PM
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
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_configuration_example09186a0080094aa6.shtml
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:
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_q_and_a_item09186a00800c263d.shtml#qa4
08-16-2010 04:55 AM
Good idea and thanks for the info. Cisco TAC suggested I use
the snmpset command from a separate window server to grab the most recent config from LMS.
The only difference in their recommendation is that they added some MIB strings that will put the config file directly into the running configuration. So, no outage for the reload is required.
Here is the example:
snmpset -v1 -c
snmpset -v1 -c
08-16-2010 04:08 PM
I thought copying from TFTP to the device's running config *merges* the two copies, at least when done on the CLI via "copy tftp running". OTOH, "copy tftp start" replaces the startup config. If the SNMP approach can actually overwrite the on-device running config, that's great and certainly a much palatable solution to replacing startupconfig+rebooting.
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