Last Modified: Oct 19, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
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, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 16.1.6.1, 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, 17.1.3, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3
Opened: Jul 16, 2025 Severity: 3-Major
A tmm core happen after moving a persistence profile to a client-ssl profile while using cli transaction or a HA full sync happens.
Traffic disrupted while tmm restarts.
This is an example that shows how the issue would appear create ltm persistence ssl ssl-910253 { defaults-from ssl } create ltm virtual v-910253 { destination 10.1.1.1:443 persist replace-all-with { ssl-910253 } profiles add { tcp } } create cli transaction modify ltm virtual v-910253 { persist none } delete ltm persistence ssl ssl-910253 create ltm persistence ssl p-ssl-910253 { defaults-from ssl } create ltm profile client-ssl ssl-910253 { defaults-from clientssl } modify ltm virtual v-910253 { persist replace-all-with { p-ssl-910253 } profiles add { ssl-910253 } } submit cli transaction
Use a different name. To reuse the example before, instead of re-using ssl-910253, the new name is clientssl-910253: create ltm persistence ssl ssl-910253 { defaults-from ssl } create ltm virtual v-910253 { destination 10.1.1.1:443 persist replace-all-with { ssl-910253 } profiles add { tcp } } create cli transaction modify ltm virtual v-910253 { persist none } delete ltm persistence ssl ssl-910253 create ltm persistence ssl p-ssl-910253 { defaults-from ssl } create ltm profile client-ssl clientssl-910253 { defaults-from clientssl } modify ltm virtual v-910253 { persist replace-all-with { p-ssl-910253 } profiles add { clientssl-910253 } } submit cli transaction
None