Versions Compared

Old Version 7

changes.mady.by.user Former user

Saved on

compared with

New Version 8

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To define a Diameter Routing profile, click on the New Configuration button and then select Diameter Routing profile in the menu.

Routing Tab

Image RemovedImage Added
The Diameter Routing profile configuration - Routing tab

...

ItemDescription
Realm Routing Strategy

Diameter requests are routed to peers in the realms in accordance with the selected Realm Routing Strategy. The following settings are available:

  • Failover: For each realm, Diameter requests are routed to the first specified peer (primary) in the Hostnames cell, or the first host resolved by a DNS query. If the connection to the first peer fails, requests to this realm are routed to the next peer (secondary) in the cell, or next host resolved by a DNS query. Failback to the first peer (primary) is performed when possible.
  • Round Robin: Diameter requests are evenly distributed to all the specified peers in the Hostnames cell, or peers resolved by DNS queries. If the connection to a peer fails, the requests are distributed to the remaining hosts. This also applies when UDRs are throttled due to the settings in the Peer Table.

The table below contains examples of how Diameter requests are routed to the peers of a realm, with the Round Robin strategy, depending on the peer connection state:

Peer 1 Status

Peer 2 StatusPeer 3 StatusRoute Distribution
OKAYOKAYOKAYPeer 1, Peer 2, or Peer 3
OKAYOKAYSUSPECTPeer 1 or Peer 2
REOPENSUSPECTOKAYPeer 3
DOWNDOWNSUSPECTPeer 3
DOWNREOPENDOWNPeer 2
DOWNDOWNDOWNNone


Diameter request are not routed to peers that are specified in the ExcludePeers field of a RequestCycle UDR. For more information about the RequestCycle UDR, see the section, RequestCycleUDR in The Diameter Base Protocol.

Enable Dynamic Peer Discovery

Select this check box when you want to use DNS queries (dynamic peer discovery) to find peer hosts in realms. The queried peer host information is buffered by the Diameter Stack agent according to the TTL (time to live) parameter in the DNS records. When the TTL has expired, the agent will attempt to refresh the information. If the refresh fails, the buffered information will be deleted.

When Enable Dynamic Peer Discovery is selected, DNS queries are performed at:

  • • Workflow start
  • • After TTL Expiration
  • • Dynamic update of Diameter routing profile


Note
titleNote!

To make changes to this setting effective, you must restart the workflow(s).

If the DNS service is unavailable (server available but service down) when starting the workflow(s), the system log entry will indicate errors in realm lookups. In order to resume lookups in DNS, you need to dynamically update the routing table in the Diameter Stack agent when the DNS is available again. For information about how to dynamically update the routing table, see the section below, To Dynamically Update the Diameter routing profile.

For information about how to select DNS servers, see the section below, DNS tab.

Realm

The realm name (case sensitive) . Realm is used as primary key in the routing table lookup. If left empty, all the destination realms are valid for this route.

For example: address.com.

Applications

The applications that this route serves. This entry is a used as a secondary key field in the routing table lookup. If left empty all the applications are valid for this route.

For example: 3,4.

Hostnames

A list of all the peer hosts in the realm. The hostnames must be selected from the Peer Table.

When Node Discovery is set to Dynamic, you should leave this field empty.

Node Discovery

The method of finding the peer hosts in the realm:

Static - The peer hosts are specified in the Hostnames field of the Realm Routing Table.

Dynamic - The Diameter Stack agent uses DNS queries (dynamic peer discovery) to find the peer hosts. These queries may resolve to multiple IP addresses or hostnames. In order to use this setting, you may need to add DNS servers to the network interfaces of your system.

Note
titleNote!

Entries in the Realm Routing Table that have the Dynamic setting are ignored (not matched), unless Enable Dynamic Peer Discovery is selected.

When a DNS server resolves a realm to peer hosts, it may return fully-qualified DNS domain names with a dot at the end. These trailing dots are removed by the Diameter Stack agent.

...