Hello,  I tried a few test cases:     import tailf-ned-fortinet-fortios-non-vdom {     prefix fortios-non-vdom;   } ....       type leafref {         path "/ncs:devices/ncs:device/ncs:name";       }     }     leaf dev-name {       type string;       default 'TESTKEY';     }     leaf fw-port-src {       tailf:info "Incoming Interface";         type leafref {            // Compiles: deref points to device tree device specified in leaf device above            // path "deref(../device)/../ncs:config/fortios-non-vdom:system/fortios-non-vdom:interface/fortios-non-vdom:interface-list/fortios-non-vdom:name";             // Compiles: likewise this set the device name to the name specified in the leaf device above           // path "/ncs:devices/ncs:device[ncs:name=current()/../device]/ncs:config/fortios-non-vdom:system/fortios-non-vdom:interface/fortios-non-vdom:interface-list/fortios-non-vdom:name";             // Compiler error: bad argument value:           //  Don't think you can specify a literal as name here, the compiler will not know how to follow the path           // path "/ncs:devices/ncs:device[ncs:name='TESTKEY']/ncs:config/fortios-non-vdom:system/fortios-non-vdom:interface/fortios-non-vdom:interface-list/fortios-non-vdom:name";             // Compiles: if you want the 'dev-name' to be static (like I think you are trying to do by specifying 'TESTKEY' above)           //  you'll need to do something like this.. to point to a leaf with the value set as a default value...           path "/ncs:devices/ncs:device[ncs:name=current()/../dev-name]/ncs:config/fortios-non-vdom:system/fortios-non-vdom:interface/fortios-non-vdom:interface-list/fortios-non-vdom:name";        }     } Makefile YANGPATH same as your's in first post.. ... View more

Usually the first thing to check is that the 'namespace identifier' e.g. the 'open-net' in your example: open-net:open-net-access Changes when converting from REST -> RESTCONF In RESTCONF this needs to be the name of the module, not the prefix defined in the module as would be the case for REST. Is your service, open-net-access a container, i.e. not a list?  If it is a list, you'll need to specify the key, here's and example  (this service is augmented under the services tree): http://127.0.0.1:8080/restconf/data/tailf-ncs:services/l2vpnpy:l2vpn=BD-109/customer_id l2vpn is the service in module l2vpnpy.     ... View more

From NSO 5.2.1 to 5.3 the built-in SSH server supportsssh-ed25519 host keys and the default SSH host key algorithm has changed to ssh-ed25519 (instead of previous ssh-rsa). OpenSSH client must be greater than version 6.5 to support this algorithm.   From NSO CHANGES file: - ncs: NSO's built in SSH server now supports ssh-ed25519 host and user keys. NSO now also supports ssh-ed25519 host keys for NETCONF NED connections. - ncs: NSO's default configuration, in the ncs.conf file written by the installer, for SSH host keys is now "ssh-ed25519" instead of the previous "ssh-rsa". To be able to connect to the built-in SSH server, the SSH client therefore must have support for "ssh-ed25519" as host key algorithm when the default configuration is in effect. This means OpenSSH is now required to be version 6.5 or later, and the python library paramiko, used by netconf-console, is required to be version 2.2 or later.     ... View more

'Prune' is an action so checking the yang model, the device is and input parameter:         tailf:action prune {         description           "Prune the portions of all queue items that contain            any of the devices in the input. This is a useful action to            run when a device has been taken off-line. When we do that            we want to ensure that no queue item remain for that            device, possibly blocking the queue. Devices which are            currently being committed to will not be pruned, if not            the 'force' option is used. Atomic queue items will            not be affected.";         tailf:info "Prune portions of all queue items in the queue";         tailf:actionpoint ncsinternal {           tailf:internal;         }         input {           leaf-list device {             type leafref {               path "/devices/device/name";             }           }   Not sure which API you are needing... for RESTCONF it would look like this:   $ curl -X POST -u admin:admin  -H 'Content-Type: application/yang-data+json' http://127.0.0.1:8080/restconf/operations/devices/commit-queue/prune -d '{"input":{"device":["ios-0"]}}' {   "tailf-ncs:output": {     "num-matched-queue-items": 0,     "num-deleted-queue-items": 0   } }   ... View more