Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > SSH v1 usage in NCM

SSH v1 usage in NCM

Table of contents
Created by Mariusz Handke, last modified by Melanie Boyd on Jun 15, 2018

Views: 1,402 Votes: 2 Revisions: 6


This article provides information on SSH v1 usage in NCM.


NCM, all supported versions


NCM only uses protocols designated by the user. During installation, there are no specific settings applied except for the Global Device Defaults which hold the following information with respect to protocols:

Execute Commands and Scripts - SSH Auto
Config Request - SSH Auto

Transfer Configs - SSH Auto


The SSH Auto option means that NCM will first negotiate with the SSH v2 protocol while attempting to connect to the device. If this fails NCM, will attempt with SSH v1. If the device is configured to accept only SSH v2, the attempt to use SSH v1 will fail, as expected.


In order to find out later on, during normal NCM operations, if SSH v1 was configured for some device, perform the following:

  1. Check if the change was applied in Global Device Defaults (available in NCM Settings).
  2. Check if the change was applied in All Connection Profiles (available in NCM Settings).
  3. Check if the change was applied to the individual device (available in Node settings).


Last modified