info illegal reference ... BGP IPV4 config protocol - CSR1000V via netconf
I have a Cisco CSR1000V version 16.7.2 as a device in my NSO. I've built a netconf package for it with the pioneer package. The connection is working and with an empty config on the router, the sync-from also works.
But if I have a BGP config on that router like the following, an error appears.
You are most probably right. Typically, there is a "must"/"when" expression that is not valid with the current configuration.
You could edit the YANG model and re-compile the NETCONF NED file. Alternative, the XE team has been pushing into a GIT repository "bug fixing" versions of these YANG models that you can download here: https://github.com/YangModels/yang/tree/master/vendor/cisco/xe . These modules may have fixed your problem but if not, please issue a TAC ticket for the XE team to take a look of them.
The XE team has put in a good effort to get the OpenConfig YANG into usable shape, but apparently something is not working correctly in the translation from native to OC config. I'd suggest that you file a bug report on the CSR. Be sure to include the exact native config when you do, and the sync-from command with the error message you showed here.
I think I'm running into a similar issue. I'm trying a sync-from from an ASR 920 running 16.12.1 and get the following error attached. Any idea how I can explore what part of the config or YANG model is causing this? I created the NED by pulling the YANG models directly off this device, which is the reference device for the NED.
SW upgrade or migration is something you never can escape from so it's better to make it part of your process. The remaining challenge is to determine when to give up what has been working to secure your future needs. Martin and the NSO team will guide y...
There is not a single golden tool that fits all purposes simply because development processes and needs are different. Instead, pick the tooling you need from the Smörgåsbord and build your environment to suit your needs. Shashidhar will guide you throug...
How Verizon Streamlined NSO Development with Continuous Integration
This is a customer success story of how Verizon ITNUC builds a CI chain to streamline the NSO development process. The containerized NSO makes testing several NSO packages in para...
It is best practice to avoid storing your secrets (e.g., passwords and shared keys) in plain text, either on NSO or on the device. In NSO, we support multiple encrypted data types that are encrypted using a local key. Similarly, many devices such as Cisco...