Hi,
looking at the ned-builder chapter in the documentation there is no indication how you would turn on tracing.
one possibility is you trace with packet capture.. but that is always quite some effort IMO. This would give you definitive answers,
Another is that you recreate what should be happening. so you have asked to fetch a module, there is a command line tool for doing basic netconf operations called netconf-console that comes with NSO. You will have to install paramiko to run it
pip3 install paramiko
then you can call the tool. Here is an example to call it to access the NSO netconf NBI and give me the output of the hello message
% netconf-console -u admin -p admin --host=localhost --port=2022 --hello
that lists all the modules,
then you can do an interactive session or use the rpc option command line option
% netconf-console -u admin -p admin --host=localhost --port=2022 -i
* Enter a NETCONF operation, end with an empty line, or only empty continuing session
<get-schema
xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">
<identifier>tailf-ncs-scheduler</identifier>
<version>2020-06-25</version>
<format>yang</format>
</get-schema>
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="3">
<data xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring"><
