Commit a Configuration

To save 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#

The configuration is checked for syntax errors. 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.

After you commit the configuration and are satisfied that it is running successfully, you should issue the request system snapshot command to back up the new software onto the /altconfig file system. If you do not issue the request system snapshot command, the configuration on the alternate boot drive will be out of sync with the configuration on the primary boot drive.

The request system snapshot command backs up the root file system to /altroot, and /config to /altconfig. The root and /config file systems are on the router's flash drive, and the /altroot and /altconfig file systems are on the router's hard drive.

Notice -After you issue this command, you cannot return to the previous version of the software, because the running and backup copies of the software are identical.