| User Data Repository Diameter User's Guide Release 12.4 E92984-01 |
|
 Previous |
 Next |
Note:
Any request for a list of connections does not include any dynamically-created connection instances.When you select a connection route groups, you can specify to pass over connections that have too high of a DOIC loss rate.
Note:
If you attempt to add or edit RADIUS connections, you cannot set values for the Local Initiate Port, Alternate Local IP Address, IPFE Initiator DAMP, Alternate Peer IP Address, Transport FQDN, CEX Configuration Set, Transport Congestion Abatement Timeout, Remote Busy Usage, Remote Busy Abatement Timeout, Message Priority Setting, Message Priority Configuration Set, Suppress Connection Unavailable Alarm, Suppress Connection Attempts, and Test Mode fields.Note:
If you attempt to add or edit Diameter connections, you cannot set values for the Shared Secret Configuration Set, Message Authenticator Configuration Set, Status-Server Configuration Set, and UDP Port fields.Table 3-18 Connections Configuration Elements
| Field (* indicates required field) | Description | Data Input Notes |
|---|---|---|
| * Connection Name | Name of the connection. The name must be unique in the system. | Format: field Range: 1 - 32 characters |
| Transport Protocol | Type of transport protocol used by this connection. The selected transport protocol must be supported by both the associated local node and peer node. If AAA protocol is selected as RADIUS, only UDP is offered. For Floating (IPFE) connections, the transport protocol selected for this connection must be included in the Supported Protocols for the IPFE target set.
Note: Do not enable IPSEC if the connection is configured with TLS/TCP or DTLS/SCTP protocol; enabling both IPSEC and TLS/TCP or DTLS/SCTP is not recommended as this would have significant performance impact. |
Format: options Range: SCTP, TCP, TLS/TCP, DTLS/SCTP, UDP Default: SCTP |
| * AAA Protocol | The AAA protocol for this connection, which defines the connection as diameter or RADIUS. | Format: List Range: Diameter, RADIUS Default: blank |
| * Local Node | Local node associated with the connection. The local node must use the same transport protocol as the peer node. The entries in the local node field are links to the page, which shows only the selected entry. If two IP addresses are configured for the local node, it is recommended that an alternate IP Address be configured for the peer node. The peer’s alternate IP address is used as a fallback for the initiation of the SCTP connection establishment if the peer’s IP address is unreachable, as well as for the validation of the IP addresses advertised by the peer in the INIT/INIT_ACK SCTP chunk.
Note: It is recommended that separate local nodes be used for uni-homed and multi-homed SCTP connections. |
Format: List Range: all configured local nodes Default: blank |
| * Connection Mode | The connection can have one of the following connection modes:
The Connection Mode must be the same for all connections to the same peer. For UNI-HOMED Connections,
For MULTI-HOMED Connections,
|
Format: List Range: diameter: initiator only, responder only, initiator & responder RADIUS: RADIUS server, RADIUS client Default: initiator & responder |
| Dynamic | Indicates whether or not the element was created dynamically (YES) or statically (NO). NO is assigned for all element instances, except for those created via Dynamic peer Discovery. | Format: checkbox (read-only on the element [Edit] page) Range: checked (the element was created as a result of Dynamic Discovery), unchecked Default: unchecked |
| Local Initiate Port | The IP source port number to be used when the connection is an initiator. This field is not available and is set to Blank when the connection Mode is Responder Only. Initiator port ranges are divided into automatically assigned and DCL-assigned sub-ranges. Depending on the type of initiator connection, fixed or IPFE, there are two or more user/DCL sub-ranges. DCL (Diameter Transport Layer) is the software layer of the stack which implements diameter transport connections. If the connection remains fixed, a warning is generated if the configured port is out of range for an initiator connection type. If you convert the fixed initiator connection to an IPFE initiator connection, you must select from the DA-MP's port range if you want to explicitly configure the initiator port. See Connection Capacity Dashboard Functions for more information about fixed and IPFE initiator connections. |
Format: numeric Range: 1024-49151 Default: Blank |
| UDP Port | For RADIUS Server connections, this is the UDP port on which the DSR expects to receive incoming RADIUS requests for this connection. For RADIUS Client connections, this is the UDP port at the destination peer node that receives the RADIUS request sent by the DSR. | Format: List Range: local (RADIUS server connections) or peer node (RADIUS client connections) UDP port numbers Default: blank |
| IP Owner | Identifies the DA-MP that owns this connection attribute. Each RCL instance ignores connection attributes that are not exclusively assigned to its local DA-MP. | Format: read-only Range: IP owner Default: blank |
| * Local IP Address | The IP address to be used as local node Address for this connection. A local node must be selected before the list becomes available, containing the IP Addresses corresponding to the selected local node. When configuring diameter TCP connections, only MP static IP addresses, TSAs and alternate TSAs can be selected as the local IP Address. If an IPFE alternate target set Address (selected from the local node's IP Address list) is assigned to the local IP Address of a diameter connection, then the alternate local IP Address selection is disabled. In this case, a Uni-homed connection is configured, but using the target set's alternate IP address as the only local IP Address for the connection.
Note: Uni-homed and multi-homes are applicable only to SCTP/Diameter connections; they are not applicable to RADIUS/UDP connections.When configuring RADIUS connections, only MP static IP addresses can be selected as local IP Address. Each IP address in the list has an identifying tag appended to it, as follows:
|
Format: List Range: all configured IP addresses for the selected local node Default: blank |
| Alternate Local IP Address | The IP address to be used as the alternate local node Address for this connection. A local node must be selected and the selected connection transport protocol must be SCTP before the list becomes available, containing the IP Addresses of the selected local node. Note: SCTP can be selected as a protocol only for diameter connections.IPFE target set Addresses are appended with the target set Name, for example, (TSA1). If an IPFE target set Address (selected from the local node's IP Address list) is assigned to the local IP Address of a diameter connection, then the only valid selection for the alternate local IP Address is the corresponding IPFE alternate target set Address (for example: if TSA1 is assigned to a local IP address of a diameter connection, then the only valid selection for the alternate local IP Address is TSA1-a. This address is used only for SCTP Multi-homing; it must be different from the selected local IP Address. An IPFE TSA and an alternate TSA cannot be identical. Note: SCTP can be selected as a protocol only for diameter connections. |
Format: List Range: all configured IP addresses for the selected local node Default: blank |
| IPFE Initiator DAMP | The IPFE initiator DA-MP for this connection. When the addition of a new floating IPFE connection is being validated, OAM validates that the addition of the floating IPFE connection does not cause, for each DA-MP in the subject target set, the total number of connections allocated to the DA-MP, to exceed the DA-MP's total capacity. If the available capacity on one or more DA-MPs in the subject target set is less than zero and any DA-MP in the subject target set is included in more than one target set, OAM allows the floating IPFE connection to be added, but also issues a warning message. If the validation fails and the subject target set does not overlap any other target set, OAM computes the available capacity for the entire subject target set (by computing available capacity for each DA-MP and summing them). If the target set available capacity is less than zero, the validation fails and an error code is generated. |
Format: List Range: available DA-MP IP addresses configured for the TSA selected for local IP Address Default: blank or IPFE initiator DA-MP |
| * Peer Node | Peer node associated with the connection. The peer node must use the same IP protocol as the local node. The entries in the peer node field are links to the page which shows only the selected entry. |
Format: List Range: all configured peer nodes Default: blank |
| Peer Node Identification | Specifies how the peer node's IP address(es) is derived when initiating a connection to the peer, and whether the peer node's IP address(es) is validated when responding to a connection from the peer. Transport FQDNs use the remote IP address(es) configured for this connection when initiating a connection to the peer, and to validate the peer node's IP address(es) when responding to a connection from the peer. Use the remote IP address(es) configured for this connection when initiating a connection to the peer and to validate the peer node's IP address(es) when responding to a connection from the peer. If no IP Address has been selected and no transport FQDN has been specified, then the only accepted choice is peer diameter identity FQDN. Use None for this connection when responding to a connection from the peer and do not validate the peer node's IP address(es). Use the DNS resolved FQDN address configured for the peer node associated with this connection when initiating a connection to the peer, and do not validate the peer node's IP address(es) when responding to a connection from the peer. The FQDN configured for the connection takes precedence over the peer's diameter Identity FQDN.
|
Format: options Range: None, IP Address Default: IP Address |
| Peer IP Address | The IP Address to be used as the peer node address for this connection. A peer node must be selected before the list becomes available, containing the IP Addresses of the selected peer node. |
Format: List Range: available IP addresses Default: blank |
| Alternate Peer IP Address | The IP Address to be used as the alternate peer node address for this connection. A peer node must be selected and the selected connection transport protocol must be SCTP before the list becomes available, containing the IP Addresses of the selected peer node. This address is used only for SCTP Multi-homing; it must be different from the selected peer IP Address. |
Format: List Range: available IP addresses Default: blank |
| Transport FQDN | Fully Qualified Domain Name for this connection.
The transport FQDN is used for DNS lookup when peer node Identification is set to transport FQDN. If a responder only connection is created without a peer node IP Address and Transport FQDN is selected, transport FQDN is required even though it is not applicable. In this case, an error code is generated (when using Transport FQDN with initiator connections. |
Format: case-insensitive string consisting of a list of labels separated by dots. A label can contain letters, digits, dash (-), and underscore (_). A label must begin with a letter, digit, or underscore, and must end with a letter or digit. Underscore can be used only as the first character. Range: FQDN - up to 255 characters; label - up to 63 characters |
| * Connection Configuration Set | Connection Configuration Set associated with the connection. The entries in the connection Configuration Set field are links to the Connection Configuration Sets (Filtered) page, which displays the attributes of only the selected entry. |
Format: List Range: all configured connection Configuration Sets, Default connection Configuration Set. Default: blank |
| CEX Configuration Set | CEX Configuration Set associated with the connection. The entries in the CEX Configuration Set field are links to the CEX Configuration Sets (Filtered) page, which shows only the selected entry. |
Format: List Range: all configured CEX Configuration Sets, "Default" CEX Configuration Set. Default: blank |
| * Capacity Configuration Set | Capacity Configuration Set associated with the connection. The Capacity Configuration Set defines reserved and maximum ingress message processing rates and alarms thresholds for this connection. The entries in the Capacity Configuration Set field are links to the Capacity Configuration Sets (Filtered) page, which displays only the selected entry. The addition of any connection having non-zero Reserved Ingress MPS is subject to capacity validation rules, which are discussed in the connection Capacity Validation content. See the MP Profiles information in Diameter Common User's Guide. |
Format: List Range: all configured Capacity Configuration Sets, "Default" Capacity Configuration Set Default: "Default" Capacity Configuration Set |
| * Transport Congestion Abatement Timeout | The amount of time spent at Egress transport Congestion Levels 3, 2, and 1 during Egress transport Congestion Abatement |
Format: numeric Range: 3 - 60 seconds Default: 5 seconds |
| * Remote Busy Usage | Defines which Request messages can be forwarded on this connection after receiving a DIAMETER_TOO_BUSY response from the connection's peer.
|
Format: List Range: Disabled, Enabled Default: Disabled |
| Remote Busy Abatement Timeout | If Remote Busy Usage is set to Enabled or Host Override, this defines the length of time in seconds the connection is considered BUSY from the last time a DIAMETER_TOO_BUSY response was received. | Format: numeric Range: 3 - 60 seconds Default: 5 seconds |
| Message Priority Setting | Defines the source of Message Priority for a Request message arriving on the connection. Possible settings are:
|
Format: options Range: blank, Read from Request Message, User Configured Default: blank |
| Message Priority Configuration Set | The Message Priority Configuration set used if Message Priority Setting is User Configured | Format: List Range: all configured Message Priority Configuration Sets Default: blank |
| Egress Message Throttling Configuration Set | Egress Message Throttling Configuration Set associated with the connection. The Egress Message Throttling Configuration Set defines the maximum Egress Message Rate and thresholds used to set the congestion level for the connection. The entries in the Egress Message Throttling Configuration Set field are links to the Egress Message Throttling Configuration Sets (Filtered) page, which displays only the selected entry. |
Format: List Range: all configured Egress Message Throttling Configuration Sets Default: blank |
| Shared Secret Configuration Set | The Shared Secret Configuration Set used for this connection. (RADIUS only) | Format: List Range: all configured Shared Secret Configuration Sets Default: -Select- |
| Message Authenticator Configuration Set | The Message Authenticator Configuration Set used for this connection. (RADIUS only) | Format: List Range: all configured Message Authenticator Configuration Sets Default: -Select- |
| Message Conversion Configuration Set | The Message Conversion Configuration Set MO assigned to this RADIUS connection. (RADIUS only) | Format: list Range: blank Default: -Select- |
| Ingress Status-Server Configuration Set | The Ingress Status-Server Configuration Set used for this connection. (RADIUS only) | Format: List Range: all configured Ingress Status-Server Configuration Sets Default: -Select- |
| Suppress Connection Unavailable Alarm | If checked, this suppresses the connection attempts on the unavailable connections when a connection attribute is configured and turned ON for the connection object, then the connection unavailable alarm on those connections is not raised. | Format: checkbox Range: checked (YES) or unchecked (NO) Default: unchecked |
| Suppress Connection Attempts | If checked, suppresses the connection attempts when a diameter peer nodes status becomes available. This attribute is not applicable for responder only connection modes. It is only applicable for initiator only and initiator and responder connection modes. With any configuration edit action that results in connection mode to responder only mode, the attribute value is returned to the default value. |
Format: checkbox Range: checked (YES) or unchecked (NO) Default: unchecked |
| Test Mode | If checked, the connection is in Test Mode. | Format: checkbox Range: checked (YES), not checked (NO) Default: not checked |
