[Contents] [Prev] [Next] [Index] [Report an Error]

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:

shared network nas-group name {
hosted-by [hosted-by...];
function (aaa);
scope [scope...];
default-peer default-peer;
update-grace-period update-grace-period;
initial-ppr-delay initial-ppr-delay;
}

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 a AAA peer group, the SAEs on the listed hosts will create device drivers for this peer group.
  3. Specify the functional interface of the peer 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 Diameter Peers

Use the following configuration statements to configure the Diameter peers:

shared network nas-group name peer name {
protocol [(tcp | sctp)...];
address [address...];
local-address local-address;
connect-timeout connect-timeout;
watchdog-timeout watchdog-timeout;
state-machine-timeout state-machine-timeout;
reconnect-timeout reconnect-timeout;
port port;
origin-host origin-host;
incoming-queue-limit incoming-queue-limit;
active-peer;
}

To configure the Diameter peer in the NAS group:

  1. From configuration mode, access the configuration statements for the peer.

    The peer name must be unique in the NAS group.

  2. Specify the protocol for the transport connection.
  3. Specify the addresses of the remote peer.
  4. (Optional) Specify the local address of the peer.
  5. (Optional) Specify the maximum amount of time to respond to a connection request.
  6. (Optional) Specify the watchdog timeout used for the connection to the remote peer.
  7. (Optional) Specify the Diameter state machine timeout.
  8. (Optional) Specify the time interval between connection attempts when the peer is in the disconnected state.
  9. (Optional) Specify the port for the client.
  10. (Optional) Specify the identifier for the endpoint that the peer presents during connection establishment.
  11. (Optional) Specify the number of messages allowed on the incoming message queue for a peer.
  12. (Optional) Specify whether the peer connection is in active mode and automatically starts communicating with the IMS AAA Server.

Classifying Interfaces

Use the following configuration statements to define interface classification scripts:

shared network nas-group name interface-classifier rule name {
script script;
}
shared network nas-group name interface-classifier rule name {
target target;
}
shared network nas-group name interface-classifier rule name condition name ...

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.

    OR

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

Selecting Routes

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

shared network nas-group name routes name term name {
precedence precedence;
}
shared network nas-group name routes name {
transaction-variable (request-packet | user-name | realm);
dictionary-attribute (user-name | user-password | chap-password | nas-ip-address | nas-port | service-type | framed-protocol | framed-ip-address | framed-ip-netmask | framed-mtu | framed-compression | login-ip-host | callback-number | state | vendor-specific | called-station-id | calling-station-id | nas-identifier | login-lat-service | login-lat-node | login-lat-group | chap-challenge | nas-port-type | port-limit | login-lat-port);
operator (equals | not_equal | present | not_present | prefix | suffix | range);
value value;
low low;
high high;
}

To configure route selection for messages from the IMS AAA 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. Only applicable 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.

[Contents] [Prev] [Next] [Index] [Report an Error]