Last Modified: Nov 07, 2022
Affected Product:
See more info
BIG-IP LTM
Known Affected Versions:
11.4.1, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 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, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2
Fixed In:
12.0.0, 11.6.5.3
Opened: Jan 29, 2015
Severity: 3-Major
Related Article:
K37104180
The BIG-IP system logs debug log information when 'dnscacheresolver.loglevel' is set to higher than debug. For example, 'dnscacheresolver.loglevel' is set to notice.
Although it might be difficult to determine the severity of the logging information, there is no known negative impact on the system.
'dnscacheresolver.loglevel' log level is set to higher than 'debug'.
This issue has no workaround at this time.
Debug logs are no longer displayed when 'dnscacheresolver.loglevel' log level is set to higher than 'debug'.
