Juniper does not advertise any known YANG modules

[nso20]

Hello,

I am trying to build NETCONF NED from below yang files, and build succeed but when trying to sync-from device, it gives the error below:

admin@ncs# show netconf-ned-builder project myned 1.0 module status
NAME REVISION STATUS
-------------------------------------------------------
junos-common-types 2018-01-01 selected,downloaded
junos-rpc-chassis 2018-01-01 selected,downloaded
junos-rpc-interfaces 2018-01-01 selected,downloaded
junos-rpc-system 2018-01-01 selected,downloaded
junos-rpc-vlans 2018-01-01 selected,downloaded

show netconf-ned-builder project myned 1.0 build-status
build-status success

devices device myjuniper sync-from
result false
info Device myjuniper does not advertise any known YANG modules

devices device myjuniper connect
result false
info Device myjuniper does not advertise any known YANG modules

NSO version: 5.3.2.1

Junos version: 18.3R1.9 

[hniska]

My guess is that none of those five yang modules contains any config definitions, seems to only be rpc calls and some type defines. 

junos-common-types 2018-01-01 selected,downloaded
junos-rpc-chassis 2018-01-01 selected,downloaded
junos-rpc-interfaces 2018-01-01 selected,downloaded
junos-rpc-system 2018-01-01 selected,downloaded
junos-rpc-vlans 2018-01-01 selected,downloaded

[nso20]

@hniska 

I tried below but still same error:

admin@ncs# show netconf-ned-builder project myned 1.0 module status
NAME REVISION STATUS
--------------------------------------------------------
junos-common-types 2018-01-01 selected,downloaded
junos-conf-interfaces 2018-01-01 selected,downloaded
junos-conf-root 2018-01-01 selected,downloaded
junos-conf-services 2018-01-01 selected,downloaded
junos-conf-vlans 2018-01-01 selected,downloaded
junos-rpc-interfaces 2018-01-01 selected,downloaded
junos-rpc-services 2018-01-01 selected,downloaded
junos-rpc-vlans 2018-01-01 selected,downloaded

admin@ncs# show netconf-ned-builder project myned 1.0 build-status
build-status success
admin@ncs#
admin@ncs# show packages package oper-status
myned-nc-1.0 X - - - - - - - - - -

admin@ncs# devices device myjuniper sync-from
result false
info Device myjuniper does not advertise any known YANG modules

[rogaglia]

Hi,

You can check if NSO loaded the new NED data models with this command (you may missed compiled the new NED via the make command).

If the data-models are loaded, check the ned traces to validate what the device is advertising.

Roque

admin@ncs> show ncs-state loaded-data-models mount onf-tapi_rc-gen-1.0:onf-tapi_rc-gen-1.0 data-model
EXPORTED EXPORTED
NAME REVISION NAMESPACE PREFIX TO ALL TO
-----------------------------------------------------------------------------------------------------------------------------
mef-common 2018-03-21 urn:mef:yang:mef-common mef-common X -
mef-common-types 2018-03-21 urn:mef:yang:mef-common-types mef-common-types X -
nrm-connectivity 2018-03-21 urn:mef:yang:nrm-connectivity nrm-connectivity X -
nrp-interface 2018-03-21 urn:mef:yang:nrp-interface nrp-interface X -
tailf-ned-onf-tapi_rc-id - http://tail-f.com/ned/onf-tapi_rc-id onf-tapi_rc-id X -
tailf-ned-onf-tapi_rc-stats - http://tail-f.com/ned/onf-tapi_rc/stats onf-tapi_rc-stats X -
tapi-common 2020-04-23 urn:onf:otcc:yang:tapi-common tapi-common X -
tapi-connectivity 2020-06-16 urn:onf:otcc:yang:tapi-connectivity tapi-connectivity X -
tapi-dsr 2020-04-23 urn:onf:otcc:yang:tapi-dsr tapi-dsr X -
tapi-equipment 2020-04-23 urn:onf:otcc:yang:tapi-equipment tapi-equipment X -
tapi-eth 2020-04-23 urn:onf:otcc:yang:tapi-eth tapi-eth X -
tapi-notification 2020-06-16 urn:onf:otcc:yang:tapi-notification tapi-notification X -
tapi-oam 2020-04-23 urn:onf:otcc:yang:tapi-oam tapi-oam X -
tapi-odu 2020-04-23 urn:onf:otcc:yang:tapi-odu tapi-odu X -
tapi-path-computation 2020-04-23 urn:onf:otcc:yang:tapi-path-computation tapi-path-computation X -
tapi-photonic-media 2020-06-16 urn:onf:otcc:yang:tapi-photonic-media tapi-photonic-media X -
tapi-topology 2020-04-23 urn:onf:otcc:yang:tapi-topology tapi-topology X -
tapi-virtual-network 2020-06-16 urn:onf:otcc:yang:tapi-virtual-network tapi-virtual-network X -

[ok][2020-12-09 19:43:34]
admin@ncs>

[nso20]

Hello@rogaglia 

yes, I already compiled it via make command. I still get the same error although the ned traces are ok as below, any advise (may be I should select different yang models) ?

admin@ncs# show ncs-state loaded-data-models mount myned-nc-1.0:myned-nc-1.0 data-model
EXPORTED EXPORTED
NAME REVISION NAMESPACE PREFIX TO ALL TO
---------------------------------------------------------------------------------------------------------------------
junos-common-types 2018-01-01 http://yang.juniper.net/junos/common/types jt X -
junos-conf-interfaces 2018-01-01 http://yang.juniper.net/junos/conf/interfaces jc-interfaces X -
junos-conf-root 2018-01-01 http://yang.juniper.net/junos/conf/root jc X -
junos-conf-services 2018-01-01 http://yang.juniper.net/junos/conf/services jc-services X -
junos-conf-vlans 2018-01-01 http://yang.juniper.net/junos/conf/vlans jc-vlans X -
junos-rpc-interfaces 2018-01-01 http://yang.juniper.net/junos/rpc/interfaces interfaces X -
junos-rpc-services 2018-01-01 http://yang.juniper.net/junos/rpc/services services X -
junos-rpc-vlans 2018-01-01 http://yang.juniper.net/junos/rpc/vlans vlans X -

[rogaglia]

I did not see your traces files. Could you also add the output of "show running devices device myjuniper" together with the missing traces?

[nso20]

Hello @rogaglia 

Please find below:

admin@ncs# show running-config devices device myjuniper
devices device myjuniper
address 1.1.1.1
port 830
ssh host-key ssh-dss
key-data ***
!
ssh host-key ssh-rsa
key-data ***
!
ssh host-key ssh-ed25519
key-data AAAAC3NzaC1lZDI1NTE5AAAAIB6MicpQEswgfYejtA4nsTzF7g313YTkhzREV1pOtzBL
!
authgroup juniper_group
device-type netconf ned-id myned-nc-1.0
trace pretty
state admin-state unlocked

>>>>out 7-Jan-2021::16:57:38.006 user: admin/49 thandle 6607 hostname nso device myjuniper
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<capabilities>
<capability>urn:ietf:params:netconf:base:1.0</capability>
<capability>urn:ietf:params:netconf:base:1.1</capability>
</capabilities>
</hello>

<<<<in 7-Jan-2021::16:57:38.176 user: admin/49 thandle 6607 hostname nso device myjuniper
<nc:hello xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">
<nc:capabilities>
<nc:capability>urn:ietf:params:netconf:base:1.0</nc:capability>
<nc:capability>urn:ietf:params:netconf:capability:candidate:1.0</nc:capability>
<nc:capability>urn:ietf:params:netconf:capability:confirmed-commit:1.0</nc:capability>
<nc:capability>urn:ietf:params:netconf:capability:validate:1.0</nc:capability>
<nc:capability>urn:ietf:params:netconf:capability:url:1.0?protocol=http,ftp,file</nc:capability>
<nc:capability>urn:ietf:params:xml:ns:netconf:base:1.0</nc:capability>
<nc:capability>urn:ietf:params:xml:ns:netconf:capability:candidate:1.0</nc:capability>
<nc:capability>urn:ietf:params:xml:ns:netconf:capability:confirmed-commit:1.0</nc:capability>
<nc:capability>urn:ietf:params:xml:ns:netconf:capability:validate:1.0</nc:capability>
<nc:capability>urn:ietf:params:xml:ns:netconf:capability:url:1.0?protocol=http,ftp,file</nc:capability>
<nc:capability>urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring</nc:capability>
<nc:capability>http://xml.juniper.net/netconf/junos/1.0</nc:capability>
<nc:capability>http://xml.juniper.net/dmi/system/1.0</nc:capability>
</nc:capabilities>
<nc:session-id>5640</nc:session-id>
</nc:hello>

>>>>out 7-Jan-2021::16:57:38.181 user: admin/49 thandle 6607 hostname nso device myjuniper session-id=5640
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
message-id="1">
<close-session/>
</rpc>

>>>>out 7-Jan-2021::16:57:38.182 user: admin/49 thandle 6607 hostname nso device myjuniper session-id=5640 NCS close

[rogaglia · Accepted solution]

I hope the problem is now clear. The modules that you created the NED for are not exposed by this Junos box in the Hello message.

NSO is expected to see the capabilities for the modules in the NED, for example: http://yang.juniper.net/junos/conf/interfaces 

Now, two things you may do to fix the problem:

1- Use the Juniper-Junos NED, which implements  http://xml.juniper.net/netconf/junos/1.0

2- Find the right Junos config/version to get the Hello message to publish what you need. Maybe someone in this forum could help you.

[erikdoesNSO]

Is this thread  related to:

ncs% request devices device pdn-crt sync-from
result false
info Device pdn-crt does not advertise any known YANG modules
[ok][2023-06-16 14:50:48]@ncs% *** ALARM connection-failure: Device pdn-crt does not advertise any known YANG modules