commit

Syntax

Release Information

Command introduced before JUNOS Release 7.4.

Description

Commit the set of changes to the database and cause the changes to take operational effect.

Options

and-quit—(Optional) Commit the configuration and, if the configuration contains no errors and the commit succeeds, exit from configuration mode.

at <"string">—(Optional) Save software configuration changes and activate the configuration at a future time, or upon reboot.

string is reboot or the future time to activate the configuration changes. Enclose the string value (including reboot) in quotation marks (“ ”). You can specify time in two formats:

• A time value in the form hh:mm[:ss] (hours, minutes, and optionally seconds)— Commit the configuration at the specified time, which must be in the future but before 11:59:59 PM on the day the commit at configuration command is issued. Use 24-hour time for the hh value; for example, 04:30:00 is 4:30:00 AM, and 20:00 is 8:00 PM. The time is interpreted with respect to the clock and time zone settings on the router.

• A date and time value in the form yyyy-mm-dd hh:mm[:ss] (year, month, date, hours, minutes, and, optionally, seconds)—Commit the configuration at the specified day and time, which must be after the commit at command is issued. Use 24-hour time for the hh value. For example, 2003-08-21 12:30:00 is 12:30 PM on August 21, 2003. The time is interpreted with respect to the clock and time zone settings on the router.

For example, commit at “18:00:00". For date and time, include both values in the same set of quotation marks. For example, commit at "2005-03-10 14:00:00".

A commit check is performed when you issue the commit at configuration mode command. If the result of the check is successful, then the current user is logged out of configuration mode, and the configuration data is left in a read-only state. No other commit can be performed until the scheduled commit is completed.

Note: If the JUNOS software fails before the configuration changes become active, all configuration changes are lost. You cannot issue the commit at configuration command when there is a pending reboot. You cannot issue the request system reboot command once you schedule a commit operation for a specific time in the future. You cannot commit a configuration when a scheduled commit is pending. For information about how to use the clear command to cancel a scheduled configuration, see the JUNOS System Basics and Services Command Reference.

check—(Optional) Verify the syntax of the configuration, but do not activate it.

comment <"comment-string">—(Optional) Add a comment that describes the committed configuration. The comment can be as long as 512 bytes and must be typed on a single line. You cannot include a comment with the commit check command. Enclose comment-string in quotation marks (" "). For example, commit comment "Includes changes recommended by SW Lab".

confirmed <minutes>—(Optional) Require that the commit be confirmed within the specified amount of time. To confirm a commit, enter either a commit or commit check command. If the commit is not confirmed within the time limit, the configuration rolls back automatically to the precommit configuration and a broadcast message is sent to all logged-in users. To show when a rollback is scheduled, enter the show system commit command.

Range: 1 through 65,535 minutes

Default: 10 minutes

display detail—(Optional) Monitors the commit process.

synchronize <force>—(Optional) (On routers with dual Routing Engines) Direct one Routing Engine to synchronize its configuration with the other. The Routing Engine on which you execute this command (request Routing Engine) copies and loads its candidate configuration to the other (responding Routing Engine). Both Routing Engines then perform 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. The commit synchronize command does not work if the responding Routing Engine has uncommitted configuration changes. However, you can enforce commit synchronization on the Routing Engines by using the force option. When you issue the commit synchronize command with the force option from one Routing Engine, the configuration sessions on the other Routing Engine will be terminated and its configuration synchronized with that on the Routing Engine from which you issued the command.

Note: When you issue the commit synchronize command, you must use the apply-groups re0 and re1 commands. For information about how to use groups, see Applying a Configuration Group. The responding Routing Engine must use JUNOS Release 5.0 or later.

Usage Guidelines

See Verifying a JUNOS Configuration, Committing a JUNOS Configuration, Scheduling a JUNOS Commit Operation, Deactivating and Reactivating Statements and Identifiers, Monitoring the JUNOS Commit Process, and Adding a Comment to Describe the Committed Configuration.

Required Privilege Level

configure—To enter configuration mode.

Note: If you are using JUNOS software in a Common Criteria environment, system log messages are created whenever a secret attribute is changed (for example, password changes or changes to the RADIUS shared secret). These changes are logged during the following configuration load operations: load merge load replace load override load update For more information, see the Secure Configuration Guide for Common Criteria and JUNOS-FIPS .

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.