11-22-2022 03:37 AM - edited 11-22-2022 04:05 AM
Hi All,
I have a nso base image to run on centos platform and a docker compose file out of that base image.
On my mac, I am trying to deploy the NSO container and I ran docker compose up.
In the logs i can see something like
<ERR> 22-Nov-2022::10:08:00.985 ec5033e0f9d5 ncs[856]: - The dependency node '/ncs:devices/device/config/ios:interface/Multilink/vlan-range/ppp' for node '/ncs:devices/device/config/ios:interface/Multilink/vlan-range/service-policy/output' in module 'tailf-ncs' does not exist
<ERR> 22-Nov-2022::10:08:00.986 ec5033e0f9d5 ncs[856]: - The dependency node '/ncs:devices/device/config/ios:interface/Multilink/vlan-range/encapsulation-pointtopoint/encapsulation' for node '/ncs:devices/device/config/ios:interface/Multilink/vlan-range/service-policy/output' in module 'tailf-ncs' does not exist
and after some time
<DEBUG> 22-Nov-2022::10:08:11.957 ec5033e0f9d5 ncs[856]: - Loading file /opt/ncs/ncs-5.6.3.1/scripts/command/device_save.sh
<INFO> 22-Nov-2022::10:08:12.068 ec5033e0f9d5 ncs[856]: - Starting to listen for Internal IPC on 127.0.0.1:4569
<INFO> 22-Nov-2022::10:08:14.221 ec5033e0f9d5 ncs[856]: - Starting the NCS Java VM
<NOTICE> 22-Nov-2022::10:08:19.918 ec5033e0f9d5 ncs[856]: - The notification replay store log ''ncs-events'' has been repaired
<NOTICE> 22-Nov-2022::10:08:19.989 ec5033e0f9d5 ncs[856]: - The notification replay store log ''kicker-events'' has been repaired
<NOTICE> 22-Nov-2022::10:08:20.028 ec5033e0f9d5 ncs[856]: - The notification replay store log ''device-notifications'' has been repaired
<NOTICE> 22-Nov-2022::10:08:20.063 ec5033e0f9d5 ncs[856]: - The notification replay store log ''service-state-changes'' has been repaired
<INFO> 22-Nov-2022::10:08:23.232 ec5033e0f9d5 ncs[856]: - Starting to listen for NETCONF SSH on 0.0.0.0:2022
<INFO> 22-Nov-2022::10:08:24.846 ec5033e0f9d5 ncs[856]: - Starting to listen for WebUI TCP on 0.0.0.0:8080
<INFO> 22-Nov-2022::10:08:24.847 ec5033e0f9d5 ncs[856]: - Starting to listen for WebUI SSL on 0.0.0.0:8888
<INFO> 22-Nov-2022::10:08:25.299 ec5033e0f9d5 ncs[856]: - Starting to listen for CLI SSH on 0.0.0.0:2024
<INFO> 22-Nov-2022::10:10:13.510 ec5033e0f9d5 ncs[856]: - NCS started vsn: 5.6.3.1
<INFO> 22-Nov-2022::10:10:13.920 ec5033e0f9d5 ncs[856]: - Starting the NCS Smart Licensing Java VM
How can i verify if my nso is properly working or not?
I have tried
docker exec -it <containerid> bash -lc 'ncs_cli -u admin' and then on the prompt , I tried some basic commands
11-24-2022 05:29 AM
Are you using a NED package? It looks like there might be something wrong with it and the dependencies of the model definition. Your NSO should most likely be working properly, but that package might not be working. I suggest that you look into that package. You can as a start see if it has been properly loaded by running the following NSO command:
admin@ncs> show packages package oper-status
11-28-2022 08:46 AM
Take a look at https://github.com/NSO-developer/nso-docker
The heavy lifting to get NSO running in Docker has been taken care of.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide