sync-from issue with self-made NED

[Noel Cantenot]

Hi,

I created a NED for Juniper SRX using devtools and build-ned command. (using NSO 6.1)

During the process, I had to remove the junos-es-rpc-security module to avoid a "already defined" error.

Everything seems to be OK, when I "devices device srx sync-from dry-run", I can see the whole configuration.

But when I "devices device sync-from", I get an error (out of nowhere): "info devices device srx config configuration groups node0 multicast-snooping-options traceoptions file filename is not configured".

There is no multicast in my SRX configuration, and why this can be a problem to sync-from for NSO ?
On the SRX I used to create the NED, the command "groups node0 multicast-snooping-options" does not existe, whereas it exists in NSO configuration (where does it come from ?).

It behaves like this command that does not exist and SRX is mandatory for NSO to sync-from... It's non sense (or I miss something) ?

Regards.

NSO Developer Hub Discussions, Developer, DevOps

[cohult]

Hi, It seems like there could be a YANG "must" statement XPath expression in one of the YANG models downloaded from the device checking the "configuration groups node0 multicast-snooping-options trace options file filename" path.
Regards

[cohult · Accepted solution]

Note that the documentation for the NETCONF NED Builder has been improved since NSO 6.2. The latest doc that is likely applicable to your NSO 6.1 use case:
https://cisco-tailf.gitbook.io/nso-docs/development/advanced-development/developing-neds/netconf-ned-development#d5e9185

[Noel Cantenot]

I upgraded the Junos version from 20.4 to 22.4, and all issues disappeared!

It should be a “bug” in Juniper exposed yang modules.
The doc I used is for NSO 5.7, and it seems to work with 6.1 (few modifications needed).

Thanks !