Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
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, 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, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 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, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1
Fixed In:
14.0.0, 12.1.6, 11.6.5.3
Opened: Mar 09, 2017 Severity: 4-Minor
When unbound (DNS cache) produces an error message, it's written to /var/log/ltm as a message from tmm. However, there is no indication that the message has anything to do with DNS caching. As a result of this issue, you might see errors similar to the following: -- err tmm5[14207]: tcp connect: errno 10 -- err tmm1[14244]: comm_point_tmm_recv_from failed: Software caused connection abort -- err tmm3[11846]: recvfrom failed
Some of these messages are benign, but there is no indication of that, or the associated functionality where the message was triggered. Difficulty troubleshooting the underlying issue.
-- Unbound (DNS cache) produces an error message. -- Viewing these logged messages in /var/log/ltm.
None.
Logged messages now indicate their association with DNS cache. For example: -- info tmm4[19404]: DNScache: sending query -- info tmm4[19404]: DNScache: response for example.com. A IN