While compiling a NED I'm receiving the following errors.  The 'system' node is most definitely included in the SNMPv2-MIB file that is provided with NSO 4.4.  Not sure what's wrong with my syntax that the container is not found. yang/snmp.yang:343: error: the node 'system' from module 'snmp' (in node 'SNMPv2-MIB' from 'SNMPv2-MIB') is not found yang/snmp.yang:347: error: the node 'system' from module 'snmp' (in node 'SNMPv2-MIB' from 'SNMPv2-MIB') is not found yang/snmp.yang:351: error: the node 'system' from module 'snmp' (in node 'SNMPv2-MIB' from 'SNMPv2-MIB') is not found yang/snmp.yang:355: error: the node 'snmp' from module 'snmp' (in node 'SNMPv2-MIB' from 'SNMPv2-MIB') is not found yang/snmp.yang:359: error: the node 'snmp' from module 'snmp' (in node 'SNMPv2-MIB' from 'SNMPv2-MIB') is not found My code in src/snmp.yang: container snmp {       description "         SNMP configuration.       ";     tailf:info "SNMP configuration";     container agent {       description "         SNMP agent configuration.       ";       tailf:callpoint snmp_agent_config {          tailf:transaction-hook subtree;       }       leaf enabled {         config false;         type boolean;         default true;       }       leaf sysDescr {         config false;         type string;         tailf:link "/SNMPv2-MIB:SNMPv2-MIB/system/sysDescr";       }       leaf sysOID {         config false;         type yang:object-identifier;         tailf:link "/SNMPv2-MIB:SNMPv2-MIB/system/sysObjectID";       }       leaf engineID {         type string {           pattern "((00:00:00:09:)((([0-9A-Fa-f]{2}):){7})([0-9A-Fa-f]{2}))";           length "35";         }         tailf:info "<Enter 12 octets, first 4 must be 00:00:00:09>";         default "00:00:00:09:00:00:06:03:09:0E:A5:BD";         tailf:cli-show-with-default;       }     } SNMPv2- yang file provided with NSO.   container SNMPv2-MIB {     container system {       tailf:snmp-oid "1.3.6.1.2.1.1";       leaf sysDescr {         type sysDescrType;         tailf:snmp-oid "1.3.6.1.2.1.1.1";         config false;       } ... View more

We are attempting for NSO to talk with CSP2100.  Reads work fine but any commit command fails with an RPC error.  Looking at the netconf & devel logs on the CSP side, there is an error adding a checkpoint.  Am I correct that the RPC failure is due to a lack of implementing add_checkpoint_running in our backend CSP2100 code? mwronkow@ncs(config-service-asa-test)# commit Aborted: RPC error towards csp2100: operation_failed: application communication failure netconf.trace 30-Nov-2016::04:36:48.266 **< sess:13 write: <rpc-reply message-id="6" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">   <rpc-error>     <error-type>application</error-type>     <error-tag>operation-failed</error-tag> <error-severity>error</error-severity>     <error-message xml:lang="en">application communication failure</error-message>   </rpc-error> </rpc-reply devel.log <ERR> 30-Nov-2016::04:36:48.265 csp2100-b confd[21370]: devel-c add_checkpoint_running error {external, "no registration found for db callback add_checkpoint_running for daemon vsb_trans_daemon id 0" ... View more