Bug ID 1971909: TMM SIGFPE "master shouldn't receive a CMP nexthop" after Clusterd seeing 1 of 2 blades down

Last Modified: Oct 15, 2025

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
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

Opened: Jun 25, 2025

Severity: 3-Major

Symptoms

Tmm crashes while passing traffic. The stack trace has an error "master shouldn't receive a CMP nexthop". /var/log/ltm contains an error err clusterd[9555]: 013a0004:3: Local slot 1: not getting clusterd pkts from slot 2; timed out on mgmt_bp after 10 seconds. Marking peer slot 2 SS_FAILED err clusterd[9555]: 013a0014:3: Blade 1: blade 2 FAILED

Impact

Traffic disrupted while tmm restarts.

Conditions

-- BIG-IP running as a tenant on VELOS -- The VELOS system is running a version that fixes ID 1556173 and 1559525 https://cdn.f5.com/product/bugtracker/ID1556173.html https://cdn.f5.com/product/bugtracker/ID1559525.html

Workaround

The workaround for this core not to happen is to upgrade to F5OS-C-1.6.2-37604.EHF-8.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips