Statement introduced in JUNOS Release 7.4.
and-quit, comment, and and-force options added in JUNOS Release 8.5.
Configure the commit command to automatically result in a commit synchronize action between dual Routing Engines within the same chassis. The Routing Engine on which you execute the commit command (requesting Routing Engine) copies and loads its candidate configuration to the other (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.
Synchronization only occurs between the Routing Engines within the same chassis. On the TX Matrix platform, when synchronization is complete, the new configuration is then distributed to the Routing Engines on the T640 routing nodes. That is, the master Routing Engine on the TX Matrix platform distributes the configuration to the master Routing Engine on each T640 routing node. Likewise, the backup Routing Engine on the TX Matrix platform distributes the configuration to the backup Routing Engine on each T640 routing node.
![]() |
Note: When you configure nonstop active routing (NSR), you must include the commit synchronize statement. Otherwise, the commit fails. |
and-quit—(Optional) Quit configuration mode if the commit synchronization succeeds.
comment—(Optional) Write a message to the commit log.
and-force—(Optional) Force a commit synchronization on the other Routing Engine (ignore warnings).
See Configuring Nonstop Active Routing.
system—To view this statement in the configuration.
system-control—To add this statement to the configuration.