How TSDN 2.0 Packages Handle "out-of-sync" devices: Hi Team,Customer environment requires that certain level of provisioning is done outside of the CNC/NSO services which requires a procedure for CNC provisioning the TSDN services that contemplates this scenario.The "no-out-of-sync-check" commit option available on the UI seems to cover that requirement of Create and Modify instances but when it comes to deletion, that option is not available leading to an incoherent status since the IETF-L3NM (l3vpn-ntw vpn-service) is deleted but the flat-l3vpn instance fails to delete (and therefore the device configuration is not removed).We end up with zombie entry and flat-l3vpn service plan shows this:ncsadmin@ncs-dectf1nsosrv1# show flat-L3vpn-plan                                                                          POST             BACK                                                           ACTIONTYPE   NAME      TRACK GOAL STATUS CODE   STATE                        STATUS    WHEN         ref STATUS-----------------------------------------------------------------------------------------------------------------------------------------------------------self   self      true  -   -        init                         not-reached -          -  -                            ready                        not-reached -          -  -endpoint DEVLF1SLR01_23 true  -   TSDN-L3VPN-302 init                         failed    2022-05-02T16:56:41 -  -                            cisco-flat-L3vpn-fp-nano-plan-services:config-apply not-reached -          -  -                            ready                        not-reached -          -  - plan failed plan error-info message "Network Element Driver: device DEVLF1SLR01: out of sync" plan status-code-detail endpoint DEVLF1SLR01_23 code        TSDN-L3VPN-302 context "Device out of sync"  context-msg "Network Element Driver: device DEVLF1SLR01: out of sync" severity      ERROR recommended-action "Check sync between device and NSO, and perform recovery steps."Our request is to:Understand what is the correct instance deletion process from UI when the device is out-of-sync;How to recover from this status;</ul>Best Regards,Fbio Gameiro
Hi Fabio,For out-of-sync devices - no-networking flag is used to make sure nothing goes to device .Use this flag as true for this case.Please follow this document to understand recovery process.TSDN Error Recovery Scenarios : Hope the above steps helps to understand recovery process.ThanksPriyankaHi Priyanka, Thanks for the clarification. Regarding the "no-out-of-sync-check" option is only available on the CNC UI for Edit/Create operations. The delete "button", when pressed and upon confirmation, doesn't give the chance to select the "no-out-of-sync-check" option (screen in attach) and therefore we will reach a "out-of-sync" issue and the deletion wont go through.What is the solution for deletion? Is the solution enabling "devices global-settings out-of-sync-commit-behaviour accept" or is there any other option?Regarding the recovery process described in the page you provided I start by seen a discrepancy between, for example, the "devices global-settings commit-queue enabled-by-default true" as "Pre-requisite config settings on NSO ." when the installation guide actually loads an XML file "config/commit-queue-settings.xml" which has "commit-queue enabled-by-default false" What are the recommended "devices global-settings" settings, namely on the commit-queue? Hi Fabio,As per webex discussion looks like you might need to try out actual CNC 2.0 packages and see if it there you see clean up action problem.We have gone over what all is supported by NSO and CNC UI for CNC 2.0 .I have tried to cover all your questions in webex.As per your confirmation i will close this ticket .ThanksPriyanka