Operating System: Mac OS
Platform: Macintosh

Please see the attached log

To reproduce:

Take the latest Add the following client configuration to netconf connector:

<module>
<type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">prefix:sal-netconf-connector</type>
<name>ncs</name>
<address xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">172.23.29.110</address>
<port xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">2022</port>
<username xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">xrvr</username>
<password xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">welcome</password>
<tcp-only xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">false</tcp-only>
<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>
</module>

which will cause ODL to attempt to connect to NCS. Observe the logs.

I am sending the logs in an email, since the attachment fails (probably due to size).

Trying ODL with the NCS:

ODL cannot retrieve any YANG schema from NCS device. NCS answers any get-schema rpc with following error:

<rpc-error>
<error-type>application</error-type>
<error-tag>invalid-value</error-tag>
<error-severity>error</error-severity>
<error-path xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:ncm="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">
/nc:rpc/ncm:get-schema
</error-path>
<error-message xml:lang="en">/get-schema/identifier: inconsistent value</error-message>
<error-info>
<bad-element>get-schema</bad-element>
</error-info>
</rpc-error>

This error is returned from NCS for all modules reported in hello message capabilities.

I was also trying to find out provided schemas by issuing a get rpc with filter set to: ietf-netconf-monitoring:netconf-state/ietf-netconf-monitoring:schemas but the data was empty.

So the NCS does not report any schemas under netconf-state, even if ietf-netconf-monitoring is supported according to hello message. And NCS responds to every get-schema request with an error.

Netconf in NCS should be examined since it does not seem to fully support ietf-netconf-monitoring.

Issue is not on ODL side