On 28.09.2015 23:24, Martin T wrote:
Hi, when I commit the candidate configuration in Junos, I tend to execute "commit check" and if configuration check succeeds, then I execute "commit comment <COMMENT>". However, when I think about it, "commit (comment)" itself should perform those very same checks that "commit check" does. If yes, then what is the point of "commit check"? Only purpose I could see is to check the validity of the candidate configuration in the middle of the configuration process, i.e. to check if the changes made in candidate configuration so far are fine but the candidate configuration is not ready to be committed.
You can use "commit check" to confirm a "commit confirmed" action. That way you don't create a new configuration file in your rollback log every time you cancel a pending rollback.
-- Harald _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
