OpenDaylight JIRA

OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us

8.20.10

820010

22-06-2022

[CONTROLLER-656] ODL does not connect to NCS https://jira.opendaylight.org/browse/CONTROLLER-656 controller <p>Please see the attached log for problems - ODL can not read yang models from NCS, even the ietf ones.</p> <p>To</p> <p>Operating System: Mac OS<br/> Platform: Macintosh</p> CONTROLLER-656

ODL does not connect to NCS

Bug Resolved Won't Do Maros Marsalek Jan Medved Tue, 29 Jul 2014 22:46:00 +0000 Wed, 30 Jul 2014 09:04:21 +0000 Wed, 30 Jul 2014 09:04:21 +0000 Helium netconf 0 3 <p>Please see the attached log</p> <p>To reproduce:</p> <p>Take the latest Add the following client configuration to netconf connector:</p> <p> <module><br/> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">prefix:sal-netconf-connector</type><br/> <name>ncs</name><br/> <address xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">172.23.29.110</address><br/> <port xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">2022</port><br/> <username xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">xrvr</username><br/> <password xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">welcome</password><br/> <tcp-only xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">false</tcp-only><br/> <event-executor xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"><br/> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:netty">prefix:netty-event-executor</type><br/> <name>global-event-executor</name><br/> </event-executor><br/> <binding-registry xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"><br/> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">prefix:binding-broker-osgi-registry</type><br/> <name>binding-osgi-broker</name><br/> </binding-registry><br/> <dom-registry xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"><br/> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:dom">prefix:dom-broker-osgi-registry</type><br/> <name>dom-broker</name><br/> </dom-registry><br/> <client-dispatcher xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"><br/> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:config:netconf">prefix:netconf-client-dispatcher</type><br/> <name>global-netconf-dispatcher</name><br/> </client-dispatcher><br/> <processing-executor xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"><br/> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:threadpool">prefix:threadpool</type><br/> <name>global-netconf-processing-executor</name><br/> </processing-executor><br/> </module></p> <p>which will cause ODL to attempt to connect to NCS. Observe the logs.</p> <p>I am sending the logs in an email, since the attachment fails (probably due to size).</p> <p>Trying ODL with the NCS:</p> <p>ODL cannot retrieve any YANG schema from NCS device. NCS answers any get-schema rpc with following error:</p> <p><rpc-error><br/> <error-type>application</error-type><br/> <error-tag>invalid-value</error-tag><br/> <error-severity>error</error-severity><br/> <error-path xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:ncm="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring"><br/> /nc:rpc/ncm:get-schema<br/> </error-path><br/> <error-message xml:lang="en">/get-schema/identifier: inconsistent value</error-message><br/> <error-info><br/> <bad-element>get-schema</bad-element><br/> </error-info><br/> </rpc-error></p> <p>This error is returned from NCS for all modules reported in hello message capabilities. </p> <p>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.</p> <p>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.</p> <p>Netconf in NCS should be examined since it does not seem to fully support ietf-netconf-monitoring.</p> <p>Issue is not on ODL side</p> Development External issue ID 1452 External issue URL Rank 0|i02lqv: