Problems with pulling config off of Cisco 7301

Question

A recent job that I created is getting ERROR: Connection Refused by 12.150.11.6 I checked my login info and all works the way it should if I ssh directly to the router. I have this problem when I try to run Cirrus against it to pull configs down. I am running the recent version of Cirrus with all updates. I have run Session trace and have included the output below. Both routers are conifgured identically in Cirrus, and I have tried using ssh auto, ssh 1, and ssh 2. Any ideas would be greatly appreciated. This is from an identical router that is working. \-->StateChange: Connecting to server<-- TimerTick: mstrData=<> State=1 - Connecting to server Pending Disconnect = False TimerState not Idle, Leaving. Got HostFingerPrint: 57:8d:dc:1f:f7:83:c7:83:3c:51:fa:b5:0b:dc:a7:d9 SWTelnet9 Crypto Information Begin Protocol = SSH2 RemoteName = SSH-1.99-Cisco-1.25 SCcipher = aes128-cbc CSCipher = aes128-cbc Keys = ssh-rsa SWTelnet9 Crypto Information End -->StateChange: Connected to server - idle<-- This is from the router that isnt working. -->StateChange: Connecting to server<-- Solarwinds.Net SWTelnet9 Version 9.0.19 Connected! -->StateChange: Disconnected from server<-- Disconnected - From: 12.150.11.6

Haley · Answer

Are you able to download the config via ssh if you right-click on the device and select download?  If you are unable to download the config via ssh when manually downloading the config, then the issue is most likely related to one of the following: device template, login information, or an uncommon character in the banner or prompt.

1. Check the device template that is listed for the device.  You can check this by double-clicking the device and viewing the Device Command Template field.  If this is set to auto-determine, then ensure Cirrus has snmp access to the device.

2. Double-check the login information is entered correctly within Cirrus.

3. We will need to see screenshots from the device when you login to the device and move through the login command prompts.  We will also need to see the Session Trace for the device.  You can enable session tracing by going to File->Settings->Advanced->Session Tracing and checking the box.  The location of the session trace is also listed in the same window.  We can help troubleshoot this step by creating a Support Ticket at https://forms.netsuite.com/app/site/crm/externalcasepage.nl?compid=638609&formid=12&h=3d0552f20b2e9bd6580b and attaching the requested files.