Bug ID 705112: DHCP server flows are not re-established after expiration

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1

Fixed In:
16.0.0, 15.1.0.2, 14.1.2.5, 13.1.3, 12.1.4.1, 11.5.9

Opened: Feb 02, 2018

Severity: 3-Major

Symptoms

DHCP relay agent does not have server flows connecting to all active DHCP servers after a while.

Impact

DHCP server traffic not load balanced.

Conditions

- More than one DHCP servers configured for a DHCP virtual. - Server flows timeout in 60 seconds

Workaround

None.

Fix Information

A new logic to re-establish server flows is introduced to ensure a relay agent will have all DHCP servers connected.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips