Last Modified: Oct 16, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
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, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 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, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 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, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2
Fixed In:
16.1.0, 15.1.5.1, 14.1.4.6, 13.1.5
Opened: Jun 17, 2020 Severity: 3-Major
If a BIG-IP device has more than 24 tmm instances and one of the tmm processes above the 24th cpu loops (e.g., in response to an internal issue), it loops indefinitely.
Traffic disrupted on the tmm process that is looping indefinitely.
-- BIG-IP i15600 / i15800 platforms. -- Another issue occurs that that causes a tmm process greater than the 24th tmm process to loop.
1. Manually change /defaults/daemon.conf to include the appropriate tmm number and respective heartbeat action if the supported tmm is not listed. Note: The change does not persist across software installs. a. mount -o remount,rw /usr b. Edit /defaults/daemon.conf and put these contents at the top of the file: sys daemon-ha tmm24 { description none heartbeat enabled heartbeat-action go-offline-downlinks-restart running enabled running-timeout 2 } sys daemon-ha tmm25 { description none heartbeat enabled heartbeat-action go-offline-downlinks-restart running enabled running-timeout 2 } sys daemon-ha tmm26 { description none heartbeat enabled heartbeat-action go-offline-downlinks-restart running enabled running-timeout 2 } sys daemon-ha tmm27 { description none heartbeat enabled heartbeat-action go-offline-downlinks-restart running enabled running-timeout 2 } c. mount -o remount,ro /usr 2. After performing the edit, load the changes into the running configuration via 'tmsh load sys config partitions all'. 3. Verify that sod is now correctly monitoring tmm instances above tmm24 using a command such as: tmsh show sys ha-status all-properties | grep "daemon-heartbeat" | grep tmm
None