| User Data Repository Diameter User's Guide Release 12.4 E92984-01 |
|
 Previous |
 Next |
Note:
You must assign a Connection Configuration Set attribute to each RADIUS Connection. When this attribute is assigned to a local node, it is ignored by RCL.Table 3-5 Configuration Sets Elements
| Field (* indicates required field) | Description | Data Input Notes |
|---|---|---|
| * Connection Configuration Set Name | Unique name of the Connection Configuration Set. |
Case-sensitive string: alphanumeric and underscore (_); must contain at least one alpha and cannot begin with a digit. Range: 1 - 32 characters |
| SCTP Options | ||
| * Retransmit Initial Timeout (ms) | Expected average network round-trip time in milliseconds. This is used to initialize the round-trip time value when an association is started but the round-trip time has not yet been measured. The round-trip time is used by SCTP in calculating when to retransmit chunks. Note: The parameter with the Local Node's Connection Configuration Set is used by the peer-initiated (responder) connection. |
Format: numeric Range: 10 - 5000 Default: 120 |
| * Retransmit Minimum Timeout (ms) | Minimum amount of time to wait for an acknowledgment for a message sent. This value prevents the retransmit timeout from becoming too small in networks with a very short round-trip time. | Format: numeric Range: 10 - 5000 Default: 120 |
| * Retransmit Maximum Timeout (ms) | Maximum amount of time to wait for an acknowledgment for a message sent. This value places an upper bound on the exponential back-off algorithm used by SCTP for retransmission timing. After this retransmit interval is reached, retransmits are sent at a constant rate until an ACK is received or the maximum attempts is reached. |
Format: numeric Range: 10 - 10000 Default: 120 |
| * Retransmit Maximum Timeout for INIT (ms) | Maximum amount of time to wait for an INIT to be acknowledged. This value overrides the Retransmit Maximum Timeout for INITs and is used to bound the initial setup time. A value of 0 indicates the Retransmit Maximum Timeout is used for INITs as well. Note: The parameter with the Local Node's Connection Configuration Set is used by the peer-initiated (responder) connection. |
Format: numeric Range: 0, 10 - 10000 Default: 120 |
| * Number of Retransmits Triggering Path Failure | Number of consecutive unsuccessful retransmits that cause a path of the SCTP association to be marked as failed. This value indicates how many SCTP retransmission attempts should be made to each destination of an SCTP association before marking the destination as failed. This value must be less than the Number of Retransmits Triggering Association Failure value. |
Format: numeric Range: 1 - 10 Default: 3 |
| * Number of Retransmits Triggering Association Failure | Number of consecutive retransmits that cause an SCTP association to be marked as failed. This value indicates how many SCTP retransmission attempts should be made to all destinations for an SCTP association before marking the association as failed. This value should not be greater than the sum of the retransmit attempts for all destinations within the association. |
Format: numeric Range: 1 - 20 Default: 5 |
| * Number of Retransmits Triggering Init Failure | Number of consecutive retransmits for INIT and COOKIE-ECHO Chunks that cause an SCTP connection to be marked as failed. This value indicates how many retransmission attempts should be made to the primary SCTP address for INIT and COOKIE-ECHO Chunks before marking the connection as failed. Note: The parameter with the Local Node's Connection Configuration Set is used by the peer-initiated (responder) connection. |
Format: numeric Range: 1 - 20 Default: 8 |
| * SACK Delay (ms) | The number of milliseconds to delay after receiving a DATA Chunk and before sending a SACK. A non-zero value for SACK Delay gives the application time to bundle DATA Chunks in the same SCTP datagram with the SACK, thereby reducing the number of packets in the network. Setting SACK Delay to zero disables this delay so that SACKs are sent as quickly as possible. |
Format: numeric Range: 1 - 200 Default: 10 |
| * SCTP Heartbeat Interval (ms) | The number of milliseconds between sending SCTP HEARTBEAT messages to a Peer. Heartbeat messages are sent only when no user data has been sent for the duration of the Heartbeat Interval. Setting the Heartbeat Interval to 0 disables heartbeating (not recommended). |
Format: numeric Range: 0, 100 - 300000 Default: 1000 |
| * Socket Send Buffer Size (bytes) | Socket send buffer size for outgoing SCTP messages. The send buffer size must be greater than or equal to the product of the bandwidth and the round trip delay for the association. Note: The parameter with the Local Node's Connection Configuration Set is used by the peer-initiated (responder) connection. |
Format: numeric Range: 8000 - 5000000 Default: 1000000 |
| * Socket Receive Buffer Size (bytes) | Socket receive buffer size for incoming SCTP messages. The receive buffer size must be greater than or equal to the product of the bandwidth and the round trip delay for the association. Note: The parameter with the Local Node's Connection Configuration Set is used by the peer-initiated (responder) connection. |
Format: numeric Range: 8000 - 5000000 Default: 1000000 |
| * Maximum Burst | Specifies the maximum burst of packets that can be emitted by this association. | Format: numeric Range: 1 - 4 Default: 4 |
| * Max Number of Inbound Streams | Maximum number of inbound SCTP streams supported locally by the SCTP connection. Note: The parameter with the Local Node's Connection Configuration Set is used by the peer-initiated (responder) connection. |
Format: numeric Range: 1 -16 Default: 8 |
| * Max Number of Outbound Streams | Maximum number of outbound SCTP streams supported locally by the SCTP connection. Note: The parameter with the Local Node's Connection Configuration Set is used by the peer-initiated (responder) connection. |
Format: numeric Range: 1 -16 Default: 8 |
| Datagram Bundling Enabled | If checked, datagram bundling is enabled for the SCTP connection. | Format: checkbox Range: checked, unchecked Default: checked |
| * Maximum Segment Size | The Maximum Size to put in any outgoing SCTP DATA chunk. If a message is larger than this size, it is fragmented by SCTP into the specified size. | Format: numeric Range: 0, 64 - 1460 Default: 0 |
| Fragmentation | If checked, a message exceeding the size of the PMTU (Path Max Transmission Unit) is fragmented and reassembled by the peer. | Format: checkbox
Range: checked, unchecked Default: checked |
| Ordered Delivery | If checked, Ordered delivery of the SCTP DATA Chunk is performed. Otherwise, unordered delivery of the SCTP DATA Chunk is performed. | Format: checkbox Range: checked, unchecked Default: unchecked |
| Diameter Options | ||
| * Connect Timer (sec) | Controls the frequency of transport connection attempts to a Peer where no active transport connection exists. Applicable only for connections configured to initiate a connection with a Peer Node. |
Format: numeric Range: 1 - 60 Default: 30 |
| * Watchdog Timer Init Value (sec) | Initial value of the application watchdog timer. | Format: numeric Range: 1 - 30 Default: 30 |
| * Capabilities Exchange Timer (sec) | Time to wait on a CER message from a Peer after a connection is initiated by the Peer. Time to wait on a CEA response from a Peer after sending the CER. Note: For local nodes, CEAs are sent in response to erroneous CERs.Note: The parameter with the Local Node's Connection Configuration Set is used by the peer-initiated (responder) connection. |
Format: numeric Range: 1 - 30 Default: 3 |
| * Disconnect Timer (sec) |
After sending a DPA message, time to wait for a Peer to disconnect transport. After sending a DPR message, time to wait for the Peer to send the DPA. If the timer expires, transport is disconnected by the application. |
Format: numeric Range: 1 - 30 Default: 3 |
| Proving Mode | Proving mode for the Configuration Set. | Format: Option Range: Suspect, Always, Never Default: Suspect |
| * Proving Timer (msec) | The time to wait for a Peer to send a DWA message in response to a DWR message during connection proving. | Format: numeric Range: 50 - 30000 Default: 500 |
| * Proving Times | The number of consecutive DWR and DWA exchanges within Proving Timer time during connection proving. |
Format: numeric Range: 1 - 1000 Default: 3 |
| * Pending Transactions Per Connection | The maximum number of Pending Requests waiting for Answers from the Peer on this connection. If the maximum is reached, this connection is not selected for routing until the number of Pending Requests falls below this value. Note: Because the pending transaction limit is located in the Connection Configuration Set, it cannot be edited unless the connection is disabled. |
Format: numeric Range: 1 - 20000 Default: 1000 |
| CEX Host IP Validation Enabled | If checked, Host-IP-Address AVP validation is enabled during CEX message exchange. | Format: checkbox Range: checked, unchecked Default: checked |
| TCP Options | ||
| Nagle Enabled | If checked, the Nagle algorithm is enabled for the TCP connection. | Format: checkbox Range: checked, unchecked Default: checked |
| * Socket Send Buffer Size (bytes) | Socket send buffer size for outgoing TCP messages. The send buffer size should be greater than or equal to the product of the bandwidth and the round trip delay for the connection. Note: The parameter with the Local Node's Connection Configuration Set is used by the peer-initiated (responder) connection. |
Format: numeric Range: Not Applicable, 8000 - 5000000 Default: 1000000 |
| * Socket Receive Buffer Size (bytes) | Socket receive buffer size for incoming TCP messages. The receive buffer size should be greater than or equal to the product of the bandwidth and the round trip delay for the connection. Note: The parameter with the Local Node's Connection Configuration Set is used by the peer-initiated (responder) connection. |
Format: numeric Range: Not Applicable, 8000 - 5000000 Default: 1000000 |
| *Maximum Segment Size | The Maximum Segment Size for outgoing TCP Packets. The TCP Maximum Segment Size is the IP maximum transmission unit (MTU) minus the size of the TCP and IPv4/IPv6 headers. Setting this value to 0 indicates the user is not limiting fragmentation. | Format: numeric Range: 0, 88 - 1460 Default: 1024 |
| Keep-Alive | If checked, TCP probes a connection that has been idle for the amount of time configurable by Keep-Alive Idle Time parameter. | Format: checkbox Range: checked, unchecked Default: unchecked |
| * Keep-Alive Idle Time | Specifies the number of seconds of idle time between Keep Alive Probes if Keep-Alive is enabled. | Format: numeric Range: 1 - 7200 Default: 1 |
| * Keep-Alive Probe Interval | If Keep-Alive is enabled, sets the interval between Keep Alive Probes in seconds. This value cannot be changed after a connection is established. | Format: numeric Range: 1 - 120 Default: 1 |
| * Keep-Alive Maximum Count | If Keep-Alive is enabled, sets the maximum number of Keep Alive Probes TCP sends without any response from the remote server, before TCP gives up and aborts the connection. | Format: numeric Range: 1 - 16 Default: 9 |
| Radius Options | ||
| Pending Transactions Per Connection | The maximum number of Pending Requests waiting for Response from Peer on this connection. If maximum Pending Transactions is reached, then this connection is not selected for routing until the Pending transactions are below this value. | Format: numeric Range: 1 - 5000 Default: 1000 |
| Prevent duplicate transactions due to egress retransmissions | This option applies to RADIUS client connections only and determines how to handle a Request being retransmitted to the same peer as before, but the corresponding transaction record (that contains the previously used source port, RADIUS ID and Request Authenticator) has expired. If this option is selected, and if the corresponding transaction record has expired, the routing application does not forward the Request to the same peer with a new RADIUS ID, source port, and Request Authenticator. An alternate peer can be selected for routing in this case. If this option is not selected, and the corresponding transaction record has expired, DSR shall select a new source port, RADIUS ID and Request Authenticator, create a new transaction record and forward the Request to the peer. | Format: checkbox Range: checked, unchecked Default: checked |
| Prevent duplicate transactions due to ingress retransmissions | This option applies to RADIUS server connections only and determines how DSR shall processes duplicate requests received from a client. A request is considered duplicate if the client retransmits a request with the same source IP address, source port number, RADIUS ID and Request Authenticator. If this option is selected, DSR shall create an ingress transaction record for the request (with the request's source IP address, port, RADIUS ID and Request Authenticator) which shall be used to admit only the first Request into DSR and prevent admitting of duplicate requests, if received, till the transaction record is present. If a Response has been sent previously to the peer, it shall be saved in the transaction record and shall be forwarded to the client in response to duplicate requests. If this option is not selected, DSR shall not maintain ingress transaction records and shall admit all Requests received from the client. | Format: checkbox Range: checked, unchecked Default: checked |
| Cached response Duration (ms) | This option applies to server connections only. Applicable only if Prevent duplicate transactions due to ingress retransmissions = Checked. This value specifies the duration for which a cached response is held in the ingress transaction record. This value should cover the potential of loss of response and further retransmissions by the client. | Format: numeric Range: 3000 - 100000 Default: 5000 |
| Priority Options | ||
| CPL1 Minimum Request Priority Allowed | If 16 Priority Admin State is enabled in System Options then Connection Configuration Set shall support insertion and update of CPL1 Minimum Request Priority Allowed values in the range of 1-15. If 16 Priority Admin State is disabled, then this field is non-configurable. |
Format: checkbox If 16 Priority Admin State is Enabled:
If 16 Priority Admin State is Disabed:
|
| CPL1 Minimum Request Priority Allowed | If 16 Priority Admin State is enabled in System Options then Connection Configuration Set shall support insertion and update of CPL2 Minimum Request Priority Allowed values in the range of 2-15. If 16 Priority Admin State is disabled, then this field is non-configurable. |
Format: checkbox If 16 Priority Admin State is Enabled:
If 16 Priority Admin State is Disabed:
|
| CPL1 Minimum Request Priority Allowed | If 16 Priority Admin State is enabled in System Options then Connection Configuration Set shall support insertion and update of CPL3 Minimum Request Priority Allowed values in the range of 3-16. If 16 Priority Admin State is disabled, then this field is non-configurable. |
Format: checkbox If 16 Priority Admin State is Enabled:
If 16 Priority Admin State is Disabed:
|
