cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1929
Views
15
Helpful
3
Replies

NSO sync-from Junos SSH subset not supported

RobvdL
Level 1
Level 1

I've loaded a netsim with Junos, IOS-XE,NX and Fortios and I've added the devices in NSO v4.7

Also I've loaded the nso4.7 most recent neds.

 

I fetched the keys without any problem.

But now when I want to sync-from to all devices, only the Junos devices are reporting an error.

sync-result {
device xxxx
result false
info Failed to authenticate towards device xxxx: SSH subsystem not supported

 

I've added the Junos devices like this

devices device xxx
address 127.0.0.1 port 10023
device-type netconf ned-id netconf
authgroup lab-test
state admin-state unlocked
 
The auth group is:
devices authgroups group lab-test
default-map remote-name admin
default-map remote-password admin
 
Now when I change the password I receive the following error:
root@ncs(config)# devices device xxx sync-from
result false
info Failed to authenticate towards device xxx: Bad password for local/remote user admin/test
 
Also when I change the authgroup to use root/root I get the same errors. (First I needed to set the root password in the netsim.)
 
What do I do wrong?
 
 
1 Accepted Solution

Accepted Solutions

lmanor
Cisco Employee
Cisco Employee

I noticed that your port configured on you on-boarded Juniper device is 10023..

 

> address 127.0.0.1 port 10023

 

Did you explicitly create your netsim device using this port?

Generally, by default the netsim devices are created using 12022, and increment for successive devices...

 

admin@ncs% show devices device * port
device jnpr-0 {
port 12022;
}
device jnpr-1 {
port 12023;
}

 

 

View solution in original post

3 Replies 3

lmanor
Cisco Employee
Cisco Employee

I noticed that your port configured on you on-boarded Juniper device is 10023..

 

> address 127.0.0.1 port 10023

 

Did you explicitly create your netsim device using this port?

Generally, by default the netsim devices are created using 12022, and increment for successive devices...

 

admin@ncs% show devices device * port
device jnpr-0 {
port 12022;
}
device jnpr-1 {
port 12023;
}

 

 

Yes you're right, thanks! I have now a successfully added all devices.

 

Didn't realize it with all those other cli based NEDs.

 

ncs-netsim list

name=xxx netconf=12022 snmp=11022 ipc=5010 cli=10022 dir=/root/install/lab/netsim/xxxx/xxxx
name=xxx netconf=12023 snmp=11023 ipc=5011 cli=10023 dir=/root/install/lab/netsim/xxxx/xxxx
name=xxx netconf=12024 snmp=11024 ipc=5012 cli=10024 dir=/root/install/lab/netsim/xxxx/xxxx
name=xxx netconf=12025 snmp=11025 ipc=5013 cli=10025 dir=/root/install/lab/netsim/xxxx/xxxx
name=xxx netconf=12026 snmp=11026 ipc=5014 cli=10026 dir=/root/install/lab/netsim/xxxx/xxxx
name=xxx netconf=12027 snmp=11027 ipc=5015 cli=10027 dir=/root/install/lab/netsim/xxxx/xxxx
name=xxx netconf=12028 snmp=11028 ipc=5016 cli=10028 dir=/root/install/lab/netsim/xxxx/xxxx
name=xxx netconf=12029 snmp=11029 ipc=5017 cli=10029 dir=/root/install/lab/netsim/xxxx/xxxx
name=xxx netconf=12030 snmp=11030 ipc=5018 cli=10030 dir=/root/install/lab/netsim/xxxx/xxxx
name=xxx netconf=12031 snmp=11031 ipc=5019 cli=10031 dir=/root/install/lab/netsim/xxxx/xxxx
name=xxx netconf=12032 snmp=11032 ipc=5020 cli=10032 dir=/root/install/lab/netsim/xxxx/xxxx
name=xxx netconf=12033 snmp=11033 ipc=5021 cli=10033 dir=/root/install/lab/netsim/xxxx/xxxx
name=xxx netconf=12034 snmp=11034 ipc=5022 cli=10034 dir=/root/install/lab/netsim/xxxx/xxxx
name=xxx netconf=12035 snmp=11035 ipc=5023 cli=10035 dir=/root/install/lab/netsim/xxxx/xxxx
name=xxx netconf=12036 snmp=11036 ipc=5024 cli=10036 dir=/root/install/lab/netsim/xxxx/xxxx
name=xxx netconf=12037 snmp=11037 ipc=5025 cli=10037 dir=/root/install/lab/netsim/xxxx/xxxx
name=xxx netconf=12038 snmp=11038 ipc=5026 cli=10038 dir=/root/install/lab/netsim/xxxx/xxxx
name=xxx netconf=12039 snmp=11039 ipc=5027 cli=10039 dir=/root/install/lab/netsim/xxxx/xxxx

 

At least now I'll never forget it :) 

lmanor
Cisco Employee
Cisco Employee

A quick related tip here... which is quite useful when using many netsim devices

 

For the netsim devices that you create you can use the ncs-setup tool to create the device on-boarding configuration automatically to a file which can be loaded by NSO on its initial startup or 'load merged' into the CDB at a later time.

 

Example:

$ ncs-netsim create-network ./packages/cisco-iosxr 2 asr
DEVICE asr0 CREATED
DEVICE asr1 CREATED
 
$ ncs-netsim add-to-network ./packages/juniper-junos 2 mx
DEVICE mx0 CREATED
DEVICE mx1 CREATED
 
$ ncs-netsim start
DEVICE asr0 OK STARTED
DEVICE asr1 OK STARTED
DEVICE mx0 OK STARTED
DEVICE mx1 OK STARTED
 
## Add netsim devices to NCS startup config in ncs-cdb/netsim_devices_init.xml
$ ncs-setup --netsim-dir ./netsim --dest .
 
$ ls ncs-cdb
netsim_devices_init.xml
 
This xml file will be read at NSO initialization when it is first started to provide the initial on-boarding config for the netsim devices.
 
Or, if NSO had previously been run prior to netsim network creation, simply 'load merge' the netsim_devices_init.xml file from NSO cli config mode to pull in the initial netsim device initial configurations:
 
% load merge ncs-cdb/netsim_devices_init.xml