A Cisco NSO service has just been deployed.
Which Cisco NSO CLI command is used to inspect the resulting device configuration changes before the changes are pushed to the network?
When a Cisco NSO service is deployed, it generates device configuration changes that need to be pushed to the network. Before pushing these changes to the network, it is important to inspect the changes to ensure that they are correct and will not cause any issues.
To inspect the resulting device configuration changes, the correct Cisco NSO CLI command is "commit dry-run outformat native". This command performs a dry-run of the commit, which means that the changes are not actually applied to the devices. Instead, the command shows the resulting configuration changes that would be made if the changes were to be committed.
The "outformat native" option specifies the output format of the command. This option is useful when the command output needs to be processed by another program or script.
The "show service impact" command is used to show the impact of a service on the network. It shows the differences between the current device configurations and the configurations that will be applied by the service.
The "pseudo-commit" command is used to test the commit process without actually making any changes to the network devices. It can be used to check the syntax of the configuration changes before they are applied.
The "show dry-run output" command shows the output of a dry-run commit. It displays the resulting configuration changes that would be made if the changes were to be committed. However, this command does not actually perform a dry-run commit like the "commit dry-run outformat native" command does.