Understanding SRC CLI Configuration Mode
In configuration mode, you can configure properties for the SRC software, such as properties for the Juniper Networks database, SRC modules, user access, and system properties.
A configuration is stored as a hierarchy of statements. In configuration mode, you create the specific hierarchy of configuration statements that you want to use. When you have finished entering the statements, you commit them, which activates the configuration.
You can create the hierarchy interactively at the CLI, or you can a load configuration from a file that you create. To activate the configuration, you commit it.
Configuration Mode Commands
Table 12 summarizes each CLI configuration mode command. The commands are listed alphabetically.
Table 12: Summary of Configuration Mode Commands
Command | Description |
|---|---|
commit | Commit the set of changes to the database and cause the changes to take operational effect. |
delete | Delete a statement or identifier. All subordinate statements and identifiers contained within the specified statement path are deleted with it. |
edit | Move inside the specified statement hierarchy. If the statement does not exist, it is created. |
exit | Exit the current level of the statement hierarchy, returning to the level before the last edit command, or exit from configuration mode. The quit and exit commands are synonyms. |
help | Display help about available configuration statements. |
history | Display the previous commands entered at the CLI. |
insert | Insert an identifier into an existing hierarchy. |
load | Load a configuration from a file. Your current location in the configuration hierarchy is ignored when the load operation occurs. |
quit | Exit the current level of the statement hierarchy, returning to the level before the last edit command, or exit from configuration mode. The quit and exit commands are synonyms. |
rename | Rename an existing configuration statement or identifier. |
rollback | Return to the previously committed configuration. The software saves only the last committed configuration. |
run | Run an operational mode CLI command without exiting from configuration mode. |
save | Save the configuration to a file in text, XML, or set format. The contents of the current level of the statement hierarchy (and below) are saved, with the statement hierarchy containing it. This action allows a section of the configuration to be saved with the statement hierarchy. |
set | Create a statement hierarchy and set identifier values. This command is similar to edit except that your current level in the hierarchy does not change. With the set command, you can also set more than one option for a configuration statement. |
show | Display the current configuration. |
top | Return to the top level of configuration command mode, which is indicated by the [edit] banner. |
up | Move up one level in the statement hierarchy. |
For more information about configuration mode commands, see SRC PE CLI Command Reference.
Configuration Statements
You configure SRC properties by including statements in the configuration. A statement consists of the following parts:
Keyword—Fixed text
Identifier (Optional)—Identifying name that you define, such as the name of an interface, or a username, which allows you and the CLI to discriminate among a collection of statements
Table 13 describes top-level CLI configuration mode statements.
Table 13: Configuration Mode Top-Level Statements
Statement | Description |
|---|---|
interfaces | Configure interfaces on the C Series Controller. |
policies | Configure routing policies. |
redirect-server | Configure the redirect server. |
routing-options | Configure static routes. |
services | Define subscriber services. |
shared | Configure ACP, admission control, congestion points, auth-cache, network devices, NIC, and SAE. |
slot | Configure properties for a component, such as ACP, Juniper Policy Server, network information collector, and SAE on a slot. |
snmp | Configure Simple Network Management Protocol (SNMP) community strings, interfaces, traps, and notifications. |
subscribers | Configure subscriber definitions. |
system | Configure systemwide properties, including the hostname, domain name, Domain Name System (DNS) server, user logins and permissions, and software processes. |
For information about specific configuration statements, see the SRC PE CLI Command Reference.
Configuration Statement Hierarchy
The SRC software configuration consists of a hierarchy of statements. There are two types of statements: container statements, which are statements that contain other statements, and leaf statements, which do not contain other statements. All the container and leaf statements together form the configuration hierarchy.
Figure 9 shows container statements and leaf statements in the sae hierarchy. To view this hierarchy at the CLI, the editing level must be set to expert.
Each statement at the top level of the configuration hierarchy resides at the trunk (or root level) of a hierarchy tree. The top-level statements are container statements, containing other statements that form the tree branches. The leaf statements are the leaves of the hierarchy tree. An individual hierarchy of statements, which starts at the trunk of the hierarchy tree, is called a statement path. Figure 9 illustrates the hierarchy tree, showing a statement path for the portion of the shared configuration hierarchy that configures the idle timeout for the SAE.
The shared statement is a top-level statement at the trunk of the configuration tree. The acp, admission-control, auth-cache, congestion-points, network, nic, and sae statements are all subordinate container statements of the shared statement (they are branches of the shared hierarchy tree). The configuration and the idle-timeout statements are successive branches in the hierarchy under the sae branch. The adjust-session-time statement is a leaf on the tree, which, in this case, specifies that when a session is terminated by an idle timeout, the session time reported in the accounting stop message is automatically reduced by the idle time.
The CLI represents the statement path shown in Figure 9 as [shared sae configuration idle-timeout], and displays the configuration as follows:
The CLI indents each level in the hierarchy to indicate each statement’s relative position in the hierarchy and generally sets off each level with braces, using an open brace at the beginning of each hierarchy level and a closing brace at the end. Each leaf statement ends with a semicolon.