Symbols
A
C
- C Series Controllers
- C Series controllers
- C Series platforms
- candidate configuration
- CLI
- command hierarchy
- command history
- command mode
- configuration mode
- command completion
- commands 1, 2
- comparing
- entering 1, 2
- exiting
- hierarchy 1, 2, 3
- navigation commands
- overview 1, 2
- statement description
- symbols in statement lists 1, 2
- verifying configurations
- editing level 1, 2
- environment settings
- help 1, 2
- interface elements
- keyboard sequences
- messages
- modes
- operating systems
- overview 1, 2
- password
- prerequisites
- privilege levels
- prompt strings
- tutorial
- working directory
- command output
- commands
- commit and-quit command 1, 2
- commit check command
- commit command 1, 2
- configuration
- configuration files
- configuration hierarchy
- configuration mode See CLI
- configuration statements
- deleting
- overview 1, 2
- symbols in statements
- configure command
- conventions
- count filter
- cursor, moving
- customer support 1
D
- delete command 1, 2
- directories on C Series Controller
- documentation
E
- edit command 1, 2
- enable command
- environment settings, CLI 1
- except filter
- exit command 1, 2
F
H
I
K
L
M
- manuals
- messages
- MORE filter
- MORE prompt
N
O
- online help See CLI, help
- operational mode
P
Q
R
- redrawing screen
- regular expressions
- rename command 1, 2
- request system halt command
- request system reboot
- restart command 1, 2
- rollback command 1, 2
- run command
S
- save command
- screen
- set cli complete-on-space command
- set cli directory command 1, 2
- set cli language command
- set cli level command
- set cli password command
- set cli prompt command
- set cli screen-length command
- set cli screen-width command
- set cli terminal command
- set command 1, 2
- show cli authorization command
- show cli command
- show cli history command
- show cli level command
- show command
- show component command 1, 2
- show configuration command
- show system information command
- SRC CLI
- starting
- SRC components
- SRC modules
- SRC software
- statements See configuration statements, names of individual statements
- support, technical See technical support
- symbols in statements
T
U
- up command
- URLs in commands
- user accounts
W
X
Download This Guide
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

Related Documentation
- Creating an SRC Configuration
- SRC Configuration Updates
- About SRC Configuration Files in XML Format
- About SRC Configuration Files in Text Format
- About SRC Configuration Files in Set Format
- Cutting and Pasting Configuration Information at the SRC CLI