load merge config/dispatch-map-settings.xml fail: load merge failed while running the command for "Configure Common Bootstrap data". I checked the folder, dispatch-map-settings.xml does not exist under config/console outputadmin@ncs% load merge config/dispatch-map-settings.xmlError: failed to open file: File/directory does not exist. File name: dispatch-map-settings.xmladmin@ncs% 
Continue with the remaining steps, and it failed to sync dispatch map. But the error message is confusing since this is a non-LSA setup and should not have concept of "CFS node".admin@ncs% request core-fp-common:cfp-common-actions sync-dispatch-mapsuccess falsedetail Dispatch Map Sync action not allowed on CFS node.Please refer to the updated installation wiki for standalone. You'll want to use the action `request devices lsa dispatch-map sync` instead.Let me know if you run into anymore issues.Thanks,RegiHi Crystal,Thank you for bringing this up! I took a look and you are right.There seems to be some outdated information in our install wiki related to dispatch map. Since we transitioned to lsa-utils package, dispatch map config and action targets has changed. Let me fix the wikis now. I will let you know when the wikis are updated.Thanks,Isaac KimHi Crystal,It seems like the wiki was updated.Please let us know if you run into any more issues. We will review the wikis again to ensure this does not happen.Thanks,Isaac KimHi Isaac,What are the different steps we need to follow? I still see the same commands to use for the following:load merge config/commit-queue-settings.xmlrequest core-fp-common:cfp-common-actions sync-dispatch-mapMaybe it takes sometime to reflect the change? Clear browser cache does not seem to help.Thanks.-CrystalThere's a fair bit of changes and the changes are reflecting on my end. We did remove `request core-fp-common:cfp-common-actions sync-dispatch-map` and replaced it with ``request devices lsa dispatch-map sync` as well as removing some bootstrap XML files.Let us know if you still have issues, maybe we can send you a copy of the page.Thanks,RegiHi Reginald,I think the problem is the URL. The one shared in this ticket is:But the one we refer to is:When use the one in this ticket, we got page not found. see screenshot attachedIt will be great if you can send a copy of the page for now.Thanks.-CrystalHi Crystal,You're correct it seems the external wiki wasn't updated. I've gone ahead and updated the page: .Please try again.Thanks,RegiHi Reginald,Yes, I see the wiki is updated. Tried the following 2 commands. "dispatch-map sync" is successful. But "load merge config/commit-queue-settings.xml" still fail because there is no such file under config/ folder. Do we still need "commit-queue-settings.xml" for non-LSA setup? Console output:============admin@ncs% load merge config/commit-queue-settings.xmlError: failed to open file: File/directory does not exist. File name: commit-queue-settings.xmladmin@ncs% request devices lsa dispatch-map syncsuccess truedetail Dispatch Map Synced SuccessfullyYes, you would need it for standalone NSO. Another issue with the wiki. The file is located under 'xml' folder. I've updated it again: Sorry for the inconvenience,RegiHi Reginald,I got the same error. And could not find xml folder on my VM. console output:============admin@ncs% load merge xml/commit-queue-settings.xmlError: failed to open file: File/directory does not exist. File name: commit-queue-settings.xmlls output from tsdn folder:====================root@nso-193:~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2# lsCHANGES config core-fp-packages example-packages get_technical_support_data.shThanks.-CrystalHi Reginald,I also do not see xml folder under config. FYI...Console output:============root@nso-193:~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2# ls configcommit-queue-settings.xml         IETF-TE-plan-notification-settings.xml L3VPN-multi-vendor-iosxr-netconf.xmlIETF-L2NM-AA-notification-settings.xml  IETF-TE-status-codes.xml        L3VPN-plan-notification-settings.xmlIETF-L2NM-internal-plan-kicker.xml    L2VPN-AA-notification-settings.xml   L3VPN-status-codes.xmlIETF-L2NM-plan-notification-settings.xml L2VPN-cfp-configuration-kicker.xml   RSVP-TE-status-codes.xmlIETF-L2NM-status-codes.xml        L2VPN-internal-plan-kicker.xml     SR-cfp-configuration-kicker.xmlIETF-L3NM-AA-notification-settings.xml  L2VPN-multi-vendor-iosxe-cli.xml    SR-internal-plan-kicker.xmlIETF-L3NM-internal-plan-kicker.xml    L2VPN-multi-vendor-iosxr-netconf.xml  SR-multi-vendor-iosxe-cli.xmlIETF-L3NM-plan-notification-settings.xml L2VPN-plan-notification-settings.xml  SR-multi-vendor-iosxr-netconf.xmlIETF-L3NM-status-codes.xml        L2VPN-status-codes.xml         SR-plan-notification-settings.xmlIETF-TE-cfp-configuration-kicker.xml   L3VPN-AA-notification-settings.xml   SR-status-codes.xmlIETF-TE-internal-plan-kicker.xml     L3VPN-cfp-configuration-kicker.xml   xe-ip-sla-resource-pool.xmlIETF-TE-multi-vendor-iosxe-cli.xml    L3VPN-internal-plan-kicker.xml     xr-sman-id-resource-pool.xmlIETF-TE-multi-vendor-iosxr-netconf.xml  L3VPN-multi-vendor-iosxe-cli.xmlGotcha, but commit-queue-settings.xml does seem to be there under config from your outputHi Crystal,It seems like there was some confusion.All TSDN bootstrap payloads can be found under <TSDN ROOT>/config.Thanks,Isaac KimHi Reginald ; Isaac,I am able to see the commit-queue-settings.xml file under config/ folder. But when run the command to load merge, it failed again. Can we have a webex on Tuesday to look further? Thanks. -Crystalconsole output:============root@nso-193:~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2/config# lscommit-queue-settings.xml         IETF-TE-internal-plan-kicker.xml    L2VPN-plan-notification-settings.xml SR-cfp-configuration-kicker.xmlIETF-L2NM-AA-notification-settings.xml  IETF-TE-multi-vendor-iosxe-cli.xml   L2VPN-status-codes.xml        SR-internal-plan-kicker.xmlIETF-L2NM-internal-plan-kicker.xml    IETF-TE-multi-vendor-iosxr-netconf.xml L3VPN-AA-notification-settings.xml  SR-multi-vendor-iosxe-cli.xmlIETF-L2NM-plan-notification-settings.xml IETF-TE-plan-notification-settings.xml L3VPN-cfp-configuration-kicker.xml  SR-multi-vendor-iosxr-netconf.xmlIETF-L2NM-status-codes.xml        IETF-TE-status-codes.xml        L3VPN-internal-plan-kicker.xml    SR-plan-notification-settings.xmlIETF-L3NM-AA-notification-settings.xml  L2VPN-AA-notification-settings.xml   L3VPN-multi-vendor-iosxe-cli.xml   SR-status-codes.xmlIETF-L3NM-internal-plan-kicker.xml    L2VPN-cfp-configuration-kicker.xml   L3VPN-multi-vendor-iosxr-netconf.xml xe-ip-sla-resource-pool.xmlIETF-L3NM-plan-notification-settings.xml L2VPN-internal-plan-kicker.xml     L3VPN-plan-notification-settings.xml xr-sman-id-resource-pool.xmlIETF-L3NM-status-codes.xml        L2VPN-multi-vendor-iosxe-cli.xml    L3VPN-status-codes.xmlIETF-TE-cfp-configuration-kicker.xml   L2VPN-multi-vendor-iosxr-netconf.xml  RSVP-TE-status-codes.xmlroot@nso-193:~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2/config# cd ..root@nso-193:~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2# ncs_cli -u adminUser admin last logged in 2022-02-18T22:09:49.932596+00:00, to nso-193, from 10.21.93.73 using cli-sshadmin connected from 10.21.93.73 using ssh on nso-193admin@ncs> configure Entering configuration mode privateadmin@ncs% load merge xml/commit-queue-settings.xmlError: failed to open file: File/directory does not exist. File name: commit-queue-settings.xmlThe file path is relative to the directory in which ncs_cli is opened.Example:If I'm in the path: /home/rechand/Downloads/nso-5.7-tsdn-internal-4.0.0-M2<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre> ~/Downloads/nso-5.7-tsdn-internal-4.0.0-M2 > ncs_cli -u admin admin@ncs> confEntering configuration mode private[ok][2022-02-18 17:36:36][edit]admin@ncs% load merge Possible completions: <filename/terminal> CHANGES conf/ core-fp-packages/ example-packages/ fp_data.json get_technical_support_data.sh init_data/ installer/ local-install/</pre></div></div>If you click the <tab> key after you type "load merge" it will try to do auto-completion and will show you the available files/directories.For your case, the "commit-queue-settings.xml" is in the "config" directory.If you still need help next week, then we can do a webex.Thanks,RegiThat is correct. If you look at the console output in my last reply: the command steps are:root@nso-193:~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2/config# lsroot@nso-193:~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2/config# cd ..root@nso-193:~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2# ncs_cli -u adminadmin@ncs> configureadmin@ncs% load merge xml/commit-queue-settings.xmlBut you're "commit-queue-settings.xml" is not in an xml folder as per your output its in config folder (~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2/config) . The very first XML file.<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>root@nso-193:~/tsdn40_m2/nso-5.7-tsdn-4.0.0-M2/config# lscommit-queue-settings.xml IETF-TE-internal-plan-kicker.xml L2VPN-plan-notification-settings.xml SR-cfp-configuration-kicker.xmlIETF-L2NM-AA-notification-settings.xml IETF-TE-multi-vendor-iosxe-cli.xml L2VPN-status-codes.xml SR-internal-plan-kicker.xmlIETF-L2NM-internal-plan-kicker.xml IETF-TE-multi-vendor-iosxr-netconf.xml L3VPN-AA-notification-settings.xml SR-multi-vendor-iosxe-cli.xmlIETF-L2NM-plan-notification-settings.xml IETF-TE-plan-notification-settings.xml L3VPN-cfp-configuration-kicker.xml SR-multi-vendor-iosxr-netconf.xmlIETF-L2NM-status-codes.xml IETF-TE-status-codes.xml L3VPN-internal-plan-kicker.xml SR-plan-notification-settings.xmlIETF-L3NM-AA-notification-settings.xml L2VPN-AA-notification-settings.xml L3VPN-multi-vendor-iosxe-cli.xml SR-status-codes.xmlIETF-L3NM-internal-plan-kicker.xml L2VPN-cfp-configuration-kicker.xml L3VPN-multi-vendor-iosxr-netconf.xml xe-ip-sla-resource-pool.xmlIETF-L3NM-plan-notification-settings.xml L2VPN-internal-plan-kicker.xml L3VPN-plan-notification-settings.xml xr-sman-id-resource-pool.xmlIETF-L3NM-status-codes.xml L2VPN-multi-vendor-iosxe-cli.xml L3VPN-status-codes.xmlIETF-TE-cfp-configuration-kicker.xml L2VPN-multi-vendor-iosxr-netconf.xml RSVP-TE-status-codes.xml</pre></div></div>Hi Reginald,I see there are 4 updates of this wiki today. I used version 5 command which is "load merge xml/commit-queue-settings.xml" instead of "load merge config/commit-queue-settings.xml. The latest version V6 has the right path.Now I am able to successfully load merge dispatch-map-settings.xml. Thanks for looking into the issue.Glad to hear it!Thanks,Regi