Applies To:Show Versions
- 16.1.1, 16.1.0
Overview: the BIG-IP system implementation of the Diameter-based
Diameter message routing configuration
Configures which IP address and port the BIG-IP system will listen on. Objects linked by using a virtual server object: protocol, Session profile, and Router profile.
Configures various Diameter options. By linking a session profile to a virtual server, it configures the virtual server to handle Diameter messages.
Links a Diameter application ID with an origin realm with a destination realm.
Links a static route to a virtual server.
Diameter supported protocols
- TCP. You can enable TLS.
- SCTP. You can enable multi-homing.
Diameter supported features
Load Balancing (LB)
Support distributing load across multiple Diameter servers across multiple realms. It can also route based on any AVP value.
High Availability (HA)
Configure in high availability mode where a failure of one chassis will cause the backup chassis to take over.
Remembers which Diameter peers are part of a session. Subsequent messages using the same session ID (persistence key) are routed to the alternate peer.
Supports modification of Diameter messages (AVP values).
Support rewriting the Origin Host, Origin Real, Destination Host, Destination Realm.
Support out-of-band and in-band Diameter monitors.
Connection auto initialization
Configure to connect to a Diameter server before receiving a client connection.
Full support for IPv6.
Supports retransmission to guarantee the delivery of a Diameter request message.
Supports Diameter loop detection.
Supports adding dynamic routes to an MRF Diameter router.
Per peer statistics
Supports collecting Diameter pool member statistics.
TCL context for a message
Supports TCL context for a message.
Diameter in-band monitor
Supports an in-band monitor to mark a pool member down with passive traffic.