commit (System)
Syntax
commit {
commit-synchronize-server;
delta-export;
fast-synchronize;
force-commit-log;
notification;
peers;
peers-synchronize;
persist-groups-inheritance | no-persist-groups-inheritance;
server;
synchronize;
}
The parameters for fast-synchronize and synchronize do not apply for the SRX Series.
Hierarchy Level
[edit system]
Description
Configure options for Junos OS commit.
Options
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 primary 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.)
force-commit-log—(Optional) Enforce log or message for each commit.
Once this is configured each commit triggered by an user mandates a comment. Only
users with admin-control privilege can enable or disable the
force-commit-log option. The following commands mandate a
comment once you enable force-commit-log option:
-
commit at -
commit confirmed -
commit and-quit -
batch mode commits -
commit synchronize, no-synchronize, and peers-synchronize -
commit scripts
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. To disable this option, use
no-persist-groups-inheritance. Starting in Junos OS Evolved
Release 19.2R1 and Junos OS Release 19.4R1, this option is enabled by default.
Junos OS Evolved requires this feature to be enabled. The
no-persist-groups-inheritance option to disable
persist-group-inheritance is not supported in Junos OS
Evolved.
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.
Junos OS Evolved does not support the following commit
configuration options:
-
fast-synchronize -
peers -
peer-synchronize -
commit-synchronize-server
Required Privilege Level
maintenance—To view or add this statement in the configuration.
Release Information
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.
Option no-persist-groups-inheritance added in Junos
OS Evolved Release 19.2R1 and Junos OS Release 19.4R1.