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

# Configuring the NAS Groups (SRC CLI)

Tasks to configure the NAS groups are:

- Configuring NAS Groups
- Configuring Diameter Peers (SRC CLI)
- Classifying Interfaces
- Selecting Routes

## Configuring NAS Groups

Use the following configuration statements to configure the NAS groups:

`

shared network nas-group name {
  hosted-by [hosted-by...];
  peers [peers...];
  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.
   `
   user@host# edit shared network nas-group name
   `
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.
   `
   [edit shared network nas-group name]
   user@host# set hosted-by [hosted-by...]
   `
3. (Optional) Specify the peers in this NAS group.
   `
   [edit shared network nas-group name]
   user@host# set peers [peers...]
   `
4. (Optional) Specify the service scopes available to subscribers connected to this NAS group.
   `
   [edit shared network nas-group name]
   user@host# set scope [scope...]
   `
5. (Optional) Specify the default peer.
   `
   [edit shared network nas-group name]
   user@host# set default-peer default-peer
   `
6. (Optional) Specify the grace period for interim updates.
   `
   [edit shared network nas-group name]
   user@host# set update-grace-period update-grace-period
   `
7. (Optional) Specify the delay for sending initial Push-Profile-Requests (PPRs) to install policies.
   `
   [edit shared network nas-group name]
   user@host# set initial-ppr-delay initial-ppr-delay
   `

## Configuring Diameter Peers (SRC CLI)

Use the following configuration statements to configure the Diameter peers:

`

shared network diameter peer name {
  protocol [(tcp | sctp)...];
  address [address...];
  enforce-source-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:

1. From configuration mode, access the statements for the peer.
   `
   user@host# edit shared network diameter peer name
   `

   The peer name must be unique.

2. Specify the protocol for the transport connection.
   `
   [edit shared network diameter peer name]
   user@host# set protocol [(tcp | sctp)...]
   `
3. Specify the addresses of the remote peer. If SCTP is the transport protocol, you can specify multiple addresses. If TCP is the transport protocol, you can specify only a single address.
   `
   [edit shared network diameter peer name]
   user@host# set address [address...]
   `
4. (Optional) Specify whether the remote peer must connect from one of the IP addresses listed by the address option.
   `
   [edit shared network diameter peer name]
   user@host# set enforce-source-address
   `
5. (Optional) Specify the local address of the peer.
   `
   [edit shared network diameter peer name]
   user@host# set local-address local-address
   `
6. (Optional) Specify the maximum amount of time to respond to a connection request.
   `
   [edit shared network diameter peer name]
   user@host# set connect-timeout connect-timeout
   `
7. (Optional) Specify the watchdog timeout used for the connection to the remote peer.
   `
   [edit shared network diameter peer name]
   user@host# set watchdog-timeout watchdog-timeout
   `
8. (Optional) Specify the Diameter state machine timeout.
   `
   [edit shared network diameter peer name]
   user@host# set state-machine-timeout state-machine-timeout
   `
9. (Optional) Specify the time interval between connection attempts when the peer is in the disconnected state.
   `
   [edit shared network diameter peer name]
   user@host# set reconnect-timeout reconnect-timeout
   `
10. (Optional) Specify the port for the client.
    `
    [edit shared network diameter peer name]
    user@host# set port port
    `
11. (Optional) Specify the identifier for the endpoint that the peer presents during connection establishment.
    `
    [edit shared network diameter peer name]
    user@host# set origin-host origin-host
    `
12. (Optional) Specify the number of messages allowed on the incoming message queue for a peer.
    `
    [edit shared network diameter peer name]
    user@host# set incoming-queue-limit incoming-queue-limit
    `
13. (Optional) Specify whether the peer connection is in active mode.
    `
    [edit shared network diameter peer name]
    user@host# set active-peer
    `

## 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.
   `
   user@host# edit shared network nas-group name interface-classifier
   `
2. Create a rule for the classifier. You can create multiple rules for the classifier.
   `
   [edit shared network nas-group name interface-classifier]
   user@host# edit rule name
   `
3. Configure either a target or a script for the rule.
   `
   [edit shared network nas-group name interface-classifier rule name]
   user@host# set script script
   `

   OR

   `
   [edit shared network nas-group name interface-classifier rule name]
   user@host# set target target
   `
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.
   `
   [edit shared network nas-group name interface-classifier rule name]
   user@host# set condition name
   `

## 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.
   `
   user@host# edit shared network nas-group name routes name
   `
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.
   `
   [edit shared network nas-group name routes name]
   user@host# set precedence precedence
   `
3. From configuration mode, access the configuration statements for route selection criteria.
   `
   user@host# edit shared network nas-group name routes name term name
   `

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

4. Specify the name of the transaction variable used as the matching criterion.
   `
   [edit shared network nas-group name routes name term name]
   user@host# set transaction-variable (request-packet | user-name | realm)
   `
5. (Optional) Specify the name of the dictionary attribute contained in the attribute store. Only applicable if the transaction variable is request-packet.
   `
   [edit shared network nas-group name routes name term name]
   user@host# set 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)
   `
6. Specify the operator for criterion matching.
   `
   [edit shared network nas-group name routes name term name]
   user@host# set operator (equals | not_equal | present | not_present | prefix | suffix | range)
   `
7. (Optional) Specify the value to be matched by the target.
   `
   [edit shared network nas-group name routes name term name]
   user@host# set value value
   `
8. (Optional) Specify the low end of the range criterion.
   `
   [edit shared network nas-group name routes name term name]
   user@host# set low low
   `
9. (Optional) Specify the high end of the range criterion.
   `
   [edit shared network nas-group name routes name term name]
   user@host# set high high
   `

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