Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Configuring the NAS Groups (SRC CLI)

 

Tasks to configure the NAS groups are:

Configuring NAS Groups

Use the following configuration statements to configure the NAS groups:

To configure the group of peers:

  1. From configuration mode, access the configuration statements for the NAS group.
  2. Specify the hosts that instantiate this peer group. If the peer group is an AAA peer group, the SAEs on the listed hosts create device drivers for this peer group.
  3. (Optional) Specify the peers in this NAS group.
  4. (Optional) Specify the service scopes available to subscribers connected to this NAS group.
  5. (Optional) Specify the default peer.
  6. (Optional) Specify the grace period for interim updates.
  7. (Optional) Specify the delay for sending initial Push-Profile-Requests (PPRs) to install policies.

Configuring the NAS Group Device Capabilities (SRC CLI)

The SAE uses user interim accounting requests to keep the user session alive. Some NAS devices do not send user interim accounting requests, which causes the user session to time out in the SAE. To support this type of NAS device, the SAE can use service interim accounting requests to keep the user session alive.

Use the following configuration statements to configure the NAS group device capabilities:

To configure the NAS group device capabilities:

  1. From configuration mode, access the configuration statements for the NAS group device capabilities.
  2. Specify whether to use service interim accounting requests.
    • If this option is set, the SAE uses service interim accounting requests to keep the user session alive in the SAE. The SAE can also send user-tracking events to plug-ins driven by SRC interim update interval.

    • If this option is not set, the SAE sends user interim tracking events only when it receives a user interim update from the NAS device.

See also

Classifying Interfaces

Use the following configuration statements to define interface classification scripts:

A classification script can contain either a target and a condition or a script. If you do not define a script, the classifier must have both a target and a condition.

To define interface classification scripts:

  1. From configuration mode, enter the interface classifier configuration for a NAS group.
  2. Create a rule for the classifier. You can create multiple rules for the classifier.
  3. Configure either a target or a script for the rule.
    • Configure the target for the rule.

      If you configure a target for the rule, you must configure a match condition. You can create multiple conditions for the rule. See Interface Classification Conditions.

    • Configure the script for the rule.

      (Optional) You can specify a script target.

      (Optional) You can include a script that has already been created.

      Where include is a reference to an existing script that is included in the script you are configuring.

Configuring NAS Group Routes

Use the following configuration statements to configure the route for messages:

To configure route selection for messages from the SRC Diameter server:

  1. From configuration mode, access the configuration statements for route selection.
  2. (Optional) Specify the order by which the route is selected. The route that meets all the matching criteria and has the lowest precedence is selected first. Routes without the precedence defined are considered after those that have the precedence defined. The route with precedence of -1 is the default route. The default route is considered after all the other routes, and only one default route can be defined.
  3. From configuration mode, access the configuration statements for route selection criteria.

    All the criteria must match for this route to be selected.

  4. Specify the name of the transaction variable used as the matching criterion.
  5. (Optional) Specify the name of the dictionary attribute contained in the attribute store. This is applicable only if the transaction variable is request-packet.
  6. Specify the operator for criterion matching.
  7. (Optional) Specify the value to be matched by the target.
  8. (Optional) Specify the low end of the range criterion.
  9. (Optional) Specify the high end of the range criterion.