NSO allows Circuit style policy deletion if it is applied to a L2VPN service: NSO allows Circuit style policy Edit/delete, When the CS policy is applied to a L2VPN service. NSO doesn't throw any validation .Every CS policy creates 2 child SR policy (head , tail). NSO allows Edit/Delete of those SR policies. Changes done to child SR policies committed successfully without any error but the changes gets reverted back within a minute to reflect the values as in CS policies. No validation/info message before accepting/after reverting the changes.Please suggest to raise a defect to track.
Hi Ajitha,As discussed on call,Quote "NSO allows Circuit style policy Edit/delete, When the CS policy is applied to a L2VPN service. NSO doesn't throw any validation"Answer: L2VPN does not track CS Policy edit/delete operations. As such, to reflect attached CS changes on L2, you must redeploy the L2 service. This is stated in our documentation : Quote "Every CS policy creates 2 child SR policy (head , tail). NSO allows Edit/Delete of those SR policies. Changes done to child SR policies committed successfully without any error but the changes gets reverted back within a minute to reflect the values as in CS policies. No validation/info message before accepting/after reverting the changes"Answer: As it is for internally generated CFP/FP services, internal services cannot be modified by user. I have updated documentation with this information here :Documentation updated here :