Thank you for the explanation!   ... View more

That did it!   Thank you very much!   Would you mind describing the statement in words? How come '.' is pointing where it does? What does the statement returns? A Boolean value? The node itself?   Thanks again! ... View more

You're pointing to {/intf-number}. '/' points to the service instance, which in your case is /services/l2-vpls:mpls-l2-vpls[service-name='Service-01']. Your xpath statement should be relative to the current context (seen on the debug output) and should not container the '/'. If I understand your model correctly, it should be something like this: {ios-interfaces/intf-number} ... View more

What about the template on the service that uses the port-channel (the one that adds a service instance on the port channel interface? Do you have nocreate there on the port-channel interface?   The nocreate tag means, if it's not there, then don't create it. Technically, it means that the service will not increase the reference counter (refcount) on the configs tagged with nocreate. When a refcount on a node reaches 0, NSO automatically deletes that node.   If you have nocreate on the port-channel on the service that uses the port, this is what should happen:   1. service that creates the port channel sets the refcount on the port-channel to 1. 2. service that adds a service instance on the port channel leaves the refcount at 1 (nocreate), and sets some other attributes on the port (change their refcount to 1). 3. You then modify the service that created the port-channel: Fastmap undos whatever that service configured in memory. This means, reducing the refcount on all the nodes that service configured - including the port-channel node, which is now at 0. This causes everything under that node to be deleted. 4. The service then re-applies its mapping logic and recreates the port-channel node, and everything under it which is part of the port-channel service (e.g. description). This causes everything that was created by this service to stay in place, but anything else to be deleted, and that might be what you're seeing.   If you remove the nocreate from the service that adds the service instance on the port-channel, then the following will happen:   1. service that creates the port channel sets the refcount on the port-channel to 1. 2. service that adds a service instance on the port channel increases on the port-channel node to 2 (merge), and sets some other attributes on the port (change their refcount to 1). 3. You then modify the service that created the port-channel: Fastmap undos whatever that service configured in memory. reducing the refcount on the port-channel node to 1. As it doesn't reach 0, NSO will NOT remove the node, and will only delete the configs which are only owned by the service which created the port-channel (e.g. port-channel description). 4. The service then re-applies its mapping logic and increments the refcount on the port-channel node to 2 again, and applies everything under it which is part of the port-channel service.     If indeed you have that nocreate on the service that creates the service instance on the port-channel interface, then remove it (change to merge), re-deploy that service instance (to set the refcount correctly) and then try your modification again.   You can actually see the refcount value on any node with "show running ... | display service-meta-data" For example:   show running-config devices device ios-0 config ios:interface Port-channel 4 | display xml | display service-meta-data ... View more

Do you happen to have any tags defined on the XML template that configures anything under the port-channel on that service (e.g. no-create)?   When you modify your port-channel service, it removes whatever it created in-memory and then re-applies it. If the port-channel instance on the device data model doesn't have any other owners, then anything under it will be removed when the port-channel service that created it is modified/re-deployed.   If the service that uses the port-channel has tags='no-create' for the port-channel node, then that may explain why the service instance under the port-channel interface is being removed. ... View more

Make sure that you modify ncs.conf with the hide-group configs as mentioned on the thread. Then, for that to take effect, you'd need to reload (ncs --reload) or restart NSO. Then unhide debug should work.   If you did the above, the only thing I can think of for it not to work is if you modified the wrong ncs.conf file. ... View more