I am not an expert in NSO, but think that this is expected behavior for this specific use case.
First. When configuration change is committed, it is not get written to the startup datastore automatically, you need to do that manually when shutting down or rebooting the device.
Second. The check-sync does not do actual comparison of the current device configuration with CDB image. It simply checks matching of commit ID on the device and in CDB. The output of the command shows that they are different, which is expected, because you did not save the configuration to startup datastore, hence the last committed ID on the router got lost. You will need to do a sync-to operation to write last committed changes to the device.
I have also get in touch with NSO support teams, and they give me the same answer. The statup datastore should be commited with an external action inside the orchestrator.
I'm confused about this behaviour, because, on some devices, netconf commit save it as statupconfig too (ios-xr for example). I have also some NXOS devices, using NXOS-CLI ned, and no running to startup config is mandatory (probably hard coded on NXOS-CLI ned).
Maybe it's because IOS-XE does not have any candidate/commit native functions (Old IOS behaviour) ?
If some of you have some experience on how netconf works on Cisco IOS-XE, maybe some words/comments could be added below ? I'm also curious how cisco make it works on SDWAN/SD-Fabric solutions, running with IOS-XE devices. As far i read on documentation, Cisco DNA center send configuration through netconf on IOS-XE devices.
The NSO Config Monitor is targeted to discover and report unmanaged device configurationsas well as configuration changes that were introduced outside of NSO. It is designed to work as plug-in package named config-monitor, which can be installed and used&...
Today we have added a Key Link to our Network and Service Assurance solution from Accedian (Solution Plus Partner). Henrik Nydell, Senior Product Manager at Accedian presented at Automation Developer Days in May. If you missed it, you will find the l...
Hi DevNet Folks, If you are studying for any DevNet certs (specifically SPAUTO or DevNet Expert) which expects you to work with Cisco NSO and you want to find an easy way to get started with NSO, I have created a following repo, where you find two im...
NSO BGP optimization with Crosswork Cloud Traffic Analysis
Wei Yan • email@example.com • CXPM Architect
Dan Backman • firstname.lastname@example.org • Crosswork Cloud
This session was only presented at the virtual event.
Link To Recording
Use a Robot for network automation
(Getting more value from your NSO Test Automation)
Scott Barvick, CTO North America, Data Ductus
This session was only presented at the Virtual event.
Link To Recording
As you build ...