Table of Contents Table of contents: Radiator® AAA Server Configuring DIAMETER server 4 - Configuring DIAMETER server Configuring <MessageLog FILECARRIER> 6 - Configuring <MessageLog FILECARRIER>

5. Configuring Diameter relay

Radiator supports Diameter relay functionality with <AuthBy DiaRelay> clause. One or more Diameter relays can be supported by a single Radiator instance. The Diameter relays are independent from each other.

5.1. <AuthBy DiaRelay>

This section describes the configuration parameters of <AuthBy DiaRelay>. See the distribution package goodies directory for relay configuration samples.

5.1.1. DiaPeerDef

This parameter defines the Diameter Peer requests should be relayed to. At least one DiaPeerDef parameters is required and some load balancing relay algorithms support multiple destinations. Relay algorithms may also have restrictions on how which attributes the lookup is based on. For more information, see Section 5.1.2. RelayAlgorithm.

Example

# Relay the requests to peer defined by DiaPeerDef with
# Identifier radiator-dia-auth-server
DiaPeerDef DiaPeerDef-Identifier=radiator-dia-auth-server

# It is also possible to look up peer based on applications
# it advertises.
#DiaPeerDef Peer-Auth-Application-Id=3GPP:3GPP SWx

5.1.2. RelayAlgorithm

This parameter defines the how Diameters requests should be relayed to the peers. At least one DiaPeerDef parameters is required. Some load balancing relay algorithms support multiple destinations.
The following algorithms are currently supported:
  • FailOver
    Messages are sent to one peer only. If the peer becomes unreachable, the next configured peer is used. When a failed peer becomes available, it's used again.
  • HashBalance
    Messages are distributed between all configured peers. If a peer is unavailable, the messages are distributed between the remaining peers. Diameter Session-Id attribute is used as the distribution key.
FailOver can use run-time information about peers for selecting the next hop. For example when a peer advertises its supported applications, Peer-Auth-Application-Id can be used to select peers based on the applications they currently advertise.
HashBalance adds to its targets only those DiaPeerDef clauses that can be found during Radiator startup. Using DiaPeerDef-Identifier is recommended. Here's an example:

Example

# Balance load to multiple Diameter peers based on Diameter Session-Id attribute
RelayAlgorithm HashBalance

# Balance to peers defined with these Identifier values
DiaPeerDef DiaPeerDef-Identifier=aaa-server1
DiaPeerDef DiaPeerDef-Identifier=aaa-server2
DiaPeerDef DiaPeerDef-Identifier=aaa-server3
DiaPeerDef DiaPeerDef-Identifier=aaa-server4
Table of Contents Table of contents: Radiator® AAA Server Configuring DIAMETER server 4 - Configuring DIAMETER server Configuring <MessageLog FILECARRIER> 6 - Configuring <MessageLog FILECARRIER>