cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

263
Views
0
Helpful
4
Replies
LoicChabert27318
Beginner

NSO - Reboot IOS-XE device leads to unsync configuration

Hi,

 

When i commit configuration from NSO, config is applied on IOS-XE device. Next, i try to reload the router.

First of all, the router ask to save configuration to startup config. Is it normal, after NSO commit, configuration is not saved to startup config ?

 

During my test scenario, i not confirm and reload the router without saving to startup (to simulate an electrical power issue).

 

When router is UP and confd/netconf server running, i try to check if configuration is sync, but i have the following output:

noc@ncs> request devices device ar01-vpn.mar92 sync-from dry-run { outformat cli }
cli
[ok][2022-05-12 16:52:37]
noc@ncs> request devices device ar01-vpn.mar92 check-sync
result out-of-sync
info got: 1652-367116-179638 expected: 1652-366528-305780

[ok][2022-05-12 16:52:43]
noc@ncs> *** ALARM out-of-sync: got: 1652-367116-179638 expected: 1652-366528-305780

With router uptime:

ar01-vpn.mar92 uptime is 6 minutes

Router version: Cisco CSR1000v 17.3.3

 

Best regards.

4 REPLIES 4
alexstev
Cisco Employee

 

Hello @LoicChabert27318,

 

I'm not an NSO expert but I thought you might want to try recreating the issue on one of our DevNet sandboxes. We have NSO, as well as CSR1000v available ---> https://devnetsandbox.cisco.com/RM/Topology 

 

You might also want to check out the Cisco Bug Search Tool --> https://bst.cloudapps.cisco.com/bugsearch/

 

Hope this helps!

Nabsch
Beginner

Hello,

 

Can you specify NSO version and also NED Name/version ?

 

 

ygorelik
Cisco Employee

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.

Yan

LoicChabert27318
Beginner

Hi,

 

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.

 

Regards.