Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

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

SSH v1 usage in NCM

Table of contents
Created by Mariusz Handke, last modified by MindTouch on Jun 23, 2016

Views: 1,020 Votes: 2 Revisions: 5

Overview

This article provides information on SSH v1 usage in NCM.

Environment

NCM 7.3 and later

Detail

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

Tags

Classifications

Public