09-14-2017 01:44 AM - edited 03-01-2019 03:59 AM
I came across a problem that requires me to add a tag that operates differently not like the standard tags like "nocreate delete create merge"
what i need is to create a new tag that doesn't delete a certain element in xml when service is removed from NSO as part of the service was already created before the NSO deployment
Solved! Go to Solution.
09-14-2017 10:30 AM
Hi,
Usually this case is handled by creating configuration using the pre modification callback. So you can create anything you want as part of the service pre modification callback and it will survive deletion of the actual service. I don't know of a way to insure that within a service template.
-Dan
09-14-2017 10:30 AM
Hi,
Usually this case is handled by creating configuration using the pre modification callback. So you can create anything you want as part of the service pre modification callback and it will survive deletion of the actual service. I don't know of a way to insure that within a service template.
-Dan
09-20-2017 01:08 AM
No matter what tag you invite ( actually I'm not sure if NSO has such an mochanism to allow you to do so for xml template), fast map will calculate what is newly generated with the service and create the inverse configuration according to your service. therefore, when a service is removed, whatever is created within this service will be removed as well unless part of the configuration is configured to device prior to the service creation. you can refer to Daniel's answer and consider the solution of pre or post modification.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide