Configuration Versions

When you change the configuration in CLI configuration mode, your changes are stored in a copy of the currently active configuration. The copy is called the candidate configuration. By default, multiple users can edit the candidate configuration at the same time, and all users immediately see the changes made by everyone. Alternatively, you can lock other users out of the candidate configuration as you enter CLI configuration mode, making them unable to change the candidate configuration until you release the lock. For finer-grained control, you can also allow multiple users each to edit nonoverlapping portions of the configuration and to commit only their own changes.

For the candidate configuration to become the active configuration running on the routing platform, you must commit it. The candidate file is checked for proper syntax, activated, and saved to a file as the currently active configuration. If the candidate configuration is committed while multiple users are editing it, all changes made by all the users take effect.

In addition to saving the candidate and active configurations, the CLI saves the previous 49 configurations that were committed. You can roll back to any of the saved previous versions, making it the candidate configuration and then committing it if desired.

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