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/NETCONF-250 netconf <p>We have encountered a device that does not advertise either :writable-running or :candidate capabilities even though it support writable-running. It would be useful to be able to specify the capability to use in the node configuration using something similar to yang-additional-capabilities to add or over ride the capabilities announced by the device. This is a situation where manual netconf can work around the bad hello capabilities exchange but the ODL netconf adaptor can not.</p> <p>Perhaps something like:</p> <p>&lt;netconf-additional-capability&gt;<br/> &lt;capability xmlns="urn:opendaylight:netconf-node-topology"&gt;<br/> urn:ietf:params:netconf:capability:writable-running:1.0<br/> &lt;/capability&gt;<br/> &lt;/netconf-additional-capability&gt;</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-250

Allow over-ride of non-module capabilities

Improvement Resolved Done Miroslav Kovac Brian Freeman Fri, 5 Aug 2016 16:05:38 +0000 Fri, 15 Mar 2019 22:22:28 +0000 Mon, 6 Mar 2017 15:36:14 +0000 netconf 0 7 <p><a href="https://git.opendaylight.org/gerrit/#/c/44897/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/44897/</a></p> <p>Hi All,</p> <p>I have investigate the Netconf device discovery and followed the below steps:</p> <p>1. <a href="https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf</a></p> <p>2.Inserted the patch into netconf project <a href="https://git.opendaylight.org/gerrit/#/c/44897/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/44897/</a></p> <p>3. Installed feature: feature:install odl-restconf-all odl-mdsal-all odl-netconf-mdsal odl-netconf-connector-all</p> <p>Result: Failed to exchange yang with Cisco Switch.</p> <p>4. From ODL controller got following logs:</p> <p>2016-09-22 14:31:33,812 | INFO | config-pusher | ConfigPusherImpl | 136 - org.opendaylight.controller.config-persister-impl - 0.6.0.SNAPSHOT | Successfully pushed configuration snapshot 99-netconf-connector.xml(odl-netconf-connector-all,odl-netconf-connector-all)<br/> 2016-09-22 14:31:33,857 | INFO | NioProcessor-11 | ClientSessionImpl | 30 - org.apache.sshd.core - 0.14.0 | Client session created<br/> 2016-09-22 14:31:33,874 | INFO | NioProcessor-11 | ClientSessionImpl | 30 - org.apache.sshd.core - 0.14.0 | Start flagging packets as pending until key exchange is done<br/> 2016-09-22 14:31:33,877 | INFO | NioProcessor-11 | ClientSessionImpl | 30 - org.apache.sshd.core - 0.14.0 | Server version string: SSH-2.0-Cisco-1.25<br/> 2016-09-22 14:31:34,864 | WARN | NioProcessor-11 | AcceptAllServerKeyVerifier | 30 - org.apache.sshd.core - 0.14.0 | Server at /10.61.20.10:22 presented unverified RSA key: 64:48:d8:32:90:17:c4:e4:0a:8a:80:81:74:71:c7:fc<br/> 2016-09-22 14:31:34,870 | INFO | NioProcessor-11 | ClientSessionImpl | 30 - org.apache.sshd.core - 0.14.0 | Dequeing pending packets<br/> 2016-09-22 14:31:35,077 | INFO | NioProcessor-11 | ClientUserAuthServiceNew | 30 - org.apache.sshd.core - 0.14.0 | Received SSH_MSG_USERAUTH_FAILURE<br/> 2016-09-22 14:31:35,083 | INFO | NioProcessor-11 | UserAuthKeyboardInteractive | 30 - org.apache.sshd.core - 0.14.0 | Received<br/> 2016-09-22 14:31:35,086 | INFO | NioProcessor-11 | ClientUserAuthServiceNew | 30 - org.apache.sshd.core - 0.14.0 | Received SSH_MSG_USERAUTH_SUCCESS<br/> 2016-09-22 14:31:35,238 | WARN | sing-executor-10 | NetconfDevice | 305 - org.opendaylight.netconf.sal-netconf-connector - 1.5.0.SNAPSHOT | RemoteDevice</p> {gaurav}: Netconf device does not provide all yang models reported in hello message capabilities, required but not provided: <span class="error">&#91;(urn:ietf:params:xml:ns:yang:ietf-inet-types?revision=2010-09-24)ietf-inet-types&#93;</span><br/> 2016-09-22 14:31:35,239 | WARN | sing-executor-10 | NetconfDevice | 305 - org.opendaylight.netconf.sal-netconf-connector - 1.5.0.SNAPSHOT | RemoteDevice{gaurav} <p>: Attempting to build schema context from required sources<br/> 2016-09-22 14:31:35,252 | ERROR | sing-executor-11 | NetconfDevice | 305 - org.opendaylight.netconf.sal-netconf-connector - 1.5.0.SNAPSHOT | RemoteDevice</p> {gaurav}: Initialization in sal failed, disconnecting from device<br/> java.lang.IllegalStateException: RemoteDevice{gaurav} <p>: No more sources for schema context<br/> at org.opendaylight.netconf.sal.connect.netconf.NetconfDevice$SchemaSetup.setUpSchema(NetconfDevice.java:479)<span class="error">&#91;305:org.opendaylight.netconf.sal-netconf-connector:1.5.0.SNAPSHOT&#93;</span><br/> at org.opendaylight.netconf.sal.connect.netconf.NetconfDevice$SchemaSetup.run(NetconfDevice.java:428)<span class="error">&#91;305:org.opendaylight.netconf.sal-netconf-connector:1.5.0.SNAPSHOT&#93;</span><br/> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)<span class="error">&#91;:1.8.0_91&#93;</span><br/> at java.util.concurrent.FutureTask.run(FutureTask.java:266)<span class="error">&#91;:1.8.0_91&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)<span class="error">&#91;:1.8.0_91&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)<span class="error">&#91;:1.8.0_91&#93;</span><br/> at java.lang.Thread.run(Thread.java:745)<span class="error">&#91;:1.8.0_91&#93;</span><br/> 2016-09-22 14:31:35,255 | WARN | sing-executor-11 | NetconfDeviceCommunicator | 305 - org.opendaylight.netconf.sal-netconf-connector - 1.5.0.SNAPSHOT | RemoteDevice</p> {gaurav} <p>: Session terminated Session closed</p> <p>What should be the next step ?</p> <p>it seems that device don't support get-schema , so you need to side load those yang file of capability reported by the device in hello message.</p> <p>Yeah, I think Om is right. Please see <a href="https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf#Connecting_to_a_device_not_supporting_netconf_monitoring" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf#Connecting_to_a_device_not_supporting_netconf_monitoring</a> for more info.</p> <p>But anyway how is this related to this bug?</p> <p>Initially, We have encountered a device that does not advertise either :writable-running or :candidate capabilities even though it support writable-running.</p> <p>So we merged the updated patch to netconf project manually in our local system, after doing that we are getting this error. That's why my query related to this bug.</p> <p>Ok AmanDeep,</p> <p>If it is not confidential, can you please post here your device's configuration? Also, have you merged latest patchset?</p> <p>**Configurations **</p> <p> &lt;modules xmlns="urn:opendaylight:params:xml:ns:yang:controller:config"&gt;<br/> &lt;!-- Loopback connection to netconf server in controller using netconf-connector --&gt;<br/> &lt;module&gt;<br/> &lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;prefix:sal-netconf-connector&lt;/type&gt;<br/> &lt;name&gt;gaurav&lt;/name&gt;<br/> &lt;address xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;"IP"&lt;/address&gt;<br/> &lt;port xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;"port"&lt;/port&gt;<br/> &lt;username xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;"username"&lt;/username&gt;<br/> &lt;password xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;"password"&lt;/password&gt;<br/> &lt;yang-module-capabilities xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;<br/> &lt;capability xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;<br/> urn:ietf:params:xml:ns:yang:ietf-inet-types?module=ietf-inet-types&amp;revision=2010-09-24<br/> &lt;/capability&gt;</p> <p>&lt;/yang-module-capabilities&gt;<br/> &lt;tcp-only xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;false&lt;/tcp-only&gt;<br/> &lt;reconnect-on-changed-schema xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;true&lt;/reconnect-on-changed-schema&gt;<br/> &lt;event-executor xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;<br/> &lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:netty"&gt;prefix:netty-event-executor&lt;/type&gt;<br/> &lt;name&gt;global-event-executor&lt;/name&gt;<br/> &lt;/event-executor&gt;<br/> &lt;binding-registry xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;<br/> &lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding"&gt;prefix:binding-broker-osgi-registry&lt;/type&gt;<br/> &lt;name&gt;binding-osgi-broker&lt;/name&gt;<br/> &lt;/binding-registry&gt;<br/> &lt;dom-registry xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;<br/> &lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:dom"&gt;prefix:dom-broker-osgi-registry&lt;/type&gt;<br/> &lt;name&gt;dom-broker&lt;/name&gt;<br/> &lt;/dom-registry&gt;<br/> &lt;client-dispatcher xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;<br/> &lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:config:netconf"&gt;prefix:netconf-client-dispatcher&lt;/type&gt;<br/> &lt;name&gt;global-netconf-dispatcher&lt;/name&gt;<br/> &lt;/client-dispatcher&gt;<br/> &lt;processing-executor xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;<br/> &lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:threadpool"&gt;prefix:threadpool&lt;/type&gt;<br/> &lt;name&gt;global-netconf-processing-executor&lt;/name&gt;<br/> &lt;/processing-executor&gt;<br/> &lt;keepalive-executor xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;<br/> &lt;type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:threadpool"&gt;prefix:scheduled-threadpool&lt;/type&gt;<br/> &lt;name&gt;global-netconf-ssh-scheduled-executor&lt;/name&gt;<br/> &lt;/keepalive-executor&gt;<br/> &lt;/module&gt;<br/> &lt;/modules&gt;<br/> &lt;/data&gt;<br/> &lt;/configuration&gt;<br/> &lt;required-capabilities&gt;<br/> &lt;![CDATA<span class="error">&#91;urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf?module=odl-sal-netconf-connector-cfg&amp;revision=2015-08-03&#93;</span>]&gt;<br/> &lt;/required-capabilities&gt;<br/> &lt;/snapshot&gt;</p> <ul> <li> <ul> <li>We have merged the latest patch **</li> </ul> </li> </ul> <p>Have you also put the ietf-inet-types model's yang schema into the ODL cache/schema folder?</p> <p>Yes we have included ietf-inet-types@2010-09-24.yang &amp; ietf-inet-types@2013-07-15.yang.</p> <p>Moreover, The capabilities also added into 99-Configurations file.</p> <p>After adding the NonModuleCapabilities getting repository issues. Solved the repository issues and added the 99-netconf-connector.xml file into karaf target.</p> <p>Now, getting exception after installing netconf-connector-all feature. </p> <p>Please find the attached logs and other configuration files.</p> <p>Attachment Investigation.zip has been added with description: logs and configuration files</p> <p>Amandeep can you please try this with the newest patchset? I have fixed possible null pointer exception..</p> <p>What exactly are these repository issues you are talking about and how have you fixed them?</p> <p>Repository issues are with netconf project. I was not able to build the project after adding non module capabilities. </p> <p>Initially, i skipped the test cases and build the project then with test cases. After changing in yang and build the project online able to solve the issues.</p> <p>Moreover, i will include the new patch and get back to you. Basically i am getting semantic errors after including 99-netconf-connector.xml. please look into that do i need to add more capabilities.?</p> <p>Hi Jakub, Please let me know if I need to do more on this defect .</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/44897/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/44897/</a></p> Development External issue ID 6346 External issue URL Rank 0|i01xdr: