Last Modified: Jul 18, 2026
Affected Product(s):
BIG-IP LTM, PEM
Known Affected Versions:
11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 12.0.0, 12.0.0 hf1, 12.0.0 hf2, 12.0.0 hf3, 12.0.0 hf4, 12.1.0, 12.1.0 hf1, 12.1.0 hf2, 12.1.1, 12.1.1 hf1, 12.1.1 hf2, 12.1.2, 12.1.2 hf1, 12.1.2 hf2, 12.1.3, 12.1.3.1, 13.0.0, 13.0.0 hf1, 13.0.0 hf2, 13.0.0 hf3, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3
Fixed In:
14.0.0, 13.1.0.4, 13.0.1, 12.1.3.2, 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
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>