Showing results for 
Search instead for 
Did you mean: 

[NSO overlapping services]

Carlos A. Silva


We are in the process of using NSO for a migration procedure.
In trying to keep this discussion simple, let's imagine we create a service A that creates a few BGP neighbor with a route-map RM-1 (that denies everything). That works without a problem.
Then for the migration, we create a service B, that changes that route-map on the BGP neighbor created by service A to RM-2. That works without a problem, too.

The problem comes when we test a rollback.

When we try to rollback the changes made by service B (*edit: by deleting service B), the configuration does not go back from RM-2 to RM-1. RM-2 stays.

Is this normal/expected? I have this theory, this is NSO and service A, trying to protect the changes made by service A that service B is trying to undo and our migration design being the problem, but I'd like confirmation.


1 Reply 1

Cisco Employee
Cisco Employee

Deleting a service should in theory result in the changes it made being reverted. But I'm not sure if what happens in your case is expected or not without knowing what the exact service modifications are and what the model it modifies looks like. A service delete will not remove config if the refcount is higher than one though. You can see the refcount and backpointer if you show the config via the CLI and pipe the output with display service-meta-data (show ... | display service-meta-data).

You can also read more about that here:!nso-5-6-development-guide-developing-nso-services/advanced-mapping-techniques

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the NSO Developer community: