https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-166 controller <p>After ODL establishes a Netconf session (as client) to libnetconfd (as server) I try to use REST interface to get device characteristics.</p> <p><a href="http://127.0.0.1:8080/restconf/operational/opendaylight-inventory:nodes/node/libnetconfd/yang-ext:mount" class="external-link" target="_blank" rel="nofollow noopener">http://127.0.0.1:8080/restconf/operational/opendaylight-inventory:nodes/node/libnetconfd/yang-ext:mount</a></p> <p>But the reply is:</p> <p>"Mount point does not contain any schema with modules."</p> <p>Attached goes the logs of the netconf session setup between ODL and libnetconfd</p> <p>The actual GET request does not generate any packets towards the server. It is handled locally in ODL</p> <p>Operating System: Mac OS<br/> Platform: PC</p> CONTROLLER-166

Opendaylight can not mount remote device

Bug Resolved Cannot Reproduce Unassigned Reinaldo Penno Thu, 20 Feb 2014 01:16:14 +0000 Tue, 25 Jul 2023 08:23:06 +0000 Thu, 27 Feb 2014 13:03:01 +0000 netconf 0 4 <p>Attachment netconflogs.txt has been added with description: Logs of netconf session between ODL and libnetconfd</p> <p>libnetconfd version:</p> <p><a href="http://code.google.com/p/libnetconf/" class="external-link" target="_blank" rel="nofollow noopener">http://code.google.com/p/libnetconf/</a></p> <p>libnetconf-0.7 was released in February 2014 </p> <p>Netopeer:</p> <p><a href="http://code.google.com/p/netopeer/" class="external-link" target="_blank" rel="nofollow noopener">http://code.google.com/p/netopeer/</a></p> <p>Latest version</p> <p>From analysis of the logs, we found out that response from libnetconfd is mallformed:</p> <p>When issuing get-schema RPC from ietf-netconf monitoring namespace is: urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring</p> <p>As in get-schema</p> <p>&lt;get-schema xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring"&gt;<br/> &lt;format&gt;yang&lt;/format&gt;<br/> &lt;identifier&gt;ietf-netconf&lt;/identifier&gt;<br/> &lt;version&gt;2011-03-08&lt;/version&gt;<br/> &lt;/get-schema&gt;<br/> &lt;/rpc&gt;</p> <p>But data element in response is from base namespace, but it should be<br/> urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring as defined in YANG specification.</p> <p>That is why ODL (which is strict about namespaces) did not process schema,<br/> because get-schema response was invalid.</p> <p>The incorrect reply (from libnetconfd, could be seen in attached logs) is bellow:</p> <p>&lt;?xml version="1.0" encoding="UTF-8"?&gt;<br/> &lt;rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="m-9"&gt;<br/> &lt;data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"&gt;module "ietf-netconf" {<br/> namespace "urn:ietf:params:xml:ns:netconf:base:1.0";<br/> prefix "nc";<br/> ...<br/> ...<br/> ...</p> <p>The root reason is bug in libnetconf.</p> <p>Opened a bug report in netopeer:</p> <p><a href="https://code.google.com/p/netopeer/issues/detail?id=10" class="external-link" target="_blank" rel="nofollow noopener">https://code.google.com/p/netopeer/issues/detail?id=10</a></p> Duplicate CONTROLLER-131 Development External issue ID 435 External issue URL Priority Rank 0|i02ipz: