Error message when trying to collect network device configuration over SSH in NCM.
search cancel

Error message when trying to collect network device configuration over SSH in NCM.

book

Article ID: 205802

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction

When attempting to capture the running configuration for a group of Cisco devices using SSH the capture fails.
 
The $SPECROOT/NCM/NCMSERV.OUT log file showed the following errors for the devices:

-----------

Host x.x.x.x:  
Login has failed. Output:  

 at com.aprisma.spectrum.scmd.RunScript.captureRunning(RunScript.java:221)
 at com.aprisma.spectrum.scmd.ScmServiceImpl.captureConfigScriptImpl(ScmServiceImpl.java:768)
 at com.aprisma.spectrum.scmd.ScmServiceImpl.captureRunningConfigRun(ScmServiceImpl.java:308)
 at com.aprisma.spectrum.scmd.ScmServiceImpl.access$000(ScmServiceImpl.java:27)
 at com.aprisma.spectrum.scmd.ScmServiceImpl$1.run(ScmServiceImpl.java:3169)
 at java.lang.Thread.run(Thread.java:748)
java.lang.Exception: 8523794
252
Use of uninitialized value $login_output in concatenation (.) or string at d:/win32app/Spectrum/NCM/cache/script_0x704fe05_0x7077df6_cap_run line 113.

-----------

The following was found in the remote devices log:
 
SSH2 0: kex algo not supported: client curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecd

Environment

Spectrum release : 22.2.x

Windows Server 2016

Cause

Cygwin home directory for the spectrum user did not exist and therefore SSH was unable to create/populate/read the known_hosts file.

Resolution

The Cygwin home directory for the spectrum account did not exist ($SPECROOT/NT-Tools/SRE/home/spectrum/)




This was causing SSH not to be able to create and update the known_hosts file in the user's directory. In turn, this was caused  the SSH connection to fail and thus the NCM capture to fail.

Recreated the Cygwin home directory for the spectrum user on each landscape

- as the spectrum user
- launch cmd prompt
- ran: bash -login



This created the spectrum folder with some basic config files




The next time the NCM capture ran and ssh was triggered the known_hosts file was created, updated with the target devices key, and the capture was then successful