ltm rule namespace DIAMETER
iRule(1) BIG-IP TMSH Manual iRule(1)
DIAMETER
Namespace DIAMETER
DESCRIPTION
The DIAMETER namespace deals with and events specifically tailored to manipulate, inspect and interact with
the DIAMETER authentication protocol.
Associated Events * DIAMETER_INGRESS - Triggered when the system receives a DIAMETER message. *
DIAMETER_EGRESS - Triggered when the system is ready to send a DIAMETER message. * DIAMETER_RETRANSMISSION -
Triggered when the system is ready to send a retransmitted DIAMETER request or a generated DIAMETER answer.
DIAMETER iRule commands operate within a Tcl context associated with the connection flow between the endpoint
and the MR proxy. The ingress and egress parts of a message\'s journey therefore operate in separate Tcl
contexts. The Tcl context contains the Tcl variables and execution state of the currently executing iRule
event. Only one iRule event can execute at a time on a connection flow, therefore messages queue to execute
their iRule events.
DIAMETER messages belong to independent transactions that are carried over the same network connection flow.
It is highly desirable for messages sharing a connection flow to execute their iRules independently of other
messages. This provides the following advantages and behavior changes:
* A message does not need to wait for an unrelated message to complete an event in order to execute its
own event.
* Messages sharing a connection flow may exit the flow in a different order than they entered.
* Tcl variables cannot be overwritten between events by another message. This capability may be enabled
in the protocol-specific router profile via the irule-scope-message attribute. Before enabling irule-scope-
message, the user\'s iRules should be examined and if necessary adjusted and tested, to ensure they do not
rely on sharing a Tcl context between messages on a connection flow.
HINTS
SEE ALSO
BIG-IP 2020-06-23 iRule(1)