[j-nsp] purpose of "commit check"?

[Ryan Harden]

We regularly make large config changes, ‘commit check’ to confirm there aren’t any syntax errors, then save the change as a patch to be applied during a maintenance window.
This saves a ton of time during maint windows as we can do configs the day before and at least be sure there are no syntax errors in the patch. Maint windows simply become: load the patch, commit confirmed comment blah, verify, done.

/Ryan

Ryan Harden
Research and Advanced Networking Architect
University of Chicago - ASN160
P: 773.834.5441

> On Sep 28, 2015, at 4:24 PM, Martin T <m4rtntns at gmail.com> 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.
> 
> 
> thanks,
> Martin
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp