Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Configuring Explicit Routing (SRC CLI)

 

Explicit routing rules can be configured for accounting and authentication requests. When you configure an accounting or authentication route, you specify:

  • (Optional) An editing rule you want to apply to the request before it is forwarded to the target.

  • A predefined accounting method that is the target for the route.

  • A predefined authentication route target (network element).

  • (Optional) A set of conditions that must be matched in the request for the route to be selected.

    When multiple routes are configured, they are evaluated in the order they are displayed by the show command. A newly created route is displayed last among the routes and has the lowest priority, so it is evaluated last. You can use the SRC CLI insert command to move a route before or after another route to change its evaluation order. The higher a route is displayed on the list, the sooner it is evaluated.

    You can specify any combination of match conditions and condition tests as described in Table 1. For a complete list of statements used to configure explicit routing rules, see Configuration Statements for SIC Explicit Accounting Routing Rules and Configuration Statements for SIC Explicit Authentication Routing Rules.

    Table 1: Explicit Routing Rule Conditions

    Match Condition

    Condition Tests

    • Realm

    • User identity

    • Request attribute

    • Present

    • Not present

    • Equals

    • Does not equal

    • Has suffix

    • Has prefix

    • Within range

    For a complete list of statements you use to configure accounting routes, see Configuration Statements for SIC Explicit Accounting Routing Rules. For a complete list of statements you use to configure authentication routes, see Configuration Statements for SIC Explicit Authentication Routing Rules.

To configure explicit routes:

  1. From configuration mode, access the configuration statement used to configure explicit routes. For example, to configure an accounting route called route66 for the server svr1, in a group called g1:
  2. (Optional) Specify the name of the predefined editing rule you want applied to the request before it is forwarded to the target. For example to apply an editing rule called er1:
  3. Specify a predefined accounting method or authentication routing target to use as the target of the route. If this route is selected, packets are routed to this target. For example, to specify an accounting method called acctg-meth1 as the target:
  4. (Optional) Specify the conditions that must be matched for the route to be selected. For example, to specify that the request must contain a realm=abc.com:
  5. Commit the configuration.
  6. Verify the routing configuration.