Need instructions on how to verify all of the "load merge" from configure bootstrap data.: Under installation - for configure bootstrap data and configure common bootstrap data, there are many 'load merge' commands need to be executed - some may or may not show any error but at the end, user may not know if all of the xml got load merged correctly or not - it would be very helpful to know some "show" command to verify this steps to ensure all of the xml were load merged.
If you look at the contents of the XML files, then you can run show commands based on that. You can also do a `commit dry-run` to check if the output matches the payload you're trying to load mergehi Reginald, there are more than 30 xml files - if we have to do a show command for each - this is not very practical way. would be good to know the show command for each block of load merge (i.e notification, kicker, etc..) Also some show command will need to have "hide/unhide tsdn" or "hide/unhide debug" prior to the 'show' command which we are not aware of. Please provide a better for user to verify during installation process. Thanks and regards!If you need to do an `unhide/hide` to load merge the payloads then you would need it for the show commands as well. You're best bet is to check before commit. Either a `commit dry-run` or `show | compare` (Juniper CLI) or `show configuration diff` (Cisco CLI).Thanks,RegiThanks Reginald for your input - the issue here is after installation and something went wrong - we would not know which command to use to verify all of the load merged were done correctly - for example - we were using LSA setup and all of the service got stuck in 'in-progress' state - we opened the ticket, , for the issue and found out that the notification-kicker was not load merged correctly or missing - so for user, it is not straight forward to know which notification is needed or which one to check with 'show' cmd. Please try to look at the issue from user point of view since it maybe obvious to nso developer to know but not the user. Thanks and regards!For now, you can do something like `commit dry-run outform xml` and the output shouldn't be too different from the bootstrap xml you're trying to load merge. You can even go ahead and verify the configs after commit. If look the the bootstrap XML files such as the kickers for example take a look at the parent tag you'll see its "kickers". as such you can do "show running-config kickers | display xml" (Cisco CLI) or "show kickers | display xml" (juniper). Just be aware if you had to do an `unhide debug` for the payload you merged then you'll need to do that as well for "show" command assuming you already ran "hide debug".In the meantime, I'll go ahead and create an internal ticket to update the documentation to add some verification for the bootstrap configs.Thanks,RegiDocumentation was updated as of M4. Closing this ticket now.