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 have committed the configuration and are satisfied that the new configuration is successfully running, 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 causes the root file system to be backed up to /altroot, and /config to be backed up 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.

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.

Commit a Configuration and Exit Configuration Mode

To save software configuration changes, activate the configuration on the router, and exit configuration mode, use the commit and-quit configuration mode command. This command succeeds only if the configuration contains no errors.

 [edit]
 user@host# commit and-quit 
 commit complete
 exiting configuration mode
 user@host> 

Activate a Configuration for a Limited Time

There might be times when you want to commit a candidate configuration, activating the configuration for a limited time to determine that it functions properly, reverting to the previous configuration afterwards. One case when you might want to do this is to ensure that a modified configuration does not lock you out of the command-line interface or the router.

To activate a configuration for a limited time, use the commit confirmed configuration mode command:

 [edit]
 user@host# commit confirmed 
 commit complete
 [edit]
 user@host#
 

As with the commit command, the commit confirmed command verifies the configuration syntax and reports any errors. If there are no errors, the configuration is activated and begins running on the router. By default, the configuration runs for 10 minutes. Then, the router reverts to the previous configuration.

To keep the new configuration active, enter a commit or commit check command within 10 minutes of the commit confirmed command.

Figure 5 illustrates how the commit confirmed command works.

Figure 5: Confirm a Configuration

To change the amount of time before you have to confirm the new configuration, specify the number of minutes when you issue the command:

 [edit]
 user@host# commit confirmed minutes 
 commit complete
 [edit]
 user@host#