11-16-2021 01:26 AM
Hi Experts,
The device is netconf based. I built the NED for this device.
I tried to connect the device via NSO, but the connection closed unexpectedly by NSO.
I checked the trace log. It showed that the NSO closed connection while getting the module info from node:
</yang-library>
<modules-state xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-library">
<module>
<name>ietf-yang-types</name>
<revision>2013-07-15</revision>
<namespace>urn:ietf:params:xml:ns:yang:ietf-yang-types</namespace>
<conformance-type>import</conformance-type>
</module>
<module>
<name>openconfig-extensions</name>
<revision>2020-06-16</revision>
<schema>file:///md/sysrepo/yang/openconfig-extensions@2020-06-16.yang</schema>
<namespace>http://openconfig.net/yang/openconfig-ext</namespace>
<conformance-type>implement</conformance-type>
</module>
<module>
<name>openconfig-inet-types</name>
<revision>2021-01-07</revision>
<schema>file:///md/sysrepo/yang/openconfig-inet-types@2021-01-07.yang</schema>
<namespace>http://ope
Can you give me some clue for the issue?
Thanks!
11-24-2021 11:53 AM
Hello @sparrow109,
Check out the NSO DRIVEN NETCONF AND YANG INTEROPERABILITY TESTING USER GUIDE V2 from tail-f, a Cisco company.
Hope this helps!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide