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.

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.

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.

Figure 9: Sample Configuration Mode Hierarchy of Statements

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.

Related Documentation

• Replacing the Current Configuration with the Default SRC Configuration
• Merging the Active Configuration with Another Configuration
• Replacing the Configuration
• Replacing Parts of the Configuration
• Adding a Configuration Through Configuration Mode Commands
• Loading a Configuration at a Specified Hierarchy Level