Go to primary content
User Data Repository Diameter User's Guide
Release 12.4
E92984-01
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

Diameter Local Node configuration elements

Table 3-15 describes the fields on the Local Nodes View, Insert, and Edit pages. Data Input Notes only apply to the Insert and Edit pages; the View page is read-only.

Table 3-15 Local Node Configuration Elements

Field (* indicates required field) Description Data Input Notes
* Local Node Name Unique name of the Local Node.

Format: string, case-sensitive; alphanumeric and underscore (_); cannot start with a digit and must contain at least one alpha

Range: 1 - 32 characters

Default: none

* Realm Realm of the Local Node; defines the administrative domain with which the user maintains an account relationship.

Format: 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: Realm - up to 255 characters; label - up to 63 characters

Default: none

* FQDN Unique Fully Qualified Domain Name; specifies exact location in the tree hierarchy of the DNS.

Format: a case-insensitive string consisting of a list of labels separated by dots. A label must contain letters, digits, dash (-), and underscore (_). A label must begin with a letter 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

Default: none

SCTP Listen Port

SCTP listen port number for the Local Node.

This SCTP Listen Port cannot be the same as a Local Initiate Port of a Connection.

Initiator port ranges are divided into user-assigned and DCL-assigned sub-ranges.

Note:

DCL-assigned sub-ranges is implemented via OAM, and is restricted to connections only.

DCL (Diameter Transport Layer) is the software layer of the stack which implements diameter transport connections.

Format: numeric

Range: 1024 - 49151

Default: 3868

TCP Listen Port

TCP listen port number for the Local Node.

This TCP Listen Port cannot be the same as a Local Initiate Port of a Connection.

Initiator port ranges are divided into user-assigned and DCL-assigned sub-ranges.

Note:

DCL-assigned sub-ranges is implemented via OAM, and is restricted to connections only.

DCL (Diameter Transport Layer) is the software layer of the stack which implements diameter transport connections.

Format: numeric

Range: 1024 - 49151

Default: 3868

DTLS/SCTP Listen Port

The DTLS/SCTP listen port number for the Local Node.

Datagram Transport Layer Security allows datagram based applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. The DTLS protocol is based on the stream-oriented Transport Layer Security (TLS) protocol.

Format: numeric

Range: 1024 - 49151

Default: 5658

TLS/TCP Listen Port

The TLS/TCP listen port number for the Local Node.

TLS (Transport Layer Security) is an application layer security protocol that runs over TCP transport.

Format: numeric

Range: 1024 - 49151

Default: 5658

RADIUS UDP Server Ports UDP Port numbers used by RADIUS clients when sending RADIUS messages to the DSR. If no UDP port is specified here, this Local Node does not receive requests from RADIUS clients.

Format: numeric

Range: 1024 - 49151

Default: none

Enable RADIUS UDP Client Ports When checked, this Local Node can send RADIUS request messages to a RADIUS server using one of the UDP ports specified in the RADIUS Client UDP Port Range.

Format: checkbox

Range: none

Default: unchecked

RADIUS Client UDP Port Range Start

The lowest UDP port number that can be used to send RADIUS request messages to a remote RADIUS server.

Note:

If this Local Node does not share any IP address with any other Local Node, this Local Node can use the default client port range start of 2000. However, if this Local Node shares any IP addresses with one or more other Local Nodes, this Local Node can only use the default port range start of 2000 if none of the other Local Nodes (that share an IP with this Local Node) overlaps the port range specified for this Local Node.

Format: numeric

Range: 1024 - 49151

Default: 2000

RADIUS Client UDP Port Range End

The highest UDP port number that can be used to send RADIUS request messages to a remote RADIUS server.

Note:

If this Local Node does not share any IP address with any other Local Node, this Local Node can use the default client port range end of 2499. However, if this Local Node shares any IP addresses with one or more other Local Nodes, this Local Node can only use the default port range end of 2499 if none of the other Local Nodes (that share an IP with this Local Node) overlaps the port range specified for this Local Node.

Format: numeric

Range: 1024 - 49151

Default: 2499

Verification Mode:

The Certificate Verification Mode for the Local Node. If TLS/TCP or DTLS/SCTP Port is configured, this field sets the Verification Mode supported by the Local Node.

Available certificate types for configuration.

Format: List

Range:
  • Verify None
  • Verify Peer
  • Fail if No Peer Certificate
  • Verify Client Once

Default: Verify None

Certificate Type
Available certificate types for configuration.

Note:

Currently, available for TLS only.

Note:

This field is required if TLS/TCP or DTLS/SCTP Ports are being used.

Format: List

Range: none

Default: none

Certificate Name

A list of available X509 TLS Security Certificates.

Note:

This field is required if TLS/TCP or DTLS/SCTP Ports are being used.

Format: List

Range: none

Default: none

* Connection Configuration Set Connection Configuration Set for the Local Node.

Format: List

Range: configured Connection Configuration Sets, Default Connection Configuration Set

* CEX Configuration Set

CEX Configuration Set associated with the Local Node.

The entries in the CEX Configuration Set field create links to the Diameter > Configuration > CEX Configuration Sets [Filtered] page, which shows only the selected entry.

The CEX Configuration Set field for the Local Node is used if the CEX Configuration Set is not associated with the Connection.

Format: List

Range: configured CEX Configuration Sets, Default CEX Configuration Set.

* IP Addresses

IP address, or addresses, available for establishing Diameter transport Connections to the Local Node. You must assign at least one IP Address, and can assign up to 128 IP addresses, to a Local Node. Up to 32 IP addresses can be IPFE Target Set Addresses.

If fewer than four XSI interfaces are configured and SCTP transport is selected, then the number of IP Addresses selected must be the same as the number of XSI interfaces.

On the Local Nodes GUI pages, each IP address has appended to it:
  • For VIP addresses, the string VIP

    VIPs are present only in 1+1 Active/Standby configurations

  • For static IP addresses, the MP Server Hostname of the DA-MP that owns the IP address

    Static IP addresses are present only in Multi-Active N+0 configurations

  • For TSAs, the name of the Target Set that the IP address corresponds (for example, TSA# and TSA#-a for alternate IP Addresses where # is the Target Set number

    TSAs can be present in either, but do not have to be present at all.

    If a TSA is selected and Initiator Connection Support is enabled, configuration of a listener to reside within responder port range is enforced. If a TSA is selected and Initiator Connection Support is not enabled and the provided port is out of range (1024 - 49151):
    • If existing local node [Edit], the operation is allowed with a warning
    • If new local node [Insert], the operation is denied with an error

    Note:

    See Adding a Connection for more information.

    If a combination of TSAs are selected (one from a target set that has Initiator Connection Support enabled, one that does not), enforce configuration of the listener to reside within responder port range is enforced. An error message is generated if the connection is configured incorrectly.

For the IPFE to differentiate between responder and initiator connections, it checks the destination port of the incoming packet. The IPFE processes the incoming packet according to rules associated with the range into which the destination port falls. To provide unambiguous destination ports, diameter routing provides non-overlapping port ranges.

Format: Lists

Range: 1 - 128 entries

Default: none