02-21-2015 07:15 AM
Is it possible to indicate to always use SSH instead of Telnet to login to a device that has not been fully discovered and no credentials determined? We have a certain set of Cisco devices that have had SNMP disabled due to a Cisco IOS bug, but I still want to collect the config. I thought that I could write a CCS or Perl script to do so, but it fails straight away when it first trys to login using Telnet, which stops the script.
My second approach was to create an external Perl API script, but I got stopped when I figured out that some of the DisSession methods appear to be missing, they are in the documention, but the .pm files are not there (open_connection, open_session_and_connection, close, etc.) Was this on purpose? Has anyone else created a cli connection using the Perl API in the sandbox?
02-21-2015 10:30 AM
Just adding that under collection and groups => config management, telnet can be totally disabled on config collection, but the order cannot be changed. It always trys telnet first.
02-27-2015 10:09 AM
What happens if you set the CLI Credentials for the device, entering only ones for SSH, and then try "Test" and "Get Configs"?
I know that by default, if SNMP collection has never worked, config collection won't be attempted. But at least it used to allow you to manually drive the CLI steps.
02-27-2015 10:17 AM
The CLI Creditials bar doesn't even show up, probably until it passes snmp and attempts to figure out the creditials. Is there any way to force that to appear some other way?