Previous page Section 3.96. <AuthBy DIAMETER> Section 3.96.1. DiaPeerDef (1195 / 1718)   Table of Contents Section 3.96.2. RelayAlgorithm Next page

3.96.1. DiaPeerDef Previous topic Parent topic Child topic Next topic

This parameter defines the Diameter peers to which requests should be sent to. When no DiaPeerDef parameters are set for an AuthBy DIAMETER, Diameter peer connection is established with the parameters configured directly within the AuthBy. DiaPeerDef requires Radiator Service Provider pack. Configuration with DiaPeerDef provides more flexibility, for example, when more than one Diameter peering is needed.
Multiple DiaPeerDef parameters allow using load balancing algorithms to relay to multiple destinations. For more information about available relay options, see file:/data/radiator-reference-manual/source/Configuration/AuthByDIAMETER/RelayAlgorithm_diaclient.dita#RelayAlgorithm.
When one or more DiaPeerDef parameters are set, the following parameters within an AuthBy DIAMETER are ignored: Peer, SCTPPeer, Port, Protocol, AuthApplicationIds, AcctAppliationIds, SupportedVendorIds, LocalAddress, LocalPort, ReconnectTimeout and DisconnectTraceLevel. These parameters are ignored because the AuthBy does not establish a direct peering.

Example

# Relay the requests to peers defined by DiaPeerDef with
# Identifier dra-1 and dra-2 using Session-Id based load balancing.
DiaPeerDef DiaPeerDef-Identifier=dra-1
DiaPeerDef DiaPeerDef-Identifier=dra-2

RelayAlgorithm HashBalance
Previous page Section 3.96. <AuthBy DIAMETER> Section 3.96.1. DiaPeerDef (1195 / 1718)   Table of Contents Section 3.96.2. RelayAlgorithm Next page