Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Modifying the Configuration


To configure the SRC software or to modify an existing configuration, you add statements to the configuration. For each statement hierarchy, you create the hierarchy starting with a statement at the top level and continuing with statements that move progressively lower in the hierarchy. Topic include:

Commands to Modify a Configuration

To modify the hierarchy, use the following configuration mode commands:

  • edit—Moves to a particular hierarchy level. If that hierarchy level does not exist, the edit command creates it. The edit command has the following syntax:

    where statement-path is the hierarchy to the configuration statement and the statement itself.

  • set—Creates a configuration statement and sets identifier values. After you issue a set command, you remain at the same level in the hierarchy. The set command has the following syntax:


    statement-path is the hierarchy to the configuration statement and the statement itself. If you have already moved to the statement’s hierarchy level, you can omit the statement path.

    statement is the configuration statement itself.

    identifier is a string that identifies an instance of a statement.

    You can also set more than one option for a configuration statement. For example:

    where transaction-variable, operator, and value are options.

    You cannot use the edit command to change the value of identifiers. You must use the set command.

Entering Values for Statement Options

When values include the following characters—space, single quotation marks (‘), double quotation marks (“), curly braces ({}), brackets ([ ]), or commas (,)—you must enclose the value in quotation marks (“ “) or use a backslash (\) before the character.

In order to distinguish parameter names from literal string values, literal string values need to be enclosed in double quotation marks. To enter them in the SRC CLI, the double quotation marks must be escaped. The recommended way to do this in the SRC CLI is to enclose the literal string (with double quotation marks) within single quotation marks—for example, “abc” is entered in the SRC CLI as ‘“abc”’. Alternatively, you can enter the literal in double quotation marks within backslashes—for example, \“abc\”. If just abc is used, it is considered a parameter and the SRC policy engine searches for the value of that parameter.

For convenience, where there is a fixed or well-known set of values for a parameter type, the SRC software provides a set of built-in global parameter definitions for each well-known value in the type. The SRC CLI generates completion lists for policy attributes of a given type from the set of global parameters defined for that type. You can also define your own global parameters to avoid the need to enter literal strings in quotations. For example, a global parameter abc=“abc” could be defined to make it convenient to enter the literal string “abc”.

To enter words or letters separated by a space, such as a full name with a first name and last name, enclose the words in quotation marks. For example:

"Chris Bee"

To enter multiple values, separate values with a space, and enclose the values with brackets. For example:


To enter a number using a regular expression, use backslashes (\) to escape the brackets. For example:


Displaying the Current Configuration

You can display the current configuration from operational mode or from configuration mode. In configuration mode, you can display the configuration at the specified hierarchy level.

To display the current configuration from configuration mode:

  • Use the show command.


To display the current configuration from operational mode:

  • Use the show configuration command.

The configuration statements appear in a fixed order; however, when you configure the C Series Controller, you can enter statements in any order.

If you omit a required statement at a particular hierarchy level, when you issue the show or show configuration command, a message indicates which statement is missing. As long as a mandatory statement is missing, the CLI continues to display this message each time you issue a show or show configuration command.

For example, the following output includes a warning that lists mandatory attributes that need to be configured:

Examples: Displaying the Current Configuration

Configure timers for aggregate services from the [edit] hierarchy level, and then view the configuration from the same hierarchy level:

Display a configuration at a specific hierarchy level:

Move to a lower level in the hierarchy, [edit shared sae configuration aggregate-services], and then display the configuration at that level:

Display all of the last committed configuration from operational mode:

Adding Configuration Statements and Identifiers

When you use the ? help to view a list of possible command completions, the output includes symbols that provide more information about the statement. The following symbols can appear in a list:

  • Angle bracket (>) before the statement name indicates that the statement is a container statement and that you can define other statements at levels below it.

  • No angle bracket (>) before the statement name indicates that the statement is a leaf statement; you cannot define other statements at hierarchy levels below it.

  • Plus sign (+) before the statement name indicates that the statement can contain a set of values. To specify a set, include the values in brackets.

  • Asterisk (*) before a statement name indicates a required statement or option that is not configured.

  • Plus/Asterisk (+*) before a statement name indicates a required option that can contain a set of values.

The following example at the [edit system services] hierarchy level shows that authentication-order, domain-search, and name-server can contain more than one value.

The following example at the [edit shared sae configuration driver] hierarchy level shows that mac-cache-expiration and unauthenticated-subscriber-dn are required statements.

If you do not type an option for a statement that requires one, a message indicates the type of information expected. In this example, you need to type an area number as an identifier to complete the logger name:

Deleting a Statement from the Configuration

Deleting a statement or an identifier effectively “unconfigures” the functionality associated with that statement or identifier, returning that functionality to its default condition.

To delete a statement or identifier:

  • Use the delete configuration mode command.

When you delete a statement, the statement and all its subordinate statements and identifiers are removed from the configuration.

For statements that can have more than one identifier, when you delete one identifier, only that identifier is deleted. The other identifiers in the statement remain.

To delete the entire hierarchy starting at the current hierarchy level:

  • In configuration mode, use the delete command. Do not specify a statement or an identifier.

    When you omit the statement or identifier, you are prompted to confirm the deletion. For example:

Examples: Deleting a Statement from the Configuration

Configure the SRC aggregate-services statements, then delete these statements from the [edit] level. Using the delete command effectively unconfigures the SAE properties for aggregate-services in the SRC software:

Configure the aggregate-services statements, then delete these statements from the [edit shared sae configuration aggregate-services] level:

Remove the configuration for a specific property (routing-options):

Renaming an Identifier

To modify a configuration, you can rename an identifier that already exists. You can do this either by deleting the identifier (using the delete command) and then adding the renamed identifier (using the set and edit commands), or you can rename the identifier using the rename mode command:

Example: Renaming an Identifier

Change the Network Time Protocol (NTP) server address to

Inserting a New Identifier

You can enter most statements and identifiers in any order. Regardless of the order in which you enter the configuration statements, the CLI always displays the configuration in a strict order. However, in a few cases the ordering of the statements matters because the configuration statements create a sequence that is analyzed in order.

For example, rules for interface, subscriber, and DHCP classification scripts are evaluated in the order in which they appear in the configuration. If you add a rule that you want to be evaluated before an existing rule, you need to modify the ordering of the rules. To modify a portion of the configuration in which the statement order matters:

  • Use the insert configuration mode command:

If you do not use the insert command, but instead simply configure the identifier, it is placed at the end of the list of similar identifiers.

You use the insert command to reorder identifiers that you have already configured.

Examples: Inserting a New Identifier

Add a new subscriber classification rule and insert it before existing rules at the [edit shared sae user-classifier] hierarchy level:

Copying a Configuration from One Configuration Location to Another

You can copy a collection of configuration statements from one place in the configuration to another. This process simplifies configuration so that you do not need to configure the same information in more than one place.

To copy a collection of configuration statements from one location to another:

For example, to copy the configuration for user Chris to another use Pat:

Displaying Set Commands for the Configuration (SRC CLI)

You can display the candidate configuration using the display set command along with the show command. The configuration displayed can be used as the basis for another configuration at the top level of the configuration hierarchy or at the current hierarchy level.

To display the configuration in the form of the set command:

The following example displays the show user admin | display set command output for the set configuration: