Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

How the SRC Configuration Is Stored

 

When you edit a configuration, you work in a copy of the current configuration to create a candidate configuration. Changes you make to the candidate configuration are visible in the CLI immediately. If multiple users edit the configuration at the same time, all users can see all changes.

To have a candidate configuration take effect, you commit the changes. At this point, the software verifies the candidate configuration for proper syntax. If multiple users are editing the configuration, when you commit the candidate configuration, all changes made by all the users take effect.

You can save the local (slot) configuration and the shared configuration. The slot (local) configuration is stored in either a text file or XML file, and the remainder of the configuration (shared) is stored in the Juniper Networks database or another directory that you have configured to store SRC configuration data.

Figure 10 illustrates the various configuration states and the configuration mode commands that you use to load, commit, copy, and save the configuration.

Figure 10: Commands for Storing and Modifying the Configuration
Commands for Storing and Modifying the
Configuration