Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

SSH Connection Refused during Config Backup Job

I am running a daily backup config job on 100 devices. Each day there are failures. Day 1, 51 failures out of 100, day 2 63 failures out of 100. All are "Connection Refused"

I tried the reset of the config settings remove number of concurrent connections from 25 to 1 but that didn't work.

I can ping the devices.

Some devices can't be reached by SSH but some can so it isn't just domain, crypto key or ACL.

Find more posts tagged with

Comments

marcrobinson

First - you are talking about NCM? If so, are the failures randomly occurring or is it mostly the same ones? I would look at the NCM job session logs. It creates a log of files, but the detail is excellent for troubleshooting. If it is usually the same ones, or one that is always failing - try a manual backup and see if it runs.

Tips for troubleshooting a connection issue (solarwinds.com)

Troubleshooting NCM performance for jobs /devices downloading configs failure - Forum - Network Configuration Manager (NCM) - THWACK (solarwinds.com) Old thwack post with lots of tidbits. Job timeout is one I would look at.

Troubleshoot issues with NCM config files (solarwinds.com)

l.mendoza

try to test the profile or credentials used for NCM.

To do this, note one device that is failing.

Go to manage node, find that node, edit then at the botttom part, try to test the NCM profile used if it's working.

Hope this helps.

stuartd

Almost certainly due to weak / old ssh ciphers in your version of Solarwinds and your end devices are running newer versions.

The answers are:

Update to 2024.2.1 to get latest ciphers built in.
Downgrade end node ciphers to weaker ones.

Or you can read this: SSH - Connection Refused Cipher Updates - An F.Y.I. where I detail it al.