I've looked at a few things, but I still come back to the testing where I can see the device is logged into- whether it's a "show ver" or "sho run" but yet the backups of the config do not happen. Thanks in advance for any help.
I specified the profile (one I created). The last SSH option was tftp. Things are much improved and now I can fix all the config backups that need a more unique profile. Thanks for checking things out and your suggestions HerrDoktor
I would turn on session tracing and see if it gives you anymore insight on why it is failing.
Success Center - Session Trace
What kind of device is it, that you want to back up?
can you reach it via SNMP to get the SysOID to determine the type of the device?
do you see what device template is used to connect to the device?
Just to be sure, do you have any ACLs in place that would prevent the Orion server from reaching this device via SSH? Additionally, are you using a custom device template?
Thank you- and thank you for the link to trace. I will try this.
Thanks for looking at this.
In this particular case, it is a 6880, but I have 17 that are being backed up and 608 that are not that are various types. I have not tested each of them on a ssh connectivity version check but the ones I have-- worked.
For this 6880, it pulls a system SysOID.
I am using the default to check for version that SW provides (but that works):
"terminal width 0${CRLF}terminal length 0"
From what I know, there should be nothing blocking tftp, but you reminded me of an idea to put a tftp server on my server and see if I can query this device (that was way last week on Friday ).
Thanks again for your thoughts, they are appreciated.
There "shouldn't" be any ACLs, but I like your thoughts. I am going to try a tftp server on my Orion server and test. It's for a 6880, I am not using custom device template right now (maybe I should be...).
Thanks for your thoughts.
Possibly SNMP write credential issue per this documentation?
https://support.solarwinds.com/SuccessCenter/s/article/Cannot-download-Running-config-No-response-using-the-specified-credentials-TFTP-Host-A-B-C-D
A session trace, to see what commands and responses are sent back and forth might be the best way here to troubleshoot.
I have solved most connectivity issues ba actually analyzing the traces.
Turns out the error was not a good pointer to a solution. It's that one of my profile ways to download was tftp rather than ssh. This correction got things backed up.
Thanks all that helped me ponder over this issue.
Ah bummer... so some of the devices picked a different connection profile, or did you specify an explicit profile for those machines?