Operating System: All
Platform: All

https://git.opendaylight.org/gerrit/#/c/44897/

Hi All,

I have investigate the Netconf device discovery and followed the below steps:

1. https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf

2.Inserted the patch into netconf project https://git.opendaylight.org/gerrit/#/c/44897/

3. Installed feature: feature:install odl-restconf-all odl-mdsal-all odl-netconf-mdsal odl-netconf-connector-all

Result: Failed to exchange yang with Cisco Switch.

4. From ODL controller got following logs:

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)
2016-09-22 14:31:33,857 | INFO | NioProcessor-11 | ClientSessionImpl | 30 - org.apache.sshd.core - 0.14.0 | Client session created
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
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
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
2016-09-22 14:31:34,870 | INFO | NioProcessor-11 | ClientSessionImpl | 30 - org.apache.sshd.core - 0.14.0 | Dequeing pending packets
2016-09-22 14:31:35,077 | INFO | NioProcessor-11 | ClientUserAuthServiceNew | 30 - org.apache.sshd.core - 0.14.0 | Received SSH_MSG_USERAUTH_FAILURE
2016-09-22 14:31:35,083 | INFO | NioProcessor-11 | UserAuthKeyboardInteractive | 30 - org.apache.sshd.core - 0.14.0 | Received
2016-09-22 14:31:35,086 | INFO | NioProcessor-11 | ClientUserAuthServiceNew | 30 - org.apache.sshd.core - 0.14.0 | Received SSH_MSG_USERAUTH_SUCCESS
2016-09-22 14:31:35,238 | WARN | sing-executor-10 | NetconfDevice | 305 - org.opendaylight.netconf.sal-netconf-connector - 1.5.0.SNAPSHOT | RemoteDevice

: Attempting to build schema context from required sources
2016-09-22 14:31:35,252 | ERROR | sing-executor-11 | NetconfDevice | 305 - org.opendaylight.netconf.sal-netconf-connector - 1.5.0.SNAPSHOT | RemoteDevice

: No more sources for schema context
at org.opendaylight.netconf.sal.connect.netconf.NetconfDevice$SchemaSetup.setUpSchema(NetconfDevice.java:479)[305:org.opendaylight.netconf.sal-netconf-connector:1.5.0.SNAPSHOT]
at org.opendaylight.netconf.sal.connect.netconf.NetconfDevice$SchemaSetup.run(NetconfDevice.java:428)[305:org.opendaylight.netconf.sal-netconf-connector:1.5.0.SNAPSHOT]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_91]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_91]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_91]
2016-09-22 14:31:35,255 | WARN | sing-executor-11 | NetconfDeviceCommunicator | 305 - org.opendaylight.netconf.sal-netconf-connector - 1.5.0.SNAPSHOT | RemoteDevice

: Session terminated Session closed

What should be the next step ?

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.

Yeah, I think Om is right. Please see https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf#Connecting_to_a_device_not_supporting_netconf_monitoring for more info.

But anyway how is this related to this bug?

Initially, We have encountered a device that does not advertise either :writable-running or :candidate capabilities even though it support writable-running.

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.

Ok AmanDeep,

If it is not confidential, can you please post here your device's configuration? Also, have you merged latest patchset?

**Configurations **

<modules xmlns="urn:opendaylight:params:xml:ns:yang:controller:config">
<!-- Loopback connection to netconf server in controller using netconf-connector -->
<module>
<type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">prefix:sal-netconf-connector</type>
<name>gaurav</name>
<address xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">"IP"</address>
<port xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">"port"</port>
<username xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">"username"</username>
<password xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">"password"</password>
<yang-module-capabilities xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">
<capability xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">
urn:ietf:params:xml:ns:yang:ietf-inet-types?module=ietf-inet-types&revision=2010-09-24
</capability>

</yang-module-capabilities>
<tcp-only xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">false</tcp-only>
<reconnect-on-changed-schema xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">true</reconnect-on-changed-schema>
<event-executor xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">
<type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:netty">prefix:netty-event-executor</type>
<name>global-event-executor</name>
</event-executor>
<binding-registry xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">
<type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">prefix:binding-broker-osgi-registry</type>
<name>binding-osgi-broker</name>
</binding-registry>
<dom-registry xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">
<type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:dom">prefix:dom-broker-osgi-registry</type>
<name>dom-broker</name>
</dom-registry>
<client-dispatcher xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">
<type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:config:netconf">prefix:netconf-client-dispatcher</type>
<name>global-netconf-dispatcher</name>
</client-dispatcher>
<processing-executor xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">
<type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:threadpool">prefix:threadpool</type>
<name>global-netconf-processing-executor</name>
</processing-executor>
<keepalive-executor xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">
<type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:threadpool">prefix:scheduled-threadpool</type>
<name>global-netconf-ssh-scheduled-executor</name>
</keepalive-executor>
</module>
</modules>
</data>
</configuration>
<required-capabilities>
<![CDATA[urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf?module=odl-sal-netconf-connector-cfg&revision=2015-08-03]]>
</required-capabilities>
</snapshot>

• • We have merged the latest patch **

Have you also put the ietf-inet-types model's yang schema into the ODL cache/schema folder?

Yes we have included ietf-inet-types@2010-09-24.yang & ietf-inet-types@2013-07-15.yang.

Moreover, The capabilities also added into 99-Configurations file.

After adding the NonModuleCapabilities getting repository issues. Solved the repository issues and added the 99-netconf-connector.xml file into karaf target.

Now, getting exception after installing netconf-connector-all feature.

Please find the attached logs and other configuration files.

Attachment Investigation.zip has been added with description: logs and configuration files

Amandeep can you please try this with the newest patchset? I have fixed possible null pointer exception..

What exactly are these repository issues you are talking about and how have you fixed them?

Repository issues are with netconf project. I was not able to build the project after adding non module capabilities.

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.

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.?

Hi Jakub, Please let me know if I need to do more on this defect .

https://git.opendaylight.org/gerrit/#/c/44897/