Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1
Opened: Jan 11, 2019 Severity: 3-Major
The system posts clock advanced messages when modifying a virtual server. You might also experience an Active/Active situation because tmm might be too busy to send high availability (HA) packets. The messages appear similar to the following: notice tmm1[12549]: 01010029:5: Clock advanced by 556 ticks
The system logs clock advanced messages, and sod kills tmm when you run the following command: tmsh load sys config Traffic disrupted while tmm restarts.
-- Virtual server has 1000 or more SSL profiles defined. -- A client SSL profile gets its defaults from another profile. -- You change the cipher settings in that other profile.
To work around this, do the following: -- Remove some of the SSL profiles from the virtual server. -- Reset the cipher settings to default.
None