The Diameter protocol provides message-routing functionality that the BIG-IP® system supports in a load-balancing configuration.
In a message routing configuration, the BIG-IP system manages requests and responses among peers. The following illustration shows a Diameter routing configuration with requests from Client 1 and Client 2 to servers located in different destination realms, Realm-A and Realm-B.
A Diameter message routing configuration
A typical Diameter message routing configuration with two realms involves configuring the following items.
|Pool||A pool for each realm directs Diameter traffic to servers.|
|Session profile||A session profile for each realm configures a session as a set of messages between two Diameter nodes on behalf of a user.|
|Transport configuration||An optional transport configuration for each realm defines how the BIG-IP system connects with the servers on your network when routing messages. You can assign a transport configuration to a virtual server or peer, as needed.|
|Peer||Each BIG-IP message-routing peer routes messages to a destination host. In this example, BIG-IP message-routing peers route messages to 10.10.10.1:3868, 10.10.10.2:3868, and 10.10.10.3:3868.|
|Static Route||Each static route specifies a set of peers in a destination realm to use in forwarding messages. In this example, Realm-A includes Peer 1 , and Realm-B includes Peer 2.|
|Router profile||A router profile configures Diameter message routing parameters and static routes to be used by a virtual server in routing Diameter messages.|
|Virtual server||Manages Diameter traffic to and from each realm and pool members.|
Complete these tasks to configure Diameter message routing on a BIG-IP® system.
|AVP||Enables persistence as determined by the AVP within the message.|
|Custom||Enables persistence as determined by a custom key specified within an iRule.|
|SNAT||The system uses the specified SNAT pool for source address translation.|
The system uses the self IP addresses of BIG-IP as the translation addresses.
The system does not translate source addresses.
|Per Blade||The number of connections are distributed and controlled per blade on a VIPRION® system.|
|Per Peer||(Default) The number of connections to a remote host is per peer.|
|Per TMM||The number of connections to a remote host is per TMM on the BIG-IP system.|
|Per Client||The number of connections to a remote host is per client connection. Responses are delivered to the connection initiating the request. This option is typically used when implementing a firewall, because of its restrictive functionality.|
|Ratio||Peer selection is based on the ratio that is set for each peer in the Selected list.|
|Sequential||Peer selection is based on the order of the peers in the Selected list.|
You can configure the BIG-IP® system to monitor pool member health using a Diameter monitor. Use a Diameter monitor to check the health of a host with an active Diameter session. The Diameter monitor also monitors a Diameter connection independently of a specific Diameter session and marks a host that had been marked down, but is online again, as available.
Perform these tasks to configure health monitors and apply the monitors to a pool:
You can view statistics for Diameter sessions and routes.