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

Last Modified: May 14, 2019

Bug Tracker

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

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 AskF5 Article:
K64307999

Symptoms

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>

Impact

Possible clutter in the TMM logs.

Conditions

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

Workaround

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