Loading...
Loading...
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
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.