To better understand what might have caused interoperability issues, NETCONF trace logging can be used on a per device basis. To enable trace logging for debugging a device issue, see the example below: NSO Window:
Terminal
Copyadmin@ncs(config)# devices device test1a trace pretty
admin@ncs(config-device-test1a)# commit
admin@ncs(config-device-test1a)# disconnect
The NETCONF trace log for test1a can be found in logs/netconf-test1a.trace.
NSO Issues
If you run into the following issue while starting NSO:
Terminal
Copy$ ncs
NCS package upgrade failed with reason 'User java class "com.tailf.packages.ned.ios.UpgradeNedId" exited with status 127'
Daemon died status=13
Make sure that the Java runtime environment has been set up on your system. Please, refer to the Prerequisites section in Chapter 1 of the NSO Installation Guide that can be found under the "doc" folder in your installation directory after NSO has been installed on your system.
DrNED Examiner Issues
The log files for capturing DrNED Examiner issues can be found in "logs/ncs-python-vm-drned-xmnr.log".
If you get the following errors while using DrNED examiner:
Terminal
Copyadmin@ncs(config-device-test1a)# drned-xmnr transitions transition-to-state state-name state1
failure PyTest not installed or DrNED running directory (/tmp/xmnr/test1a/test/drned-skeleton) not set up