topic Re: Problem with configuring NSO device-type cli ned-id in NSO Developer Hub Discussions

Problem with configuring NSO device-type cli ned-id

wesleyderks — Wed, 23 Sep 2020 21:34:17 GMT

I am trying to configure the NSO in the lab NSO Fundamentals, but I get stuck when I add the device edge-sw01. When I follow the steps one off the commands isn't recognized. This are the steps what on the site is writen:

devices device edge-sw01

address 10.10.20.172

authgroup labadmin

device-type cli ned-id cisco-ios-cli-6.44

device-type cli protocol telnet

ssh host-key-verification none commit

All the commands are accepted, only device-type cli ned-id cisco-ios-cli-6.44 isn't possible to add. Also I tryed the load merge command from a copy off the config from 10.10.20.49, but I get the same error on line 5 what is the same command.

The only 3 options what I have got are these:

admin@ncs(config-device-edge-sw01)# device-type cli ned-id ?
Description: The NED Identity
Possible completions:
[lsa-netconf] lsa-netconf netconf snmp

What I am doing wrong? Hopefully anyone has a answer for my problem, thanks anyway for reading

Gr Wesley

Re: Problem with configuring NSO device-type cli ned-id

lmanor — Thu, 24 Sep 2020 20:27:15 GMT

It looks like you may not have the cisco-ios-cli-6.44 NED package (or any other NED for that matter) loaded into NSO.

If you show packages what is loaded into NSO:

From operational cli mode:

admin@ncs# show packages package oper-status

Re: Problem with configuring NSO device-type cli ned-id

wesleyderks — Fri, 25 Sep 2020 13:24:42 GMT

Hello Imanor

Thanks for the reply. It seems that is the problem that the NED packages aren't loaded in the NSO

admin@ncs# show packages package oper-status
% No entries found.

I thought that I loaded the NED packages in a early state with these commands

ncs-setup --dest ${NCS_DIR}/packages/neds

ncs-setup --package nso/packages/neds/cisco-ios-cli-6.44 \
> --package nso/packages/neds/cisco-nx-cli-5.15 \
> --package nso/packages/neds/cisco-iosxr-cli-7.20 \
> --package nso/packages/neds/cisco-asa-cli-6.8 \
> --dest nso-instance

After these commands I saw in the directory nso-instance these logical links created

lrwxrwxrwx 1 developer docker 26 Sep 25 04:48 cisco-asa-cli-6.8 -> packages/cisco-asa-cli-6.8
lrwxrwxrwx 1 developer docker 27 Sep 25 04:48 cisco-ios-cli-6.44 -> packages/cisco-ios-cli-6.44
lrwxrwxrwx 1 developer docker 29 Sep 25 04:48 cisco-iosxr-cli-7.20 -> packages/cisco-iosxr-cli-7.20
lrwxrwxrwx 1 developer docker 26 Sep 25 04:48 cisco-nx-cli-5.15 -> packages/cisco-nx-cli-5.15

Did I forget something or isn't the configuration correct? I follewed 3 times the steps, but I don't see what is wrong.

Re: Problem with configuring NSO device-type cli ned-id

lmanor — Fri, 25 Sep 2020 16:19:06 GMT

So, the ncs-setup command will create a new NSO 'run-time' directory to use with a NSO 'local' install.

Generally the run-time directory is created outside of the NSO product install directory.

This command above (I didn't see this command in the lab example):

ncs-setup --dest ${NCS_DIR}/packages/neds

created a new directory called 'neds' as a NSO run-time directory, overwriting the NEDs provided with your NSO distribution.

Subsequent linking to neds in that directory which are no longer there - so your links are going nowhere so NSO has nothing to load.

So you'll need to re-install NSO to get those NEDs back and then proceed as follows:

I keep a directory called Projects where I put all my NSO run-time directories, say it's at ~/Projects:

$ cd ~/Projects

Projects$ source ~/NCS/releases/nso-5.3.1/ncsrc

Projects$ echo $NCS_DIR

/Users/lmanor/NCS/releases/nso-5.3.1

Projects$

Projects$ ncs-setup --package $NCS_DIR/packages/neds/cisco-ios-cli-3.8 --package $NCS_DIR/packages/neds/cisco-nx-cli-3.0 --package $NCS_DIR/packages/neds/cisco-iosxr-cli-3.5 --package $NCS_DIR/packages/neds/cisco-asa-cli-6.6 --dest nso-runtime
Projects$ cd nso-runtime
nso-runtime$ ls
README.ncs logs ncs-cdb ncs.conf packages scripts state
nso-runtime$ cd packages/
packages$ ls -altr
total 0
lrwxr-xr-x 1 lmanor staff 68 Sep 25 12:07 cisco-ios-cli-3.8 -> /Users/lmanor/NCS/releases/nso-5.3.1/packages/neds/cisco-ios-cli-3.8
lrwxr-xr-x 1 lmanor staff 67 Sep 25 12:07 cisco-nx-cli-3.0 -> /Users/lmanor/NCS/releases/nso-5.3.1/packages/neds/cisco-nx-cli-3.0
lrwxr-xr-x 1 lmanor staff 70 Sep 25 12:07 cisco-iosxr-cli-3.5 -> /Users/lmanor/NCS/releases/nso-5.3.1/packages/neds/cisco-iosxr-cli-3.5
lrwxr-xr-x 1 lmanor staff 68 Sep 25 12:07 cisco-asa-cli-6.6 -> /Users/lmanor/NCS/releases/nso-5.3.1/packages/neds/cisco-asa-cli-6.6
drwxr-xr-x 6 lmanor staff 192 Sep 25 12:07 .
drwxr-xr-x 9 lmanor staff 288 Sep 25 12:07 ..
packages$ ls cisco-asa-cli-6.6
CHANGES LICENSES.nedcom build-meta-data.xml netsim private-jar src
LICENSE README load-dir package-meta-data.xml shared-jar

Then from the nso run-time directory, start NSO:

packages$ cd ..

nso-runtime$ ncs

nso-runtime$ ncs_cli -u admin

admin connected from 127.0.0.1 using console on LMANOR-M-24MR
admin@ncs>

admin@ncs> show packages package oper-status
PACKAGE
PROGRAM META FILE
CODE JAVA PYTHON BAD NCS PACKAGE PACKAGE CIRCULAR DATA LOAD ERROR
NAME UP ERROR UNINITIALIZED UNINITIALIZED VERSION NAME VERSION DEPENDENCY ERROR ERROR INFO
------------------------------------------------------------------------------------------------------------------------------
cisco-asa-cli-6.6 X - - - - - - - - - -
cisco-ios-cli-3.8 X - - - - - - - - - -
cisco-iosxr-cli-3.5 X - - - - - - - - - -
cisco-nx-cli-3.0 X - - - - - - - - - -

Re: Problem with configuring NSO device-type cli ned-id

wesleyderks — Sat, 26 Sep 2020 14:30:17 GMT

Thanks for the reply, at this moment there is a maintenance window, so I will try the solution after the weekend

greatings Wesley

Re: Problem with configuring NSO device-type cli ned-id

wesleyderks — Tue, 29 Sep 2020 20:11:29 GMT

Thanks Imanor,

I tryed the steps again today and everything is working fine

Gr Wesley

Re: Problem with configuring NSO device-type cli ned-id

RiekCyber — Wed, 01 Mar 2023 20:04:20 GMT

Hello,

You just have to copy the NED package you need from ./ncs-6.0/packages/neds/ to ./ncs-run/packages/

Then You have to reload the package in the cli with the command admin@ncs# packages reload

>> https://www.ciscolive.com/c/dam/r/ciscolive/emea/docs/2019/pdf/LABSPG-2442-LG.pdf .

There is no NED package in the ncs-run directory by default.

Truly yours,

Re: Problem with configuring NSO device-type cli ned-id

aj.riveras — Tue, 30 Jan 2024 22:34:57 GMT

Thanks your suggestion did it for me. Have a great day!

Re: Problem with configuring NSO device-type cli ned-id

Jesus Illescas — Wed, 31 Jan 2024 09:20:57 GMT

If you are starting with NSO, I highly recommend to take a look at these learning labs.

- https://developer.cisco.com/learning/labs/learn-nso-with-netsim/

- https://developer.cisco.com/learning/tracks/get_started_with_nso/

They go step-by-step to getting started with NSO. There you can find detailed guides and you can practice with a live environment directly on the web browser.

The NSO you can find there is based on the official NSO container.

Let us know any suggestion, we are actively update them.