Bug ID 546877: Tmm assert 'tcp_set_persist: retransmit pending'

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
11.2.1, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Fixed In:
12.1.0, 11.6.4, 11.5.9

Opened: Sep 18, 2015
Severity: 2-Critical
Related Article:
K10934171

Symptoms

The tmm issues a 'tcp_set_persist: retransmit pending' assert.

Impact

TMM asserts 'tcp_set_persist: retransmit pending'. Traffic disrupted while tmm restarts.

Conditions

Occurs in the TCP stack when the two internal timers, persistence timer and retransmission timer, are active simultaneously.

Workaround

Use the performance TCP stack. This can be done by disabling all of the following profile parameters: - mptcp - rate-pace - congestion-control algorithms other than reno, newreno, scalable, highspeed, or none - tail-loss-probe

Fix Information

TMM supports canceling of the zero window persistence timer.

Behavior Change