The parameters for fast-synchronize and synchronize do not apply for the SRX Series.
Statement introduced in Junos OS Release 7.4.
Option persist-groups-inheritance added in Junos OS Release 13.2.
Option delta-export added in Junos OS Release 14.2.
Option peers added in Junos OS Release 14.2R6
Option peers-synchronize added in Junos OS Release 14.2R6
Configure options for Junos OS commit.
commit-synchronize-server—(Optional) Specify traceoptions for commit synchronize server actions.
delta-export—(Optional) Configure system commit to export only the changes made in the candidate configuration instead of exporting the entire candidate configuration to the configuration database. This helps to reduce the time taken to commit the configuration changes..
fast-synchronize—(Optional) Configure commits to run in parallel (simultaneously) on both the master and backup Routing Engines to reduce the time required for commit synchronization. The fast-synchronize configuration is valid only on systems with two Routing Engines. (Option not available for SRX Series.)
notification—(Optional) Notify applications upon commit completion.
peers—(Optional) Specify the host names or IP addresses of the MC-LAG peers and the user authentication details for the users administering the MC-LAG peers that are participating in commit synchronization.
Starting in Junos OS Release 17.1R1, the peers option at the [edit system commit] hierarchy level is not supported in batch configuration mode.
peers-synchronize—(Optional) Configure a commit synchronization on MC-LAG peers.
persist-group-inheritance—(Optional) Configure this option to improve commit performance for systems that use many configuration groups that use wildcards. This option causes the full inheritance paths of the configuration groups to be built in the database instead of in the process memory.
server—(Optional) Configure a default batch commit.
synchronize—(Optional) For devices with multiple Routing Engines only. Configure the commit command to automatically perform a commit synchronize action between dual Routing Engines within the same chassis. The Routing Engine on which you execute the commit command (the requesting Routing Engine) copies and loads its candidate configuration to the other (the responding) Routing Engine. Each Routing Engine then performs a syntax check on the candidate configuration file being committed. If no errors are found, the configuration is activated and becomes the current operational configuration on both Routing Engines. (Option not available for SRX Series.)
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
maintenance—To view this
statement in the configuration.
maintenance-control—To add this statement to the configuration.