Last Modified: May 19, 2025
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2
Fixed In:
17.0.0, 16.1.5, 15.1.10
Opened: Nov 21, 2023 Severity: 3-Major
The stale connections cannot be deleted with TMSH command: #tmsh delete sys connection command Stale connection: >>> any6.any any6.any <IP> <IP> tcp 255282 (tmm: 1) none none >>> any6.any any6.any <IP> <IP> tcp 255273 (tmm: 1) none none
Attempts to delete the flow through TMSH are ineffective and the flow remains for the remainder of the TMM lifetime.
- When "irule-scope-message" set to Yes, in a MRF routing profile. (This is not protocol specific - it's a general MRF behaviour.) ltm message-routing generic router simple_router { app-service none defaults-from messagerouter description none ignore-client-port no irule-scope-message yes <--------- per message TCL scope And use SessionDB operations on multi-TMM configuration. when MR_INGRESS { table lookup "Freddo" log local0. "Hey, an ingress message [MR::message id]" }
Do not use per message TCP scope. irule-scope-message no <----- not use per message TCL scope
None