Bug ID 723658: TMM core when processing an unexpected remote session DB response.

Last Modified: Jul 12, 2023

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

Known Affected Versions:
14.0.0, 13.1.0, 13.0.1, 13.0.0, 12.1.3, 12.1.2

Fixed In:
14.0.0.5

Opened: Jun 08, 2018

Severity: 2-Critical

Symptoms

Using CGNAT or FW-NAT on a cluster may cause a TMM core if there are intra-cluster communication issues that cause CMP state transitions. The system writes messages to /var/log/tmm* similar to the following: notice CDP: exceeded 1/2 timeout for PG 1 notice CDP: PG 1 timed out notice CDP: New pending state 0f -> 0d notice Immediately transitioning dissaggregator to state 0xd notice cmp state: 0xd notice CDP: New pending state 0d -> 0f ... notice cmp state: 0xf notice CDP: exceeded 1/2 timeout for PG 1

Impact

Traffic disrupted while tmm restarts.

Conditions

-- A LSN pool or FW-NAT source translation that has persistence enabled. -- Intra-cluster communication issues that cause CMP state transitions.

Workaround

There is no workaround at this time.

Fix Information

TMM does not crash when an unexpected remote session DB response is received.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips