Closed krihal closed 8 months ago
The error seems to be an openconfig network-instances configuration on the top-level of the MX. The openconfig yang is not announced by the MX and is also a separate(second) top-level root of the configuration. This means that the opeconfig needs to be loaded and mounted separately, in some other mechanism than the regular.
This might be a reason to consider https://github.com/clicon/clixon-controller/issues/21
Note the "fixed ref" ^ is a mistake, should be #19
This should now be possible to do using device profiles and adding local module-sets for openconfig
When connection to Juniper MX: