Bug ID 611467: TMM coredump at dhcpv4_server_set_flow_key().

Last Modified: Feb 13, 2019

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2

Fixed In:
13.0.0, 12.1.2

Opened: Aug 17, 2016
Severity: 2-Critical
Related AskF5 Article:
K20984520

Symptoms

TMM coredump at dhcpv4_server_set_flow_key().

Impact

Traffic disrupted while tmm restarts.

Conditions

1. You are using Policy Enforcement Manager (PEM) DHCP to discover subscribers. 2. You have configured a DHCP relay virtual server. 3. Two PEM DHCP subscriber connections share the same connection to a remote DHCP server. 4. One of the PEM DHCP subscriber connections expires. 5. The non-expired PEM DHCP subscriber connection sends a new DHCP request. 6. The remote PEM DHCP server responds to the new PEM subscriber request.

Workaround

The client uses broadcast to do DHCP renewal is an indication the client did not get ACK from DHCP server when it uses unicast to talk to DHCP server directly. The most likely reason for this to happen is the server routing table is not configured to send DHCP ACK packets back to the client. You can work around this problem by configuring DHCP server routing table so that it knows how to send DHCP ACK to the client.

Fix Information

None

Behavior Change