Bug ID 527992: tmm might crash with 'DHCP:dhcp_server_flow_connect' error when the server flow is already connected to a different client.

Last Modified: Sep 13, 2023

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

Known Affected Versions:
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.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.1.0, 11.6.1 HF2

Opened: Jun 15, 2015

Severity: 2-Critical

Related Article: K55145052

Symptoms

When the DHCP server flow is trying to connect to the same client flow that is already connected and not released, there might be a tmm crash.

Impact

Traffic disrupted while tmm restarts.

Conditions

This can occur when using the dhcpv6 profile.

Workaround

None.

Fix Information

tmm no longer crashes with 'DHCP:dhcp_server_flow_connect' error when the server flow is already connected to a different client.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips