Last Modified: Feb 07, 2024
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 16.1.0, 16.1.1
Fixed In:
17.0.0, 16.1.2, 15.1.4.1
Opened: May 13, 2021 Severity: 4-Minor
MRF DIAMETER is not DIAMETER-application aware. It does not have application-specific business logic. When creating a DIAMETER solution, BIG-IP operators often need to write iRule scripts that remove a session persistence entry at the end of a transaction.
iRule script is required.
Some applications require removal of the persistence entry upon successful and unsuccessful completion of a transaction. root@(bigip1)(cfg-sync Standalone)(Active)(/Common)(tmos)# list ltm rule log_dia_error ltm rule log_dia_error { when DIAMETER_INGRESS { set cmd_code [DIAMETER::command] if { $cmd_code == 272 } { set cc_req_type [DIAMETER::avp data get 416 integer32] if {[DIAMETER::is_response] && $cc_req_type == 3 } { log local0. "Persistence record delete-on-any" DIAMETER::persist delete-on-any } } }
None
DIAMETER::persist irule are supported to remove a persistence entry based on the result status of a answer message. below irule commands are supported. DIAMETER::persist delete-on-any DIAMETER::persist delete-on-success DIAMETER::persist delete-on-failure DIAMETER::persist delete-none