Committing a JUNOS Configuration

[Contents] [Prev] [Next] [Index] [Report an Error]

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



[edit]
user@host# commit 

commit complete
[edit]
user@host#

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:



[edit edit-path]
‘offending-statement;’

error-message

For example:



[edit firewall filter login-allowed term allowed from]
‘icmp-type [ echo-request echo-reply ];’
keyword ‘echo-reply’ unrecognized

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.

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.

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.

[Contents] [Prev] [Next] [Index] [Report an Error]