• Supported Platforms
• EX Series
• M Series
• MX Series
• T Series

• Related Topics
• Committing a Junos Configuration and Exiting Configuration Mode
• Activating a Junos Configuration but Requiring Confirmation
• Backing Up the Committed Configuration on the Alternate Boot Drive
• Committing a Junos Configuration
• Forms of the configure Command

Committing a Junos Configuration

To save Junos OS configuration changes to the configuration database and activate the configuration on the router, use the commit configuration mode command:

When you enter the commit command, the configuration is first checked for syntax errors (commit check). Then, if the syntax is correct, the configuration is activated and becomes the current, operational router configuration.

You can issue the commit command from any hierarchy level.

If the configuration contains syntax errors, a message indicates the location of the error and the configuration is not activated. The error message has the following format:

For example:

You must correct the error before recommitting the configuration. To return quickly to the hierarchy level where the error is located, copy the path from the first line of the error and paste it at the configuration mode prompt at the [edit] hierarchy level.

Note: CLI commit-time warnings displayed for configuration changes at the [edit interfaces] hierarchy level are removed and are logged as system log messages. This is also applicable to VRRP configuration at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number family (inet | inet6) address address] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family (inet | inet6) address address]

When you commit a configuration, you commit the entire configuration in its current form. If more than one user is modifying the configuration, committing it saves and activates the changes of all the users.

If you are using Junos OS 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 mergeload replaceload overrideload update For more information, see the Secure Configuration Guide for Common Criteria and Junos-FIPS. We do not recommend performing a commit operation on the backup Routing Engine when graceful Routing Engine switchover is enabled on the router.