I've got a weird issue I haven't seen before. I'm trying to set up config backups to a device and ultimately set it up for realtime change detection, but i'm unable to get NCM to SSH to the device to get the backup. If I launch putty from the same server Solarwinds is installed on, I can SSH to the device with the same credentials just fine. I set NCM to use a local account to get into the device and pull the config it fails. Here's what I dug up when I enabled SSH logging events:
Sep 10 16:28:53.431 EDT: %SSH-5-SSH2_USERAUTH: User 'ncmservice' authentication for SSH2 Session from 10.1.8.142 (tty = 2) using crypto cipher 'aes128-cbc', hmac 'hmac-sha1' Failed
Sep 10 16:28:53.431 EDT: %SSH-5-SSH2_CLOSE: SSH2 Session from 10.1.8.142 (tty = 2) for user 'ncmservice' using crypto cipher 'aes128-cbc', hmac 'hmac-sha1' closed
Sep 10 16:28:57.567 EDT: %SSH-5-SSH2_USERAUTH: User 'ncmservice' authentication for SSH2 Session from 10.1.8.142 (tty = 3) using crypto cipher 'aes128-cbc', hmac 'hmac-sha1' Failed
Sep 10 16:28:57.567 EDT: %SSH-5-SSH2_CLOSE: SSH2 Session from 10.1.8.142 (tty = 3) for user 'ncmservice' using crypto cipher 'aes128-cbc', hmac 'hmac-sha1' closed
Sep 10 16:29:01.719 EDT: %SSH-5-SSH2_USERAUTH: User 'ncmservice' authentication for SSH2 Session from 10.1.8.142 (tty = 2) using crypto cipher 'aes128-cbc', hmac 'hmac-sha1' Failed
Sep 10 16:29:01.719 EDT: %SSH-5-SSH2_CLOSE: SSH2 Session from 10.1.8.142 (tty = 2) for user 'ncmservice' using crypto cipher 'aes128-cbc', hmac 'hmac-sha1' closed
Sep 10 16:32:53.725 EDT: %SSH-5-SSH2_CLOSE: SSH2 Session from 10.1.8.142 (tty = 1) for user 'ncmservice' using crypto cipher 'aes256-cbc', hmac 'hmac-sha1' closed
Sep 10 16:35:05.026 EDT: %SSH-5-SSH2_USERAUTH: User 'ncmservice' authentication for SSH2 Session from 10.1.8.142 (tty = 1) using crypto cipher 'aes256-cbc', hmac 'hmac-sha1' Failed
Sep 10 16:35:05.026 EDT: %SSH-5-SSH2_CLOSE: SSH2 Session from 10.1.8.142 (tty = 1) for user 'ncmservice' using crypto cipher 'aes256-cbc', hmac 'hmac-sha1' closed
Sep 10 16:36:02.174 EDT: %SSH-5-SSH2_USERAUTH: User 'ncmservice' authentication for SSH2 Session from 10.1.8.142 (tty = 1) using crypto cipher 'aes256-cbc', hmac 'hmac-sha1' Succeeded
Sep 10 16:36:08.530 EDT: %SSH-5-SSH2_CLOSE: SSH2 Session from 10.1.8.142 (tty = 1) for user 'ncmservice' using crypto cipher 'aes256-cbc', hmac 'hmac-sha1' closed
The thing that sticks out at me is the differing crypto ciphers (aes128-cbc vs aes256-cbc) when using Putty vs Solarwinds. Is there some way to change settings in NCM so it uses AES256?