I developed a fairly simple Loopback interface service. If I create a service instance the configuration is applied to the router. If I change the configuration of the device via NSO cli the configuration will change after the commit and the sync check of the Loopback service will fail as I expected. I would like to prevent that somebody will break a service due to missconfiguration. Unfortunately there will be manual and service configurations in my case .
Is it possible to lock certain Parts of the configuration for manual changes?
Is there a easy way to see which parts of the configuration is managed by a service? I found that this is possible via displaying the refcount in the configuration.
Generally, having two systems (operator and NSO here) doing overlapping configuration is not a good idea. There should be clear demarcation of the configuration space that is being touched by each.
Sometimes the operators may have to scribble stuff to resolve highly critical issues and they might have very short time to get things working.. This is when, after the fact, NSO can help check which service instances have gone out-of-sync and help with the reconciliation. Bring service configs back into policy.
You could explore NACM rules and have different users for service/manual configuration. Not sure if that will help. However, best to have clear demarcation of the config space.
Save the Date for the virtual NSO Developer Days event in APJC (Singapore time)! More information including the registration link with the agenda will be provided closer to the event date.
Save the Date for our next virtual NSO Developer Days event! The registration link with the agenda will be provided shortly.
During this 2 hour event, we will give you a packed agenda with customer success stories and insights, NSO deep dives, and up...
Hank Preston and Jason Belk presented at Network Field Day 23 to a network engineer audience. Jason shared his personal journey from network engineer to automation evangelist, and how Cisco Network Services Orchestrator (NSO) drew him deeper into automati...