Bug ID 680729: DHCP Trace log incorrectly marked as an Error log.

Last Modified: Oct 16, 2023

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

Known Affected Versions:
11.6.0, 11.6.1, 11.6.2, 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, 12.1.0, 12.1.1, 12.1.2, 12.1.3,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.1.0,,,

Fixed In:
14.0.0,, 13.0.1,, 11.6.3

Opened: Aug 29, 2017

Severity: 4-Minor

Related Article: K64307999


The following sample DHCP debug log may be found repeatedly in the TMM logs. <#> <date> <slot#> notice DHCP:dhcpv4_xh_timer_callback/1053: Entering: <mac-addr>


Possible clutter in the TMM logs.


Send a DHCP request through a DHCP virtual and wait for 30 seconds for the DHCP callback to trigger.


Set the db variable to critical. To do so, run the following command: setdb tmm.dhcp.log.level critical

Fix Information

The following log can be seen only when DHCP debug logs are set to enabled. <#> <date> <slot#> notice DHCP:dhcpv4_xh_timer_callback/1053: Entering: <mac-addr>

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips