Error SPC-NCM-20007 is shown when doing a device configuration capture in Spectrum NCM
search cancel

Error SPC-NCM-20007 is shown when doing a device configuration capture in Spectrum NCM


Article ID: 4147


Updated On:


CA Spectrum DX NetOps


You receive a message stating that the authentication information was incorrect when attempting to access a device through NCM. 

SPC-NCM-20007: Capture Running Script Returned Error [252]:  Login Error:  Use of uninitialized value in concatenation (.) or string at C:\Windows\TEMP\script_24 line 110.



NCM connection to devices via SSH


If there has been a hardware change between two devices that previously had established an SSH connection, the SSH key becomes invalid and needs to be updated to reflect the new hardware.


The SSH keys are stored in the .ssh directory.  This directory is hidden and located in the root folder of the Spectrum Install user. 

1.   Access Command Prompt on the SpectroSERVER

2.   Login to the bash shell using ‘bash –login’

3.   Change home directory of the user that Spectrum was installed with ($ cd ~). Or you can look at the directory:

$SPECROOT/NT-Tools/SRE/home/<Spectrum Install Owner account>/ 

which is the same location as /home/<Spectrum Install Owner account> directory (on Windows platform).

4.   Change to the .ssh directory

5.   Edit the known_hosts file

6.   Search for the device name or IP address with the ‘wrong’ key

7.   Delete that key from the file (the whole line)

Or run this command line:

ssh-keygen -R <IP address with wrong key>

8.   Establish an SSH session to the device that the ‘wrong’ key was associated with

9.   You will see a message asking if you’d like to save the key for this device

10. Answer yes to the prompt; then that key will be saved in the known_hosts file for that device

    NOTE: There may also be a .ssh file located in directory:



Additional Information

Run ssh-keygen command with the help argument to get a usage display:

$ ssh-keygen help

Too many arguments.

usage: ssh-keygen [-q] [-b bits] [-t dsa | ecdsa | ed25519 | rsa] [-m format]

                  [-N new_passphrase] [-C comment] [-f output_keyfile]

       ssh-keygen -p [-P old_passphrase] [-N new_passphrase] [-m format]

                   [-f keyfile]

       ssh-keygen -i [-m key_format] [-f input_keyfile]

       ssh-keygen -e [-m key_format] [-f input_keyfile]

       ssh-keygen -y [-f input_keyfile]

       ssh-keygen -c [-P passphrase] [-C comment] [-f keyfile]

       ssh-keygen -l [-v] [-E fingerprint_hash] [-f input_keyfile]

       ssh-keygen -B [-f input_keyfile]

       ssh-keygen -D pkcs11

       ssh-keygen -F hostname [-f known_hosts_file] [-l]

       ssh-keygen -H [-f known_hosts_file]

       ssh-keygen -R hostname [-f known_hosts_file]

       ssh-keygen -r hostname [-f input_keyfile] [-g]

       ssh-keygen -G output_file [-v] [-b bits] [-M memory] [-S start_point]

       ssh-keygen -T output_file -f input_file [-v] [-a rounds] [-J num_lines]

                  [-j start_line] [-K checkpt] [-W generator]

       ssh-keygen -s ca_key -I certificate_identity [-h] [-U]

                  [-D pkcs11_provider] [-n principals] [-O option]

                  [-V validity_interval] [-z serial_number] file ...

       ssh-keygen -L [-f input_keyfile]

       ssh-keygen -A

       ssh-keygen -k -f krl_file [-u] [-s ca_public] [-z version_number]

                  file ...

       ssh-keygen -Q -f krl_file file ...